Testskill
Analysis
This is an instruction-only skill-vetting checklist with no code or credentials, but users should verify the package identity and treat reviewed skill contents as untrusted.
Findings (3)
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.
Read ALL files in the skill. Check for these RED FLAGS
The skill's purpose requires inspecting untrusted skill files, which may themselves contain prompt instructions or misleading content. The artifact frames this as review, not execution, so this is a caution rather than a concern.
curl -s "https://api.github.com/repos/OWNER/REPO" ... curl -s "https://raw.githubusercontent.com/OWNER/REPO/main/skills/SKILL_NAME/SKILL.md"
The skill documents optional curl commands to query GitHub and fetch a target SKILL.md. This network use is purpose-aligned for vetting repositories and does not instruct automatic execution of fetched content.
"slug": "skill-vetter"
The bundled metadata says slug "skill-vetter", while the provided registry metadata lists slug "skill-vetter-liomi" and a different owner ID. For an instruction-only skill this is not high impact, but it is a provenance inconsistency worth checking.
