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 efficient, fully actionable command reference with excellent conciseness and progressive disclosure. The only gap is the absence of validation/verification notes for the batch and destructive commands.

Suggestions

Add a brief note on verifying results after `scan` (e.g. check `blogwatcher articles` for new items) and before `remove` (e.g. confirm via `blogwatcher blogs`).

Consider a one-line caution for `read-all` since it irreversibly marks every article as read.

DimensionReasoningScore

Conciseness

The body is a lean CLI reference with install, quick start, command list, and example output; it assumes Claude's competence with no padded explanations of concepts.

5 / 5

Actionability

Every command is copy-paste ready with real arguments (e.g. `blogwatcher add "My Blog" https://example.com`) and concrete example output covers the common cases.

5 / 5

Workflow Clarity

Commands are unambiguous single actions, but batch/destructive operations like `scan`, `read-all`, and `remove` carry no validation or verification guidance, preventing a 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clear sections (Install, Quick start, Common commands, Example output, Notes), meeting the simple-skill exception.

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 and clearly identifies a distinct niche with good natural keywords, but it omits an explicit "Use when" trigger clause, capping completeness. Adding trigger guidance would raise the score.

Suggestions

Append a "Use when..." clause naming concrete triggers, e.g. "Use when the user wants to track blog updates or monitor RSS/Atom feeds."

Add a couple of concrete actions or synonyms (e.g. "subscribe", ".rss", "feed updates") to broaden trigger term coverage.

Consider listing 1-2 more specific capabilities (e.g. "scan for new articles", "mark articles read") to lift specificity above 3.

DimensionReasoningScore

Specificity

"Monitor blogs and RSS/Atom feeds for updates" names the domain and one concrete action (monitoring for updates) but offers no further concrete actions, matching the anchor for 1-2 actions without comprehensive coverage.

3 / 5

Completeness

The description gives a clear "what" but lacks any "Use when..." or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Natural keywords like "blogs", "RSS/Atom feeds", and "updates" map well to what users say, though synonyms such as "feed reader", "subscribe", or file extensions like ".rss" are missing.

4 / 5

Distinctiveness Conflict Risk

Blog/RSS feed monitoring is a clear niche and the named "blogwatcher CLI" makes it distinct from other skills with minimal conflict risk.

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.

Validation13 / 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.