CtrlK
BlogDocsLog inGet started
Tessl Logo

slack-summary

Distill a Slack channel or thread into actionable summary

62

Quality

73%

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

92%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 an exemplar of lean, high-signal instruction: it defines when to engage, what to confirm up front, the exact output shape, and hard negative constraints, all without padding. The only gap is the absence of a worked example of the output format, which is what keeps actionability at 4 rather than 5.

Suggestions

Add a one-line worked example for one output section (e.g. a sample 'Action items' line showing the @mention / owes-what / by-when format) to make the output shape fully copy-paste ready.

Optionally name how messages are retrieved (e.g. which Slack tool/export or search command to use), or state that the retrieval method depends on the available Slack integration, so the first execution step is not left implicit.

DimensionReasoningScore

Conciseness

Every line is instructional ("Default to the last 7 days when not specified, but say so", "Don't invent assignees") with no padding and no explanation of concepts Claude already knows. This matches the anchor for lean and efficient content where every token earns its place.

5 / 5

Actionability

The guidance is concrete and specific — named output sections, citation requirements, @mention rules, and a default time window — matching the anchor for mostly executable guidance with minor gaps. It falls short of anchor 5 because there is no worked example of the output shape (e.g. a sample 'Action items' line) and no pointer to how messages are retrieved.

4 / 5

Workflow Clarity

The flow is unambiguous: confirm channel(s) and time window ("Confirm before searching"), then produce the three-section output, with explicit edge-case handling ("If the channel was empty in the time window, say so — don't fabricate filler"). This is a simple, single-purpose, non-destructive skill, so the simple-skill exception applies and the single action is unambiguous.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle directories), and is organized into clear, well-labeled sections (When to use, Required inputs, Output shape, What not to do). Per the rubric guideline, a short skill with no need for external references scores 5 with just well-organized sections.

5 / 5

Total

19

/

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 domain, but it only states a single action and entirely lacks a 'Use when...' trigger clause, which caps completeness and leaves natural trigger phrasings uncovered. Adding explicit trigger guidance with the phrases users actually say would raise most dimensions.

Suggestions

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

Include the natural phrases users say as trigger terms, such as "catch me up", "what happened in #channel", or "recap", alongside the current keywords.

Briefly name the concrete outputs of the distillation (key decisions, open questions, action items) to make the capability more specific and comprehensive.

DimensionReasoningScore

Specificity

The description names the domain ("Slack channel or thread") and one concrete action ("Distill... into actionable summary"), matching the anchor for 1-2 concrete actions that are not comprehensive. It does not enumerate the specific outputs of the distillation (decisions, action items, open questions), which keeps it below anchor 4.

3 / 5

Completeness

It has a clear "what" ("Distill a Slack channel or thread into actionable summary") but no "when" / "Use when..." clause at all. Per the judging guidelines, a missing explicit trigger guidance caps completeness at 3, matching the anchor for a clear 'what' with 'when' missing. It is above anchor 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Relevant keywords are present ("Slack", "channel", "thread", "summarize") but common natural variations users would say are missing, e.g. "catch me up", "recap", "what happened in", "digest". This matches the anchor for some relevant keywords missing common variations, and falls short of anchor 4's good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"Slack channel or thread" carves out a clear niche with distinct triggers, with only minor overlap risk against closely related skills (other Slack skills or generic summarization skills). It is below anchor 5 because "summary" alone is a broadly shared trigger term.

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.

Validation — 16 / 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.