CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pp-learn-loop-example

Printing Press CLI for Learn Loop Example. Golden fixture exercising the spec-declared self-learning loop.

Quality

65%

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-learn-loop-api/learn-loop-example/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 delivers exceptionally actionable, well-sequenced operational guidance with real validation checkpoints and error-recovery loops — the learning-loop protocol in particular is unambiguous and executable. Its weaknesses are size-related: a ~420-line monolithic file with no progressive disclosure into bundle files, and a few padded or duplicated passages. Splitting reference material out and trimming the meta-commentary would raise both conciseness and structure without losing any operational value.

Suggestions

Move the stable reference material — the recall response envelope JSON schema, exit-code table, CSV-formula-injection contract, MCP HTTP/origin configuration, and path-resolution rules — into a references/ file (e.g., references/cli-contract.md) and keep SKILL.md as the operational core with clearly signaled one-level-deep links.

Delete the duplicated read-only prohibition (keep the 'When Not to Use This CLI' section, drop the repeated list under Agent Mode) and cut the generator meta-commentary about the sync-walker fixture and EXAMPLE-*/ALPHA/BRAVO identifiers, which an operator never needs.

DimensionReasoningScore

Conciseness

Most sections are dense, command-first, and assume Claude's competence, but there is removable fat: the 'Golden fixture... mirrors the sync-walker fixture' paragraph is generator meta-commentary irrelevant to operating the CLI, and the read-only prohibition is stated twice (the 'When Not to Use This CLI' section and again as 'Read-only — do not use this CLI for create, update, delete...' under Agent Mode). It is not 4 because those sections can be cut without losing guidance; not 2 because most of the body is tight and operational.

3 / 5

Actionability

Guidance is fully executable and copy-paste ready throughout: the npx install command, `echo "$TOKEN" | learn-loop-example-pp-cli auth set-token`, the file-then-$QUERY recall/teach/playbook-amend invocations, the which/auth/profile/feedback command sets, and the exit-code table. Specific examples cover the common cases, matching the top anchor.

5 / 5

Workflow Clarity

The learning loop is sequenced as six explicit steps (recall → decision tree → warnings → teach → playbooks → amend) with concrete validation checkpoints ('You must verify the CLI is installed before invoking any command', 'check that the printed payload matches the behavior you verified', 'Do not proceed with skill commands until verification succeeds') and error-recovery feedback loops (confirm/reject, graceful degradation for older binaries, empty-store short-circuit). No destructive or batch operation lacks validation — even `local-data purge` previews and requires `--yes`.

5 / 5

Progressive Disclosure

Section headers are clear and in-file navigation is good, but the skill is a single ~28KB monolith with no bundle files at all (no references/, scripts/, or assets/ exist), while content that clearly belongs in separate files is inlined: the full recall-envelope JSON schema, exit-code and CSV-injection contract details, MCP HTTP transport configuration, and path-resolution internals. It is above anchor 2 because the structure is genuinely good rather than minimal, but below 4 because the split is wholly absent, not a minor gap.

3 / 5

Total

16

/

20

Passed

Description

41%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 identifies a distinct, low-conflict niche but reads as generator meta-commentary about a golden fixture rather than a capability statement. It names no concrete actions, includes no natural trigger phrases, and completely lacks a 'when to use' clause. It would rarely be selected by a user stating a task in their own words.

Suggestions

Add a 'Use when...' clause naming concrete trigger moments, e.g., 'Use when the user asks to list games or leagues, sync or inspect learn-loop-example data, or work with the learn-loop-example CLI/MCP server.'

Replace the fixture meta-language ('Golden fixture exercising the spec-declared self-learning loop') with the CLI's actual capabilities: read-only inspection of games and per-game leagues, offline SQLite sync, and the recall/teach/playbook self-learning loop.

Include natural trigger keywords users would actually say — 'learn-loop-example', 'pp-cli', 'games', 'leagues', 'recall', 'teach', 'learnings', 'playbook' — so the skill surfaces for task-shaped requests, not just product-name mentions.

DimensionReasoningScore

Specificity

The description names the domain ('Printing Press CLI for Learn Loop Example') but lists no concrete user-facing capabilities — 'Golden fixture exercising the spec-declared self-learning loop' describes the fixture's generator purpose, not actions like listing games, fetching leagues, or teaching/recalling learnings. It names the domain with minimal actions, matching anchor 2 rather than 3, which requires at least one concrete action.

2 / 5

Completeness

The 'what' is present and reasonably clear (a printing-press CLI demonstrating a self-learning loop), but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline. It is not 2 because the 'what' is not vague, and not 4 because no 'when' exists at all.

3 / 5

Trigger Term Quality

The only candidate trigger terms are project jargon ('Printing Press', 'Golden fixture', 'spec-declared self-learning loop') with no natural task phrases a user would say (e.g., 'list games', 'leagues', 'learn loop CLI'). It sits above anchor 1 only because the product name 'Learn Loop Example' is itself a sayable trigger, but coverage is far below the good-keyword anchor 4.

2 / 5

Distinctiveness Conflict Risk

The niche is highly specific (a CLI for the 'Learn Loop Example' fixture), so overlap with other skills is minimal. It falls short of anchor 5 because the distinct trigger surface is thin and jargon-heavy rather than a rich set of natural, unambiguous triggers.

4 / 5

Total

11

/

20

Passed

Validation

75%

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

Validation — 12 / 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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository

mvanhorn/cli-printing-press

Path

testdata/golden/expected/generate-learn-loop-api/learn-loop-example/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.