CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

slack

Load to bind an overseer's mailbox to a private Slack channel, run or check the relay, or post an alert or a file to Slack.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/slack/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

A lean, information-dense body with executable commands and detailed behavioral rules that largely assumes Claude's competence. Its weaknesses are the absence of an explicit getting-started workflow sequence and references to files that are not present in the bundle, embedded in prose rather than clearly signposted.

Suggestions

Add a short numbered quick-start sequence (setup → install → listen → check with --status) so the workflow order is explicit rather than implied by the command listing.

Collect the file references (journal.md schemas, secret-value.ere, communication-modes.md, messages.md) into a clearly labeled references section, and ensure the referenced files ship with the skill bundle.

Include one or two worked example invocations with realistic values (e.g. a post command with --channel and --text) to cover the most common cases.

DimensionReasoningScore

Conciseness

The body is dense and operational — no explanations of concepts Claude already knows, and nearly every line carries project-specific facts ("Every outbound text and file passes the secret-value pattern..."). Not 5 because the kendex "Project Instructions" marker block and a few restated rules could be trimmed; not 3 because there is no unnecessary explanation or padding of substance.

4 / 5

Actionability

Provides a full copy-paste-ready command block with every verb and flag ("slack setup [--root ROOT] [--name NAME | --take CHANNEL_ID]"), concrete output line formats ("slack: ts=TS edited=TS|- bot=ID text=TEXT"), and delegates exhaustive detail to "slack --help". Not 5 because there are no worked example invocations with real values for the common cases.

4 / 5

Workflow Clarity

Validation and checkpoint content exists — secret-pattern refusals, file checks before upload, keyed failure causes with retry on the next poll, and the "listen --status" doctor row — but it is scattered across rules rather than sequenced, and the setup→install→listen workflow is only implied by the command listing order. Not 4 because there is no explicit step sequence for getting a relay running; not 2 because error handling and status checking are described in detail.

3 / 5

Progressive Disclosure

Sections (Rules, Message standard, Doctor row) are well-organized and detail is delegated one level deep to "slack --help", but most referenced paths ("schemas/journal.md", "references/secret-value.ere", "../orch/references/communication-modes.md", "../communication/references/messages.md", "kendex.settings.toml.example") do not exist in the provided bundle (only scripts/slack and scripts/lib are present) and are buried mid-prose rather than clearly signaled. Not 4 because the dangling references and in-prose embedding leave navigation uncertain; not 2 because the structure itself is sound and the top-level overview is appropriate.

3 / 5

Total

14

/

20

Passed

Description

66%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.

A concise, third-person description with concrete actions and a distinct Slack-relay niche, but it lacks any explicit "when to use this" trigger guidance, which caps its completeness. Trigger-term coverage is good for the domain though missing common synonyms like "send" or "message".

Suggestions

Add an explicit trigger clause, e.g. "Use when setting up or checking the Slack relay for a checkout, or when asked to post an alert, message, or file to Slack."

Include natural synonyms users would say — "send a message to Slack", "Slack notification" — to broaden trigger-term coverage.

Mention the read capability ("read messages from a Slack channel") so the description covers all supported verbs.

DimensionReasoningScore

Specificity

Names several concrete actions — "bind an overseer's mailbox to a private Slack channel", "run or check the relay", "post an alert or a file to Slack" — but omits verbs the body supports (read, compact, install), leaving minor coverage gaps. Not 5 because coverage is not comprehensive; not 3 because it lists more than 1-2 actions.

4 / 5

Completeness

The "what" is clear (bind a mailbox to a Slack channel, run/check the relay, post alerts or files), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is entirely absent rather than merely implicit-but-stated.

3 / 5

Trigger Term Quality

Contains natural phrases users would say — "post an alert or a file to Slack", "private Slack channel", "run or check the relay" — giving good keyword coverage for the Slack domain. Not 5 because common synonyms like "send", "message", or "notify" are missing; not 3 because coverage goes beyond a single generic keyword.

4 / 5

Distinctiveness Conflict Risk

The overseer-mailbox-to-Slack-channel relay is a clear, narrowly-scoped niche with distinct triggers, giving minimal conflict risk with unrelated skills. Not 5 because "run or check the relay" is a generic phrasing that could brush against other relay or messaging skills; not 3 because the domain is far more specific than overlapping-generic.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 3 missing, 3 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

vanillagreencom/kendex

Path

.agents/skills/slack/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.