slack-bot-creator
Slack Bot Creator - Auto-activating skill for Business Automation. Triggers on: slack bot creator, slack bot creator Part of the Business Automation skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/slack-bot-creator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a title repeated with boilerplate category metadata. It provides no concrete actions, no meaningful trigger terms beyond the skill name, and no guidance on when Claude should select it. It would be nearly indistinguishable from any other Slack-related skill in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Slack bots using Bolt framework, configures event subscriptions, sets up slash commands, and implements message handlers.'
Add an explicit 'Use when...' clause with natural trigger terms like 'build a slack bot', 'slack app', 'slack integration', 'slack API', 'chatbot for slack', 'slash command'.
Remove the duplicated trigger term and replace with diverse, natural language variations users would actually type when requesting this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Slack Bot Creator' and 'Business Automation' without listing any concrete actions like creating webhooks, setting up event handlers, configuring OAuth, or writing bot logic. It is extremely vague about what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no 'when should Claude use it' clause. The 'Triggers on' line is just a repeated keyword, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'slack bot creator' repeated twice. It misses natural variations users would say like 'build a slack bot', 'slack integration', 'slack app', 'chatbot for slack', 'slack API', or 'slack automation'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Slack Bot' provides some specificity that distinguishes it from generic automation skills, but 'Business Automation' is very broad and could overlap with many other skills. Without concrete actions, it's unclear how it differs from a general Slack integration skill. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a placeholder template with no actual instructional value. It contains no concrete guidance, code examples, API references, or workflow steps for creating a Slack bot. Every section merely restates that the skill is about 'slack bot creator' without providing any actionable information.
Suggestions
Add concrete, executable code examples showing how to set up a Slack bot using the Slack Bolt SDK or Slack API, including OAuth configuration, event subscriptions, and a basic message handler.
Define a clear multi-step workflow: 1) Create Slack App in API dashboard, 2) Configure OAuth scopes, 3) Set up event subscriptions, 4) Implement bot logic, 5) Deploy and verify — with validation at each step.
Remove all the meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) that describe the skill abstractly and replace them with actual technical instructions.
Add references to Slack API documentation and link to separate files for advanced topics like interactive components, slash commands, or deployment configurations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance, code, or specific instructions for creating a Slack bot. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code, no commands, no API references, no specific steps for creating a Slack bot. The content only describes what the skill claims to do rather than actually instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. Creating a Slack bot is inherently a multi-step process (app creation, OAuth setup, event subscriptions, deployment) and none of this is addressed. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to external files, and no structured navigation to deeper content. There is nothing to progressively disclose because there is no substantive content. | 1 / 3 |
Total | 4 / 12 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3e83543
- 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.