CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pp-public-param-golden

Printing Press CLI for Public Param Golden. Public parameter name golden fixture

Quality

56%

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-public-param-names/public-param-golden/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 is a strong operational contract: commands are executable, the learning loop is sequenced with validation and feedback loops throughout, and edge cases (older binaries, empty stores, TLS/PATH failures) are anticipated. Its weaknesses are size and layout — a ~410-line monolith with repeated guidance that would benefit from splitting the learning protocol and envelope schemas into reference files and trimming duplicated prose.

Suggestions

Move the learning-loop protocol (Steps 1-6 plus the recall envelope JSON) into a references/LEARNING.md and keep a short recall-first summary in SKILL.md, cutting the body roughly in half.

Deduplicate the do-not-interpolate-user-text guidance into one stated-once rule instead of repeating it in Steps 1, 4, and 6, and delete the stray "Public parameter name golden fixture" line at line 32.

Move the path-resolution details and MCP host configuration examples into a references/ reference file, keeping only the doctor and --home essentials inline.

DimensionReasoningScore

Conciseness

Most content is CLI-specific contract detail Claude cannot know elsewhere (envelope shapes, exit codes, path resolution), so it largely earns its tokens, but the ~410-line body repeats the do-not-interpolate guidance across Steps 1, 4, and 6, reproduces the full recall envelope JSON inline, and carries a stray duplicate of the description ("Public parameter name golden fixture") at line 32. This matches anchor 3 ("mostly efficient but includes some unnecessary explanation or could be tightened") rather than 4, where trimming would be minor.

3 / 5

Actionability

Every section carries copy-paste-ready commands with concrete flags and example values ("stores find --address example-value ... --agent --select id,name", "npx -y @mvanhorn/printing-press-library install public-param-golden --cli-only", "claude mcp add public-param-golden-pp-mcp -- public-param-golden-pp-mcp"), plus exit-code tables and full JSON envelope examples covering the common cases. Remaining placeholders like <id1> are legitimate parameter slots, not gaps.

5 / 5

Workflow Clarity

The learning loop is a clearly sequenced 6-step protocol with an explicit decision tree, a warnings taxonomy, and feedback loops (learnings confirm prints the payload before materializing; trial-then-confirm; reject tombstones the derivation signature). Validation checkpoints are thorough — verify install and --version before any command, doctor --fail-on warn, --dry-run semantics, and local-data purge previewing before --yes deletion — so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

No references/, scripts/, or assets/ directories exist; everything is inlined in a single ~410-line SKILL.md. Section headers are well-organized, but the learning-loop protocol, recall envelope schema, and path/MCP configuration details clearly belong in separate reference files, matching anchor 3 ("content that should be separate is inline"). Not anchor 2 because structure and navigation within the file are good.

3 / 5

Total

16

/

20

Passed

Description

21%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 tool but tells neither Claude nor the user what it does or when to reach for it. It is a label, not a capability statement, and would almost never win a trigger decision on its own merits. Rewriting it around the CLI's actual verbs with an explicit use-when clause would move every dimension up.

Suggestions

State the concrete capabilities in third person, e.g., "Looks up public parameter records and finds nearby stores by address via the public-param-golden CLI".

Add an explicit trigger clause: "Use when the user asks about public parameters, store locations, or finding nearby stores."

Include natural keywords and synonyms users would say (store lookup, nearby stores, public param, golden fixture) so the skill is discoverable by intent rather than only by its proper noun.

DimensionReasoningScore

Specificity

"Printing Press CLI for Public Param Golden" names the domain but contains no action verbs, and "Public parameter name golden fixture" is a noun phrase rather than a capability. It is above anchor 1 because the tool/domain is named specifically, but below anchor 3 because not a single concrete action (e.g., store lookup, finding nearby stores) is stated.

2 / 5

Completeness

The "what" is vague (a CLI whose purpose is never stated) and the "when" is entirely absent — no "Use when..." clause or equivalent trigger guidance. Per the guideline capping completeness at 3 for a missing trigger clause, and given the vague "what", this sits at anchor 2 rather than 3.

2 / 5

Trigger Term Quality

The description consists entirely of proper nouns and jargon ("Printing Press", "Public Param Golden", "golden fixture") with no natural phrase a user would actually say. This matches anchor 1 ("only technical jargon or entirely generic language").

1 / 5

Distinctiveness Conflict Risk

"Public Param Golden" is a unique proper noun so accidental triggering is unlikely, but the description provides no functional distinction from sibling Printing Press CLI skills — the differentiation is nominal, not behavioral. Not anchor 4 because a fleet of similarly-named pp-* CLI skills would overlap on the generic "Printing Press CLI" framing.

3 / 5

Total

8

/

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-public-param-names/public-param-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.