CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-telegram

Add Telegram channel integration via Chat SDK.

Quality

74%

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 ./.claude/skills/add-telegram/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 body is a highly actionable, well-sequenced runbook: executable nc: directives with exact commands, explicit validation checkpoints at each risky step, and thorough failure-recovery guidance covering both first-bot and second-bot flows. Its only weaknesses are minor over-explanation in a few spots and a monolithic single-file layout, which is nonetheless a deliberate design choice for deterministic parser application.

DimensionReasoningScore

Conciseness

The body is dense with executable directives and avoids teaching general concepts, but a few passages over-explain — e.g., "Telegram calls them 'groups' and 'chats.'" (terminology Claude already knows) and rationale prose like "The picker link is navigation, not authorization". Minor trimmable material, so not a 5 and not a 3.

4 / 5

Actionability

Fully executable throughout: exact file lists in nc:copy fences, the exact import line, a pinned dependency (@chat-adapter/telegram@4.41.1), copy-paste commands (curl -sf https://api.telegram.org/bot{{bot_token}}/getMe | jq -er '.result.username'), token-validation regexes, and concrete ncl commands. Both common cases — first install and a second bot — are covered.

5 / 5

Workflow Clarity

A clear ordered sequence (Apply → Credentials → Restart → Pair → wire) with explicit validation checkpoints: "Build first: it guards the typed createChatSdkBridge(...) core call", the getMe token check that "fails here if the token is bad", duplicate-token refusal checks, restart-before-pairing rationale, and a troubleshooting section providing error-recovery feedback loops.

5 / 5

Progressive Disclosure

Well-organized single document with clear section headers and clearly signaled external pointers (/init-first-agent, the telegram-multi-instance skill on the channels branch); no bundle files exist, and the single-file layout is deliberately parser-applicable. Not a 5 because the ~300-line monolith inlines peripheral content (troubleshooting, channel info) that could live in reference files; not a 3 because structure is good and references are clearly signaled, not buried.

4 / 5

Total

18

/

20

Passed

Description

48%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 short, clear, and specific to the Telegram/Chat SDK niche, but it is minimal: a single generic action, no "Use when..." trigger guidance, and it omits the natural term "bot" that users would most likely say. It distinguishes itself from unrelated skills but not from closely related channel skills.

Suggestions

Add an explicit trigger clause, e.g.: "Use when the user wants to add Telegram as a messaging channel, create a Telegram bot, or pair their Telegram chat."

Include the natural trigger term "bot" (as in "Telegram bot") and common phrasings like "connect" or "set up", since the workflow centers on BotFather bot creation.

Enumerate 1-2 more concrete actions (e.g., "installs and registers the Telegram adapter, creates the bot, and pairs the chat") to raise specificity beyond the single generic verb "Add".

DimensionReasoningScore

Specificity

"Add Telegram channel integration via Chat SDK" names the domain concretely but offers only one minimal, generic action ("Add ... integration"), matching the "Processes PDF files" anchor. It is not a 3 because no second concrete action (e.g., installing the adapter, pairing a chat) is enumerated.

2 / 5

Completeness

The "what" is clear ("Add Telegram channel integration via Chat SDK") but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3. Not a 2 because the "what" is specific rather than vague.

3 / 5

Trigger Term Quality

"Telegram" is a natural, specific keyword, but the description omits the most natural terms a user would say for this bot-creation workflow — "bot", "Telegram bot", "connect", "set up". Some relevant keywords, missing common variations, so not a 4.

3 / 5

Distinctiveness Conflict Risk

"Telegram" combined with "Chat SDK" carves a clear niche with minimal conflict risk against unrelated skills. It is not a 5 because sibling channel-integration skills built on the same Chat SDK bridge could overlap, and no trigger phrasing disambiguates them.

4 / 5

Total

12

/

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: 1 missing

Warning

Total

15

/

16

Passed

Repository

nanocoai/nanoclaw

Path

.claude/skills/add-telegram/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.