SKILLEMALL.ai

CA pp-printing-press-oauth2

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

mvanhorn/cli-printing-press Claude Code author: mvanhorn MIT 9 files body ≈ 6 787 tokens Open the sourcegithub.com↗ analyzed 13 h ago

Printing Press CLI for Printing Press Oauth2.

As a process A 80/100 · Runs to the end — weak spots: consistency

IntegrationSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
82/100
safety, quality, tests
Safety 60%
94
Quality 40%
63
Run on models
none yet
Process rating
A
80/100
Runs to the end
Consistency w 8
40
When it triggers w 12
50
Result and completion w 14
60
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 2

✓ No critical or high findings

Medium and low: 2
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Bash
  • low Dangerous commands cmd-quarantine-file README.md:40
    Removes the macOS quarantine flag from one file (usual for a downloaded CLI; make sure the file is the intended binary) (quoted — discussed, not commanded)
    Download a pre-built binary for your platform from the [latest release](https://github.com/mvanhorn/printing-press-library/releases/tag/prin…ent). On macOS, clear the Gatekeeper q
    quoted

Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 6787 tokens (recommended < 5000); move details to references/
  • note edit-residue the text marks something as outdated (lines 100): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 80/100

  • 40Consistency. Frontmatter name (pp-printing-press-oauth2) differs from the folder (printing-press-oauth2-device-code)
  • 50When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 6787 tokens
  • 85Steps. 46 steps, 1 vague phrases
  • 100Tools and files. Tools declared in frontmatter
  • 100Inputs and preconditions. Inputs and preconditions are listed
  • 100Failures and branches. 1 branches, has a failure section
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 14 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (9 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 106: 120–800 characters recommended
  • +2Single-language instructions
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 46 items
  • +3Output format is stated explicitly
  • +4Has examples (16 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.