slack-notifications
Slack MCP integration for agent-to-human notifications and bi-directional communication. Use when agents need to post progress updates, request approvals, or read user responses via Slack channels and threads.
77
96%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 a well-crafted skill description that clearly identifies the tool (Slack MCP), the domain (agent-to-human communication), and specific use cases (progress updates, approvals, reading responses). It includes an explicit 'Use when' clause with natural trigger terms and is distinctive enough to avoid conflicts with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'post progress updates', 'request approvals', 'read user responses', and specifies the medium 'via Slack channels and threads'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Slack MCP integration for agent-to-human notifications and bi-directional communication') and when ('Use when agents need to post progress updates, request approvals, or read user responses via Slack channels and threads'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Slack', 'notifications', 'approvals', 'progress updates', 'channels', 'threads'. Covers both the platform name and common use-case terms like 'bi-directional communication'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets Slack MCP integration for agent-to-human communication patterns. The combination of 'Slack', 'MCP', 'agent-to-human', and specific actions like 'request approvals' creates a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%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, well-crafted skill that efficiently communicates Slack MCP integration patterns with concrete, executable examples. The bi-directional communication workflow is particularly well-designed with clear sequencing, error handling, and session recovery. The only minor weakness is that referenced files (REFERENCE.md, notifications-config.md) cannot be verified since no bundle was provided.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what Slack is or how MCP works. Token-efficient with inline code examples that serve double duty as documentation and executable guidance. | 3 / 3 |
Actionability | Provides concrete, executable MCP invocation examples with real function calls, specific message formats, polling logic with regex patterns, and clear parameters. The approval polling code is copy-paste ready with interval/timeout guidance. | 3 / 3 |
Workflow Clarity | The bi-directional communication flow is clearly sequenced (steps 1-5) with explicit handling for each outcome path: chat response wins, Slack polling with timeout, and session-end checkpoint recovery. Error handling is present (throw on failed post) and the dual-channel pattern includes a clear feedback loop. | 3 / 3 |
Progressive Disclosure | References to REFERENCE.md for OAuth scopes and security guidelines are well-signaled, and project config is pointed to a separate file. However, no bundle files were provided to verify REFERENCE.md exists, and the notification-config reference points to a path that may not exist. The skill itself is well-structured but the references can't be validated. | 2 / 3 |
Total | 11 / 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.
- Repository
- monkilabs/opencastle
- Commit
7a69a05
- 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.