Name: discord
Rating: 55.2 (1 reviews)
Author: membranedev

discord

Discord integration. Manage data, records, and automate workflows. Use when the user wants to interact with Discord data.

Quality

62%

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 ./skills/discord/SKILL.md

Quality

Content

67%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 strong, command-driven integration guide with a well-sequenced, validated connection state machine. Its main weaknesses are unnecessary concept/marketing prose, a duplicated command section, a dangling "Step 2" cross-reference, and a lack of fully-worked examples or post-action verification.

Suggestions

Remove the "Discord is a voice, video, and text chat application…" sentence and the "so you can focus on the integration logic rather than auth plumbing" marketing clause; Claude already knows what Discord is.

Fix the dangling "skip to Step 2" reference by either labeling the next section "Step 2: Search for actions" or rewording to "skip to Searching for actions below".

Merge the "Popular actions" section into "Searching for actions" to eliminate the duplicated `action list` command, and add one fully-worked example (real action id + --input) plus a verify-the-output step.

Dimension	Reasoning	Score
Conciseness	Mostly efficient commands, but it explains what Discord is ("Discord is a voice, video, and text chat application…"), includes a marketing line about Membrane auth plumbing, and duplicates the action-list command in the "Popular actions" section.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands throughout (login, connection ensure, polling, action list/run, request) plus a full proxy-options table, but examples lean on generic placeholders (<actionId>, CONNECTION_ID, /path/to/endpoint) with no fully-worked real example.	4 / 5
Workflow Clarity	The connection workflow is a clear state machine with explicit checkpoints and feedback loops (poll --wait, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after action), though the dangling "Step 2" reference and absence of post-run verification are minor gaps.	4 / 5
Progressive Disclosure	A single well-organized SKILL.md with clearly labeled sections and no bundle files; not a 5 because everything is inline with no reference pointers and some sections ("Discord Overview", "Popular actions") are thin or redundant.	4 / 5
	Total	15 / 20 Passed

Description

57%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 has an explicit trigger clause and a distinctive Discord niche, but its capability statement is vague and generic rather than naming concrete actions. Trigger-term coverage relies almost entirely on the word "Discord" with little task-level vocabulary.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete Discord actions, e.g. "Send messages, manage channels and roles, and read server data."

Expand trigger terms to include natural task phrases users say, such as "Discord messages", "channels", "servers", or "guilds", not just "Discord data".

Tighten the "when" clause to name specific intents (e.g. "Use when the user wants to send or read Discord messages, manage channels, or automate Discord workflows.").

Dimension	Reasoning	Score
Specificity	It names the domain (Discord) but the actions are minimal and generic — "Manage data, records, and automate workflows" is abstract with no concrete operations like sending messages or managing channels.	2 / 5
Completeness	Both a "what" ("Discord integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Discord data.") are present, with the trigger clause reasonably explicit.	4 / 5
Trigger Term Quality	"Discord" and "interact with Discord data" are relevant natural keywords, but coverage is thin and missing common variations users would say (e.g. messages, channels, servers, guilds).	3 / 5
Distinctiveness Conflict Risk	Discord is a clear, named-app niche with distinct triggers and low conflict risk against unrelated skills, though the generic "interact with Discord data" phrasing leaves minor overlap risk with hypothetical other Discord skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/discord/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.