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.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary compact skill body: every line is operational, the approval workflow has explicit checkpoints and recovery, and structure is clean with a single clearly-signaled external reference. It assumes Claude's competence and earns every token.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational throughout — exact env vars, scopes, rate limits, and tool params with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Guidance is fully executable: concrete env vars, required scopes, tool signatures with parameters, a 30s/10min polling cadence, an exact approval message format, and the approved/yes/go vs rejected/no/stop matching keywords.	5 / 5
Workflow Clarity	The dual-channel approvals workflow is a numbered sequence with explicit validation/polling checkpoints, a timeout, a first-response-wins rule, and a session-end checkpoint recovery loop — matching the anchor for clear sequence with feedback loops.	5 / 5
Progressive Disclosure	Under 50 lines, single-purpose, with well-organized sections and a single one-level-deep external pointer (.opencastle/stack/notifications-config.md); no bundle files exist, so well-organized sections suffice for full marks.	5 / 5
	Total	20 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-targeted description that clearly answers both what the skill does and when to use it, in third person, with concrete actions and natural trigger terms. Minor room for additional synonym/variation coverage keeps specificity and trigger_term_quality just below full marks.

Dimension	Reasoning	Score
Specificity	"post progress updates, request approvals, or read user responses" names several concrete actions in the Slack notification domain, falling just short of the comprehensive multi-action coverage of the 5 anchor.	4 / 5
Completeness	It explicitly states 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") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Phrases like "Slack channels and threads", "progress updates", "approvals", and "user responses" are natural things a user would say, with good but not exhaustive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (agent-to-human Slack notifications/approvals) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Path: src/orchestrator/plugins/slack/SKILL.md
Commit: fa0c341

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.