Check a Claude Code plugin before publishing. Inspect file placement, required configuration fields, metadata at the start of skill and agent files, and MCP tool references, then report failures with practical suggestions for fixing them.
Validate a Claude Code plugin structure, frontmatter, and MCP tool references
Review the instructions the agent will receive before you install.
Validate that a plugin follows the correct Claude Code plugin format.
After creating or modifying a plugin, run validation to catch structural issues before publishing.
.claude-plugin/plugin.json exists at plugin rootname equals the directory name; version is semverskills/<name>/SKILL.md is a valid skill (Claude Code auto-discovers from directory; plugin.json MUST NOT list a skills array)commands/<name>.md is a valid command (auto-discovered; no commands array in plugin.json)agents/<name>.md is a valid agent (auto-discovered; no agents array in plugin.json)skills, commands, or agents arrays in plugin.json is a validation error (they cause Claude Code to reject the plugin)name, description, and allowed-tools (no wildcards)name, description, and model.claude-plugin/allowed-tools use the mcp__plugin_ruflo-core_ruflo__* prefix AND exist: list the real tools with npx @claude-flow/cli@latest mcp tools and flag any name not in it (typos such as hooks_post_task for hooks_post-task, or agentdb_pattern_search for agentdb_pattern-search, are format-valid but do not exist). Also run the repo gates when inside the ruflo repo: node scripts/audit-skill-frontmatter.mjs, audit-plugin-manifest.mjs, audit-plugin-mcp-prefix.mjsplugin.json and assert no skills / commands / agents arrays presentskills/*/SKILL.md, commands/*.md, agents/*.md and validate each frontmatterallowed-tools has no wildcardsNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.