Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md - `SKILL.md` (required — stop if missing)
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed assistant for restructuring and evaluating Claude Code skill files, with user confirmation required before writes.
Install only if you want an agent to inspect and potentially edit skill instruction files. Review the proposed plan before saying go, keep backups or version control for skills being changed, and use the A/B evaluation mode only when you are comfortable with extra workspace files and multiple subagent runs.
Referenced artifact was not completely inspected
- `SKILL.md` (required — stop if missing)
The skill explicitly instructs the agent to create files and update SKILL.md, which is self-modification of agent behavior artifacts. Even with a 'lossless' rule and confirmation step, modifying a skill’s own instruction files is high risk because it can persistently alter future agent behavior, propagate mistakes, or introduce unsafe directives into the skill itself.
Once confirmed, write in this order to preserve losslessness:
1. Create new `rules/*.md` files with the content they'll receive
2. Update SKILL.md — remove only the content that was written in step 1
3. If enriching: create new template/resource files
Never remove content from SKILL.md until it has been written to its destination file.
The manifest describes a skill focused on restructuring SKILL.md content, optimizing rules loading, adding templates/resources, and rewriting vague instructions. Lines L187-L274 instead define a benchmark-results analyzer that reviews benchmark.json across runs, analyzes pass/fail patterns and resource metrics, and writes observational notes, which is a separate evaluation capability not covered by the manifest description.
The trigger phrases are broad enough to match common requests like 'help me structure my rules files' or 'make this rule more precise,' which can cause the skill to activate in contexts broader than intended. Overbroad activation is dangerous because it may steer unrelated conversations into file-reading and modification workflows without sufficient necessity.
The skill’s declared purpose is restructuring a skill’s rules/file layout, but this section introduces a substantially broader A/B evaluation and benchmarking workflow with workspace creation, grading, benchmarking, and reporting. That scope expansion can cause the agent to perform unnecessary multi-step operations and create artifacts beyond the user’s likely intent, increasing the risk of overreach and unintended file changes.
This section directs multi-subagent orchestration, repeated task spawning, artifact persistence, and benchmark generation even though those behaviors are not necessary for basic rules-file design. Such orchestration increases operational complexity, token usage, and the chance of unintended actions across the filesystem, making the skill more capable than its stated mission requires.
The benchmark section states the analyzer's purpose is to surface patterns and anomalies across multiple runs, not suggest skill improvements. Earlier in the same file, the primary workflow explicitly instructs the agent to identify loser weaknesses and generate prioritized improvement suggestions, so the document presents conflicting intent for what this agent should do.
This markdown skill description directs the agent to save results to a JSON file, which is a file-write operation affecting user or system data. The document does not include any warning or disclosure that it will create or overwrite a file at the specified path.