Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill slack-bot-creatorSlack Bot Creator - Auto-activating skill for Business Automation. Triggers on: slack bot creator, slack bot creator Part of the Business Automation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill over others. The redundant trigger terms and generic category label add no value.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Slack bots using the Slack API, configures webhooks, sets up slash commands, and implements message handlers.'
Include a 'Use when...' clause with natural trigger terms like 'build a slack bot', 'slack integration', 'slack app', 'automate slack', 'slack webhook', or 'chatbot for slack'.
Remove the redundant duplicate trigger term and expand with varied phrasings users might naturally use when requesting this functionality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Slack Bot Creator' without describing any concrete actions. It doesn't explain what the skill actually does - no mention of creating bots, configuring webhooks, writing code, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'slack bot creator' repeated twice. Missing natural variations users might say like 'build slack bot', 'slack integration', 'slack app', 'chatbot for slack', or 'slack automation'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Slack Bot Creator' is somewhat specific to Slack, the vague 'Business Automation' category and lack of detail could cause overlap with other automation or integration skills. The Slack focus provides some distinctiveness. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is entirely generic boilerplate with no actual guidance on creating Slack bots. It lacks any concrete code, API references, authentication steps, or workflow for bot development. The content could apply to virtually any topic by swapping the phrase 'slack bot creator' with something else.
Suggestions
Add executable code examples showing Slack API authentication, event subscription setup, and basic message handling using Bolt SDK or similar
Include a clear workflow: 1) Create Slack app, 2) Configure OAuth scopes, 3) Set up event subscriptions, 4) Deploy bot endpoint, 5) Test with validation steps
Reference specific Slack API documentation and include links to manifest.yaml examples or configuration templates
Remove all generic capability descriptions and replace with specific Slack bot patterns (slash commands, interactive messages, scheduled messages)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Slack bot creation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, API references, or specific implementation steps are provided. The content describes what the skill does abstractly rather than instructing how to actually create a Slack bot. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints for creating a Slack bot. The 'Capabilities' section lists vague promises without any actual process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed documentation, API guides, or example files. There's no structure pointing to deeper resources. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
Table of Contents
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.