blogwatcher

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

Quality

68%

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

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 content is highly actionable with copy-paste CLI commands and good conciseness, but lacks validation guidance for its batch/destructive operations and carries an irrelevant migration-metadata section. Structure is otherwise clean for a simple single-purpose skill.

Suggestions

Add a brief validation/verification step for batch and destructive commands (e.g., run "blogwatcher articles" after "read-all" or "scan" to confirm the result).

Remove or relocate the "PilotDeck Migration Note" review metadata so the body stays focused on skill usage.

Clarify the intended workflow sequence (add blog -> scan -> review articles -> mark read) with a short ordered list.

Dimension	Reasoning	Score
Conciseness	The body is lean: direct command lists and short example-output blocks with no concept over-explanation. Not a 5 because the "PilotDeck Migration Note" section is review metadata that does not help Claude use the skill and could be trimmed.	4 / 5
Actionability	Copy-paste-ready commands cover the common cases ("blogwatcher add", "blogwatcher scan", "blogwatcher read 1", "blogwatcher read-all") plus an install command and concrete example output. Fully executable guidance matching the top anchor.	5 / 5
Workflow Clarity	Commands are listed but the skill includes batch/destructive operations ("read-all", "remove") with no validation or verification steps, which caps workflow clarity at 3 per the guideline. Not a 4 because explicit checkpoints for these risky operations are absent.	3 / 5
Progressive Disclosure	Well-organized sections (Install, Quick start, Common commands, Example output, Notes) with no bundle files needed, appropriate for a short single-purpose skill. Not a 5 because the out-of-place PilotDeck migration metadata slightly disrupts otherwise clean organization.	4 / 5
	Total	16 / 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 and names a concrete domain and action with good natural trigger terms, but it lacks an explicit "Use when..." clause, which caps its completeness. It is reasonably distinct thanks to the named CLI and specific feed-monitoring niche.

Suggestions

Add a "Use when..." clause naming user triggers, e.g. "Use when monitoring blogs or RSS/Atom feeds for new posts or feed updates."

Include a couple more concrete actions (e.g., "add, scan, and track feed updates") to lift specificity toward comprehensive coverage.

Add common synonyms such as "feed reader" or "subscribe to feeds" to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Monitor blogs and RSS/Atom feeds for updates" names the domain and one concrete action (monitoring for updates), matching the anchor that lists 1-2 concrete actions without comprehensive coverage. Not a 2 because the action is concrete rather than minimal/generic; not a 4 because only a single action is named.	3 / 5
Completeness	It clearly states what the skill does ("Monitor blogs and RSS/Atom feeds for updates") but provides no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the guidelines. Not a 4 because the "when" is entirely missing rather than weakly implied.	3 / 5
Trigger Term Quality	"blogs", "RSS/Atom feeds", and "updates" are natural terms users would say, giving good keyword coverage. Not a 5 because common variations like "feed reader", "subscribe", or specific file extensions are absent.	4 / 5
Distinctiveness Conflict Risk	"blogs and RSS/Atom feeds" plus the named "blogwatcher CLI" carve a distinct niche with minor overlap risk against general feed/news skills. Not a 5 because no explicit trigger phrases further differentiate it from related feed-monitoring skills.	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: eaa7c2b

Reviewed: 3 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.