Verified:GitHub

plugin-readiness

Assesses Claude Code plugin production readiness across six governance and infrastructure domains.

1|Updated Jun 27, 2026

Search Tags:#claude code #model routing #ai governance #infrastructure health #html report #maturity assessment #plugin readiness

Ready to run

npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill plugin-readiness-vickysrawat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-readiness
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/plugin-readiness
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill plugin-readiness-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams adopting an AI-assisted development plugin lack a structured way to verify the plugin itself is configured, governed, and healthy enough for production use, leading to silent misconfigurations in model routing, memory, and governance rails. ## Core Features & Use Cases - Six-domain maturity scoring: Evaluates infrastructure health, model routing, memory health, governance rails, skill quality, and session budget on a 1-5 maturity scale. - Evidence-based assessment: Reads only plugin state files (plugin.json, .claude/, memory/, ledgers) and never touches application source code. - HTML readiness report: Produces a RAG-scored report with executive summary, domain findings, and a remediation roadmap in prod-readiness/. - Use Case: Before rolling the plugin out to a development team, an AI Architect runs the assessment to confirm rules are in sync, security scans are current, and no sessions are hitting context limits. ## Quick Start Ask the assistant to run a plugin production readiness assessment and generate the readiness report.

Frequently Asked Questions about plugin-readiness

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

FAQPage Schema

How do I check if my Claude Code plugin is production ready?▼

Run the plugin readiness assessment, which scores six domains including infrastructure health, model routing, and governance rails on a 1-5 maturity scale. It produces an HTML report with a ready, conditionally ready, not ready, or blocked verdict.

What does the plugin readiness assessment evaluate?▼

It evaluates six domains: infrastructure health via 17 setup-status checks, model routing configuration, memory and context health, governance rails like ICEA files and security scans, skill quality and consent governance, and session token budget.

Does the readiness assessment read my application source code?▼

No, it is a Category C skill that reads only plugin state files such as plugin.json, .claude/ directories, memory logs, and review ledgers. It never reads application source files.

Why is my plugin readiness verdict blocked or not ready?▼

A blocked verdict occurs when any domain scores 1 or a security scan was never run on a B-series application. A not-ready verdict occurs when infrastructure or governance domains score below 3, or the enforcement floor is missing without a recorded opt-out.

Where is the plugin readiness report saved?▼

The report is written as an HTML file to the prod-readiness/ directory with the filename pattern plugin-readiness-{date}.html. It includes an executive summary, domain findings, and a remediation roadmap.