From discovery
Use when asked to lint, audit, review, or score AI-facing instruction files such as SKILL.md, AGENT.md, AGENTS.md, CLAUDE.md, platform body.md files, prompt files, rules, policies, and agent-facing references. NOT for plugin manifests, application code review, harness configuration review, ordinary docs, tests, or generated build output.
How this skill is triggered — by the user, by Claude, or both
Slash command
/discovery:reviewing-instructionsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
The host SKILL.md is canonical. This overlay only adds Claude-specific argument,
The host SKILL.md is canonical. This overlay only adds Claude-specific argument, task, and aggregation behavior.
From $ARGUMENTS:
--model <name>: override model resolution--team: use parallel review agents for large scopes--rerank: use calibration anchors and pairwise comparison when comparing versionsUse direct review for one file or one small skill folder.
Use parallel tasks only when scope contains multiple independent files or plugins. Launch at most 3 review tasks at once. Batch deterministically by sorted path, not by estimated difficulty.
Each task prompt must include:
references/scoring-rubric.mdreferences/model-resolution.mdreferences/skill-architecture.md when the scope includes SKILL.md, AGENT.md, body.md, or agent-facing referencesWhen task results return:
When $ARGUMENTS contains --rerank, read references/calibration.md.
For two versions of a file, compare gates first, then dimensions, then final score.
If the difference is less than 0.5, report a tie.
Use web lookup for model docs only when local references are missing or the user asks for current vendor guidance. If web access fails, use local references or generic context and report the gap.
npx claudepluginhub alexei-led/cc-thingz --plugin discoveryGuides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.