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. user: "Clean up the vector store after I deleted some files" assistant: "I'll use vector-db-cleanup to remove orphaned…
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. user: "Index these new plugin files into the vector database" assistant: "I'll use vector-db-ingest to…
Interactively initializes the Vector DB plugin. Guided discovery asks which folders to index, confirms the manifest, then scaffolds vectorprofiles.json for high-performance In-Process or Native Server connections. Mandatory first step before ingestion or search.
Start the Native Python ChromaDB background server. Use when semantic search returns connection refused on port 8110, or when the user wants to enable concurrent agent read/writes.
Semantic search skill for retrieving code and documentation from the ChromaDB vector store. Use when you need concept-based search across the repository (Phase 2 of the 3-phase search protocol). V2 includes L4/L5 retrieval constraints.
Selects the optimal agent orchestration or looping strategy for a given task using a deterministic decision tree. Distinguishes between solo discovery, dual-loop delegation, adversarial review, parallel swarms, meta-learning, and deterministic graph-state machines.
Systematically analyze agent plugins and skills to extract design patterns, architectural decisions, and reusable techniques. Trigger with "analyze this plugin", "mine patterns from", "review plugin structure", "extract learnings from", "what patterns does this plugin use", "check if this plugin is well-structured"…
This skill should be used when the user asks to "audit a plugin", "validate my plugin", "check plugin structure", "verify plugin is correct", "validate .claude-plugin/plugin.json", "check if my plugin is compliant", "review plugin components", or mentions plugin validation or structure compliance. Also trigger…
Audits and aligns individual agent skills and sub-agents against ecosystem evolution standards, verifying line budgets, evals schemas, and hub-and-spoke isolation.
Activate when the user wants to compile an APM package into top-level context documents such as AGENTS.md, CLAUDE.md, or GEMINI.md, especially for Codex, Gemini, OpenCode, or agents-protocol style hosts. Do not use when the user only needs per-skill installation; use install-apm-package instead.
Activate when the user wants to add APM governance, lockfile/audit readiness, or multi-runtime package management to an existing Claude/Copilot/agent plugin, or explicitly convert a plugin into an APM-native package.
Scaffolds a Copilot GitHub agent, an agent that runs in GitHub Actions, a GitHub workflow agent, or a GitHub Agentic Workflow (gh-aw) from an existing skill. Supports three target configurations: Target A (Custom Copilot agent), Target B (GitHub Agentic Workflow), and Target C (CI/CD Smart Failure agent).
Activate when the user wants to create a new APM-native package from scratch for reusable agent skills, agents, commands, hooks, MCP configuration, prompts, or governance-managed agent assets. Do not use this for existing plugin migration; use convert-plugin-to-apm instead.
Deploys a skill as an Azure AI Foundry hosted agent. NOT for Docker runtime skills (use create-docker-skill) and NOT for MCP server integrations (use create-mcp-integration).
Scaffolds a new slash command in an existing plugin. NOT for creating event-driven hooks (use create-hook) and NOT for standard skills (use create-skill).
Scaffolds an agent skill with a Docker runtime environment. NOT for normal local skills (use create-skill) and NOT for Azure hosted agents (use create-azure-agent).
Scaffolds a deterministic GitHub Actions CI/CD workflow YAML. NOT for scaffolding interactive agentic workflows (use create-agentic-workflow) and NOT for local event-driven hooks (use create-hook).
Scaffolds a new event-driven hook in a plugin. NOT for creating interactive slash commands (use create-command) and NOT for GitHub Actions agentic workflows (use create-agentic-workflow).
Adds an MCP server integration configuration to an existing plugin. NOT for scaffolding a brand-new plugin (use create-plugin) and NOT for Azure hosted agents (use create-azure-agent).
Scaffolds a new top-level agent plugin directory. NOT for scaffolding single skills (use create-skill) and NOT for adding MCP integrations to existing plugins (use create-mcp-integration).
Creates a new stateless skill in an existing plugin. Use this for procedural skills with no persistent state. NOT for sub-agents (use create-sub-agent) and NOT for skills that need stateful counters or session memory (use create-stateful-skill).
★not rated 6 todayA59 tokens
MIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: