posthog-ui-skills
Posthog's UI design system. Use when building interfaces inspired by Posthog's aesthetic - dark mode, Inter font, 4px grid.
75
68%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/posthog/SKILL.mdQuality
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 effectively identifies a clear niche (Posthog's design system) and includes an explicit 'Use when' clause, making it strong on completeness and distinctiveness. However, it lacks concrete action verbs describing what the skill actually does (e.g., generating components, applying styles) and could benefit from additional trigger terms users might naturally use.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates UI components, applies color palettes, and generates layouts following Posthog's design system.'
Include additional natural trigger terms users might say, such as 'Posthog-style', 'design tokens', 'UI theme', 'component styling', or 'dashboard design'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI design system) and mentions some specific elements (dark mode, Inter font, 4px grid), but doesn't list concrete actions like 'create components', 'apply styling', or 'generate layouts'. | 2 / 3 |
Completeness | Clearly answers both what ('Posthog's UI design system') and when ('Use when building interfaces inspired by Posthog's aesthetic - dark mode, Inter font, 4px grid') with an explicit 'Use when' clause and trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes 'Posthog' as a strong trigger term and some design-related terms like 'dark mode', 'Inter font', '4px grid', but misses common user phrases like 'design system', 'UI components', 'styling', 'theme', or 'Posthog-style'. | 2 / 3 |
Distinctiveness Conflict Risk | The specificity to Posthog's design system with its particular aesthetic characteristics (dark mode, Inter font, 4px grid) creates a clear niche that is unlikely to conflict with other design system skills. | 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 constraints using MUST/SHOULD/NEVER language and specific values in organized tables. Its main weaknesses are the lack of executable code examples (CSS variables, Tailwind config snippets) and some redundancy in reference sections. The content would benefit from being more actionable with copy-paste ready implementation code and splitting detailed reference tables into separate files.
Suggestions
Add executable code examples: a CSS custom properties block defining the semantic tokens, and/or a Tailwind config snippet implementing the design scale
Remove redundant reference sections (e.g., 'Border Radius Reference' repeating '3px', 'Typography Reference' duplicating the Text Styles table) to improve conciseness
Consider splitting detailed tables (semantic tokens, text styles, component variants) into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with key constraints
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient with table-based references and clear MUST/SHOULD/NEVER constraints, but includes some redundancy (e.g., repeating border-radius '3px' in both the rules and a separate 'Border Radius Reference' section, listing font families used '7x' which adds little value). Some sections like 'Typography Reference' duplicate information already in the Text Styles table. | 2 / 3 |
Actionability | The skill provides specific values (hex codes, pixel sizes, font weights) which are concrete, but lacks executable code examples showing how to implement these tokens in CSS/Tailwind/React. The guidance is specific enough to act on but would benefit from copy-paste ready code snippets (e.g., CSS custom properties block, Tailwind config). | 2 / 3 |
Workflow Clarity | This is a reference/design-system skill rather than a multi-step workflow, so the single-purpose nature applies. The content is clearly organized into logical sections (Colors, Typography, Spacing, etc.) with unambiguous constraints using MUST/SHOULD/NEVER language, making it easy to follow as a checklist. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and tables, but it's a fairly long monolithic file. Some sections (like the full semantic token table, all text styles, and layout patterns) could be split into referenced files to keep the main skill leaner. No external references are provided. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%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
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.