CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

45

Quality

47%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/slack-bot-builder/SKILL.md

The canonical home for this skill is slack-bot-builder in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

36%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 contains useful, specific Bolt patterns but is undermined by truncated code blocks, a malformed Sharp Edges table, and no validation workflow or external references. Completing the code examples and fixing the table would most improve the skill.

Suggestions

Complete the truncated code blocks (Bolt App, Block Kit, OAuth) so examples are copy-paste executable, or move full examples into reference files and link to them.

Rebuild the Sharp Edges table so each row's Solution cell contains concrete guidance instead of bare '## ...' header text.

Add explicit validation/verification checkpoints for the security-sensitive OAuth/token-storage steps (e.g., verify token encryption, test installation round-trip).

DimensionReasoningScore

Conciseness

Noticeably verbose: large inlined code blocks (full modal JSON, full incident-notification blocks) are truncated mid-way, the redundant '**When to use**' arrays repeat trigger guidance, and a placeholder 'When to Use' section adds no value.

2 / 5

Actionability

Provides real Python code rather than pseudocode, but every example is cut off mid-block (truncated with ```), so the guidance is concrete yet incomplete and not copy-paste ready.

3 / 5

Workflow Clarity

There is no sequenced multi-step workflow or validation checkpoints; the Sharp Edges table is malformed (solutions are bare '## ...' headers with no content), and token/OAuth handling lacks verification steps.

2 / 5

Progressive Disclosure

Section headers (Bolt App Foundation, Block Kit UI, OAuth, Sharp Edges) give some structure, but long code that belongs in reference files is inlined and truncated, with no external references or bundle files to offload it.

3 / 5

Total

10

/

20

Passed

Description

58%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 clearly conveys what the framework handles and is distinctively Slack-scoped, but it lacks an explicit 'Use when...' trigger clause and omits common natural terms like 'Slack bot'. Adding concrete trigger phrases would raise both completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when building Slack bots or Slack apps, migrating from legacy Slack APIs, or working with the Bolt framework.' clause.

Add natural user phrases such as 'Slack bot', 'slash command', and 'Block Kit' to broaden trigger coverage.

Reframe actions as the skill's capabilities (e.g., 'Builds Slack bots using Bolt...') rather than only what the framework does.

DimensionReasoningScore

Specificity

Lists several concrete actions ('handles authentication, event routing, request verification, and HTTP request processing') but they describe the framework rather than the skill's own capabilities, leaving minor coverage gaps.

4 / 5

Completeness

Has a clear 'what' (the four handled concerns) but no explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes 'Slack', 'Bolt framework', and 'building apps', but misses the natural phrases users say like 'Slack bot', 'slash command', 'Block Kit', or 'OAuth'.

3 / 5

Distinctiveness Conflict Risk

The Slack/Bolt combination is a clear, mostly-distinct niche with minimal overlap risk, though 'building apps' is generic enough to keep it just below the most-distinct anchor.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.