CtrlK
BlogDocsLog inGet started
Tessl Logo

remote-from-slack

AI DevKit · Connect the current agent session to an available Slack 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-slack/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 an efficient, highly actionable workflow with clear sequencing and confirmation gates for the one destructive operation. The only gap is the absence of an explicit error-recovery feedback loop, which keeps workflow clarity at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is lean: a one-line purpose, a terse tool-preference note, an 8-step workflow of bare commands, and a short Boundaries list, with no padding or explanation of concepts Claude already knows; every token earns its place, matching the lean-and-efficient anchor.

5 / 5

Actionability

Each step ships an executable command ("ai-devkit status --json", "channel start <channel> --agent <agent-name> --daemon", "channel stop <channel>") with only expected substitutions, covering the common cases copy-paste ready, matching the fully-executable anchor.

5 / 5

Workflow Clarity

The 8-step sequence is clearly ordered with explicit stop conditions ("Stop if setup leaves manual actions", "Stop after giving that action") and a confirmation gate before the destructive "channel stop", but it lacks an explicit error-recovery feedback loop (e.g. what to do if start fails), so it sits at clear-sequence-most-checkpoints rather than full checklists/feedback loops.

4 / 5

Progressive Disclosure

The skill is a single under-50-line SKILL.md with no need for external references and is well-organized into Workflow and Boundaries sections, so the simple-skill exception allows a top score; no nested or buried references exist.

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 clearly distinct but omits any explicit "when to use" trigger guidance, which caps completeness and limits trigger-term coverage. It is solid but would benefit from a Use-when clause naming natural user phrasing.

Suggestions

Append a "Use when..." clause naming natural triggers, e.g. "Use when the user wants to control or chat with this session from Slack."

Add common synonyms such as "remote control", "chat from Slack", or "Slack bridge" to broaden trigger-term coverage.

Consider naming a second concrete action (e.g. "start, stop, and report a Slack bridge") to lift specificity above a single action.

DimensionReasoningScore

Specificity

"Connect the current agent session to an available Slack channel bridge" names the domain (Slack channel bridging) and one concrete action (connect), matching the anchor for 1-2 concrete actions without being comprehensive; it is above the single-generic-action level 2 because the action is specific rather than minimal.

3 / 5

Completeness

The description gives a clear "what" (connect an agent session to a Slack channel bridge) but includes no "Use when..." trigger clause, so per the boundary guidance a missing explicit trigger caps completeness at 3; it is not 2 because the "what" is clear rather than vague.

3 / 5

Trigger Term Quality

"Slack" and "channel" are relevant natural keywords a user might say, but the description lacks common variations or synonyms such as "chat from Slack", "control from Slack", or "remote", matching the anchor for some relevant keywords with missing synonyms; it does not reach 4 because coverage is thin.

3 / 5

Distinctiveness Conflict Risk

The Slack-channel-bridge niche for an agent session is mostly distinct with only minor overlap risk against other remote-control skills, matching the "mostly distinct" anchor; it falls short of 5 because the trigger phrases are not comprehensive enough to guarantee minimal conflict.

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.