discord-ui-skills

Discord's UI design system. Use when building interfaces inspired by Discord's aesthetic - light mode, Inter font, 4px grid.

Quality

68%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/discord/SKILL.md

Quality

Discovery

75%

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 a clear niche and explicit trigger guidance, making it distinctive and complete. However, it lacks concrete action verbs describing what the skill actually does (e.g., style components, apply color palettes) and could include more natural trigger terms users might use when requesting Discord-inspired designs.

Suggestions

Add specific concrete actions like 'Applies Discord color tokens, styles components, creates chat-like layouts' to improve specificity.

Expand trigger terms to include common variations like 'Discord theme', 'Discord-style UI', 'chat interface', 'dark mode' (if supported), and 'messaging app design'.

Dimension	Reasoning	Score
Specificity	Names the domain (Discord's UI design system) and mentions some specific elements (light mode, Inter font, 4px grid), but doesn't list concrete actions like 'create layouts', 'style components', or 'apply color tokens'.	2 / 3
Completeness	Clearly answers both what ('Discord's UI design system') and when ('Use when building interfaces inspired by Discord's aesthetic - light mode, Inter font, 4px grid'), with an explicit 'Use when' clause and trigger context.	3 / 3
Trigger Term Quality	Includes 'Discord' and some design terms like 'Inter font', '4px grid', 'light mode', but misses common user terms like 'Discord theme', 'Discord-style', 'chat UI', 'dark mode', 'Discord colors', or 'messaging app design'.	2 / 3
Distinctiveness Conflict Risk	Very distinct niche — specifically Discord's design system. Unlikely to conflict with other UI/design skills due to the explicit Discord branding and specific design tokens mentioned.	3 / 3
	Total	10 / 12 Passed

Implementation

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured design system reference with clear constraint language (MUST/SHOULD/NEVER) and specific values. Its main weaknesses are the lack of executable code examples showing how to implement these constraints in practice, and some redundancy in the typography and border sections. The content would benefit from at least one concrete implementation example and better progressive disclosure by moving detailed reference tables to separate files.

Suggestions

Add at least one concrete code example (e.g., a CSS/Tailwind card component or button) demonstrating the design tokens in use

Remove redundant sections like 'Border Radius Reference' (which just repeats '9px') and 'Typography Reference' (which restates the text styles table)

Consolidate the multiple `text-14px` entries into a single entry with a note about color variations, or explain why they differ

Consider moving the detailed reference tables (Text Styles, Semantic Tokens) to a separate REFERENCE.md and keeping SKILL.md as a concise overview

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints. However, there's redundancy (e.g., the Typography Reference section repeats information already in the Text Styles table, and the Border Radius Reference section adds nothing beyond what's already stated). Some token values like multiple `text-14px` entries with different colors could be consolidated.	2 / 3
Actionability	The skill provides specific values (hex codes, pixel sizes, font weights) which are concrete and actionable for implementation. However, it lacks any executable code examples - no CSS snippets, no Tailwind classes, no component code. For a UI design system skill, at least one concrete implementation example (e.g., a button component or card layout) would significantly improve actionability.	2 / 3
Workflow Clarity	This is a reference/constraint skill rather than a multi-step workflow skill. The 'When to Apply' section clearly scopes when to use it, and the constraints are organized by domain (colors, typography, spacing, etc.) with clear MUST/SHOULD/NEVER priority levels. For this type of declarative design system skill, the single-task clarity is unambiguous.	3 / 3
Progressive Disclosure	The content is well-organized with clear section headers and tables, but it's a fairly long monolithic document. Some sections (like the full text styles table with 10+ entries, or the detailed semantic tokens) could be split into a reference file, keeping SKILL.md as a concise overview with links to detailed specs.	2 / 3
	Total	9 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ihlamury/design-skills
Commit: 126714e

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