catalan-adobe/slack-cdp
Control Slack via CDP or headless API tokens. Navigate channels, read/send messages, search conversations, check unreads, and manage status. Two modes: CDP (Slack desktop with --remote-debugging-port) for full UI control, or headless (xoxp/xoxb token) for data operations without Slack running. Triggers on: slack, read slack, search slack, slack unreads, send slack message, slack status, navigate slack, check slack, slack messages, go to channel, slack DM.
91
91%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
Quality
Discovery
100%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 is an excellent skill description that covers all key dimensions thoroughly. It provides specific concrete actions, two clearly differentiated operational modes, and an explicit comprehensive list of trigger terms. The description is concise yet information-dense, making it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: navigate channels, read/send messages, search conversations, check unreads, manage status. Also describes two distinct operational modes (CDP and headless) with clear details about each. | 3 / 3 |
Completeness | Clearly answers both 'what' (control Slack via CDP or headless API tokens with specific actions listed) and 'when' (explicit 'Triggers on:' clause with comprehensive trigger terms). Both dimensions are thoroughly covered. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms explicitly listed: 'slack', 'read slack', 'search slack', 'slack unreads', 'send slack message', 'slack status', 'navigate slack', 'check slack', 'slack messages', 'go to channel', 'slack DM'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around Slack specifically. The two-mode architecture (CDP vs headless) and Slack-specific trigger terms make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent workflow clarity including verification steps, decision trees, and error recovery. The main weakness is length — at ~180 lines, some sections (particularly token setup and headless API examples) could be extracted to referenced files to improve conciseness and progressive disclosure. The decision tree and chaining patterns are particularly well done.
Suggestions
Extract the 'Obtaining tokens' section into a separate TOKENS.md file and reference it from the main skill, as it's a setup task rather than operational guidance.
Consider moving the headless API curl examples to a separate HEADLESS.md reference file, keeping just the decision criteria (headless vs CDP) in the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining concepts Claude already knows, but some sections could be tightened — the token obtaining instructions are quite detailed (step-by-step OAuth flow Claude likely knows), and the headless vs CDP decision section partially repeats information from the earlier decision tree. | 2 / 3 |
Actionability | Excellent actionability throughout — every command is fully executable with concrete bash examples, the script location logic is copy-paste ready, curl commands for headless mode are complete with proper headers and parameters, and chaining patterns show real multi-step workflows. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints — the 'after navigate, always verify with where' pattern is a proper feedback loop, the decision tree clearly routes to the right tool, chaining patterns show ordered steps, and the error recovery table provides clear fix actions for each failure mode. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and logical organization, but it's a fairly long monolithic document. The headless API calls, token obtaining instructions, and error recovery table could reasonably be split into referenced files to keep the main skill leaner. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents