CtrlK
BlogDocsLog inGet started
Tessl Logo

add-reactions

Add WhatsApp emoji reaction support — receive, send, store, and search reactions.

71

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 exemplar procedural skill: lean, fully executable, with a clearly sequenced apply-and-verify workflow that includes idempotency checking, explicit validation gates, and troubleshooting feedback loops. No material weaknesses were found in any dimension.

DimensionReasoningScore

Conciseness

The body contains no concept explanations and no padding — every section is executable commands, concrete checks, or tight bullet troubleshooting (e.g. the one-line pre-flight "test -f src/status-tracker.ts"). Every token earns its place.

5 / 5

Actionability

Guidance is fully executable and copy-paste ready throughout: git remote/fetch/merge with a package-lock conflict fallback, "npx tsx scripts/migrate-reactions.ts", "npm test"/"npm run build", platform-specific restart commands, and a sqlite3 verification query. Verification steps concretely describe what to do on the phone and what to check.

5 / 5

Workflow Clarity

A clear three-phase sequence with an idempotency pre-check ("If already applied, skip to Phase 3"), explicit validation checkpoints ("All tests must pass and build must be clean before proceeding"), database verification queries, and troubleshooting feedback loops (e.g. "table reactions already exists" → skip migration; blocked IPC reaction → check authorization). This matches the anchor with explicit validation steps and error-recovery loops.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed; all ~117 lines are procedural content that belongs inline in SKILL.md, organized under clear phase and section headers with nothing that should be split into a separate file and no buried references.

5 / 5

Total

20

/

20

Passed

Description

75%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 specific, action-oriented, and clearly distinct, but it lacks an explicit "Use when..." trigger clause, which both caps completeness and limits natural trigger-term coverage. Adding a trigger clause naming common user phrasings (react, react to a message, emoji response) would raise it to top quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions reactions, wants the agent to react to WhatsApp messages, or asks about emoji response history."

Include the verb form and synonyms users naturally say — "react"/"reacting" and "emoji response" — alongside "reaction" to broaden trigger matching.

Optionally name the concrete surfaces (MCP tool, SQLite history) to sharpen distinctiveness against generic messaging skills.

DimensionReasoningScore

Specificity

"receive, send, store, and search reactions" lists four concrete actions covering the full reaction lifecycle (ingest, emit, persist, query), matching the comprehensive-coverage anchor; there is no meaningful gap within the domain.

5 / 5

Completeness

The "what" is clearly stated ("Add WhatsApp emoji reaction support — receive, send, store, and search reactions"), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms like "WhatsApp", "emoji", "reaction", and "add reaction" are present, but the verb form "react"/"reacting to a message" and synonyms such as "emoji response" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"WhatsApp emoji reaction support" names a narrow, well-defined niche with distinct triggers (WhatsApp, emoji, reactions), giving minimal conflict risk with other skills.

5 / 5

Total

17

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
jbaruch/nanoclaw-telegram
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.