create-manifest

Create a Trellis migration manifest and matching docs-site changelogs for a target release by analyzing commits since the previous release. Use when preparing a patch, beta, rc, or minor release manifest.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced release workflow with strong validation checkpoints and concrete commands. It is efficient but carries some narrative padding and is entirely inline with no supporting bundle files, leaving minor room for progressive disclosure gains.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes Claude's competence (commands, tables, terse voice rules), but includes some explanatory padding such as the multi-sentence publishing rationale and dogfooding narrative that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready bash commands, concrete JSON manifest templates, explicit field-decision tables, and specific verification commands covering common release cases end to end.	5 / 5
Workflow Clarity	Eleven clearly numbered steps with explicit validation checkpoints (Step 9 preflight, Step 10 review checklist, submodule-push verification) and error-recovery guidance (re-run CI path, fix workflow/scripts), satisfying the feedback-loop requirement for destructive/batch release operations.	5 / 5
Progressive Disclosure	Well-organized into clear sections with pointers to deeper references (style-guide.md, release-lifecycle.md, create-manifest.js validator); the file is somewhat long and inline-heavy with no bundle files to offload, but most detail is appropriately placed.	4 / 5
	Total	18 / 20 Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that states concrete actions and an explicit 'Use when' trigger tied to release types. Minor room to broaden trigger synonyms, but overall well-constructed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('analyze commits', 'create manifest', 'matching docs-site changelogs') and specifies the target object ('a Trellis migration manifest'), giving comprehensive concrete coverage.	5 / 5
Completeness	Clearly answers 'what' (create a migration manifest and matching changelogs by analyzing commits) and 'when' via the explicit 'Use when preparing a patch, beta, rc, or minor release manifest' clause.	5 / 5
Trigger Term Quality	Strong natural triggers ('patch', 'beta', 'rc', or minor release manifest') but lacks synonyms/variations a user might say, such as 'release notes' or 'changelog'; good but not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	Has a clear niche (Trellis release manifests) with distinct trigger terms unlikely to collide with unrelated skills; minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: mindfold-ai/Trellis
Path: .codex/skills/create-manifest/SKILL.md
Commit: 64e6636

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.