AC newman
Automated API testing with Postman collections via Newman CLI. Use when user requests API testing, collection execution, automated testing, CI/CD integration, or mentions "Postman", "Newman", "API tests", "run collection", or "automated testing".
Automated API testing with Postman collections via Newman CLI.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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
-
low Secrets in code
secret-password-literalREADME.md:151Hard-coded password / key literal (may be an example)export API_KEY="sk_l…xyz"
-
low Exfiltration
exfil-webhook-urlreferences/advanced-patterns.md:110Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)newman run collection.json -r slack-reporter.js --reporter-slack-webhookUrl="https://hooks.slack.com/..."
placeholder
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1881 tokens
- 100Running it twice. No mutating operations
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -33 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 246: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 31 items
- +4Has examples (16 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.