slack-notification-triage

Triage recent Slack activity into a priority queue or task list for the user.

Quality

68%

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 ./plugins/slack/skills/slack-notification-triage/SKILL.md

Quality

Content

87%Weight 40%Scale 1-3

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 and concise, with a well-sequenced workflow and clean single-file organization; the main gap is the absence of an explicit validation/coverage checkpoint in the batch paging steps.

Suggestions

Add an explicit coverage-validation step after the paging/search substeps, e.g. 'Before prioritizing, confirm you have a reasonable set of unique conversations; if coverage looks thin for a scope, page deeper or retry the next search type.'

Tighten the minor redundancy between step 10 ('Read the full Formatting Rules section') and step 11 by merging them into a single checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is lean and tool-call dense with no concept explanations Claude already knows (no 'what Slack is'), so every section earns its place; minor restating of purpose in the intro and steps 10-11 is negligible, keeping it at the 'lean and efficient' anchor.	3 / 3
Actionability	It gives concrete, parameterized commands with exact arguments (slack_read_channel limit 100, slack_search_public_and_private with from:<@USER_ID> / channel_types="im" / query strings) plus a copy-paste output template, matching the 'fully executable commands; specific examples' anchor.	3 / 3
Workflow Clarity	The 12-step sequence is clearly ordered (including an explicit 'search in this order' sublist), but for a batch paging/searching operation there is no explicit validation or coverage checkpoint, so per the rubric's batch-operation guidance workflow clarity is capped at 2 rather than 3.	2 / 3
Progressive Disclosure	The content is well-organized into Start Here / Workflow / Formatting Rules, self-contained with no nested or multi-level references; the only external link is a clearly signaled one-level sibling skill (../slack-outgoing-message/SKILL.md), so it meets the 'clear overview, well-organized' anchor.	3 / 3
	Total	11 / 12 Passed

Description

50%Weight 40%Scale 1-3

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 is concise and names a concrete capability, but it lacks an explicit 'Use when' trigger clause and natural trigger-term coverage, leaving what is essentially an even 2 across all dimensions.

Suggestions

Add an explicit 'Use when...' clause listing natural user phrasings, e.g. 'Use when the user asks to triage Slack, catch up on Slack messages, or find what needs a reply, mention, or follow-up.'

Expand concrete actions to earn specificity 3, e.g. 'Surfaces messages needing a reply, flags blockers and approval requests, and builds a priority task list.'

Include common trigger variations ('messages', 'mentions', 'unread', 'notifications') to improve trigger-term quality and distinctiveness from other Slack skills.

Dimension	Reasoning	Score
Specificity	The description names a concrete domain ('recent Slack activity') and a concrete action/output ('Triage ... into a priority queue or task list'), matching the 'names domain and some actions' anchor; it does not list multiple distinct actions like the score-3 example, so it stays at 2.	2 / 3
Completeness	It clearly states what the skill does but provides no 'Use when...' or equivalent trigger clause, so 'when' is only implied; the rubric explicitly caps completeness at 2 when such a clause is missing.	2 / 3
Trigger Term Quality	'Slack activity' is a natural keyword a user might say, but the description omits common variations users would actually use ('messages', 'mentions', 'unread', 'notifications', 'what needs a reply'), fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The Slack-triage niche is somewhat specific, but with no explicit when/trigger guidance it could overlap with sibling Slack skills (e.g. slack-outgoing-message) and general Slack reading skills, matching the 'somewhat specific but could still overlap' anchor rather than the clear-niche score 3.	2 / 3
	Total	8 / 12 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: openai/plugins
Path: plugins/slack/skills/slack-notification-triage/SKILL.md
Commit: 11c74d6

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