blogwatcher

Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/blogwatcher/SKILL.md

The canonical home for this skill is blogwatcher in openclaw/openclaw

Quality

Content

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

A lean, fully executable reference for a simple single-purpose CLI skill: concise, copy-paste-ready commands with realistic example output and no padding. The only weakness is workflow framing — the typical add → scan → read flow is implicit, and the batch/destructive commands (read-all, remove) appear without any verification guidance.

Dimension	Reasoning	Score
Conciseness	The body is ~45 lean lines: a one-line install command, a command list, short example outputs, and a pointer to `--help`. It never explains what RSS/blogs are and every line is directly usable, matching 'Lean and efficient; assumes Claude's competence; every token earns its place'. Not 4 because there is no over-explanation to trim.	5 / 5
Actionability	All seven common commands are concrete, copy-paste-ready invocations with real arguments (e.g. `blogwatcher add "My Blog" https://example.com`), plus verbatim example outputs, matching 'Fully executable; copy-paste ready commands; specific examples cover the common cases'. The `--help` pointers cover the remaining flag surface.	5 / 5
Workflow Clarity	Commands are listed flat with no explicit sequence (add → scan → read is only implied by listing order), and batch/destructive operations (`read-all`, `remove`) carry no validation or caution guidance, which per the guidelines caps workflow clarity at 3. Not 2 because the command set itself is well-defined and the implied order is discernible.	3 / 5
Progressive Disclosure	This is a simple skill under 50 lines with no bundle files and no need for external references; the body is organized into clear sections (Install, Quick start, Common commands, Example output, Notes), which per the simple-skill guideline earns a 5. Structure is flat, well-labeled, and easy to navigate.	5 / 5
	Total	18 / 20 Passed

Description

53%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, but it describes only one generic action and entirely omits when to use the skill. Adding a 'Use when...' clause with natural trigger phrases would substantially improve it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to track blog updates, follow RSS/Atom feeds, or check for new posts on websites.'

Mention 1-2 more concrete capabilities (e.g. add/remove feeds, scan for new articles, mark articles read) to raise specificity from one generic action to a fuller picture.

Include common user phrasings and synonyms such as 'new posts', 'subscribe to', and 'follow' so natural-language triggering matches more variants.

Dimension	Reasoning	Score
Specificity	"Monitor blogs and RSS/Atom feeds for updates" names the domain clearly but offers only one generic action ("monitor ... for updates") — matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is not score 2 because the domain and action are concrete (not 'Processes data'-level vague), and not score 4 because no additional specific actions (add, scan, mark read, remove) are listed.	3 / 5
Completeness	The 'what' is clearly stated (monitor blogs and RSS/Atom feeds for updates via the blogwatcher CLI), but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. Not 4 because 'when' is entirely absent rather than just under-specified.	3 / 5
Trigger Term Quality	Keywords "blogs", "RSS/Atom feeds", and "updates" are relevant and natural, but common variations users would actually say — "new posts", "subscribe", "follow", "feed reader" — are absent, matching 'Some relevant keywords but missing common variations or synonyms'. It falls short of 4 because coverage is three terms with no synonyms or extensions.	3 / 5
Distinctiveness Conflict Risk	The niche (blog/RSS feed monitoring via a specific CLI) is distinct with little overlap risk against generic document or web skills, matching 'Mostly distinct; minor overlap risk with closely related skills'. Not 5 because the 5 anchor expects explicit distinct trigger phrases, which the description lacks.	4 / 5
	Total	13 / 20 Passed

Validation

81%

Warnings & errors only

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

Criteria	Description	Result
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: Bitterbot-AI/bitterbot-desktop
Path: skills/blogwatcher/SKILL.md
Commit: 1c7dc1b

Reviewed: 19 hours ago

Table of Contents

Discovery Implementation Validation

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.