Use this skill when reviewing a complete Skill package for architecture, scope, triggers, independent installation, bilingual consistency, Eval readiness, and evidence boundaries; triggers include Skill quality review and package review.
Check path, name, and semantic consistency across SKILL.md, the primary Prompt, agents/openai.yaml, examples/references, and evals/.
Check independent installation: relative resources still resolve when only this Skill directory is copied, with no hard dependency on another Skill's private files.
Report blocking issues, important suggestions, information gaps, and evidence boundaries; separate static findings from runtime/model conclusions.
Constraints
This is a static package review. Do not execute the business task or silently modify the Skill.
Directory completeness, skill-up validate, CLI install smoke, and Project status cannot prove runtime behavior, model effectiveness, business acceptance, Quality Score, or release approval.
Do not invent environments, dependencies, metrics, trigger observations, or execution facts. Use UNASSESSED, NOT_RUN, BLOCKED, or INSUFFICIENT_EVIDENCE when evidence is absent.
Do not create a second Eval Engine, Judge, Benchmark, or Quality Score.
Reference files
Read prompts/skill-quality-review.md for the complete review output contract.
Inspect the target Skill's SKILL.md, Prompt, metadata, references, examples, and evals/ together.
Use repository contracts as optional deep references and preserve missing-runtime limitations.
Common pitfalls
Treating directory completeness, CLI smoke, or Project status as runtime or model evidence.
Reviewing only prose while missing metadata, eval, installation, or bilingual inconsistencies.
Adding a cross-Skill private-file dependency to make a package appear complete.
Best practices
Start with scope and information gaps, then trace each claim to a file and evidence level.
Separate blocking defects from suggestions and unassessed areas.
Keep the review package-level, reproducible, and independent of local machine paths.
Progressive disclosure
Read prompts/skill-quality-review.md before producing the report; it is the output contract.
Read the target Skill's evals/ when behavior coverage matters, but do not call configuration validation runtime evidence.
Read repository Evaluation Contract and local trace rules for deeper evidence when available. If a copied Skill does not contain them, preserve the limitation instead of creating filesystem coupling.
Pre-delivery checklist
Scope, document roles, and input gaps are explicit
Triggers, inputs, outputs, constraints, independent installation, and Eval readiness were checked
Blocking issues, suggestions, unassessed items, and evidence levels are traceable
Static checks are not presented as runtime/model evidence
Choosing the review scope
Use this Skill for the package-wide contract and installation readiness, including files, metadata, resources, examples, and evals. Use skill-prose-review for a bounded passage, Prompt, or document contract; a prose-only review cannot establish package completeness.
308 étoiles
Use this skill when reviewing a complete Skill package for architecture, scope, triggers, independent installation, bilingual consistency, Eval readiness, and evidence boundaries; triggers include Ski
1---2name: skill-quality-review3description: Use this skill when reviewing a complete Skill package for architecture, scope, triggers, independent…4---56# skills/en/skill-engineering/skill-quality-review/SKILL.md
S
SKILL.mdSkill d'agent
Transport
Fichier
État
Répertorié
Vue d'ensemble
À propos de skill-quality-review
Use this skill when reviewing a complete Skill package for architecture, scope, triggers, independent installation, bilingual consistency, Eval readiness, and evidence boundaries; triggers include Skill quality review and package review.
FAQ
Questions
Comment installer skill-quality-review ?
Téléchargez skills/en/skill-engineering/skill-quality-review/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
Où se trouve skill-quality-review ?
L'éditeur le maintient sur https://github.com/naodeng/awesome-qa-skills.
Quels agents peuvent utiliser skill-quality-review ?
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.