skills.rest
LYGOLANG
LYGOLANGCOMMUNITY
Explore all skills by this author →
GitHub

plugin-checker

Validates Claude Code and Codex plugins through staged checks, host E2E, and independent review.

Updated Jul 3, 2026
Search Tags:#claude code#mcp#quality gate#e2e testing#plugin verification#host validation#release check
One-click install
npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill plugin-checker-lygolang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-checker
Source: https://github.com/LYGOLANG/fufan-cc-flow/tree/main/bundled-plugins/plugin-builder/skills/plugin-checker
Command: npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill plugin-checker-lygolang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It prevents shipping plugins that merely look finished by requiring evidence-backed verification of every claim: artifact integrity, MCP contracts, UI behavior, security, and real installation on each required host before a plugin can be marked SHIPPABLE. ## Core Features & Use Cases - Staged Verification Pipeline: Runs eight stages from artifact integrity and static contract checks through build, MCP probe, UI/state tests, UI-to-Agent round trips, security negative tests, and per-target host verification. - Conditional Check Activation: Enables job, network, destructive-action, and complexity-Class-C checks only when plugin.yaml declares them, keeping optional and experimental targets from blocking required ones. - Independent Review Loop: Dispatches a fresh-context plugin-reviewer subagent for two-stage contract and quality review, and routes failures back to the builder skill for fixes with re-verification from the earliest affected gate. - Use Case: After a plugin-builder finishes a Claude Code plugin with an MCP server and UI, run this checker to produce a Plugin-Check-Report.md with per-target HOST_VERIFIED evidence, or a BLOCKED verdict listing required findings and fix paths. ## Quick Start Ask the agent to run the plugin checker on the current plugin project and produce a check report with per-target verification status.

Frequently Asked Questions about plugin-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a Claude Code plugin before release?▼

Run the plugin checker, which executes staged gates from artifact integrity through real host installation. A plugin is only SHIPPABLE when every required target is HOST_VERIFIED, all required acceptance criteria pass, and the independent reviewer reports zero REQUIRED findings.

What is the difference between BUILD_VALID and HOST_VERIFIED status?▼

BUILD_VALID means static checks, build, and local MCP probes passed but real host E2E is incomplete. HOST_VERIFIED requires actual installation on the target host, component discovery, core task execution, and reopen recovery with recorded evidence.

Does the checker support Codex plugins as well as Claude Code?▼

Yes. Codex targets are verified with codex doctor, TUI /mcp checks, and real installation via codex plugin add, since Codex has no validate command or --plugin-dir equivalent. Cache-busting version suffixes are required when reinstalling updated Codex plugins.

What happens when a check fails during verification?▼

The failure is recorded as a finding with evidence, project state is rolled back to BUILDING or an earlier phase, and the appropriate builder skill is invoked to fix it. Verification then reruns from the earliest affected gate, and repeated failures without new evidence halt the loop.

Why does the checker require an independent reviewer subagent?▼

Self-review by the building agent misses contract drift and quality gaps, so a fresh-context plugin-reviewer performs two-stage contract and quality review read-only. Any REQUIRED finding from that review blocks SHIPPABLE regardless of other passing checks.

Can a plugin ship if only one of multiple target hosts is verified?▼

No. Evidence from one target cannot substitute for another, and every required target must independently reach HOST_VERIFIED. Optional or experimental targets may be DEFERRED but must be explicitly reported rather than implied complete.

Related Skills

Explore More Software Engineering Skills→
mambo-wangmambo-wang
3

brainstorming

Guides collaborative design exploration and produces approved specification documents before implementation.

Community
Advanced
leejaedusleejaedus

plugin-install

Install a Claude Code plugin from a GitHub repository URL.

Community
Advanced
LongTermSupportLongTermSupport

phpstan-runner

Executes PHPStan static analysis and iteratively applies fixes until clean.

Official
Intermediate
wojonswojons
4

testing-level-poc

Define minimal manual and unit testing strategies for Proof of Concept projects.

Community
Basic