slack-realtime-events

Real-time event handling with Socket Mode and Events API. Use when building interactive Slack bots, handling message events, app mentions, reactions, button clicks, modal submissions, slash commands, or any event-driven Slack application functionality.

Quality

80%

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-go-sdk/skills/slack-realtime-events/SKILL.md

Quality

Content

71%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.

A well-organized, code-heavy body with good decision guidance and lean prose. Its main weakness is progressive disclosure: the skill leans on five external reference files that are absent from the bundle, leaving the overview pointing at missing details.

Suggestions

Create the referenced bundle files (socket-mode-setup.md, events-api-webhooks.md, interactive-components.md, slash-commands.md, event-types.md) or fix the broken ../../references/ paths so the links resolve within the skill directory.

Make code examples fully copy-paste ready: define or inline the undefined helpers (botUserID, processCommand, updateMessage) and show how each handler is dispatched from the client.Events loop.

Move the per-event-type handler examples (reaction, modal submission) into the referenced detail files to keep SKILL.md a tighter overview.

Dimension	Reasoning	Score
Conciseness	Lean body of code examples and short lists with no re-teaching of concepts Claude already knows; a few inline handler examples (reaction, modal) could be trimmed or moved to reference files.	4 / 5
Actionability	Mostly executable Go code with concrete patterns, but several fragments depend on undefined helpers (botUserID, processCommand, updateMessage) and handlers are never wired into the event loop.	4 / 5
Workflow Clarity	Clear decision guidance for Socket Mode vs Events API and a logical flow from setup through event handling to graceful shutdown and pitfalls; no validation checkpoints are required for this non-destructive domain.	4 / 5
Progressive Disclosure	The body is well-structured with clearly signaled one-level-deep references, but none of the five referenced files (socket-mode-setup.md, events-api-webhooks.md, interactive-components.md, slash-commands.md, event-types.md) exist in the bundle, and the paths point outside the skill directory (../../references/), so navigation is broken.	3 / 5
	Total	15 / 20 Passed

Description

83%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.

A strong description with a clear what-and-when structure and a rich set of concrete trigger phrases. Minor improvements possible by adding natural synonyms (webhook, Slack app) and tightening distinctiveness against sibling Slack skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('Real-time event handling with Socket Mode and Events API') and enumerates several concrete handled events ('message events, app mentions, reactions, button clicks, modal submissions, slash commands'), with only minor gaps such as setup/config actions.	4 / 5
Completeness	Explicitly answers both what ('Real-time event handling with Socket Mode and Events API') and when ('Use when building interactive Slack bots, handling message events...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural terms users would say ('interactive Slack bots', 'app mentions', 'button clicks', 'slash commands'), but a few common synonyms are missing such as 'webhook', 'Slack app', or 'real-time messaging'.	4 / 5
Distinctiveness Conflict Risk	Clear Slack real-time events niche, but trigger terms like 'button clicks, modal submissions, slash commands' could overlap with a sibling Slack interactive-components skill.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 5 suspicious	Warning

	Total	14 / 16 Passed

Repository: freightCognition/linehaulai-claude-marketplace
Path: plugins/slack-go-sdk/skills/slack-realtime-events/SKILL.md
Commit: 88571a6

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