BC x-rfc
RFC (Request for Comments) document query tool providing access to Internet protocol standards. Use this skill whenever the user needs to look up, search, read, or learn about RFC documents. Covers: list RFCs (x rfc ls), view by number (x rfc 791), search (x rfc : http), and AI summary (x rfc :: tls). Triggered by queries like "RFC 791", "TCP standard", "HTTP protocol", "TLS specs", "SMTP RFC", "what is RFC 1918?", or any Internet protocol standard lookup.
As a process C 60/100 · Has gaps — weak spots: result and completion, failures and branches, 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.
- 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
-
high Dangerous commands
cmd-pipe-to-shelldata/install.md:104Downloads and executes remote code from an unrecognised host (pipe to shell)curl -fsSL https://get.x-cmd.com | sh
Medium and low: 1
-
medium Dangerous commands
cmd-pipe-to-shelldata/install.md:25Downloads and executes remote code from an unrecognised host (pipe to shell) (quoted — discussed, not commanded)command: "curl -fsSL https://get.x-cmd.com | sh"
quoted
Files scanned: 3. 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 60/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 231 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (3 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 460: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.