CtrlK
BlogDocsLog inGet started
Tessl Logo

blogwatcher

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

84

1.96x
Quality

79%

Does it follow best practices?

Impact

100%

1.96x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

The canonical home for this skill is blogwatcher in openclaw/openclaw

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 an exemplary lean CLI reference: fully executable commands, real example output, and clean section organization with zero padding. The only gap is the absence of a sequenced getting-started workflow (add → scan → read) and any verification step around the batch-style `scan` and `read-all` commands.

DimensionReasoningScore

Conciseness

The body is a lean catalog — "Add a blog: blogwatcher add 'My Blog' https://example.com" and similar one-liners — with no padding and no explanation of concepts Claude already knows (no RSS/Atom tutorial, no library discussion). It matches anchor 5 ('every token earns its place'); there is nothing to trim for anchor 4.

5 / 5

Actionability

Every common command is given as a copy-paste-ready invocation ("blogwatcher scan", "blogwatcher read 1", "blogwatcher remove 'My Blog'") plus real example output blocks for `blogs` and `scan`, matching anchor 5 ('fully executable; copy-paste ready... specific examples cover the common cases').

5 / 5

Workflow Clarity

Each command is unambiguous and complete, but the typical usage flow (add a blog → scan → read articles) is never sequenced, and the batch operations (`scan` across all blogs, `read-all`) have no verification checkpoint — anchor 4's 'clear sequence with most checkpoints... minor validation gaps'. Not 5 because no explicit sequence or validation steps are shown; not 3 because this is a thin one-shot CLI wrapper where the gaps are minor rather than structural.

4 / 5

Progressive Disclosure

The body is under 50 lines with no need for external references, and it is organized into clear sections (Install, Quick start, Common commands, Example output, Notes). Per the rubric's guideline for such simple skills, well-organized sections alone warrant anchor 5.

5 / 5

Total

19

/

20

Passed

Description

65%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, third-person, and names a clear, distinct niche, but it is thin on capabilities and completely lacks a 'Use when...' trigger clause. Adding explicit trigger conditions and one or two more concrete capabilities would raise both completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to track blog or feed updates, check for new posts, or mentions RSS/Atom feeds."

Name one or two more concrete capabilities (e.g. "add blogs, scan for new articles, and mark articles as read") to lift specificity from one generic action to several specific ones.

Include common synonyms such as "new posts", "articles", and "subscribe" to broaden natural trigger-term coverage.

DimensionReasoningScore

Specificity

The description names its domain ("blogs and RSS/Atom feeds") and one concrete action ("Monitor... for updates"), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It stays at 3 rather than 4 because only a single generic verb is given — no enumeration of capabilities such as adding blogs, scanning, or marking 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 caps completeness at 3 per the judging guidelines. Not 4 because the 'when' is entirely absent rather than merely implicit-but-stated.

3 / 5

Trigger Term Quality

Phrases like "Monitor blogs", "RSS/Atom feeds", and "updates" are natural terms a user would say, giving good keyword coverage. A few common variations are missing ("new posts", "articles", "subscribe", "feed reader"), so it falls short of the comprehensive-synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Blog and RSS/Atom feed monitoring with a named CLI ("blogwatcher") is a clear niche with distinct triggers and minimal conflict risk. The domain terms themselves (blogs, RSS/Atom feeds) are distinguishing rather than overlapping, so it matches anchor 5 rather than the 'minor overlap risk' of anchor 4.

5 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 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

13

/

16

Passed

Repository
trpc-group/trpc-agent-go
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.