跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

ln-61-skill-reviewer

Reviews standalone skills and their configured distribution surfaces before publication. Use for skill release readiness; not for product code or implementation-plan review.

levnikolaevich · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add levnikolaevich/claude-code-skills --skill ln-61-skill-reviewer

技能说明


name: ln-61-skill-reviewer description: "Reviews standalone skills and their configured distribution surfaces before publication. Use for skill release readiness; not for product code or implementation-plan review."

Skill Reviewer

Goal: Review skill changes without modifying the repository or external state.

Execution contract: Treat the ordered checkbox workflow below as this skill's Definition of Done. Track every checkbox as PENDING, then resolve it to PROVEN with concrete evidence, CLEARED with evidence that its conditional trigger is absent, or UNPROVEN; reading, mentioning, delegating, skipping, or tool failure is not proof. Before returning, resolve every PENDING, count only PROVEN and CLEARED items as complete, apply this skill's verdict, decision, and approval rules to every UNPROVEN, and prepend Checklist: X/Y completeIncomplete: None | section/item — reason; outcome impact; exact next action; list every UNPROVEN item.

Tool Routing

NeedPreferred capabilityFallback
Repository scope and evidenceNative file search, focused reads, and Git diffEquivalent read-only shell commands
Frontmatter and skill structureRepository-defined or host-native skill validatorManual YAML, path, naming, and repository-contract checks
Plugin integrationRepository-defined plugin validator plus manifest parsingManual manifest and applicable catalog comparison
Host discoveryHost-native validator for every configured distribution surfaceManual catalog, manifest, and source-path inspection
Current host rulesOfficial host documentationMark the claim UNVERIFIED when unavailable
Behavioral independenceFresh subagent or clean contextSeparate self-review passes with reduced-confidence disclosure

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 the review target from explicit paths, the Git diff, staged files, and untracked files.
  • 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 non-obvious domain rules, tool-routing decisions, safety gates, evidence requirements, verdict mapping, output contract, and residual risks.
  • Flag explanations a capable current model already knows unless they prevent a demonstrated execution failure.
  • 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 workflow through missing tools, insufficient context, dirty Git state, failed commands, and conflicting evidence.
  • Check that the output contract distinguishes facts, inferences, missing evidence, verdict, and residual risk.
  • Inspect neighboring descriptions for trigger overlap without assuming the skills know about one another.

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 configur
阅读完整来源 ↗