CtrlK
BlogDocsLog inGet started
Tessl Logo

blogwatcher

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

74

1.96x
Quality

63%

Does it follow best practices?

Impact

100%

1.96x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/blogwatcher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted, concise skill that provides all necessary information for using the blogwatcher CLI without any bloat. Its main strength is actionability—every command is concrete and ready to use. The only minor weakness is that the commands could be presented in a more explicit workflow sequence rather than a flat list.

Suggestions

Consider ordering the 'Common commands' section as a numbered workflow (1. Add a blog, 2. Scan for updates, 3. List articles, 4. Mark read) to make the typical usage sequence explicit.

DimensionReasoningScore

Conciseness

The content is lean and efficient. Every line serves a purpose—install command, common commands, example output. No unnecessary explanations of what RSS feeds are or how CLI tools work.

3 / 3

Actionability

Provides fully concrete, copy-paste ready commands for every common operation (add, list, scan, read, remove). The example output helps Claude understand expected behavior. The install command is specific and executable.

3 / 3

Workflow Clarity

The commands are listed but not sequenced into a clear workflow. For a monitoring tool, a natural workflow would be: add → scan → articles → read, but this is left implicit. However, since this is a simple, non-destructive tool, the lack of validation steps is less critical.

2 / 3

Progressive Disclosure

For a simple, single-purpose skill under 50 lines with no bundle files, the content is well-organized with clear sections (install, quick start, common commands, example output, notes). No external references are needed.

3 / 3

Total

11

/

12

Passed

Description

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 clear niche tool (blogwatcher CLI) and domain (RSS/Atom feeds), which makes it distinctive. However, it lacks a 'Use when...' clause and doesn't enumerate specific actions beyond 'monitor for updates', leaving it incomplete and somewhat vague for skill selection purposes.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to track blog updates, check RSS/Atom feeds, or manage feed subscriptions.'

List more specific actions the skill supports, such as 'add/remove feeds, check for new posts, list recent entries, configure update intervals'.

Include additional natural trigger terms like 'feed reader', 'subscriptions', 'new posts', 'syndication', or 'web feed'.

DimensionReasoningScore

Specificity

Names the domain (blogs, RSS/Atom feeds) and one action (monitor for updates), and mentions the specific tool (blogwatcher CLI), but doesn't list multiple concrete actions like adding feeds, filtering, configuring alerts, etc.

2 / 3

Completeness

Describes what it does (monitor blogs and feeds) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also thin — so this lands at 1.

1 / 3

Trigger Term Quality

Includes relevant keywords like 'blogs', 'RSS', 'Atom', 'feeds', and 'blogwatcher' which users might naturally say, but misses common variations like 'subscriptions', 'news feeds', 'feed reader', 'new posts', or 'syndication'.

2 / 3

Distinctiveness Conflict Risk

The mention of 'blogwatcher CLI' and the specific focus on RSS/Atom feeds creates a clear niche that is unlikely to conflict with other skills.

3 / 3

Total

8

/

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.

Validation8 / 11 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

8

/

11

Passed

Repository
deepgram/dglabs-deepclaw
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.