slack-bot-builder

The Bolt framework is Slack's recommended approach for building apps. It handles authentication, event routing, request verification, and HTTP request processing so you can focus on app logic.

Quality

38%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/slack-bot-builder/SKILL.md

Quality

Content

32%Scale 1-5

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

This skill suffers from truncated code examples that waste token budget without delivering complete, executable guidance. The Sharp Edges table is entirely broken with placeholder text, removing what could be the most valuable section. The content lacks workflow sequencing, validation steps, and progressive disclosure structure, reading more like incomplete documentation fragments than an actionable skill.

Suggestions

Complete all truncated code examples or trim them to shorter, fully executable snippets that demonstrate the core pattern without being cut off.

Fix the Sharp Edges table by replacing placeholder 'Issue' text with actual issues and providing real solution content instead of empty section headers.

Add a clear workflow section that sequences the steps for building a Slack bot (e.g., 1. Create app in Slack dashboard, 2. Configure tokens, 3. Set up Bolt, 4. Add handlers, 5. Test with Socket Mode, 6. Deploy) with validation checkpoints.

Split the three patterns into separate referenced files and keep SKILL.md as a concise overview with links, removing verbose introductory text that explains concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	The skill is noticeably verbose. It explains what Bolt is and its benefits (Claude already knows this), lists 'when to use' bullets that are obvious, includes a statistic about OAuth abandonment rates, and repeats framework descriptions. The code examples are long but mostly useful, though they are truncated which wastes the tokens spent on them.	2 / 5
Actionability	The code examples are concrete and mostly executable, but every single one is truncated mid-code, making none of them copy-paste ready. The Sharp Edges table is broken—it shows 'Issue' placeholders instead of actual issues, and the solutions are just section headers with no content. This significantly undermines actionability.	3 / 5
Workflow Clarity	There is no clear workflow or sequenced process for building a Slack bot. The content presents disconnected patterns (Bolt setup, Block Kit, OAuth) without explaining how they fit together or what order to follow. There are no validation checkpoints, no error recovery steps, and no guidance on testing or verifying the bot works.	2 / 5
Progressive Disclosure	The content is a monolithic wall of long code examples with no references to external files and no bundle structure. The three patterns plus OAuth could be split into separate files with a concise overview in SKILL.md. The Block Kit Builder link is the only external reference. Content organization is flat with no navigation aids.	2 / 5
	Total	9 / 20 Passed

Description

45%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 reads more like a summary of the Bolt framework's features than a skill description that helps Claude decide when to use it. It lacks a 'Use when...' clause entirely, which is critical for skill selection. The Slack/Bolt specificity provides decent distinctiveness, but the description would benefit from concrete skill actions and explicit trigger guidance.

Suggestions

Add a 'Use when...' clause with trigger terms like 'build a Slack app', 'Slack bot', 'Slack integration', 'Bolt framework', or 'slash commands'.

Reframe capabilities as concrete actions the skill performs, e.g., 'Scaffolds Slack Bolt apps, configures event listeners, sets up slash commands, and implements interactive message handlers.'

Include natural synonyms and related terms users might say, such as 'Slack bot', 'Slack workspace', 'interactive messages', 'block kit', or specific language runtimes like 'Node.js' or 'Python'.

Dimension	Reasoning	Score
Specificity	Names the domain (Slack Bolt framework) and lists several capabilities (authentication, event routing, request verification, HTTP request processing), but these describe what the framework does rather than what the skill teaches the user to do. The actions are more about the framework's features than concrete skill actions like 'scaffold a Bolt app' or 'configure event listeners'.	3 / 5
Completeness	Provides a 'what' (describes the Bolt framework's capabilities) but has no 'when' clause at all. There is no 'Use when...' guidance or equivalent trigger phrasing to help Claude know when to select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 3, and the 'what' is more about the framework than the skill's purpose, pushing it to 2.	2 / 5
Trigger Term Quality	Includes relevant keywords like 'Bolt', 'Slack', 'apps', 'authentication', 'event routing', but misses natural user phrases like 'Slack bot', 'Slack integration', 'build a Slack app', 'slash commands', 'interactive messages', or language-specific terms like 'Node.js' or 'Python'.	3 / 5
Distinctiveness Conflict Risk	The mention of 'Bolt framework' and 'Slack' provides a fairly distinct niche. It could potentially overlap with a general Slack API skill or a broader app-building skill, but the specific framework name reduces conflict risk significantly.	4 / 5
	Total	12 / 20 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/slack-bot-builder/SKILL.md
Commit: 57c135b

Reviewed: 19 hours ago

Table of Contents

Discovery Implementation Validation

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.