CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

watchers

Poll RSS, JSON APIs, and GitHub with watermark dedup.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/devops/watchers/SKILL.md
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.

A lean, highly actionable overview that correctly delegates implementation to the four bundled scripts, with a genuinely useful pitfalls section covering non-obvious contracts. Only minor coherence gaps — the "handle all three" antecedent and unexplained flags like --max — keep workflow clarity from full marks.

Suggestions

Fix the "The scripts below handle all three" antecedent — it follows four numbered steps, so say "all four steps" or "all three scripts" — and add a line on what the agent should do when a watcher exits non-zero inside a cron tick (retry, skip, or report the error).

Briefly state what "--max" does (or point readers to the scripts' --help), since it appears in the primary usage example unexplained.

DimensionReasoningScore

Conciseness

Every section carries non-obvious contract information ("First run records a baseline", "max 500" ID cap, "Empty stdout on no-new", sandbox-writability caveat) and nothing explains concepts Claude already knows like what RSS or cron is. The one-line intro overlaps slightly with later sections but serves as a legitimate overview, fitting anchor 5's "every token earns its place" rather than anchor 4's trimmable over-explanation.

5 / 5

Actionability

Three copy-paste-ready commands with real values ("--name hn --url https://news.ycombinator.com/rss --max 5", "--id-field event_id --items-path data.events", "--repo NousResearch/hermes-agent --scope issues"), concrete state-inspection commands ("cat", "rm"), and a ready-made cron prompt covering the summarize-or-stay-silent contract. Examples cover the common cases for all three scripts, matching anchor 5.

5 / 5

Workflow Clarity

The Mental model sequences fetch → compare → write → emit and the usage-to-cron wiring is unambiguous, but "The scripts below handle all three" immediately follows four numbered steps (ambiguous antecedent — three scripts or three steps?), and beyond "Non-zero exit on fetch errors" there is no explicit error-recovery guidance (e.g. what the agent should do when a poll fails inside a cron tick). This fits anchor 4 (clear sequence, minor validation gaps) rather than anchor 5's explicit feedback loops.

4 / 5

Progressive Disclosure

All four bundle files referenced in the body (watch_rss.py, watch_github.py, watch_http_json.py, _watermark.py) exist in scripts/ and are referenced one level deep via a script → use → dedup-key table and a named install path. Implementation detail stays in the bundle while SKILL.md remains an overview ("See any of the three reference scripts"), matching anchor 5; nothing inlined belongs in a separate file.

5 / 5

Total

19

/

20

Passed

Description

53%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 names concrete domains and a specific dedup mechanism, giving it a clear "what" and a fairly distinct niche. However, it entirely lacks trigger guidance and misses the natural verbs (watch, monitor, notify) users would say when needing this skill.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to watch or monitor an RSS/Atom feed, a GitHub repo's issues/releases, or a JSON endpoint for new items."

Pair the jargon term with plain user language — e.g. "...so only new items are reported" — and include natural verbs like "watch" and "notify".

State the outcome of polling (notifying on new items) so the "what" covers what actually happens to detected changes.

DimensionReasoningScore

Specificity

"Poll RSS, JSON APIs, and GitHub" names three concrete domains and "watermark dedup" a specific mechanism, but "Poll" is the only action verb — no notify, report, or scheduling outcome is stated, so coverage is not comprehensive. It is more concrete than anchor 2 ("Processes PDF files") thanks to the named dedup technique, but does not list the several actions required for anchor 4.

3 / 5

Completeness

The "what" is clear (polling three source types with deduplication), but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description, which caps this at 3 per the judging guidelines. It cannot score 4 because "when" is entirely absent rather than just weakly implied.

3 / 5

Trigger Term Quality

"Poll", "RSS", and "GitHub" are terms users would naturally say, but the description omits the most common phrasings for this need — "watch", "monitor", "notify me when", "feed" — and "watermark dedup" is internal jargon. This matches anchor 3 ("Some relevant keywords but missing common variations or synonyms") rather than anchor 4's "good keyword coverage".

3 / 5

Distinctiveness Conflict Risk

The "watermark dedup" framing plus the named sources (RSS, GitHub) carves a fairly distinct polling/monitoring niche with a clear trigger surface. Only "JSON APIs" is broad enough to overlap with a generic HTTP-request or API skill, matching anchor 4 ("Mostly distinct; minor overlap risk with closely related skills") rather than anchor 5's minimal conflict risk.

4 / 5

Total

13

/

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

NousResearch/hermes-agent

Path

optional-skills/devops/watchers/SKILL.md

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.