CtrlK
BlogDocsLog inGet started
Tessl Logo

slack-channel-summarization

Summarize activity from one Slack channel and return a concise recap, post-ready update, or summary doc.

73

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 concise, actionable, and clearly sequenced with concrete tool calls and a binding output template, and it is well-organized with shallow references. It is a strong instruction-only skill.

DimensionReasoningScore

Conciseness

Lean body with no explanation of concepts Claude already knows; every section (Start Here, Workflow, Formatting Rules) earns its place with concrete defaults. Not a 2 because there is no padded or unnecessary explanation to tighten.

3 / 3

Actionability

Provides concrete tool calls with parameters (slack_read_channel with limit:100, oldest/latest, slack_read_thread defaulting to 50 replies, slack_create_canvas) plus a copy-paste output template. Not a 2 because guidance is fully executable rather than pseudocode or abstract direction.

3 / 3

Workflow Clarity

A clear 7-step numbered sequence with explicit conditional branches (window vs no window) and delivery intent rules. Not a 2 because the sequence and decision points are explicit; the read/summarize context is non-destructive so the missing-validation cap for batch/destructive ops does not apply.

3 / 3

Progressive Disclosure

Single, well-organized file with clearly signaled one-level references (a sibling skill link) and no nested references. Not a 2 because content is appropriately inline and navigable rather than a monolithic wall or deeply nested pointer chain.

3 / 3

Total

12

/

12

Passed

Description

82%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 specific, uses natural trigger terms, and carves out a clear niche, but it omits an explicit 'Use when...' trigger clause, which caps completeness at 2.

Suggestions

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

Include common phrasings users might say such as 'catch up on', 'what did I miss in', or 'recap the last messages in' the channel.

DimensionReasoningScore

Specificity

Lists concrete actions and outputs: 'Summarize activity from one Slack channel and return a concise recap, post-ready update, or summary doc', naming multiple specific deliverables rather than vague language. Not a 2 because it goes beyond naming a single action to enumerating concrete output types.

3 / 3

Completeness

Clearly states what the skill does but lacks an explicit 'Use when...' trigger clause; the when is only implied by the topic. Capped at 2 per the guideline that a missing explicit trigger clause limits completeness, and not a 3 because there is no 'when should Claude use it' guidance in the description.

2 / 3

Trigger Term Quality

Includes natural terms users would say: 'Slack channel', 'recap', 'update', 'summary doc'. Not a 2 because the term coverage spans the common phrasings a user would naturally request rather than only a single keyword.

3 / 3

Distinctiveness Conflict Risk

Has a clear niche (summarizing one Slack channel) with distinct triggers unlikely to overlap sibling skills like slack-outgoing-message. Not a 2 because the scope is narrow and unambiguous rather than broadly overlapping.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
openai/plugins
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.