Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.
Install with Tessl CLI
npx tessl i github:Hung-Reo/hungreo-openclaw --skill blogwatcher78
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 clear niche (RSS/Atom feed monitoring) with a specific tool (blogwatcher CLI), making it distinctive. However, it lacks explicit trigger guidance ('Use when...') and could benefit from listing more specific actions the skill can perform beyond just 'monitor'.
Suggestions
Add a 'Use when...' clause with trigger terms like 'RSS', 'feed updates', 'blog monitoring', 'subscribe to feeds', or 'check for new posts'
Expand the capability list with specific actions such as 'add feeds, check for new posts, list subscriptions, configure update intervals'
Include common user phrasings like 'subscribe to blog', 'track website updates', or 'news feed'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (blogs, RSS/Atom feeds) and a general action (monitor for updates), but doesn't list multiple specific concrete actions like adding feeds, checking specific entries, or configuring alerts. | 2 / 3 |
Completeness | Describes what it does (monitor blogs/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' which users might naturally say, but missing common variations like 'subscribe', 'news feeds', 'syndication', or 'feed reader'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers - RSS/Atom feeds and blogwatcher CLI are specific enough that this is unlikely to conflict with other skills; the tool name provides additional distinctiveness. | 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 exemplifies token efficiency and actionability. It provides all essential commands with concrete examples and expected outputs, without any unnecessary explanation of concepts Claude already knows. The structure is appropriate for a simple CLI tool skill.
| 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 is specific, and example outputs show exactly what to expect. | 3 / 3 |
Workflow Clarity | For this simple CLI tool, the workflow is implicit but clear: add blogs → scan → view articles → mark read. No destructive operations requiring validation checkpoints. | 3 / 3 |
Progressive Disclosure | Appropriately structured for a simple skill under 50 lines. Quick start, common commands, and examples are well-organized. Points to --help for deeper discovery. | 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 | |
Table of Contents
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.