SKILLEMALL.ai

BF agent2rss-client

Agent2RSS 客户端,管理 RSS 频道并推送内容。触发:用户提到 Agent2RSS/RSS 频道/推送文章/上传文章/创建频道/设置默认频道/幂等性。

ClawHub Agent Skills author: Yao Tutu v0.2.1 7 files · 1 script body ≈ 430 tokens open source ↗ analyzed 33 h ago

As a process F 36/100 · Will not run — References files that are not bundled: references/e2e-test.md

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
F
36/100
Will not run
References files that are not bundled: references/e2e-test.md
Tools and files w 18
0
Result and completion w 14
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
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.

Lint

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: references/e2e-test.md
  • warning spec-missing no spec.yaml: behaviour contract not defined (run `skilltest init`)
  • warning triggers-missing spec.yaml has no triggers.positive: skill triggering is not tested
  • warning evals-missing no evals/evals.json: behaviour is not tested (run `skilltest init`)
  • note body-refs-not-included the skill has 1 reference files (rules/ references/ docs/) that a single-turn run does not see: add run.include_files: [auto] or --include-files auto

Process rating: all ten parameters 36/100

Will not run. References files that are not bundled: references/e2e-test.md
  • 0Tools and files. 1 referenced file(s) missing: references/e2e-test.md
  • 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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 40Consistency. Frontmatter name (agent2rss-client) differs from the folder (agent2rss)
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 26 steps
  • 100Execution cost. Instruction body is 430 tokens

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 80: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 26 items
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 1 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.

External checks

ClawHub: suspicious
The skill does what it says, but it can expose RSS channel tokens through its examples and dry-run output, so users should review it before use.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026