Ln 81 Skill Reviewer

Skill Reviewer

Goal: Review skill quality and configured distribution surfaces without modifying reviewed source or external systems. Distinguish static contract assurance from observed execution behavior.

Execution contract: The checklist defines completion. Track each item internally as PENDING, PROVEN with evidence, CLEARED with evidence its condition is absent, or UNPROVEN with a gap; reading, delegation, tool failure, a zero exit status, or a self-reported success is not proof; only the observed outcome is. Reconcile after each section. Before returning, resolve all PENDING, count only PROVEN and CLEARED, and apply verdict and approval rules to every gap. Preserve intent, scope, and existing authorization. Continue authorized work; ask only for consequential unresolved choices or required external approval. When no one can answer during the run, state the exact question and apply the skill's verdict for the remaining gap instead of waiting or guessing. Scale depth to material risk without skipping checks. Preserve dependency and safety order; otherwise choose an appropriate verification method. Accept equivalent user or repository evidence; no other skill, named artifact, or complete lifecycle is required. Preserve source requirement and decision IDs. Bind reused evidence to relevant source versions, dirty changes, configuration, and environment; invalidate only affected claims. On continuation, reconcile task, authorization, current state, and unresolved evidence. For long work, return a compact continuation record or update an already authorized artifact; read-only skills do not persist it. Distinguish artifact readiness, verified behavior, and external-action authority. Prepare authorized work before required approval. If blocked by an instruction, cite its exact source and unresolved boundary; do not invent approval gates from caution.

Tool Routing

Use external research only for current host behavior or a changing standard. Do not use web sources to override the repository's actual files, installed versions, or local validation output.

Tool absence is not itself a skill defect. Apply the documented fallback and use BLOCKED only when the missing capability prevents a reliable verdict.

Checklist

Establish scope and evidence

• Resolve target paths, Git diff, staged and untracked files; establish review mode: static content/distribution review, or behavioral validation when requested or warranted and permitted. Honor an explicit no-testing instruction; do not run scenarios or delegate evaluation in static-only mode.
• Read the repository instructions, skill contracts, and every configured host catalog before judging repository-specific conventions; do not require a catalog that the repository does not distribute.
• Separate primary skills from manifests, catalogs, and documentation affected by the same change.
• Confirm the repository-defined canonical skill layout; treat unauthorized, stale, or divergent host-specific copies as defects, while permitting adapters or generated copies that repository policy explicitly requires.
• Confirm frontmatter and folder naming satisfy the repository contract and each target host; require only name and description when that is the declared local convention rather than imposing it universally.
• Check that each description states the capability, positive trigger, and important near-negative boundary.
• Check that descriptions stay within the host limit and avoid claims broader than the workflow supports.
• Confirm each skill is standalone: no required skill, MCP server, tracker, coordinator, worker, or shared runtime.
• Apply the repository's declared completion convention; when an ordered checklist is the Definition of Done, flag a duplicate completion section.
• Preserve domain algorithms, tool routing, safety gates, evidence, verdicts, output, and residual risks. For removed checks, identify the retained obligation owner or explain why the check does not support the Goal; item count alone proves neither loss nor preservation.
• Flag generic explanations that add no decision value; preserve non-obvious domain knowledge and concrete safeguards even when no prior failure was recorded.
• Check content hierarchy and single-source ownership: keep each rule in the narrowest canonical section and flag repeated or contradictory guidance across the body, supporting files, manifests, and repository instructions.
• Flag filler, generated-summary prose, copied implementation or business logic, and volatile versions, paths, counts, defaults, or host behavior that can be replaced by a stable contract, authoritative source, capability description, or explicit update trigger.
• Verify every required capability has an available tool path, a credible fallback, or an explicit BLOCKED outcome.
• Check that each skill's mutation boundary matches its declared outcome; read-only workflows must not acquire implicit write authority.
• For optimization or experiment skills, require an evidence-based retain, discard, or rollback decision when they mutate state.
• For test-building or other bounded writers, confirm they cannot repair product code or touch unapproved external state unless their declared contract explicitly authorizes it.
• Trace the text through normal completion, missing tools, insufficient context, dirty Git state, failed commands, and conflicting evidence. Check prerequisites precede dependent actions, stop conditions permit safe progress, and verdicts cover failure states without contradiction.
• Check input/output compatibility, evidence invalidation, continuation, and instruction conflicts.
• Check that the output contract distinguishes facts, inferences, missing evidence, verdict, and residual risk.
• Compare neighboring triggers with each skill's Goal; require instructions to support an outcome, evidence need, or scope/safety constraint. Flag irrelevant work, missing obligations, and ambiguous branches without making skills depend on each other.

Repository Validation

• Discover and run every repository-required skill validator for the changed skill directories; do not assume a validator name or location absent from repository evidence.
• If a required validator is unavailable, manually validate YAML parsing, naming, description constraints, and required file layout against the repository and host contracts.
• Run every repository-required plugin or package validator for affected distribution units.
• Run each host-native strict validator when its corresponding catalog or manifest exists; record its actual coverage and do not treat marketplace validation as skill-frontmatter validation unless the host demonstrably traverses those skills.
• Parse all configured catalogs; compare plugin names and ordering only when repository policy requires cross-host parity.
• Confirm every declared catalog source, manifest path, and skill path exists.
• Confirm duplicated metadata such as plugin descriptions agree wherever the repository requires parity.
• For marketplace repositories, confirm stable identifiers have not changed unintentionally; display branding is not an identifier substitute.
• Search for stale names, deleted paths, draft markers, MCP coupling, orchestration terms, and generated copies.
• Apply line-count targets only when repository policy defines them, and treat them as a maintenance constraint rather than evidence of behavioral quality.