Content
71%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is well-structured and notably strong on executable verification (a complete signed-manifest check script with fail-fast validation), and its safety contract and scope sections are lean and specific. Its main weakness is that the detailed builder guidance is deferred to files (SPEC.md, placeholder folders) that are not present in the bundle, so the promised deep layer is missing.
Suggestions
Ship the referenced `SPEC.md` (or inline its essential content) — the body instructs "Read `SPEC.md` before implementing" but the file does not exist in the bundle, leaving the skill's core second level missing.
Create the placeholder folders (`lib/`, `host-services/`, `mcp-tools/`, `test/`) or remove/reframe the Builder Entry Points table, since none of the mapped paths currently exist.
Move the ~70-line release-verification script into a `scripts/verify-release.sh` with a one-line invocation, keeping SKILL.md as a lean overview and improving token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Sections are terse bullet lists that assume the reader's competence (Safety Contract, Scope, Out of Scope), and the long shell script consists of non-derivable specifics (URLs, pubkey hash) rather than padding. Not a 5 because the ~70-line verification script and the Vercel install section are installer-facing material that inflates the main file beyond what the core builder guidance needs. | 4 / 5 |
Actionability | The verification section ships a fully executable, copy-paste-ready script with a concrete install command, and the "Required First Implementation Behavior" list gives specific, checkable requirements. Not a 5 because key guidance points to artifacts that don't exist in the bundle ("Read `SPEC.md` before implementing" — no SPEC.md present), and the placeholder-folder table describes directories that are not shipped. | 4 / 5 |
Workflow Clarity | The release-verification workflow has explicit validation checkpoints with fail-fast error messages (fingerprint mismatch, signature verify, per-file checksum) and a gating rule ("Only install or extract the archive after this verification succeeds"), and implementation behavior starts with "Validate config without starting the proxy". Not a 5 because the builder-side sequence is a requirements list without feedback/recovery loops, and the SPEC.md that would carry the detailed process is missing. | 4 / 5 |
Progressive Disclosure | Sections are well-organized and clearly signaled, but the body's central instruction ("Read `SPEC.md` before implementing") references a file absent from the bundle, and the Builder Entry Points table maps nonexistent placeholder folders. Not a 2 because the structure itself is good and nothing is deeply nested; not a 4 because the primary deep-content reference is broken, leaving no usable second level at all. | 3 / 5 |
Total | 15 / 20 Passed |