slack-ui-skills

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

Quality

62%

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/slack/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 'Use when' clause and is distinctive enough to avoid conflicts with other skills. However, it lacks concrete action verbs describing what the skill actually does (e.g., styling components, applying color schemes) and could benefit from more natural trigger terms users might use when requesting Slack-like interfaces.

Suggestions

Add specific concrete actions like 'Applies Slack's color palette, component styles, spacing, and typography to UI designs'.

Include additional natural trigger terms such as 'Slack-style', 'chat interface design', 'messaging app UI', or 'Slack theme'.

Dimension	Reasoning	Score
Specificity	Names the domain (Slack 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 palettes'.	2 / 3
Completeness	Clearly answers both what ('Slack's UI design system') and when ('Use when building interfaces inspired by Slack's aesthetic - light mode, Inter font, 4px grid'), with an explicit 'Use when' clause and trigger conditions.	3 / 3
Trigger Term Quality	Includes 'Slack', 'UI design system', 'light mode', 'Inter font', and '4px grid' which are somewhat relevant, but misses natural user terms like 'Slack-style', 'messaging app UI', 'chat interface', 'Slack theme', or 'Slack colors'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche — Slack's design system is distinct from other UI design skills. The mention of Slack specifically, along with Inter font and 4px grid, makes it unlikely to conflict with other design system skills.	3 / 3
	Total	10 / 12 Passed

Implementation

50%

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

This skill provides a structured design system reference with clear semantic tokens, typography specs, and interaction guidelines using a helpful MUST/SHOULD/NEVER constraint hierarchy. However, it appears to contain raw extraction artifacts (0px input heights, inconsistent element widths, redundant typography references) that undermine credibility, and lacks executable code examples showing implementation in actual CSS/Tailwind/component code. The content would benefit from curation to remove suspicious values and addition of implementation snippets.

Suggestions

Add executable code examples showing implementation (e.g., Tailwind config with custom theme values, CSS custom properties block, or a sample component using the design tokens)

Review and remove apparent extraction artifacts: '0px' input height, inconsistent 'element widths: 15px, 67px, 13px, 16px, 17px', and duplicate body-secondary entries with slightly different specs

Move detailed reference tables (full text styles, all font sizes, border radius scale) into a separate REFERENCE.md file and link to it from the main skill

Add a brief workflow section explaining the order of application (e.g., 'Apply layout constraints first, then typography, then color tokens') to guide implementation sequence

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints, but includes some redundant information (e.g., the Typography Reference section repeats font sizes already shown in the table, 'Count' column with all 1s adds no value, and some detected values like '0px input height' seem like artifacts rather than intentional design specs).	2 / 3
Actionability	Provides concrete design tokens, specific values, and clear constraints (MUST/SHOULD/NEVER), which is actionable for a design system skill. However, there are no code examples showing how to implement these values (e.g., Tailwind config, CSS custom properties, or component snippets), and some specs seem like raw extraction artifacts (e.g., '0px height for input fields', inconsistent element widths like '15px, 67px, 13px') rather than curated, executable guidance.	2 / 3
Workflow Clarity	For a design system reference skill, the sections are logically organized and the MUST/SHOULD/NEVER hierarchy provides clear priority. However, there's no workflow for how to apply these guidelines (e.g., 'start with layout, then typography, then colors') and no validation steps to verify compliance with the design system.	2 / 3
Progressive Disclosure	The content is well-sectioned with clear headings and tables, making it scannable. However, at ~150 lines with detailed reference tables, some content (like the full text styles table or border radius reference) could be split into separate reference files, and there are no cross-references to external files for deeper detail.	2 / 3
	Total	8 / 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.