CtrlK
BlogDocsLog inGet started
Tessl Logo

slack-summary

Distill a Slack channel or thread into actionable summary

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./surfsense_backend/app/agents/chat/multi_agent_chat/main_agent/skills/builtin/slack-summary/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 a lean, well-organized instruction skill that gives concrete input-gathering, output-shape, and anti-fabrication guidance without padding. Its main gap is the absence of a worked output example and an explicit citation-verification step, which keep actionability and workflow clarity at 4 rather than 5.

Suggestions

Add one short worked example of the three-section output so the expected format is unambiguous and copy-paste-ready.

Add an explicit verification step requiring that every cited decision/question be checked against a real retrieved message before emitting the summary, closing the workflow-clarity feedback-loop gap.

Briefly note the search mechanism or source of truth (e.g., Slack MCP / history export) so Claude knows where to pull messages from.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it never explains what Slack is, gives only operational guidance ('Confirm before searching', a three-section output shape, a tight 'What not to do' list), and every line earns its place, matching the anchor 5 'lean and efficient' example rather than the slightly-padded anchor 4.

5 / 5

Actionability

It gives concrete, specific guidance — exact input confirmations (channel(s)/thread(s), time window with a 7-day default), a precise three-section output structure with citation and @mention rules, and explicit edge-case handling — but lacks a concrete worked example of the output and does not specify the search mechanism, so it is mostly-executable with minor gaps per anchor 4 rather than fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

There is a clear sequence (confirm inputs -> search -> produce the three sections) with verification checkpoints ('Don't guess if ambiguous', 'If the channel was empty... say so', 'don't fabricate filler', 'don't invent assignees'), but there is no explicit citation-verification feedback loop, fitting anchor 4's 'clear sequence with most checkpoints present; minor validation gaps' rather than the full feedback-loop anchor 5; the destructive/batch cap does not apply since summarization is read-only.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files, and is organized into well-signaled sections (When to use, Required inputs, Output shape, What not to do), so per the simple-skills exception it scores 5 with just well-organized sections and no need for external references.

5 / 5

Total

18

/

20

Passed

Description

53%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 is concise and names a clear, distinct niche (Slack channel/thread summarization) with a concrete output, but it lacks an explicit 'Use when...' trigger clause and uses the less-natural verb 'Distill' instead of the terms users actually say. Adding concrete trigger phrases would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases, e.g. 'Use when the user asks to summarize or catch up on a Slack channel or thread.'

Replace or supplement 'Distill' with the words users actually say ('summarize', 'catch me up on', 'what happened in') to improve trigger-term quality.

Name a second concrete capability (e.g., 'highlights key decisions and action items') to move specificity from a single action toward comprehensive coverage.

DimensionReasoningScore

Specificity

The phrase 'Distill a Slack channel or thread into actionable summary' names the domain (Slack channel/thread) and one concrete action with a concrete output (distill into an actionable summary), but coverage is limited to a single action and is not comprehensive, matching anchor 3 rather than the broader multi-action anchor 4 or the minimal/generic anchor 2.

3 / 5

Completeness

It gives a clear 'what' (distill Slack into an actionable summary) but has no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 3 with the 'when' only weakly implied.

3 / 5

Trigger Term Quality

It includes relevant natural nouns a user would say ('Slack', 'channel', 'thread', 'summary') but uses the jargon verb 'Distill' and omits the common phrasings users actually say ('summarize', 'catch me up', 'what happened'), so it has some relevant keywords but misses common variations, fitting anchor 3 rather than the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

The Slack/channel/thread niche is mostly distinct with a low conflict risk against other skills, though it could minorly overlap with a generic summarization skill, fitting anchor 4 rather than the fully-distinct anchor 5 or the broader-overlap anchor 3.

4 / 5

Total

13

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MODSetter/SurfSense
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.