BC http-request-builder
Build and test HTTP requests with CLI interface: headers, auth, body, cookies, with history and templates.
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
How to improve
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
-
low Secrets in code
secret-high-entropy-tokenREADME.md:32High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)--auth bearer --token "eyJh…CJ9"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:61High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)--auth bearer --token "eyJh…CJ9"
quoted
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Build and test HTTP requests with CLI interface: headers, auth, bo… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 49 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1354 tokens
- 100Progress reporting. Reports progress
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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 14 headings
- +3Step-by-step instructions: 49 items
- +4Has examples (7 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.
External checks
ClawHub: suspicious
This appears to be a legitimate HTTP testing tool, but it can store tokens, headers, and request bodies in plaintext local files without strong warning or redaction.
LLM: suspicious (high) · VirusTotal: · 29 May 2026