SKILLEMALL.ai

AC danish-news-aggregator

Comprehensive Danish News RSS Aggregator - combines 100+ Danish RSS feeds into category-based unified feeds. Produces 6 curated RSS feeds: - danish-all.xml (top 30 sources) - danish-national.xml (newspapers) - danish-regional.xml (local news) - danish-sports.xml (sports) - danish-business.xml (finance) - danish-tech.xml (technology) - danish-english.xml (English-language Denmark) Auto-refreshes every 15 minutes, deduplicates, ranks by source authority.

modbender/skill-library-mcp Agent Skills author: modbender MIT 6 files body ≈ 585 tokens Open the sourcegithub.com analyzed 2 d ago

Comprehensive Danish News RSS Aggregator - combines 100+ Danish RSS feeds into category-based unified feeds.

As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

GeneratorDockerInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
C
62/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
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.
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: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 62/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
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. No external tools needed
  • 100Steps. 15 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 585 tokens
  • 100Running it twice. No mutating operations

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 458: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 15 items
  • +3Output format is stated explicitly
  • +4Has examples (4 code blocks)

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