CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pp-printing-press-oauth2

Printing Press CLI for Printing Press Oauth2. Purpose-built fixture for the OAuth2 device-code auth shape.

Quality

62%

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-oauth2-device-code/printing-press-oauth2-device-code/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 body is an actionable, well-validated operations manual: every workflow carries concrete commands, exit-code semantics, and verification steps, with the learning loop as an exemplary feedback-rich protocol. Its weaknesses are structural, not instructional — the ~420-line monolith inlines envelope schemas, path contracts, and MCP setup that belong in one-level-deep reference files, and key caveats are repeated two or three times over.

Suggestions

Move the recall/teach envelope JSON schema, the path-and-state resolution contract, and the MCP HTTP server configuration into one-level-deep reference files (e.g. references/learning-loop.md, references/paths.md, references/mcp.md) with short pointers from SKILL.md.

Deduplicate the read-only restriction (stated in "When Not to Use This CLI", the Agent Mode "Read-only" bullet, and Direct Use) and the no-shell-interpolation caveat (repeated in Steps 1, 4, and 6) into a single stated-once rule.

Replace non-executable hedges like "use the category-specific Go fallback after publish" with the actual fallback command, or drop them until the publish state makes them actionable.

DimensionReasoningScore

Conciseness

The body is dense with CLI-specific contract detail Claude cannot know (flags, envelopes, exit codes), but it is noticeably repetitive: the read-only restriction appears in "When Not to Use This CLI", the "Read-only" bullet, and again in Direct Use; the no-shell-interpolation caveat is repeated across Steps 1, 4, and 6; and "Purpose-built fixture for the OAuth2 device-code auth shape" is duplicated from the frontmatter. This fits 'mostly efficient but could be tightened' rather than anchor 4's 'minor instances'.

3 / 5

Actionability

Most guidance is copy-paste executable — exact commands with flags (`printing-press-oauth2-pp-cli items --agent --select id,name`), full envelope JSON, exit-code table, MCP registration snippets — with minor gaps such as "use the category-specific Go fallback after publish" and "Run auth setup for setup details if needed", which are non-executable hand-waves. Not anchor 5 because these vague spots leave small holes in the common install/auth path.

4 / 5

Workflow Clarity

The learning loop is a clearly sequenced six-step protocol with explicit validation checkpoints (verify `--version` before any command, `doctor`, confirm-payload-before-materialize on candidates, reject tombstoning) and genuine feedback loops (amend on divergence, confirm/reject on candidates); destructive operations are gated (`local-data purge` previews and requires `--yes`), so the destructive-cap does not apply. This matches the anchor-5 example's validate-fix-retry structure.

5 / 5

Progressive Disclosure

There are no bundle files at all (no references/, scripts/, or assets/), so ~400 lines of material that clearly belongs in separate files — the recall/teach envelope schema, the path-resolution contract, MCP server configuration, the learning-loop protocol — are all inlined in SKILL.md. Section headers are good and navigation is possible (above anchor 2's 'no section headers' example), but content that should be split out is inline with no references, matching anchor 3.

3 / 5

Total

15

/

20

Passed

Description

40%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 is highly distinctive but functionally hollow: it identifies the niche yet never states what the CLI does or when to invoke it. Without a single concrete action or a 'Use when' trigger clause, an agent would struggle to know what the skill accomplishes or when to activate it.

Suggestions

State 2-4 concrete capabilities in place of the fixture meta-language, e.g. "Lists, exports, and syncs Printing Press Oauth2 items via its read-only CLI, with OAuth2 device-code authentication."

Add an explicit trigger clause: "Use when the user mentions Printing Press Oauth2, device-code login, or asks to inspect/export its items."

Replace "Purpose-built fixture for the OAuth2 device-code auth shape" — which describes the artifact's provenance rather than any capability — with user-facing language about what the skill does.

DimensionReasoningScore

Specificity

"Printing Press CLI for Printing Press Oauth2" names the domain but describes no concrete actions, and "Purpose-built fixture for the OAuth2 device-code auth shape" is meta-purpose language rather than a capability — matching the 'names the domain but actions are minimal or generic' anchor, not anchor 3 which requires 1-2 concrete actions.

2 / 5

Completeness

The 'what' is vague — the description never says what the CLI actually does (list, export, sync, inspect) — and the 'when' is entirely absent with no 'Use when...' clause or equivalent trigger guidance; this fits the 'vague what and no when' anchor rather than anchor 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

"Printing Press", "Oauth2", "device-code", and "auth" are relevant keywords a user in this niche might say, but common natural variations ("login", "sign in", "authenticate", "device code flow") are missing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The product-specific naming ("Printing Press Oauth2", device-code auth fixture) creates a clear niche with minimal overlap risk, but unlike the anchor-5 example it lacks explicit distinct trigger phrases, so it sits at 'mostly distinct; minor overlap risk'.

4 / 5

Total

11

/

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-oauth2-device-code/printing-press-oauth2-device-code/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.