CtrlK
BlogDocsLog inGet started
Tessl Logo

remote-from-telegram

AI DevKit · Connect the current agent session to an available Telegram channel bridge.

62

Quality

73%

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 ./skills/remote-from-telegram/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.

The body is a concise, fully executable CLI workflow with strong sequencing, conditional stops, and a confirmation gate before the one destructive action (stopping a running bridge). The only gap is a verification step after starting the bridge to confirm it is actually running.

DimensionReasoningScore

Conciseness

The body is lean throughout: a one-line trigger, a brief justified operational note about running outside sandboxes, and terse numbered steps with inline commands, with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

It provides fully executable ai-devkit commands (status --json, channel list, agent list --json, channel connect, channel start --daemon, channel stop) with the necessary <channel> and <agent-name> placeholders, covering the common cases copy-paste ready, matching the top anchor.

5 / 5

Workflow Clarity

The eight-step sequence is clear with explicit checkpoints (readiness gate in step 1, stop conditions in steps 4 and 6, confirmation before stopping a running bridge), but there is no post-start verification that the bridge actually connected, leaving a minor validation gap that keeps it below the explicit-feedback-loop level-5 anchor.

4 / 5

Progressive Disclosure

The content is self-contained with well-organized Workflow and Boundaries sections, no bundle files, and no nested references; for a short single-purpose skill with no need for external references this matches the top anchor.

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 is specific and narrowly scoped to a Telegram channel bridge, but it omits an explicit 'when to use' trigger clause, which caps completeness. Adding a 'Use when…' clause naming natural triggers like controlling or chatting with the session from Telegram would raise the score.

Suggestions

Add an explicit 'Use when…' clause, e.g. 'Use when the user wants to control or chat with the current session from Telegram,' to satisfy the completeness and trigger-term dimensions.

Surface natural trigger phrases such as 'control from Telegram', 'chat from Telegram', or 'remote control' alongside the technical 'channel bridge' terminology.

Optionally name a second concrete action (e.g. reporting or stopping the bridge) to lift specificity above the single-action anchor.

DimensionReasoningScore

Specificity

The phrase 'Connect the current agent session to an available Telegram channel bridge' names the domain and one concrete action, but offers no breadth of capabilities, matching the '1-2 concrete actions' anchor rather than the 'several specific actions' anchor above.

3 / 5

Completeness

It clearly states what the skill does (connect the session to a Telegram bridge) but provides no 'Use when…' trigger clause; per the rubric guideline a missing trigger clause caps completeness at 3, so it does not reach the level-4 'both what and when' anchor.

3 / 5

Trigger Term Quality

'Telegram' is a natural keyword a user would say, but the surrounding terms ('agent session', 'channel bridge') are technical and common variations like 'control from Telegram', 'chat from Telegram', or 'remote' are absent, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The Telegram-specific, AI-DevKit-scoped niche is clearly distinguishable with a distinct trigger, but there is minor overlap risk with other channel-bridge skills (Slack, Discord), placing it at 'mostly distinct; minor overlap' rather than the minimal-conflict level-5 anchor.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
codeaholicguy/ai-devkit
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.