BF rss-digest
Generate a structured daily or weekly digest from an OPML file of RSS/Atom feeds. Fetches articles from a configurable time window (last 24h or 7 days), optionally filters by keywords/topics, and outputs a formatted markdown file suitable for Obsidian or Discord. Use when the user asks to: generate an RSS digest, summarize their feeds, build a news roundup, read their OPML feeds, or schedule a daily/weekly newsletter from RSS. Triggers on phrases like "rss digest", "feed digest", "summarize my feeds", "daily news roundup", "weekly digest from OPML", or "what's in my feeds today".
As a process F 47/100 · Will not run — References files that are not bundled: references/opml-example.opml
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Dangerous commands
cmd-cron-mentionSKILL.md:70Mentions editing / listing crontab (quoted — discussed, not commanded)Add to crontab (`crontab -e`) for a daily digest at 7 AM ET:
quoted
Files scanned: 5. 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: Generate a structured daily or weekly digest from an OPML file of … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
missing-refreference to a missing file: references/opml-example.opml
Process rating: all ten parameters 47/100
- 0Tools and files. 1 referenced file(s) missing: references/opml-example.opml
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (rss-digest) differs from the folder (nai-rss-digest)
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 8 steps
- 100Execution cost. Instruction body is 1082 tokens
- 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
- +4Description does not say when NOT to use the skill (false activations)
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 586: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 8 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.