add-telegram

Add Telegram channel integration via Chat SDK.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/add-telegram/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a well-sequenced, validated workflow; its main weakness is monolithic organization with no progressive disclosure despite reference-style sections that could be split out.

Suggestions

Move the Channel Info and Troubleshooting sections into separate reference files (e.g., CHANNEL-INFO.md, TROUBLESHOOTING.md) with one-line pointers from SKILL.md to improve progressive disclosure.

Trim the explanatory prose surrounding each directive to the essential rationale to lift conciseness toward 3.

Keep the validated build→test→restart→pair ordering exactly as-is; it is the strongest part of the skill.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of padding about concepts Claude already knows, but a substantial volume of explanatory prose around each directive (idempotency rationale, ordering justifications) could be tightened, matching the score-2 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	Every step ships executable, copy-paste-ready guidance — exact `nc:` directives, file paths, a pinned version (`@chat-adapter/telegram@4.29.0`), and concrete commands (`pnpm run build`, the `curl \| jq` getMe) — matching the score-3 fully-executable anchor.	3 / 3
Workflow Clarity	The Apply section is a numbered 1–5 sequence with explicit validation checkpoints (build guards the typed call and dependency; the registration test catches drift; `getMe` validates the token; restart precedes pairing) plus troubleshooting feedback loops, matching the score-3 anchor.	3 / 3
Progressive Disclosure	The skill is self-contained with no bundle files and clear section headings, but at ~170 lines it is monolithic and keeps reference-y material (Channel Info, Troubleshooting) inline that could live in separate reference files, fitting the score-2 'content that should be separate is inline' anchor rather than the under-50-line simple-skill exemption.	2 / 3
	Total	10 / 12 Passed

Description

57%Weight 40%Scale 1-3

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 and distinct but one-dimensional: it states a single action with no use-when trigger guidance, which caps completeness and leaves trigger coverage thin.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke the skill (e.g., 'Use when adding Telegram as a chat channel or when the user mentions Telegram bots/BotFather').

List the concrete actions performed (copy adapter, register, pair) rather than the single verb 'Add' to lift specificity to 3.

Include natural trigger variations users would say ('Telegram bot', 'Telegram channel', 'BotFather') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Quotes "Add Telegram channel integration via Chat SDK" name the domain (Telegram channel) and one concrete action (add integration), but only a single action is listed rather than multiple specific concrete actions, matching the score-2 anchor.	2 / 3
Completeness	It clearly states what the skill does ("Add Telegram channel integration via Chat SDK") but provides no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	"Telegram" is a natural keyword a user would say, but the description lacks common variations and offers no broader trigger phrasing, fitting the score-2 anchor of some relevant keywords missing variations.	2 / 3
Distinctiveness Conflict Risk	"Telegram channel integration" carves out a clear, distinct niche unlikely to trigger for other channel skills, matching the score-3 anchor of a clear niche with distinct triggers.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: nanocoai/nanoclaw
Path: .claude/skills/add-telegram/SKILL.md
Commit: 641963c

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.