BC RFC文档服务
一个用于从ietf.org网站获取、解析和阅读RFC文档的MCP服务器，提供程序化交互工具。
一个用于从ietf.org网站获取、解析和阅读RFC文档的MCP服务器，提供程序化交互工具。
As a process C 50/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 0
✓ No critical or high findings
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 50/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (RFC文档服务) differs from the folder (rfc-doc)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 14 steps
- 100Execution cost. Instruction body is 602 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
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 46: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 15 headings
- +3Step-by-step instructions: 14 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.
External checks
ClawHub: suspicious
This skill presents itself as an ietf.org RFC reader but routes requests and an API key through a third-party service while persistently storing the key locally.
LLM: suspicious (high) · VirusTotal: · 3 Jul 2026