plugins/agent-plugin-analyzer/tests/gold-standard-plugin/skills/example-skill/SKILL.md
Use when demonstrating a correctly structured agent skill. Trigger when the user asks to "show a well-formed skill", "give me a skill template", or "what does a compliant SKILL.md look like". Also triggers for regression testing: this fixture MUST score maturity >= L2 with zero Critical or Error findings.
npx skillsauth add richfrem/agent-plugins-skills example-skillInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill demonstrates the canonical structure for a compliant Agent Skill.
When analyzed by agent-plugin-analyzer, this fixture MUST:
This skill uses Progressive Disclosure. Load only what you need:
./acceptance-criteria.md./analysis-notes.mdIdentify what the user needs:
analyze-plugin against this fixture and confirm expected scoresPresent the relevant output based on the user's goal. Always confirm the acceptance
criteria in ./acceptance-criteria.md are satisfied before marking complete.
| Principle | Implementation |
|-----------|---------------|
| Progressive Disclosure | Deep content in references/, lean SKILL.md |
| Acceptance Criteria Gate | Explicit checklist in ./acceptance-criteria.md |
| Structured Output | Table-formatted step summary |
| Trigger Vocabulary | Rich description with multiple phrasing variants |
tools
Ingests repository files into the ChromaDB vector store. Builds or updates the vector index from a manifest or directory scan using ingest.py. Use when new files need to be indexed or the vector store is out of date. <example> user: "Index these new plugin files into the vector database" assistant: "I'll use vector-db-ingest to add them to the vector store." </example> <example> user: "The vector store is missing recent files -- update it" assistant: "I'll use vector-db-ingest to re-index the changes." </example>
data-ai
Removes stale and orphaned chunks from the ChromaDB vector store for files that have been deleted or renamed. Use after files are removed or moved to keep the vector index in sync with the filesystem. <example> user: "Clean up the vector store after I deleted some files" assistant: "I'll use vector-db-cleanup to remove orphaned chunks." </example> <example> user: "The vector database has chunks for files that no longer exist" assistant: "I'll run vector-db-cleanup to prune them." </example>
testing
Audit Vector DB coverage -- compares the live filesystem manifest against the ChromaDB index to identify coverage gaps.
development
3-Phase Knowledge Search strategy for the RLM Factory ecosystem. Auto-invoked when tasks involve finding code, documentation, or architecture context in the repository. Enforces the optimal search order: RLM Summary Scan (O(1)) -> Vector DB Semantic Search -> Grep/Exact Match. Never skip phases.