blogwatcher
Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.
73
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%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 identifies a specific tool (blogwatcher CLI) and domain (RSS/Atom feed monitoring), giving it good distinctiveness. However, it lacks explicit trigger guidance ('Use when...') and could benefit from listing more concrete actions beyond just 'monitor'. The description is too brief to help Claude confidently select this skill.
Suggestions
Add a 'Use when...' clause with trigger terms like 'RSS', 'feed updates', 'blog subscriptions', 'track blogs', or 'syndication'
Expand the action list to include specific capabilities like 'subscribe to feeds', 'check for new posts', 'list feed entries', or 'export feed content'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (blogs, RSS/Atom feeds) and a general action (monitor for updates), but doesn't list multiple concrete actions like subscribing, filtering, alerting, or exporting. | 2 / 3 |
Completeness | Describes what the skill does (monitor feeds) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'blogs', 'RSS', 'Atom', 'feeds', and 'updates' that users might say, but missing common variations like 'subscribe', 'news feeds', 'syndication', or 'feed reader'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'blogwatcher CLI', 'RSS/Atom feeds', and blog monitoring creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, well-crafted skill that demonstrates ideal token efficiency. It provides all necessary commands with concrete examples and expected outputs, assumes Claude's competence with CLI tools, and organizes content logically without unnecessary verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what RSS feeds are or how CLI tools work. Every line provides actionable information. | 3 / 3 |
Actionability | Provides complete, copy-paste ready commands for all common operations. Installation command, all major CLI commands, and example outputs are concrete and executable. | 3 / 3 |
Workflow Clarity | For this simple single-purpose CLI tool, the workflow is clear: add blogs, scan for updates, read articles. The command sequence is logical and the example outputs show expected behavior. | 3 / 3 |
Progressive Disclosure | Appropriately structured for a simple skill under 50 lines. Clear sections (Install, Quick start, Common commands, Example output, Notes) with no need for external references. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 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 | 8 / 11 Passed | |
- 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.