blogwatcher

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

82%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 content is highly actionable and token-efficient: concrete commands, install instructions, and real output examples with zero filler. Main weaknesses are implicit rather than explicit workflow sequencing, non-header section labels, and an internal migration note that should be removed.

Dimension	Reasoning	Score
Conciseness	The body is lean — a command list, install command, and example output with no explanation of concepts Claude already knows. It is not a 5 because the 'PilotDeck Migration Note' section (internal source path, review status) is migration metadata that wastes tokens and should be trimmed.	4 / 5
Actionability	Every command is copy-paste ready (e.g., `blogwatcher add "My Blog" https://example.com`, `go install github.com/Hyaxia/blogwatcher/cmd/blogwatcher@latest`), and real example output blocks for `blogs` and `scan` cover the common cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The intended flow (install → add a blog → scan → read articles) is legible from the ordered command list and illustrated with example output, but the sequence is implicit rather than stated, and there are no validation checkpoints (e.g., confirm the blog was added before scanning). The destructive `remove` and batch `read-all` commands are peripheral rather than the core workflow, so the batch/destruction cap is not triggered.	4 / 5
Progressive Disclosure	No bundle files exist, and the short, self-contained body appropriately needs no external references; the simple-skill guidance applies. It is not a 5 because section labels ('Install', 'Quick start', 'Common commands', 'Example output') are plain lines rather than markdown headers, and the migration-note section is misplaced internal content that hurts organization.	4 / 5
	Total	17 / 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.

The description is concise, specific, and occupies a distinct niche, but it lacks a 'Use when...' trigger clause, which caps completeness and weakens routing. Adding explicit usage triggers and one or two more concrete capabilities would lift it substantially.

Suggestions

Append a trigger clause, e.g., 'Use when the user wants to follow blogs, subscribe to RSS/Atom feeds, or check for new posts/articles.'

Name one or two more concrete capabilities in the description (e.g., add/remove blogs, scan feeds, mark articles read) to raise specificity from domain-plus-one-action to a comprehensive action list.

Include natural synonyms such as 'follow', 'subscribe', or 'new posts' so users phrasing the need differently still surface this skill.

Dimension	Reasoning	Score
Specificity	"Monitor blogs and RSS/Atom feeds for updates" names the domain ("blogs", "RSS/Atom feeds") and one concrete action ("Monitor... for updates"), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is not a 4 because it does not list several specific actions (e.g., add, scan, mark articles read).	3 / 5
Completeness	It clearly answers 'what' ("Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI") but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. It is not a 2 because the 'what' is specific and concrete, not vague.	3 / 5
Trigger Term Quality	The description includes natural terms users would say — "blogs", "RSS/Atom feeds", "updates", "monitor" — giving good keyword coverage, but misses common variations like "follow", "subscribe", "new posts", or "feed reader", so it is a 4 rather than 5 and clearly above the single-keyword anchor at 3.	4 / 5
Distinctiveness Conflict Risk	RSS/Atom feed monitoring via a specific CLI is a clear niche with minimal conflict risk, but without explicit trigger phrases it has minor overlap potential with general web-monitoring/scraping skills, matching 'Mostly distinct; minor overlap risk' rather than the fully-distinct anchor at 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: OpenBMB/PilotDeck
Path: skills/blogwatcher/SKILL.md
Commit: 66bfd09

Reviewed: 2 days 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.