CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

verify-printing-press

Drive the real Printing Press end to end and capture proof. It builds the cli-printing-press binary, prints the golden fixture CLI into a decoy HOME, and runs the printed CLI, its MCP server, and the press's own verifiers against a request-logging mock. Use it to prove that a generator, template, MCP, or verifier change works in an emitted CLI, rather than only in Go tests or golden text.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

96%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.

An excellent operational skill body: dense, executable, and sequenced with genuine validation and recovery loops. The only gap is path-base ambiguity for its references — the bundle contains only scripts/, while features/README.md and the golden fixture live outside it relative to an unstated root.

Suggestions

Clarify the path base up front: distinguish skill-directory-relative paths (scripts/) from repo-relative paths (testdata/golden/fixtures/golden-api.yaml, features/README.md) instead of saying all paths are relative to the skill directory.

State where features/README.md lives (or use its explicit repo-relative path) so the 'read it before driving' reference resolves unambiguously for a reader starting from the skill bundle.

DimensionReasoningScore

Conciseness

The body is lean and information-dense — every section carries operational facts (45s warm-build timing, decoy HOME rationale, the four ready checks, proof standards) and teaches no concepts Claude already knows. Not 4: there is no over-explanation to trim; even the intro orients with project-specific facts rather than padding.

5 / 5

Actionability

Fully executable, copy-paste-ready commands throughout — launch, doctor, drives with real flags and a literal JSON payload ('{"projectId":"proj-1"}'), press verify invocations, and cleanup — plus variant cases (-e K=V, generating a different spec). Not 4: the common cases (CLI list/create, MCP list/call, press verify, requests) are each covered by a runnable example.

5 / 5

Workflow Clarity

The Launch → Doctor → Drive → Evidence → Cleanup sequence has explicit validation checkpoints (the four 'Ready means' checks, doctor before first drive / after surprising drives) and a real error-recovery loop ('A changed binary, HEAD, or press source fails doctor: ... clean up and relaunch'). Not 4: checkpoints are explicit and timed, not merely present.

5 / 5

Progressive Disclosure

Good structure with a well-signaled one-level-deep reference ('features/README.md is the index; read it before driving') and documented interfaces for the three bundled scripts, all of which exist. Not 5: the body states 'paths below are relative to this skill directory' yet then references repo-relative paths (testdata/golden/fixtures/golden-api.yaml, features/README.md) that are not part of the skill bundle, leaving a minor navigation ambiguity.

4 / 5

Total

19

/

20

Passed

Description

92%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: concrete, third-person, and explicit about both capability and trigger conditions, with a clearly bounded project niche. The only weakness is modest synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'builds the cli-printing-press binary', 'prints the golden fixture CLI into a decoy HOME', 'runs the printed CLI, its MCP server, and the press's own verifiers against a request-logging mock' — comprehensively covering the skill's surface. It exceeds the 'several specific actions; minor gaps' anchor because build, print, drive, and prove are all explicitly named.

5 / 5

Completeness

Both what and when are explicitly answered: the what is the build/print/run/capture-proof action list, and the when is the explicit clause 'Use it to prove that a generator, template, MCP, or verifier change works in an emitted CLI, rather than only in Go tests or golden text' with concrete trigger conditions. Not 4, because the when clause names the four specific change types rather than being merely serviceable.

5 / 5

Trigger Term Quality

Good natural-term coverage for the domain: 'generator, template, MCP, or verifier change', 'emitted CLI', 'Go tests', 'golden'. A few natural phrases a user might say ('verify', 'e2e', 'regression') are missing, so it fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of the top anchor.

4 / 5

Distinctiveness Conflict Risk

Highly niche project vocabulary — 'Printing Press', 'cli-printing-press', 'printed CLI', 'press's verifiers' — forms a clear trigger set with minimal overlap risk against any generic skill. Not 4: there is no closely related skill category these terms would collide with.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

mvanhorn/cli-printing-press

Path

.agents/skills/verify-printing-press/SKILL.md

Reviewed

Table of Contents

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.