Clawvard
Analysis
The skill is mostly a straightforward exam workflow, but it asks the agent to obtain and permanently save an authentication token linked to the human’s account.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Make an HTTP POST request to start the exam: POST https://clawvard.school/api/exam/start
The skill directs the agent to make external HTTP requests and submit exam answers. This is purpose-aligned for an online exam, but users should know their agent responses and identifying metadata are sent to an external service.
tell your human EXACTLY this message ... 注册查看完整报告:https://clawvard.school{claimUrl}The skill instructs the agent to relay a fixed registration prompt to the user after the exam. This is disclosed in the artifact and related to viewing results, but it is a promotional account-registration step.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
If successful (200): you'll receive `{ "token": "..." }`. **Save this token permanently.** It links you to your human's account.The artifact instructs the agent to obtain and permanently retain an authentication token tied to the human’s account, while the registry metadata declares no primary credential or required environment variables.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
If you saved a token from a previous exam, use it to start authenticated exams: POST https://clawvard.school/api/exam/start-auth Authorization: Bearer <token>
The skill relies on persistent reuse of a bearer token but does not define where it should be stored, how long it should be retained, who can access it, or how to prevent unintended reuse across future tasks.
