# claude-plugins-validation - Doramagic AI Context Pack > Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated. ## Sufficiency Principle - **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary. - **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work. ## How the Host AI Should Use This You are reading the AI Context Pack that Doramagic compiled for claude-plugins-validation. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project. ## Claim Consumption Rules - **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure. - **Minimum status for a fact**: `supported` - `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path. - `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying. - `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact. - `unverified`: Must not be used as fact; state clearly that evidence is insufficient. - `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf. ## Who It Fits Best - **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0004` supported 0.86 - **Users who want to bring professional workflows into a host AI**: The repo contains Skill documents. Evidence: `skills/cpv-add-component-to-plugin/SKILL.md`, `skills/cpv-add-dependency/SKILL.md`, `skills/cpv-add-hook/SKILL.md`, `skills/cpv-batch-caching-audit/SKILL.md` et al. Claim: `clm_0005` supported 0.86 ## What It Can Do - **AI Skill / Agent Instruction Asset Library** (Previewable before install): The project contains Skill or Agent instruction files that a host AI can read, useful for bringing professional workflows into hosts like Claude, Codex, or Cursor. Evidence: `skills/cpv-add-component-to-plugin/SKILL.md`, `skills/cpv-add-dependency/SKILL.md`, `skills/cpv-add-hook/SKILL.md`, `skills/cpv-batch-caching-audit/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Multi-Host Install and Distribution** (Verify after install): The project contains plugin or marketplace configuration, indicating it targets install and distribution across one or more AI hosts. Evidence: `.claude-plugin/plugin.json`, `skills/cpv-main-menu-skill/skill-menus/03-path-source-plugin.json`, `skills/cpv-main-menu-skill/skill-menus/09-validate-marketplace.json` Claim: `clm_0002` supported 0.86 - **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `CLAUDE.md` Claim: `clm_0003` supported 0.86 ## How to Start - `npx misroute, xmllint correctly routes to the docker fallback on a bare runner, but` Evidence: `CLAUDE.md` Claim: `clm_0006` supported 0.86 ## Continue-or-Stop Decision Card - **Current recommendation**: Needs admin / security approval - **Why**: Continuing may involve secrets, accounts, external services, or sensitive context; get admin or security approval first. ### 30-Second Read - **What to do now**: Needs admin / security approval - **Minimum safe next step**: Run Prompt Preview first; if credentials or an enterprise environment are involved, get approval before trialing - **Do not trust yet**: Tool permission boundaries cannot be trusted before install. - **Continuing will touch**: Command execution, Host AI configuration, Local environment or project files ### What You Can Trust Now - **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0004` supported 0.86 - **Target-audience signal: Users who want to bring professional workflows into a host AI** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `skills/cpv-add-component-to-plugin/SKILL.md`, `skills/cpv-add-dependency/SKILL.md`, `skills/cpv-add-hook/SKILL.md`, `skills/cpv-batch-caching-audit/SKILL.md` et al. Claim: `clm_0005` supported 0.86 - **Capability exists: AI Skill / Agent Instruction Asset Library** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `skills/cpv-add-component-to-plugin/SKILL.md`, `skills/cpv-add-dependency/SKILL.md`, `skills/cpv-add-hook/SKILL.md`, `skills/cpv-batch-caching-audit/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Capability exists: Multi-Host Install and Distribution** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `.claude-plugin/plugin.json`, `skills/cpv-main-menu-skill/skill-menus/03-path-source-plugin.json`, `skills/cpv-main-menu-skill/skill-menus/09-validate-marketplace.json` Claim: `clm_0002` supported 0.86 - **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `CLAUDE.md` Claim: `clm_0003` supported 0.86 - **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `CLAUDE.md` Claim: `clm_0006` supported 0.86 ### What You Cannot Trust Yet - **Tool permission boundaries cannot be trusted before install.** (unverified): MCP/tool projects usually touch files, the network, the browser, or external APIs, so permissions and logs must be checked for real. - **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project. - **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment. - **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior. Evidence: `.claude-plugin/plugin.json`, `CLAUDE.md`, `skills/cpv-add-component-to-plugin/SKILL.md`, `skills/cpv-add-dependency/SKILL.md` et al. - **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first. - **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment. Evidence: `.claude-plugin/plugin.json`, `skills/cpv-main-menu-skill/skill-menus/03-path-source-plugin.json`, `skills/cpv-main-menu-skill/skill-menus/09-validate-marketplace.json` - **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. - **Do the install commands require network access, permissions, or global writes?** (unverified): This affects install risk in both enterprise and personal environments. Evidence: `CLAUDE.md` ### What Continuing Will Touch - **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `CLAUDE.md` - **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `.claude-plugin/plugin.json`, `CLAUDE.md`, `skills/cpv-add-component-to-plugin/SKILL.md`, `skills/cpv-add-dependency/SKILL.md` et al. - **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `.claude-plugin/plugin.json`, `CLAUDE.md`, `skills/cpv-main-menu-skill/skill-menus/03-path-source-plugin.json`, `skills/cpv-main-menu-skill/skill-menus/09-validate-marketplace.json` - **Environment variables / API keys**: Project entry docs explicitly showing API key, token, secret, or account credential configuration. Why: If a real install needs credentials, use test credentials first and go through a permission/compliance review. Evidence: `CLAUDE.md`, `skills/cpv-canonical-pipeline/references/v2-1-80-features.md`, `skills/cpv-fix-validation/references/hook-fixes.md`, `skills/cpv-fix-validation/references/mcp-fixes.md` - **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts. ### Minimum Safe Next Steps - **Run Prompt Preview first**: Use a pre-install interactive trial to judge whether the way of working fits; it needs no authorization or environment change. (applies when: Applies to any project, especially when output quality is unknown.) - **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.) - **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.) - **Do not use real production credentials**: Once an environment variable / API key enters the host or toolchain, it can create account and compliance risk. (applies when: When environment signals like API, TOKEN, KEY, or SECRET appear.) - **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.) ### Exit Plan - **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable. - **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state. - **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually. - **Be ready to revoke test API keys or tokens**: If test credentials leak or are misused, you can cut losses quickly. - **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck. ## What Can Only Be Previewed - Explain who the project fits and what it can do - Demonstrate a typical conversation flow based on project docs - Help the user decide whether it is worth installing or researching further ## What Must Be Verified After Install - Actually installing the Skill, plugin, or CLI - Running scripts, modifying local files, or accessing external services - Verifying real output quality, performance, and compatibility ## Boundary & Risk Decision Card - **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0007` inferred 0.45 - **Host AI plugin or Skill rule conflicts**: New rules may change how the user's existing host AI behaves. Mitigation: Inspect the plugin manifest and Skill files before installing, and test in isolation if needed. Evidence: `.claude-plugin/plugin.json`, `skills/cpv-main-menu-skill/skill-menus/03-path-source-plugin.json`, `skills/cpv-main-menu-skill/skill-menus/09-validate-marketplace.json` Claim: `clm_0008` supported 0.86 - **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `CLAUDE.md` Claim: `clm_0009` supported 0.86, `clm_0010` supported 0.86, `clm_0011` supported 0.86, `clm_0012` contradicted 0.20 et al. - **Source document conflict: skill_count**: The project documentation states inconsistent counts; the AI Context Pack must warn the user not to treat any single number as a verified fact. Mitigation: Flag it as unverified in both the Human Manual and the AI Context Pack rather than forcing a single number. Evidence: `CLAUDE.md`, `design/tasks/TRDD-20260519_162841+0200-9dd64dbf-the-skills-menu-canonical-method.md`, `design/tasks/TRDD-20260522_175413+0200-94e06820-body-tool-consistency.md`, `agents/cpv-plugin-fixer-agent.md` Claim: `clm_0009` supported 0.86, `clm_0010` supported 0.86, `clm_0011` supported 0.86, `clm_0012` contradicted 0.20 et al. - **Source document conflict: agent_count**: The project documentation states inconsistent counts; the AI Context Pack must warn the user not to treat any single number as a verified fact. Mitigation: Flag it as unverified in both the Human Manual and the AI Context Pack rather than forcing a single number. Evidence: `design/tasks/TRDD-20260519_140653+0200-478d9687-skills-index-universal-loader.md`, `design/tasks/TRDD-20260519_162841+0200-9dd64dbf-the-skills-menu-canonical-method.md`, `design/tasks/TRDD-20260531_084030+0200-88a1081c-recheck-exec-sink-indirection.md`, `CLAUDE.md` Claim: `clm_0009` supported 0.86, `clm_0010` supported 0.86, `clm_0011` supported 0.86, `clm_0012` contradicted 0.20 et al. - **Source file conflict skill_count**: multiple values `14, 32, 41, 200` found; verify before real use. - **Source file conflict agent_count**: multiple values `11, 12, 14` found; verify before real use. - **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment. - **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. - **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments. ## Pre-Work Working Context ### Loading Order - First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset. - Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative. - Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match. - When you need to carry out a concrete task, check role_skill_index first, then evidence_index. - For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required. ### Task Routes - **AI Skill / Agent Instruction Asset Library**: Use role_skill_index / evidence_index to help the user pick a usable role, Skill, or workflow first. Boundary: Can be experienced via a pre-install Prompt. Evidence: `skills/cpv-add-component-to-plugin/SKILL.md`, `skills/cpv-add-dependency/SKILL.md`, `skills/cpv-add-hook/SKILL.md`, `skills/cpv-batch-caching-audit/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Multi-Host Install and Distribution**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `.claude-plugin/plugin.json`, `skills/cpv-main-menu-skill/skill-menus/03-path-source-plugin.json`, `skills/cpv-main-menu-skill/skill-menus/09-validate-marketplace.json` Claim: `clm_0002` supported 0.86 - **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `CLAUDE.md` Claim: `clm_0003` supported 0.86 ### Context Scale - Total files: 514 - Important-file coverage: 40/514 - Evidence index entries: 78 - Role / Skill entries: 49 ### Handling Insufficient Evidence - **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts. - **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install. - **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run. - **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version. ## Prompt Recipes ### Fit assessment - Goal: Judge whether this project fits the user's current task. - Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation. ```text Based on the AI Context Pack for claude-plugins-validation, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id. ``` ### Pre-install experience - Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise. - Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language. ```text Treat claude-plugins-validation as a pre-install experience asset, not an already-installed tool or a real runtime environment. Output exactly four parts: 1. Ask me 3 necessary questions first. 2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow. 3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run. 4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project. Hard boundaries: - Do not claim you have installed, run, executed tests, modified files, or produced real results. - Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing". - If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...". - The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating". - Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment. - Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions. ``` ### Role / Skill selection - Goal: Pick the best-matching asset from the project's roles or Skills. - Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed. ```text Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs. ``` ### Risk pre-check - Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting. - Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items. ```text Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have. ``` ### Host AI kickoff instruction - Goal: Turn the project context into a host AI instruction for the start of a conversation. - Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI. ```text Based on the AI Context Pack for claude-plugins-validation, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results. ``` ## Role / Skill Index - Indexed 49 role / Skill / project-doc entries. - **cpv-add-component-to-plugin** (skill): Add a new component skill / agent / command / hook / mcp to an existing plugin. Use when scaffolding a single component into a plugin without re-running the generator. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-add-component-to-plugin”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-add-component-to-plugin/SKILL.md` - **cpv-add-dependency** (skill): Add plugin dependencies to a target plugin explicit --add specs or --from copy from another plugin's plugin.json . Use when adding/copying plugin.json::dependencies entries with atomic rollback on regression. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-add-dependency”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-add-dependency/SKILL.md` - **cpv-add-hook** (skill): Add a new hook entry to hooks/hooks.json in an existing plugin idempotent — skips duplicate entries; cross-platform-aware . Use when adding a new event-handler that must run identically on Linux/macOS/Windows. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-add-hook”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-add-hook/SKILL.md` - **cpv-batch-caching-audit** (skill): Fleet-wide read-only cache audit. Accepts local paths, GitHub URLs, marketplaces, lists, and @listfile shapes. One cpv-cache-optimizer-agent per plugin runs Phase 1 only — detects CA-01..CA-07 prompt-cache invalidation patterns, no fixes. Use when surveying cache-invalidation findings across many plugins without applying changes. Trigger with /cpv-batch-caching-audit. Activation hint: When the user's task is highly relevant to the workflow described by “cpv-batch-caching-audit”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-batch-caching-audit/SKILL.md` - **cpv-batch-caching-optimize** (skill): Fleet-wide parallel cache fix. Accepts local paths, GitHub URLs, marketplaces, lists, and @listfile shapes. One cpv-cache-optimizer-agent per plugin runs Phase 1 audit + Phase 2 fix + Phase 3 re-validate; Phase 4 broader refactor SKIPPED run the cpv-cache-optimizer-agent on a single plugin to opt in . Use when applying CA-01..CA-07 fixes across many plugins. Trigger with /cpv-batch-caching-optimize. Activation hint: When the user's task is highly relevant to the workflow described by “cpv-batch-caching-optimize”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-batch-caching-optimize/SKILL.md` - **cpv-batch-fix-protocol** (skill): Schema reference for the /cpv-batch-fix parallel-shard fix protocol — manifest format, status format, planner/aggregator contracts. Use when implementing a new consumer of the batch protocol or extending the planner/aggregator. Used dynamically via cpv-the-skills-menu TRDD-478d9687 — any CPV agent can invoke. Activation hint: When the user's task is highly relevant to the workflow described by “cpv-batch-fix-protocol”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-batch-fix-protocol/SKILL.md` - **cpv-batch-fix** (skill): Parallel fix for one OR many plugins. Accepts local paths, GitHub URLs, marketplaces, lists, and @listfile shapes. Single-plugin input → per-shard fan-out v2.91.0 protocol . Marketplace/list input → per-plugin fan-out one cpv-plugin-fixer-agent per plugin, internal sharding when needed . Use when applying validation fixes across many plugins. Trigger with /cpv-batch-fix. Activation hint: When the user's task is highly relevant to the workflow described by “cpv-batch-fix”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-batch-fix/SKILL.md` - **cpv-batch-full-scan-and-fix** (skill): Maximum-coverage same-turn sweep across a marketplace / list / single plugin. Each cpv-plugin-fixer-agent reads every source file ONCE and runs validate + security + caching audit + caching optimize + verify-FPs + fix inline. ~5× cheaper than running the four separate batch skills sequentially. Use when applying every-checker fixes across many plugins at once. Trigger with /cpv-batch-full-scan-and-fix. Activation hint: When the user's task is highly relevant to the workflow described by “cpv-batch-full-scan-and-fix”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-batch-full-scan-and-fix/SKILL.md` - **cpv-batch-scope-diagnose-and-fix** (skill): Same-turn scope-aware diagnose + fix across a fleet of project folders. One cpv-doctor-agent per project scans + verifies + applies obvious fixes inline NIT, CRITICAL, and safe MAJOR/MINOR auto; unsafe MAJOR/MINOR reported in pending fixes . Cuts per-project token cost ~2× vs running scope-diagnose + scope-fix separately. LOCAL paths only. Use when applying obvious scope-aware doctor fixes across many project folder… Activation hint: When the user's task is highly relevant to the workflow described by “cpv-batch-scope-diagnose-and-fix”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-batch-scope-diagnose-and-fix/SKILL.md` - **cpv-batch-scope-diagnose** (skill): Read-only fleet-wide scope-aware doctor. One cpv-doctor-agent per project diagnoses the requested scope — user the home .claude tree , project the project .claude tree , local settings.local.json , or full all + cross-scope conflict checker . LOCAL paths only — URL inputs are CRITICAL errors because the doctor needs filesystem access to the Claude installation. Use when surveying many project folders' .claude trees… Activation hint: When the user's task is highly relevant to the workflow described by “cpv-batch-scope-diagnose”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-batch-scope-diagnose/SKILL.md` - **cpv-batch-scope-fix** (skill): Apply scope-aware doctor fixes across a fleet of project folders. One cpv-doctor-agent per project in batch scope fix mode handles the requested scope user / project / local / full . Auto-applies NIT and CRITICAL fixes; reports MAJOR / MINOR fixes in pending fixes for user approval. LOCAL paths only. Use when applying mechanical doctor fixes across many project folders. Trigger with /cpv-batch-scope-fix. Activation hint: When the user's task is highly relevant to the workflow described by “cpv-batch-scope-fix”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-batch-scope-fix/SKILL.md` - **cpv-batch-security-audit** (skill): Fleet-wide parallel security audit. Accepts local paths, GitHub URLs, marketplaces, lists, and @listfile shapes. One cpv-plugin-validator-agent per plugin runs ONLY validate security 5 external scanners + AI/security rules . Use when checking supply-chain risk across many plugins. Trigger with /cpv-batch-security-audit or 'security-audit every plugin in X'. Activation hint: When the user's task is highly relevant to the workflow described by “cpv-batch-security-audit”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-batch-security-audit/SKILL.md` - **cpv-batch-validate-and-fix** (skill): Same-turn parallel validate-and-fix across a marketplace / list / single plugin. Each cpv-plugin-fixer-agent reads every source file ONCE — scans + verifies false positives via v2.100.x AST/JSON/markdown classifier + llm-externalizer with file-range syntax + fixes inline. ~3× cheaper per plugin than running cpv-batch-validate + cpv-batch-fix separately. Use when applying validation fixes across many plugins and you… Activation hint: When the user's task is highly relevant to the workflow described by “cpv-batch-validate-and-fix”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-batch-validate-and-fix/SKILL.md` - **cpv-batch-validate** (skill): Fleet-wide parallel validation. Accepts local paths, GitHub URLs, marketplaces, lists, and @listfile shapes. Dispatches one cpv-plugin-validator-agent per plugin default 8 parallel, cap 16 . Use when validating many plugins at once — e.g. every plugin in a marketplace. Trigger with /cpv-batch-validate or 'validate every plugin in X'. Activation hint: When the user's task is highly relevant to the workflow described by “cpv-batch-validate”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-batch-validate/SKILL.md` - **cpv-bump-version** (skill): Bump plugin version and run the full publish pipeline plugin.json, pyproject.toml, README badge, CHANGELOG, push, release . Use when bumping version + publishing the current plugin via publish.py. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-bump-version”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-bump-version/SKILL.md` - **cpv-cache-validation-skill** (skill): Validate plugins / projects against Anthropic's prompt-cache invalidation patterns CA-01..CA-07 . Use when auditing for cache regressions or fixing CA-01..CA-07 findings. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-cache-validation-skill”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-cache-validation-skill/SKILL.md` - **cpv-canonical-pipeline** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-canonical-pipeline”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-canonical-pipeline/SKILL.md` - **cpv-create-micro-agents-workflow** (skill): EXPERIMENTAL RLM Recursive Language Model generator — build a minimal launcher agent plus a TypeScript Workflow coordinator that decomposes any task into skill-focused micro-agents near-empty context each , runs and verifies them. Use when you want skill-per-agent, low-context execution instead of one big prefilled agent. Trigger with "create a micro-agents workflow" or /cpv-create-micro-agents-workflow. Activation hint: When the user's task is highly relevant to the workflow described by “cpv-create-micro-agents-workflow”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-create-micro-agents-workflow/SKILL.md` - **cpv-create-mono-agent** (skill): EXPERIMENTAL prefill-everything generator — build one MONO-agent whose body inlines ALL of a plugin's non-meta skills, so it is ready from turn 1 with every skill already in its cached context one big cache-creation, then cheap cache-reads, no dynamic skill loading that would break the prompt cache . Use when you want a single always-loaded mega-agent. Trigger with "create a mono-agent" or /cpv-create-mono-agent. Activation hint: When the user's task is highly relevant to the workflow described by “cpv-create-mono-agent”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-create-mono-agent/SKILL.md` - **cpv-create-plugin** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-create-plugin”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-create-plugin/SKILL.md` - **cpv-deterministic-codemod** (skill): Deterministic codemod CLI — bulk-fix backtick-path to markdown-link, add TOC stubs, dedup blank lines, and other mechanical text transforms issue 17 . Zero LLM cost. Use when mechanical fixes outnumber semantic ones. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-deterministic-codemod”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-deterministic-codemod/SKILL.md` - **cpv-devitalize-threats** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-devitalize-threats”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-devitalize-threats/SKILL.md` - **cpv-diagnose-plugin-architecture** (skill): Advisory diagnostic that detects when a Claude Code plugin ships files not needed at runtime — build-only source, dependency trees, dev-only dirs, regenerable build caches — and recommends the existing CPV lean-separation. Use when the user asks 'is my plugin too big', 'what files ship', 'reduce install size', 'lean the plugin', 'diagnose plugin architecture', 'unneeded files shipped', or wants to know which paths b… Activation hint: When the user's task is highly relevant to the workflow described by “cpv-diagnose-plugin-architecture”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-diagnose-plugin-architecture/SKILL.md` - **cpv-fix-marketplace-validation** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-fix-marketplace-validation”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-fix-marketplace-validation/SKILL.md` - **cpv-fix-validation** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-fix-validation”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-fix-validation/SKILL.md` - **cpv-harden-and-redact** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-harden-and-redact”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-harden-and-redact/SKILL.md` - **cpv-link-plugin-marketplace** (skill): Link an existing plugin to an existing marketplace local or GitHub source . Use when appending an existing plugin to a marketplace.json. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-link-plugin-marketplace”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-link-plugin-marketplace/SKILL.md` - **cpv-main-menu-skill** (skill): Routes the /cpv-main-menu Stop-hook menu via scripts/print menu.py + claude-menu-system. Used dynamically via cpv-the-skills-menu TRDD-478d9687 — used by the /cpv-main-menu flow. Use when navigating CPV's many commands via a single entry point. Activation hint: When the user's task is highly relevant to the workflow described by “cpv-main-menu-skill”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-main-menu-skill/SKILL.md` - **cpv-marketplace-authoring-contract** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-marketplace-authoring-contract”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-marketplace-authoring-contract/SKILL.md` - **cpv-migrate-marketplace-architecture** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-migrate-marketplace-architecture”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-migrate-marketplace-architecture/SKILL.md` - **cpv-pack-components** (skill): Pack a folder of standalone components skill/agent/command/hook/mcp/lsp/monitor/output-style into a new installable plugin. Use when bundling loose components into a single publishable plugin. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-pack-components”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-pack-components/SKILL.md` - **cpv-plugin-management** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-plugin-management”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-plugin-management/SKILL.md` - **cpv-plugin-validation-skill** (skill): Validates Claude Code plugins for structural correctness, quality, and marketplace readiness. Use when validating, fixing, migrating, upgrading, or scaffolding a plugin. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Embeds canonical plugins-reference.md. Activation hint: When the user's task is highly relevant to the workflow described by “cpv-plugin-validation-skill”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-plugin-validation-skill/SKILL.md` - **cpv-publish-to-marketplace** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-publish-to-marketplace”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-publish-to-marketplace/SKILL.md` - **cpv-refresh-readme** (skill): Refresh AUTO- marker blocks in a plugin's README auto-detected components table . Use when the README's components list has drifted from the filesystem. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-refresh-readme”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-refresh-readme/SKILL.md` - **cpv-register-mcp** (skill): Register a new MCP server in an existing plugin's .mcp.json stdio default; supports HTTP transport via --http-url; cross-platform command via Python/Node . Use when adding a new MCP server entry. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-register-mcp”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-register-mcp/SKILL.md` - **cpv-scaffold-agent** (skill): Scaffold a new agent in an existing plugin creates agents/{NAME}.md with valid frontmatter that passes validate plugin out of the box . Use when adding a single agent to an existing plugin. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-scaffold-agent”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-scaffold-agent/SKILL.md` - **cpv-scaffold-command** (skill): Scaffold a new slash command in an existing plugin creates commands/{NAME}.md with valid frontmatter that passes validate plugin out of the box . Use when adding a single slash command to an existing plugin. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-scaffold-command”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-scaffold-command/SKILL.md` - **cpv-scaffold-skill** (skill): Scaffold a new skill in an existing plugin creates skills/{NAME}/SKILL.md with valid frontmatter that passes validate plugin out of the box . Use when adding a single skill to an existing plugin. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-scaffold-skill”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-scaffold-skill/SKILL.md` - **cpv-semantic-validation-skill** (skill): Deep AI semantic validation for skills/agents. Use when checking triggering, clarity, examples. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . 10x token cost. Activation hint: When the user's task is highly relevant to the workflow described by “cpv-semantic-validation-skill”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-semantic-validation-skill/SKILL.md` - **cpv-setup-github-marketplace** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-setup-github-marketplace”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-setup-github-marketplace/SKILL.md` - **cpv-setup-marketplace-auto-notification** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-setup-marketplace-auto-notification”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-setup-marketplace-auto-notification/SKILL.md` - **cpv-setup-plugin-repo** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-setup-plugin-repo”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-setup-plugin-repo/SKILL.md` - **cpv-show-version** (skill): Show the CPV management tools version. Use when reporting the installed CPV CLI version. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-show-version”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-show-version/SKILL.md` - **cpv-skill-validation-skill** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-skill-validation-skill”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-skill-validation-skill/SKILL.md` - **cpv-standardize-plugin** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “cpv-standardize-plugin”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-standardize-plugin/SKILL.md` - **cpv-strip-dev-submodules** (skill): Move dev-only folders or compile source out of a plugin's MAIN repo into a SEPARATE repo referenced by pinned URL + SHA, so the installed plugin stops shipping them. Use when shrinking a plugin install before publishing, or when creating the PUBLIC compile-source repo the ship-only-binary canon requires. Used dynamically via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-strip-dev-submodules”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-strip-dev-submodules/SKILL.md` - **cpv-the-skills-menu-create** (skill): Convert any Claude Code plugin from static agent skill assignment to cpv-the-skills-menu method. Use when migrating a plugin so its agents load operational skills dynamically via the Skill tool instead of preloading static lists. Trigger with /cpv-the-skills-menu-create or when the user asks to migrate / standardize / decouple a plugin's skill discovery. Used via cpv-the-skills-menu TRDD-478d9687 . Activation hint: When the user's task is highly relevant to the workflow described by “cpv-the-skills-menu-create”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-the-skills-menu-create/SKILL.md` - **cpv-the-skills-menu** (skill): Agent-facing à-la-carte menu of every claude-plugins-validation CPV skill, agent, and script: classifies a plugin-quality request — validate, security-scan, fix, cache-optimize, create, publish, marketplace, manage, semantic-grade — and routes it to the right tool. Use when a request mentions CPV, the CPV skills menu, or validating / fixing / publishing / scanning / cache-optimizing a plugin and the exact tool is un… Activation hint: When the user's task is highly relevant to the workflow described by “cpv-the-skills-menu”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/cpv-the-skills-menu/SKILL.md` ## Evidence Index - Indexed 78 evidence entries. - **Claude Plugins Validation CPV** (documentation): ! Version https://img.shields.io/badge/version-3.23.1-blue ! Tests https://img.shields.io/badge/tests-10000%2B%20passed-brightgreen ! Validation https://img.shields.io/badge/validation-0%20issues-brightgreen ! License https://img.shields.io/badge/license-MIT-green Evidence: `README.md` - **cpv-fix-marketplace-validation — References Stub** (documentation): cpv-fix-marketplace-validation — References Stub Evidence: `skills/cpv-fix-marketplace-validation/references/README.md` - **Plugin Validation Skill** (documentation): Comprehensive validation skill for Claude Code plugins, marketplaces, hooks, skills, and MCP servers. Evidence: `skills/cpv-plugin-validation-skill/README.md` - **cpv-add-component-to-plugin** (skill_instruction): Adds a new component skill / agent / command / hook / mcp to an existing plugin without re-running the generator or hand-editing scaffolds. Each component lands as a minimal but valid stub with frontmatter that passes validate plugin / validate skill out of the box. Loaded dynamically via cpv-the-skills-menu, reached via the Manage → Add component menu branch. Evidence: `skills/cpv-add-component-to-plugin/SKILL.md` - **cpv-add-dependency** (skill_instruction): Adds one or more plugin dependencies to a target plugin's plugin.json::dependencies array. Two input modes that can be combined; the engine deduplicates by name last-write-wins , sorts the result alphabetically, writes atomically, and rolls back from a .bak if the post-write validation introduces any new CRITICAL/MAJOR finding. Loaded dynamically via cpv-the-skills-menu, reached via the Create → Add dependencies menu branch. Evidence: `skills/cpv-add-dependency/SKILL.md` - **cpv-add-hook** (skill_instruction): Adds a new hook entry to a plugin's hooks/hooks.json . The scaffold is idempotent — re-running with the same event+command is a no-op. The new hook command MUST be cross-platform: prefer Python or Node.js delegation. Bash-only constructs set -euo pipefail , , $