obsidian-ui-skills
Obsidian's UI design system. Use when building interfaces inspired by Obsidian'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/obsidian/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 is concise and clearly scoped to a specific design system niche, with an explicit 'Use when' clause that aids skill selection. Its main weakness is the lack of concrete action verbs describing what the skill actually does (e.g., generates components, applies styles, creates layouts), and it could benefit from a few more natural trigger terms users might use.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Generates UI components, applies color tokens, and styles layouts following Obsidian's design system.'
Include additional trigger term variations such as 'Obsidian-style', 'Obsidian theme', 'note-taking app UI', or 'vault interface' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Obsidian UI design system) and mentions some specific elements (dark mode, Inter font, 4px grid), but doesn't list concrete actions like 'apply styles', 'generate components', or 'create layouts'. | 2 / 3 |
Completeness | Clearly answers both 'what' (Obsidian's UI design system) and 'when' (Use when building interfaces inspired by Obsidian's aesthetic) with explicit trigger guidance including specific design attributes. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Obsidian', 'dark mode', 'Inter font', and '4px grid', but misses common variations users might say such as 'Obsidian-style', 'Obsidian theme', 'note-taking app UI', or 'sidebar design'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets Obsidian's aesthetic with concrete design tokens (Inter font, 4px grid, dark mode), making it unlikely to conflict with generic UI or 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 reasonably well-structured design system reference with clear MUST/SHOULD/NEVER constraints and specific token values. Its main weaknesses are the lack of executable code examples (no CSS/Tailwind/component snippets) and some apparent data quality issues (0px input height, surface-raised being near-white in a dark theme). The content would benefit from being more concise with a separate detailed reference file and adding at least one implementation example.
Suggestions
Add at least one executable code example — e.g., a CSS custom properties block defining the semantic tokens, or a sample component implementation using the design system values.
Review and fix apparent data extraction artifacts: '0px' input height and '#FEFEFD' (near-white) as 'surface-raised' in a dark theme seem incorrect and could mislead Claude.
Split the detailed reference tables (full text styles, all font sizes, border radius scale) into a separate REFERENCE.md file, keeping SKILL.md focused on the core constraints and most-used tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with its table-based format and MUST/SHOULD/NEVER constraints, but includes some redundancy (e.g., listing both HEX and RGB for every color, the 'Typography Reference' section repeating font families/sizes already shown in the table, and some questionable values like '0px' input height that seem like extraction artifacts rather than intentional design tokens). The detected layout patterns section adds little value. | 2 / 3 |
Actionability | The skill provides concrete design tokens, specific values, and clear constraints (MUST/SHOULD/NEVER), which is good. However, it lacks executable code examples — no CSS snippets, no Tailwind config, no component code. For a UI design system skill, having at least one concrete implementation example (e.g., a button component or a CSS custom properties block) would make it significantly more actionable. | 2 / 3 |
Workflow Clarity | This is a reference/constraint skill rather than a multi-step workflow skill. For its purpose — providing design system constraints — the content is clearly organized into logical sections (Colors, Typography, Spacing, etc.) with unambiguous rules. The single-purpose nature of each section makes the guidance clear and easy to follow. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and tables, but it's a fairly long monolithic document (~150 lines of dense specification). Some sections like the full text styles table, typography reference, and border radius reference could be split into a separate reference file, keeping the SKILL.md as a concise overview with the most critical constraints. | 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.