CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pp-printing-press-golden

Printing Press CLI for Printing Press Studio. Purpose-built fixture for golden generation coverage.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./testdata/golden/expected/generate-golden-api/printing-press-golden/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is highly actionable with genuinely strong workflow sequencing and validation checkpoints, especially the learning-loop protocol. Its weaknesses are length and layout: repetitive warnings and inlined reference-grade detail make it overlong, and with zero reference files it is a monolith rather than an overview with progressive disclosure.

Suggestions

Move the learning-loop protocol (Steps 1-6, envelope schema, decision tree) and the MCP installation details into reference files (e.g. references/learning-loop.md, references/mcp.md), leaving SKILL.md a concise overview with well-signaled one-level-deep links (progressive_disclosure, conciseness).

State the shell-interpolation rule (write question via file tool, then QUERY=$(cat ...)) once in a single place and reference it from the recall/teach/amend steps instead of repeating it four times (conciseness).

Fill or remove the empty "reports" section and replace "use the category-specific Go fallback after publish" with the actual fallback command or delete the sentence until it exists (actionability).

DimensionReasoningScore

Conciseness

The body is dense CLI-contract information rather than padded filler, but at ~440 lines it could be tightened significantly: the shell-interpolation warning is repeated roughly four times across the learning-loop steps, a 30-line JSON envelope schema and a 40-line decision tree are inlined, and "Purpose-built fixture for golden generation coverage" duplicates the frontmatter. More than the "minor instances" of anchor 4, but not the padded/irrelevant content of anchor 2.

3 / 5

Actionability

Guidance is overwhelmingly concrete and executable — real commands (`printing-press-golden-pp-cli auth setup`, `doctor --fail-on warn`), flags, env vars, an exit-code table, and copy-paste blocks with expected JSON output. Minor gaps keep it from anchor 5: the "reports" section is an empty header with no commands, "the category-specific Go fallback after publish" is not actionable, and the Command Reference omits per-command arguments.

4 / 5

Workflow Clarity

The learning loop is sequenced as explicit steps 1-6 with a decision tree, a mandatory warnings checklist (Step 3), confirm-before-materialize validation for candidates, graceful degradation for older binaries, and error-recovery paths; the install flow requires verification before proceeding with failure troubleshooting; destructive operations (`local-data purge`, `profile delete`) are gated by preview and `--yes`. This matches anchor 5's explicit validation steps, feedback loops, and checklists.

5 / 5

Progressive Disclosure

Section headers are clear and well-ordered, but the skill is a ~440-line monolith with no bundle files at all: the learning-loop protocol, envelope schemas, and MCP configuration clearly belong in separate reference files. Anchor 3 fits — good structure, but content that should be separate is inline; it cannot reach anchor 4 because no references exist and the far-over-50-line body carries everything.

3 / 5

Total

15

/

20

Passed

Description

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

The description names the product but says nothing about what the CLI does or when to use it, relying on a single proper noun plus internal fixture jargon. It would rarely be selected by a user describing a task in their own words. Adding capability keywords and an explicit 'Use when...' clause would move it up two anchor levels.

Suggestions

State the concrete capabilities in the description, e.g. "Manage currencies, projects, reports, and tickets via the Printing Press Studio CLI" — this fixes both specificity and trigger terms.

Add an explicit trigger clause such as "Use when working with Printing Press Studio data: currencies, projects, reports, or tickets" so the skill fires on task-level language (completeness).

Drop the internal jargon phrase "Purpose-built fixture for golden generation coverage" — no user query contains those words, so it adds no trigger value and wastes the description budget.

DimensionReasoningScore

Specificity

"Printing Press CLI for Printing Press Studio" names the domain but lists no concrete actions; "Purpose-built fixture for golden generation coverage" is meta-commentary about the fixture, not a capability. Not anchor 1 (a specific tool is named, not pure abstraction), but far from anchor 3 which requires 1-2 concrete actions.

2 / 5

Completeness

The "what" is vague (a CLI for a studio — for doing what?) and the "when" is entirely absent, matching anchor 2 ("Has a vague 'what' and no 'when'"). The missing 'Use when...' clause caps completeness at 3, and the unclear "what" keeps it at 2.

2 / 5

Trigger Term Quality

Only the product name appears as a keyword; there are no capability terms a user would naturally say (no "tickets", "currencies", "projects", "reports"), and "golden generation coverage" is internal jargon no user would utter. Better than anchor 1 (a real product name exists) but below anchor 3 (no relevant capability keywords or their variations).

2 / 5

Distinctiveness Conflict Risk

The named product niche ("Printing Press CLI for Printing Press Studio") is mostly distinct with only minor overlap risk against other CLI-wrapper skills. Not anchor 5 because no distinct trigger phrases are stated, leaving nothing to discriminate when it should fire versus sibling skills.

4 / 5

Total

10

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

mvanhorn/cli-printing-press

Path

testdata/golden/expected/generate-golden-api/printing-press-golden/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.