Prepare for India's medical entrance exam with progress tracking, weak area analysis, spaced repetition, and college targeting.
Security Analysis
high confidenceThe skill's requested actions and files are consistent with its stated purpose (a local NEET study assistant); it stores data under ~/neet/ and does not ask for external credentials or installs.
The name/description (NEET study assistant) matches the included files and instructions: scheduling, progress tracking, mock analysis, spaced repetition, and college targeting. There are no unrelated environment variables, binaries, or external services required.
The SKILL.md instructs the agent to create, read, and update a structured directory at ~/neet/ (profile.md, subjects/, sessions/, mocks/, flashcards/, etc.). This behavior is coherent with the skill's purpose but means the agent will need filesystem write/read access to the user's home directory. The instructions do not reference external endpoints or request unrelated system paths, but the storage of personal profile and progress data is explicit and extensive.
No install spec and no code files — this is instruction-only. That minimizes installation risk (nothing is downloaded or written to disk by an installer).
The skill requests no environment variables, credentials, or special config paths. The primary data footprint is local user data (personal profile, mock results, wellbeing notes), which is proportionate to a tutoring/tracking assistant.
always:false and no mechanism to modify other skills or global agent configs. The skill expects to persist data under ~/neet/, which is normal for a local assistant. Autonomous invocation is allowed by platform default but not combined with other concerning privileges here.
Guidance
This skill is internally consistent and appears to be a local study assistant, but it will create and update files in ~/neet/ containing personal data (name, category, exam date, mock scores, wellbeing notes). Before installing or enabling: 1) Confirm you are comfortable with the agent having read/write access to that directory (or change the path in the skill files). 2) Back up or encrypt sensitive files if needed. 3) If you prefer not to keep persistent local records, run the skill in an isolated account, a sandbox, or disable autonomous invocation so you approve actions manually. 4) Review the created files after first use to ensure nothing unexpected is stored or transmitted. If you need, ask the skill author to add an option to choose storage location or to avoid persisting sensitive fields.
Latest Release
v1.0.0
Initial release
More by @ivangdavila
Published by @ivangdavila on ClawHub
