CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pp-printing-press-rich

Printing Press CLI for Printing Press Rich. Purpose-built fixture for rich auth env-var model coverage.

Quality

55%

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

Fix and improve this skill with Tessl

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

Quality

Content

63%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 body delivers concrete, executable, well-sequenced guidance with genuine validation checkpoints, especially in the learning-loop protocol. Its weaknesses are redundancy and monolithic structure: ~400 lines with no reference files, duplicated statements, and a misplaced TLS paragraph.

Suggestions

Move the learning-loop protocol (Steps 1-6, the recall response envelope, and the warnings catalog) to a references/ file, keeping a short protocol summary in SKILL.md that points to it.

De-duplicate the read-only prohibition and the credentials.toml location, and relocate the TLS/CA-bundle paragraph to a relevant section instead of "When Not to Use This CLI".

Remove the repeated fixture sentence from the body and add a minimal playbook-file JSON example so the `--playbook-file` path is fully actionable.

DimensionReasoningScore

Conciseness

The body is dense with operational specifics rather than explanations of known concepts, but contains clear redundancy: "Purpose-built fixture for rich auth env-var model coverage." is repeated verbatim, the read-only prohibition appears in both "When Not to Use This CLI" and the "Read-only" bullet, the credentials.toml location is stated in two sections, and a TLS paragraph is misplaced under "When Not to Use". Mostly efficient but needs tightening.

3 / 5

Actionability

Commands are largely copy-paste ready: the npx install line, `--version` verification, recall/teach/playbook amend invocations with argv-safe patterns, an exit-code table, and the `--deliver` sink table. Minor gaps: the `--playbook-file ~/playbooks/<shape>.json` shape is described but never shown with a concrete example.

4 / 5

Workflow Clarity

The learning loop (Steps 1-6) is explicitly sequenced with a decision tree, and validation is present throughout: mandatory install verification ("Do not proceed with skill commands until verification succeeds"), `learnings confirm` printing the payload to check before materializing, graceful degradation for older binaries, and `doctor` checks. Falls short of 5 because misplaced and duplicated sections (TLS paragraph under "When Not to Use") leave minor gaps in the top-level flow.

4 / 5

Progressive Disclosure

No bundle files or reference files exist; all ~400 lines are inlined in a single SKILL.md. The learning-loop protocol (~180 lines), MCP server setup, and output-delivery details clearly belong in separate reference files. Section headers provide reasonable structure, so this lands at "some structure but content that should be separate is inline" rather than minimal structure.

3 / 5

Total

14

/

20

Passed

Description

28%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 its domain but reads as internal fixture metadata rather than a capability description for a user or agent. It lists no concrete actions, no trigger terms, and no "Use when..." guidance, leaving both the what and the when under-answered.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger phrases (e.g., when the user mentions Printing Press Rich, listing items, or inspecting/exporting its data).

Replace the fixture jargon ('Purpose-built fixture for rich auth env-var model coverage') with 2-4 concrete capabilities the CLI actually provides, such as listing items, read-only inspection/export/sync, and agent-mode output.

Clarify the what/when boundary so a reader can distinguish this skill from sibling printing-press CLI skills (state the read-only scope and the binary name as the distinct trigger).

DimensionReasoningScore

Specificity

"Printing Press CLI for Printing Press Rich" names the domain but lists no concrete actions or capabilities; "Purpose-built fixture for rich auth env-var model coverage" is developer meta-language, not a user-facing capability. This matches the anchor for naming the domain with minimal or generic actions rather than listing 1-2 concrete actions.

2 / 5

Completeness

The "what" is only vaguely implied (drives a CLI) and the "when" is entirely absent — there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3. It falls to 2 because even the "what" is vague.

2 / 5

Trigger Term Quality

No natural phrases a user would say appear; "rich auth env-var model coverage" is internal jargon and the product name is merely repeated. Only one generic keyword exists, missing the natural terms and variations users would actually use.

2 / 5

Distinctiveness Conflict Risk

The product-specific naming ("Printing Press Rich") creates a distinguishable niche, but the generic "CLI for..." framing and fixture language could overlap with sibling printing-press skills. Somewhat specific but overlap risk remains.

3 / 5

Total

9

/

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-rich-auth/printing-press-rich-auth/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.