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

90%

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.

Excellent procedural skill content: every step is executable with exact commands, validation checkpoints and error-recovery loops are thorough, and detail is appropriately delegated to referenced spec files. The only minor improvements are deduplicating the no-local-publish rule and moving the field-reference tables to a reference file.

Dimension	Reasoning	Score
Conciseness	The body is dense and project-specific — field tables, exact commands, and terse Do/Don't lists with no explanations of concepts Claude already knows. The only trimmable redundancy is the "never publish locally" invariant, which is stated three times (Package release model, Step 9, Step 11), keeping it just short of the leanest anchor.	4 / 5
Actionability	Guidance is fully executable and copy-paste ready: exact git log/diff commands, a JSON manifest piped via heredoc into `node packages/cli/scripts/create-manifest.js`, concrete preflight script invocations, and a submodule-verification command complete with the expected CI failure message ("fatal: remote error: upload-pack: not our ref <SHA>").	5 / 5
Workflow Clarity	An explicit 11-step sequence with strong validation checkpoints: Step 9 preflight (release-preflight checks, lint, typecheck, test), a Step 10 five-item confirm checklist, Step 11 post-publish `npm view` verification, and an explicit error-recovery loop ("If CI fails… fix the workflow/scripts and re-run the CI path. Do not use local publish to fill the gap").	5 / 5
Progressive Disclosure	Well-organized per-step sections with full detail correctly delegated via clearly signaled, one-level-deep pointers (".trellis/spec/docs-site/docs/style-guide.md", "Full reference: .trellis/spec/docs-site/docs/release-lifecycle.md") and no bundle files to mis-navigate. At ~240 lines with everything inline, the manifest field tables (Steps 5/5a) and MDX formatting rules could arguably live in a reference file — a minor organization gap rather than a clear misplacement.	4 / 5
	Total	18 / 20 Passed

Description

87%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 description: it clearly and explicitly states both what it does and when to use it, with concrete, natural trigger terms and a distinct niche. The only weakness is modest coverage of the skill's full scope (verification and CI publishing steps) and a few missing synonyms such as "release notes" or "publish".

Dimension	Reasoning	Score
Specificity	"Create a Trellis migration manifest and matching docs-site changelogs for a target release by analyzing commits since the previous release" lists several concrete actions (create manifest, create matching changelogs, analyze commits), but coverage has minor gaps — the skill also covers preflight verification, submodule checks, and CI publishing, none of which are mentioned.	4 / 5
Completeness	The first sentence explicitly states what the skill does and "Use when preparing a patch, beta, rc, or minor release manifest" explicitly states when to use it with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	"Use when preparing a patch, beta, rc, or minor release manifest" plus "changelog" and "release" give good natural keyword coverage, but common variations users might say — "release notes", "publish a release", "cut a release" — are missing, so it falls just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	"Trellis migration manifest" names a highly specific niche (Trellis release tooling) with distinct triggers like "beta", "rc", and "minor release manifest", so conflict risk with other skills is minimal.	5 / 5
	Total	18 / 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: f089cb3

Reviewed: 3 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.