ultracite
Ultracite multi-provider linting/formatting (Biome, ESLint, Oxlint). Use for v6/v7 setup, provider selection, Git hooks, MCP integration, AI hooks, migrations, or encountering configuration, type-aware linting, monorepo errors.
62
75%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/ultracite/skills/ultracite/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the tool (Ultracite), lists specific capabilities (linting/formatting across multiple providers), and provides explicit trigger conditions via a 'Use for...' clause covering setup, migrations, and common error scenarios. The description is concise, uses third person voice, and includes highly specific trigger terms that minimize conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: linting/formatting, v6/v7 setup, provider selection, Git hooks, MCP integration, AI hooks, migrations, and troubleshooting configuration/monorepo errors. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (multi-provider linting/formatting with Biome, ESLint, Oxlint) and 'when' ('Use for v6/v7 setup, provider selection, Git hooks, MCP integration, AI hooks, migrations, or encountering configuration, type-aware linting, monorepo errors'). The 'Use for...' clause explicitly lists trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: Biome, ESLint, Oxlint, Git hooks, MCP integration, linting, formatting, monorepo, type-aware linting, migrations. These cover the specific tools and common terms a developer would use when seeking help with this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — 'Ultracite' is a specific tool name, and the combination of multi-provider linting with Biome/ESLint/Oxlint, MCP integration, and AI hooks creates a very clear niche that is unlikely to conflict with generic linting or formatting skills. | 3 / 3 |
Total | 12 / 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 is highly actionable with excellent concrete code examples and commands, but severely undermined by extreme verbosity and redundancy. Content that belongs in reference files (detailed provider comparisons, full configuration guides, extensive 'when to use' criteria) is inlined in the main SKILL.md, creating a monolithic document that wastes token budget. The Summary section alone duplicates most of the document's content, and key information like installation commands appears 3+ times.
Suggestions
Reduce the SKILL.md to ~150 lines by moving detailed provider comparisons, full configuration examples, 'When to Use' criteria, and the 'When to Load References' mapping into reference files, keeping only a quick-start overview in the main file.
Eliminate the Summary section entirely—it duplicates nearly every section above it. If a summary is needed, limit it to 5-10 lines maximum.
Consolidate the 'When to Load References' section into a simple markdown table (reference file | trigger topics) instead of the current ~80-line expanded format.
Add explicit validation/verification steps to the ESLint/Prettier migration workflow (e.g., 'Run ultracite doctor after migration' and 'Run ultracite check . to verify no regressions') to match the quality of the v6→v7 migration steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines. Massive amounts of redundancy: the Summary section repeats nearly everything from the body, provider comparison is stated multiple times, installation commands appear in at least 3 places, and 'When to Use' criteria are repeated in the Summary. Explains concepts Claude already knows (what ESLint/Prettier are, what monorepos are, what Git hooks do). The 'When to Load References' section alone is ~80 lines of content that could be a simple table. | 1 / 3 |
Actionability | Provides fully executable, copy-paste-ready commands and configuration snippets throughout: init commands with flags, biome.jsonc examples, VS Code settings, package.json scripts, Husky pre-commit hooks, manual setup steps, and CLI usage patterns. Code examples are concrete and complete. | 3 / 3 |
Workflow Clarity | The v6→v7 migration has clear numbered steps including a validation checkpoint (run doctor), and installation has a verify step. However, the migration from ESLint/Prettier lacks validation/verification steps (just says 'Test thoroughly'), and the Project Suitability Assessment workflow mixes bash commands with assessment logic without clear checkpoints. The overall document structure makes it hard to follow sequential workflows due to information being spread across many sections. | 2 / 3 |
Progressive Disclosure | References to external files are well-signaled and one-level deep (references/*.md, scripts/*.sh), and the 'When to Load References' section provides good navigation. However, the SKILL.md itself is monolithic with enormous amounts of inline content that should be in reference files (e.g., the full provider comparison, detailed installation options, complete configuration examples, the entire 'When to Use' section). The main file tries to be both overview and comprehensive guide simultaneously. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (889 lines); consider splitting into references/ and linking | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- secondsky/claude-skills
- Commit
5e92b71
- 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.