CtrlK
BlogDocsLog inGet started
Tessl Logo

blogwatcher

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./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.

The content is concise, highly actionable, and well-organized for a simple CLI skill, with executable commands and realistic example output. The only gap is the lack of validation/confirmation guidance for batch and destructive operations, which keeps workflow clarity at the middle level.

Suggestions

Add a brief validation/confirmation step for destructive or batch operations (e.g., suggest listing blogs before `remove`, or confirming before `read-all`).

Clarify the intended usage sequence (add blog -> scan -> articles -> read) as a short ordered workflow so the typical lifecycle is explicit.

Consider noting how to verify a scan succeeded (e.g., re-running `blogwatcher articles` to confirm new entries were recorded) as a feedback checkpoint.

DimensionReasoningScore

Conciseness

The body is lean and well-organized: a one-line install, a compact command list, and short example outputs, with no over-explanation of concepts Claude already knows; nearly every token earns its place.

3 / 3

Actionability

Provides fully executable, copy-paste-ready CLI commands (e.g., `blogwatcher add "My Blog" https://example.com`, `blogwatcher scan`, `go install ...@latest`) alongside concrete example output, matching the anchor for executable, specific examples.

3 / 3

Workflow Clarity

Commands are listed and usage is unambiguous for a simple tool, but batch/destructive operations like `read-all` and `remove` appear without any validation or confirmation checkpoint, which the rubric says should cap workflow clarity at 2.

2 / 3

Progressive Disclosure

This is a short (<50 line) single-purpose skill with no bundle files and no external references needed; the content is cleanly sectioned (Install, Quick start, Common commands, Example output, Notes), which the rubric allows to score 3 for simple skills.

3 / 3

Total

11

/

12

Passed

Description

50%

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 clear and specific about a niche tool, but it lacks an explicit 'Use when...' trigger clause and only names a single core action, leaving both trigger coverage and completeness at the middle level. Adding invocation triggers and a broader action list would raise it.

Suggestions

Append an explicit 'Use when...' clause naming user-side triggers (e.g., 'Use when the user wants to track blog posts, monitor RSS/Atom feeds for new entries, or manage feed subscriptions').

Broaden trigger-term coverage to include natural variations such as 'subscribe', 'feed reader', 'new posts', and 'track feeds'.

List a few more concrete actions (e.g., add/list/scan/read/remove blogs) to lift specificity from a single action to multiple specific actions.

DimensionReasoningScore

Specificity

Names the domain ('blogs and RSS/Atom feeds') and one concrete action ('Monitor ... for updates') but does not enumerate multiple distinct actions, matching the anchor for naming a domain with some actions rather than comprehensive.

2 / 3

Completeness

Clearly states what the skill does, but provides no explicit 'Use when...' trigger guidance, so the 'when' is only implied; per the rubric a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant natural keywords ('blogs', 'RSS/Atom feeds', 'updates') but misses common variations a user might say ('subscribe', 'feed reader', 'new posts', 'track'), so coverage is partial rather than complete.

2 / 3

Distinctiveness Conflict Risk

The named 'blogwatcher CLI' and RSS/Atom niche are somewhat specific, but the absence of explicit trigger guidance means it could still overlap with generic feed-tracking skills, matching the 'somewhat specific but could overlap' anchor.

2 / 3

Total

8

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
OpenBMB/PilotDeck
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.