CtrlK
BlogDocsLog inGet started
Tessl Logo

slack-summary

Distill a Slack channel or thread into actionable summary

66

Quality

78%

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

100%

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 tight, well-structured instruction set: it disambiguates inputs, defines a precise three-part output shape with citation rules, and includes concrete guardrails, all without padding or unnecessary references.

DimensionReasoningScore

Conciseness

The body is lean and instruction-only with no padding or explanations of concepts Claude already knows — e.g. 'Confirm before searching', 'Don't invent assignees' — so every token earns its place, matching the 'lean and efficient' anchor.

3 / 3

Actionability

It gives concrete executable guidance: confirm channel(s)/thread(s) and time window (default 7 days), then produce three named sections with citation rules and '@mention who owes what by when' — copy-paste-ready direction rather than abstract description.

3 / 3

Workflow Clarity

The sequence is explicit — confirm inputs before searching, then summarize into three sections, with the empty-channel verification as a checkpoint — and as a read-only (non-destructive) task it meets the simple-skill allowance for full marks.

3 / 3

Progressive Disclosure

At roughly 25 lines with no need for external references, the well-organized sections (When to use, Required inputs, Output shape, What not to do) satisfy the under-50-lines allowance for full progressive-disclosure marks.

3 / 3

Total

12

/

12

Passed

Description

57%

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 occupies a clear niche, but it states only one action and omits an explicit 'Use when...' trigger clause, leaving it at the mid-level for specificity, trigger terms, and completeness.

Suggestions

Add a 'Use when...' clause with natural user phrasings (e.g., 'Use when the user asks to summarize Slack, catch up on a channel, or recap a thread').

List concrete output actions beyond 'summarize' (e.g., 'extract key decisions, open questions, and action items') to raise specificity.

DimensionReasoningScore

Specificity

Quotes 'Distill a Slack channel or thread into actionable summary' — it names the domain (Slack channel/thread) and one core action (distill into summary), but does not enumerate multiple distinct concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the level-3 multi-action example.

2 / 3

Completeness

It answers 'what' (distill Slack into actionable summary) but lacks any explicit trigger/'when' guidance; per the rubric a missing 'Use when...' clause caps completeness at 2.

2 / 3

Trigger Term Quality

It surfaces natural terms ('Slack channel or thread', 'summary') but offers no 'Use when...' clause listing common user phrasings like 'catch me up' or 'what happened in #channel', fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The Slack summarization niche is clearly bounded by 'Slack channel or thread' triggers, making it unlikely to fire for unrelated skills; this matches the 'clear niche with distinct triggers' anchor.

3 / 3

Total

9

/

12

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.