CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rss-feeds

Read RSS, Atom, JSON feeds; discover feeds behind a page.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/research/rss-feeds/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Excellent content: fully executable commands that match the bundled script's real CLI, a dense quick-reference of feed URL patterns, and pitfalls covering non-obvious failure modes without a wasted token. The only room for improvement is embedding explicit per-step validation in the Procedure rather than relying on the Pitfalls and Verification sections.

DimensionReasoningScore

Conciseness

Every section earns its tokens: the Quick Reference table supplies non-obvious feed URL patterns, Pitfalls covers genuinely obscure failure modes (Reddit's anonymous throttle, RFC 822 vs ISO 8601 dates, Cloudflare 403s), and nothing explains concepts Claude already knows. It stays lean while making the skill's boundary explicit ('does not fetch full article bodies — pass an entry's link to web_extract').

5 / 5

Actionability

The 'How to Run' block gives four copy-paste-ready commands with real URLs and flags (--limit, --since, --json) that match the actual script CLI exactly (verified against scripts/feed.py: read/discover subcommands with those arguments), and the Verification section provides a concrete checkable command. This matches the fully-executable anchor with common cases covered.

5 / 5

Workflow Clarity

The numbered Procedure (①-④) sequences discovery → bounding → full-text extraction → citation, and Pitfalls plus the Verification section provide error-recovery guidance and an end-state check. It falls short of a 5 because the workflow steps themselves embed no per-step validation checkpoints (e.g. what to check in the output before proceeding), which is a minor gap rather than the explicit validate-fix-retry loop of the top anchor.

4 / 5

Progressive Disclosure

The body is a well-organized overview with clearly signaled one-level-deep references: the only bundle file (scripts/feed.py) is referenced by a correct, relative path and invoked consistently, and implementation detail is properly pushed into the script rather than inlined. Sections are compact and easy to navigate, with the Quick Reference kept at a size appropriate for the main file.

5 / 5

Total

19

/

20

Passed

Description

61%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, concrete description that clearly states what the skill does and carves out a distinct feed-reading niche, but it omits any explicit 'use when' trigger guidance and leans on only two action verbs. Adding a trigger clause and a few natural synonyms would lift both completeness and trigger-term coverage.

Suggestions

Append a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user asks about RSS/Atom feeds, wants the latest posts or releases from a site, or asks whether a page has a feed.'

Add natural trigger synonyms such as 'news feed', 'blog feed', 'subscribe', or 'podcast' to broaden natural keyword coverage.

Consider one more specific capability phrase (e.g. 'normalizes dates and outputs sorted, machine-readable entries') to make the action coverage more comprehensive.

DimensionReasoningScore

Specificity

The description names the domain ("RSS, Atom, JSON feeds") and two concrete actions — "Read ... feeds" and "discover feeds behind a page" — matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not a 4 because only two actions are listed and 'read' is fairly minimal; it is above a 2 because the actions are concrete rather than generic.

3 / 5

Completeness

The 'what' is clear (read feeds, discover feeds) but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. This fits the score-3 anchor exactly; it is above a 2 because the 'what' is concrete, and below 4 because 'when' is entirely absent.

3 / 5

Trigger Term Quality

Keywords "RSS", "Atom", "JSON feeds", and "feeds" cover the main natural phrasings (e.g. 'read this RSS feed', 'does this site have a feed'), with 'discover' covering the page-to-feed case. A few natural synonyms are missing ('news feed', 'subscribe', 'podcast'), which keeps it below the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

Feed reading is a clear niche with distinct triggers (RSS/Atom/JSON feed URLs), so it is mostly distinct from other skills. Minor overlap risk remains with general web-reading/extraction skills, keeping it at 4 rather than 5.

4 / 5

Total

14

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/research/rss-feeds/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.