plugins/agent-plugin-analyzer/skills/mine-skill/SKILL.md
Trigger with "mine this skill", "analyze this skill", "run targeted skill analysis", "extract patterns from this skill", or when you want focused analysis on a single Agent Skill directory without processing an entire plugin. Use this when the user points to a specific skill folder or says "look at this skill".
npx skillsauth add richfrem/agent-plugins-skills mine-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 requires Python 3.8+ and standard library only. No external packages needed.
To install this skill's dependencies:
pip-compile ./requirements.in
pip install -r ./requirements.txt
See ./requirements.txt for the dependency lockfile (currently empty — standard library only).
Run the targeted analysis pipeline on a single Agent Skill. This allows for focused extraction and synthesis from isolated directories without processing an entire plugin.
analyze-plugin skill, focused purely on this component.synthesize-learnings./mine-skill <path-to-skill-directory>
# Analyze a specific skill within a knowledge plugin
/mine-skill claude-knowledgework-plugins/sales/skills/call-prep
# Analyze one of our own core skills
/mine-skill plugins\ reference/agent-scaffolders/skills/create-plugin
analyze-plugin operating in Single Skill Mode on the provided $ARGUMENTS.scripts/inventory_plugin.py runs against the skill path.
Security scanning is enabled by default. Credential detection, network call detection, and environment variable checks run on all script files unless
--no-securityis passed.
references/pattern-catalog.md and detects anti-patterns.synthesize-learnings is invoked to map discovered patterns back to our core agent-scaffolders and agent-skill-open-specifications.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.