CA pp-printing-press-rich
Printing Press CLI for Printing Press Rich. Purpose-built fixture for rich auth env-var model coverage.
Printing Press CLI for Printing Press Rich.
As a process A 82/100 · Runs to the end — weak spots: consistency
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Bash
-
low Secrets in code
secret-high-entropy-tokeninternal/cli/root_test.go:170High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)// Test…de2 covers the end-to-end contract:
fixture -
low Secrets in code
secret-high-entropy-tokeninternal/cli/root_test.go:174High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)func Test…de2(t *testing.T) {fixture -
low Secrets in code
secret-high-entropy-tokeninternal/mcp/bound/bound_test.go:288High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)func Test…ies(t *testing.T) {fixture -
low Dangerous commands
cmd-quarantine-fileREADME.md:40Removes 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/printing-press-rich-current). On macOS, clear the Gatekeeper qua
quoted
Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 6764 tokens (recommended < 5000); move details to references/ - note
edit-residuethe text marks something as outdated (lines 97): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 82/100
- 40Consistency. Frontmatter name (pp-printing-press-rich) differs from the folder (printing-press-rich-auth)
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 6764 tokens
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 46 steps
- 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 103: 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.