Name: slack
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

slack

Slack integration. Manage communication data, records, and workflows. Use when the user wants to interact with Slack data.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/slack/SKILL.md

Quality

Content

57%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.

The body is highly actionable with copy-paste Membrane commands and a clear connection/polling workflow, but it over-explains Slack basics, lacks validation guidance for destructive actions, and inlines a large actions table that would suit a separate reference file.

Suggestions

Drop the "Slack is a messaging app..." introductory paragraph and other explanatory prose Claude already knows.

Add an explicit validation/confirmation checkpoint before destructive actions like delete-message and delete-file.

Move the Popular-actions table into a referenced file (e.g. ACTIONS.md) and link to it from a short overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but opens by explaining what Slack is ("Slack is a messaging app for businesses...") and includes prose like the URL-normalization aside that Claude does not need, so it could be tightened.	3 / 5
Actionability	It provides many concrete, executable CLI commands and a JSON-input example, but the Popular-actions table lists a "Key" without clarifying how it maps to the `membrane action run <actionId>` argument, a minor gap keeping it below 5.	4 / 5
Workflow Clarity	The connect-and-poll sequence has a clear feedback loop, but destructive actions exposed in the table (delete-message, delete-file) have no validation or confirmation step, which caps workflow clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	The file is well-sectioned, but the 20-row Popular-actions table is bulk API reference content inlined in SKILL.md rather than split into a referenced file, and no one-level-deep references are signaled.	3 / 5
	Total	13 / 20 Passed

Description

66%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.

The description pairs an explicit use-when trigger with a Slack-specific niche, but its capability wording stays abstract ("communication data, records, and workflows") instead of naming concrete Slack actions. It is clearly Slack-distinct yet light on natural trigger variations and specific verbs.

Suggestions

Replace generic verbs with concrete Slack actions, e.g. "Send and search messages, list channels and users, manage files and reminders."

Add natural trigger terms users actually say, such as "messages", "channels", "DMs", or "post to Slack".

Tighten the when-clause to mention specific intents like "posting messages, searching channels, or managing Slack files".

Dimension	Reasoning	Score
Specificity	"Manage communication data, records, and workflows" names the Slack domain and a couple of actions, but they are generic abstractions rather than concrete operations like posting or searching messages, so it is not comprehensive enough for a 4.	3 / 5
Completeness	It states both a what ("Manage communication data, records, and workflows") and an explicit when ("Use when the user wants to interact with Slack data"), but the what is somewhat generic and the when could be more specific, placing it at 4 rather than 5.	4 / 5
Trigger Term Quality	The dominant natural term "Slack" appears ("Slack integration", "interact with Slack data"), but common variations users actually say — messages, channels, DMs — are missing, matching the anchor with relevant keywords but absent synonyms.	3 / 5
Distinctiveness Conflict Risk	"Slack" is a named product giving the skill a clear niche with a distinct trigger and minimal overlap risk with other skills, matching the clear-niche anchor.	5 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/slack/SKILL.md
Commit: f484c82

Reviewed: 4 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.