BB oo-postman
Postman (postman.com). Use this skill for ANY Postman request — reading, creating, updating, and deleting data. Whenever a task involves Postman, use this skill instead of calling the API directly.
Postman (postman.com). Use this skill for ANY Postman request — reading, creating, updating, and deleting data. Whenever a task involves Postman, use this…
As a process B 66/100 · Nearly there — weak spots: result and completion, execution cost, progress reporting
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 1
-
high Dangerous commands
cmd-pipe-to-shellSKILL.md:189Downloads and executes remote code from an unrecognised host (pipe to shell)curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8448 tokens (recommended < 5000); move details to references/ - note
edit-residuethe text marks something as outdated (lines 31, 52, 66, 94, 105, 116): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 66/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 40Execution cost. Instruction body is 8448 tokens: crowds the task out of the window
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 145 steps, 2 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 197: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 145 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.