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 extremely weak across all dimensions. It reads as a template placeholder rather than a functional skill description—it names the skill and its category but provides no concrete actions, no explicit trigger guidance, and only a duplicated trigger term. It would be nearly useless for Claude to differentiate this skill from others in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Slack bots using the Slack API, configures webhooks, sets up event subscriptions, builds interactive message handlers, and deploys bot applications.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to build a Slack bot, create a Slack integration, automate Slack messages, set up a Slack app, or work with the Slack API.'
Remove the duplicated trigger term and expand with varied natural language phrases users would actually say, such as 'Slack chatbot', 'Slack automation', 'Slack webhook', 'build a bot for Slack'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Slack Bot Creator') and category ('Business Automation') but lists no concrete actions like 'create webhooks', 'configure event subscriptions', 'set up message handlers', etc. | 1 / 3 |
Completeness | The 'what' is extremely vague (just a name, no actions described) and the 'when' is missing entirely—there is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the redundant 'slack bot creator, slack bot creator'. It misses natural user phrases like 'build a Slack bot', 'Slack integration', 'Slack app', 'chatbot for Slack', 'Slack API', or 'automate Slack messages'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Slack Bot' provides some domain specificity that distinguishes it from generic automation skills, but the lack of concrete actions and the broad 'Business Automation' label could cause overlap with other automation-related skills. | 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 is an empty placeholder with no substantive content. It contains no actionable instructions, no code examples, no specific Slack API guidance, and no workflow for actually creating a Slack bot. It reads as auto-generated boilerplate that repeats the skill name without teaching Claude anything useful.
Suggestions
Add concrete, executable code examples for creating a Slack bot (e.g., using Bolt for Python/JS, setting up event listeners, handling slash commands) with specific API endpoints and OAuth scope requirements.
Define a clear multi-step workflow: create Slack app → configure OAuth scopes → set up event subscriptions → implement bot logic → deploy and test, with validation at each step.
Remove all generic filler text ('Provides step-by-step guidance', 'Follows industry best practices') and replace with actual Slack-specific technical content such as manifest.yaml configuration, token types, and rate limit handling.
Add references to supporting files for advanced topics (e.g., INTERACTIVE_MESSAGES.md, DEPLOYMENT.md) to enable progressive disclosure of complex Slack bot features.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'slack bot creator' excessively, and provides zero domain-specific information. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is no concrete code, no commands, no specific API references, no configuration examples, and no executable guidance whatsoever. The skill describes rather than instructs, offering only vague platitudes like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | There is no workflow, no sequence of steps, no validation checkpoints, and no process described at all. Creating a Slack bot involves multiple concrete steps (app creation, OAuth scopes, event subscriptions, deployment) and none are mentioned. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to organize in the first place. | 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
3a2d27d
- 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.