CtrlK
BlogDocsLog inGet started
Tessl Logo

slack-formatting

Format messages for Slack using mrkdwn syntax. Use when responding to Slack channels (folder starts with "slack_" or JID contains slack identifiers).

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Scale 1-3

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

This is a well-crafted, concise skill that efficiently communicates Slack mrkdwn formatting rules. It excels at providing concrete syntax examples, a clear anti-pattern section showing what NOT to use (critical for Claude which defaults to standard Markdown), and a practical example message. The quick rules summary at the end provides an excellent at-a-glance reference.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It's a reference-style skill that presents only what Claude needs to know — the syntax differences between standard Markdown and Slack mrkdwn. No unnecessary explanations of what Slack is or how messaging works.

3 / 3

Actionability

Provides concrete, copy-paste-ready syntax examples for every formatting element, a complete example message, and a clear 'What NOT to use' section with specific alternatives. The quick rules at the end serve as an actionable checklist.

3 / 3

Workflow Clarity

This is a single-task skill (formatting messages) with no multi-step destructive operations. The workflow is unambiguous: detect Slack context, then apply mrkdwn formatting rules. The detection step and formatting reference are clearly sequenced.

3 / 3

Progressive Disclosure

For a skill under 50 lines of conceptual content, the organization is excellent — clear sections (detection, reference, anti-patterns, example, quick rules) with logical progression. No need for external file references given the scope.

3 / 3

Total

12

/

12

Passed

Description

75%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 well-structured with clear 'what' and 'when' clauses, and occupies a distinct niche that minimizes conflict risk. However, it could benefit from listing more specific formatting actions (e.g., bold, links, code blocks, mentions) and including more natural user-facing trigger terms beyond the technical folder/JID identifiers.

Suggestions

Add specific formatting actions like 'bold, italic, code blocks, links, mentions, lists' to improve specificity.

Include more natural trigger terms users might say, such as 'Slack message', 'Slack formatting', 'Slack markdown', or 'Slack bot response'.

DimensionReasoningScore

Specificity

Names the domain (Slack messaging) and a specific action (format messages using mrkdwn syntax), but doesn't list multiple concrete actions like formatting bold text, creating lists, handling code blocks, links, mentions, etc.

2 / 3

Completeness

Clearly answers both 'what' (format messages for Slack using mrkdwn syntax) and 'when' (responding to Slack channels, folder starts with 'slack_' or JID contains slack identifiers) with explicit trigger conditions.

3 / 3

Trigger Term Quality

Includes 'Slack', 'mrkdwn', and 'slack_' folder prefix as trigger terms, but misses common user-facing terms like 'Slack message formatting', 'bold', 'italic', 'code blocks', 'Slack markdown', or 'Slack bot responses'. The JID reference is technical jargon.

2 / 3

Distinctiveness Conflict Risk

Highly distinctive — Slack mrkdwn formatting is a clear niche with specific triggers (slack_ folder prefix, JID identifiers) that are unlikely to conflict with other skills like general markdown formatting or other messaging platforms.

3 / 3

Total

10

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
jbaruch/nanoclaw-telegram
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.