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

96%

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

92%

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 procedure with strong validation checkpoints and feedback loops. Its main weakness is progressive disclosure: the body is a long monolithic procedure rather than an overview pointing to detailed materials, despite good external reference pointers.

Suggestions

Move the detailed manifest-field and per-migration-entry tables (Steps 5 and 5a) into a reference file (e.g. references/manifest-fields.md) and link to it from a short summary, so SKILL.md reads as an overview.

Extract the docs-lifecycle table (Step 8) into the already-referenced release-lifecycle.md or a dedicated references/ file, keeping only the per-patch decision rule inline.

Split the Step 4 changelog voice/style rules into a references/changelog-style.md file referenced from the style-guide pointer, reducing inline prose.

Dimension	Reasoning	Score
Conciseness	Dense operational guidance (commands, tables, tight Do/Do-not lists) that assumes Claude's competence and never explains known concepts like git or npm; length is warranted by the 11-step release complexity, so it earns score 3 rather than the verbosity-flagged 2.	3 / 3
Actionability	Fully executable commands throughout (git log/diff, node create-manifest.js, pnpm release, npm view) plus decision tables for manifest fields — copy-paste ready with no pseudocode.	3 / 3
Workflow Clarity	Eleven clearly sequenced steps with explicit validation checkpoints (Step 9 preflight, Step 10 review checklist with a concrete submodule-push verification command) and a feedback loop ("If CI fails... fix the workflow/scripts and re-run").	3 / 3
Progressive Disclosure	Well-signaled one-level external references ("Full reference: .trellis/spec/docs-site/docs/release-lifecycle.md"), but the ~240-line body is largely monolithic with detailed field tables and docs-lifecycle content that could be split into separate reference files, matching the score-2 anchor of inline content that should be separate.	2 / 3
	Total	11 / 12 Passed

Description

100%

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 description: concrete actions, explicit "Use when" trigger guidance covering all release types, and a clear niche that avoids skill conflicts. Third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Create a Trellis migration manifest and matching docs-site changelogs" and "analyzing commits since the previous release" — matching the score-3 anchor of multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers what (create manifest + changelogs by analyzing commits) and when via an explicit "Use when preparing a patch, beta, rc, or minor release manifest" trigger clause.	3 / 3
Trigger Term Quality	Natural release-prep terms a user would say ("patch, beta, rc, or minor release", "manifest", "changelogs") give good coverage, not just technical jargon.	3 / 3
Distinctiveness Conflict Risk	A narrow niche (Trellis release manifest + docs changelogs) with distinct release-type triggers makes overlap with other skills unlikely.	3 / 3
	Total	12 / 12 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: 12e279a

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.