CtrlK
BlogDocsLog inGet started
Tessl Logo

blogwatcher

Monitor blogs and RSS/Atom feeds via blogwatcher-cli tool.

54

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/research/blogwatcher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

The body is a strong, executable CLI reference with excellent actionability and clean organization, but it presents commands as a menu without a sequenced workflow or validation guidance for destructive/batch operations.

Suggestions

Add a short sequenced quick-start workflow (add a blog -> scan -> list unread -> mark read) with an explicit validation checkpoint after scanning.

Document a verify/confirmation step before destructive or batch operations (e.g., preview affected blogs before 'read-all --yes' or 'remove --yes').

Trim the overlap between the intro sentence and the Notes section to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is an efficient command reference with tables and example output and assumes Claude's competence; only minor repetition between the intro and the Notes section could be trimmed, fitting anchor 4.

4 / 5

Actionability

Commands are copy-paste ready with exact flags covering add, scan, articles, read/unread, import, and env-var configuration, matching the anchor-5 example of fully executable guidance.

5 / 5

Workflow Clarity

It is a command menu rather than a sequenced workflow, and batch/destructive operations (remove --yes, read-all) lack validation checkpoints; the destructive/batch cap holds workflow clarity at 3.

3 / 5

Progressive Disclosure

No bundle files exist, so all content lives in SKILL.md, but it is well organized into clear one-level sections with no nested references; minor gaps keep it at 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

48%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.

The description is concise and names a clear niche plus tooling, but it stops at one generic action and omits any 'Use when' trigger guidance, capping completeness and trigger coverage.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when the user wants to track blog or RSS/Atom feed updates, monitor subscriptions, or import OPML files.'

Expand the action verbs beyond 'Monitor' to concrete capabilities like 'add, scan, and manage read/unread articles' to raise specificity.

Include common synonyms/file types (RSS, Atom, feeds, OPML, subscriptions) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Monitor blogs and RSS/Atom feeds" names the domain plus a single generic action ("Monitor"), matching anchor 2; it does not list a second concrete action like "extract" that would warrant a 3.

2 / 5

Completeness

The description gives a clear 'what' (monitor blogs and RSS/Atom feeds) but has no 'Use when...' trigger clause; per the judging guidelines a missing trigger caps completeness at 3.

3 / 5

Trigger Term Quality

"blogs" and "RSS/Atom feeds" are natural terms users say, but common variations/synonyms like feeds, subscriptions, OPML, or feed-reader are missing, fitting anchor 3.

3 / 5

Distinctiveness Conflict Risk

Blog/RSS-feed monitoring with a named tool is a clear, mostly distinct niche with minor overlap risk; not a 5 because it lacks the explicit trigger phrases the anchor-5 example relies on.

4 / 5

Total

12

/

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.

Validation13 / 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
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.