Publication Review
Overview
Use this skill to decide whether a MetaSkill skill is ready to publish. It combines a deterministic script pass with a manual contract review.
Workflow
- Identify the target skill directory.
- Review the candidate's
SKILL.md,agents/openai.yaml, directly referenced resources, and any scripts it promises to use. - If the target is a collection-level README or root doc, review only the publication-facing claims in that file.
- Review the candidate's
- Run the lightweight checker when Python is available:
uv run python .\publication-review\scripts\review_skill.py <path-to-skill>
- Read
references/publication-checklist.mdand apply the manual checks that scripts cannot prove. - Report blockers first, then warnings, then the exact files reviewed.
- Do not mark a skill public-ready if its trigger description promises automation, semantic judgment, external integrations, or generated artifacts that are not implemented by included resources or clearly marked as manual.
Review Focus
- Privacy: no private paths, accounts, service identifiers, unpublished content, personal notes, or operational logs.
- Structure:
SKILL.mdfrontmatter follows the systemskill-creatorvalidator; folder names use lowercase hyphen-case; optional directories are used by the skill. - Contract truthfulness: every promised behavior is implemented, delegated to included scripts/resources, or explicitly labeled as manual or optional.
- Public examples: examples use generic fixtures such as
example-skill,sample-project, orprivate-workspace. - Metadata:
agents/openai.yaml, when present, matches the skill body and does not introduce unsupported claims.
Output
Use this shape for final review notes:
Blockers
- <file>: <issue and required fix>
Warnings
- <file>: <risk or cleanup suggestion>
Reviewed
- <files and commands actually checked>