CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/ultracite/skills/ultracite/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

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

A highly actionable, well-referenced skill body with excellent executable commands, complete config examples, and a genuine one-level-deep reference bundle with a load-on-demand index. Its weaknesses are self-duplication (the Summary and When-to-Use sections repeat earlier content), a dated version section, and a few inaccurate or dangling pointers (.windsurfrules for Claude Code, README.md, dependency-upgrade skill).

Suggestions

Delete or drastically shrink the Summary section — it restates 'When to Use', the provider comparison, and key advantages already covered above — and drop the dated 'Package Versions (verified 2026-08-03)' section or move it to a maintenance/old-patterns note.

Fix the incorrect and dangling pointers: Claude Code rules should not be listed as `.windsurfrules` (that is Windsurf's file), and references to a nonexistent README.md and `dependency-upgrade` skill should be removed or replaced with real bundle paths.

Add inline failure branches to the main workflows (e.g., after 'Run `npx ultracite doctor`' in the migration steps, state what to do when doctor reports invalid preset paths), and trim inlined provider/migration detail in favor of the already excellent reference files.

DimensionReasoningScore

Conciseness

The bulk is efficient, executable content (commands, configs, flags), but there is real padding: the ~55-line Summary section duplicates 'When to Use', the provider comparison, and the key advantages verbatim; install commands appear three times; and the 'Package Versions (verified 2026-08-03)' section embeds time-sensitive date/version info outside any old-patterns section, which the guidelines say should penalize conciseness. Not 2 because the document rarely explains concepts Claude already knows and most sections earn their tokens; not 4 because the duplication and dated version info go beyond 'minor instances'.

3 / 5

Actionability

Nearly everything is copy-paste ready: `bun x ultracite init --linter biome`, full biome.jsonc heredocs, VS Code settings JSON, hook scripts, and documented CLI flags with expected `doctor` output. Not 5 because of concrete errors that would misdirect action: Claude Code rules are listed as generating `.windsurfrules` (that is Windsurf's file), and 'See README.md' plus 'Load the `dependency-upgrade` skill' point at files that do not exist in this bundle.

4 / 5

Workflow Clarity

Sequences are clear and validation is mostly present: the v6→v7 migration steps include 'Run `npx ultracite doctor` to validate configuration' and 'Test linting: `npx ultracite check .`', and 'Verify Installation' shows expected command output. Not 5 because failure branches are not inline (no 'if validation fails, do X' loop in the workflow itself — recovery is deferred to the troubleshooting reference), and the init flow lists 10 steps without checkpoints between them.

4 / 5

Progressive Disclosure

Scored against the actual bundle: all 15 markdown references and 2 scripts cited in the body exist, are one level deep, and are well signaled both inline ('For complete X, see references/X.md') and via a dedicated 'When to Load References' index mapping topics to files. Not 5 because the SKILL.md itself inlines substantial detail that duplicates the reference files (full provider sections, migration examples, monorepo structures), and the dangling README.md / dependency-upgrade pointers break navigation.

4 / 5

Total

15

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed description that states what the skill does, names all three providers, and gives an explicit, enumerated 'Use for...' trigger clause covering setup, hooks, migrations, and error scenarios. The only gap is a few missing natural trigger synonyms (prettier, biome.jsonc).

Suggestions

Add 'prettier' and 'eslint replacement / prettier replacement' to the trigger clause since migrating from Prettier is one of the most common ways users would phrase the need.

Consider including a concrete config artifact term like 'biome.jsonc' so users asking about a specific config file surface this skill.

The trailing phrase 'or encountering configuration, type-aware linting, monorepo errors' is grammatically awkward; rephrase as 'or troubleshooting configuration, type-aware linting, or monorepo errors' for clarity.

DimensionReasoningScore

Specificity

Names the domain and several concrete capability areas — 'multi-provider linting/formatting (Biome, ESLint, Oxlint)', 'v6/v7 setup, provider selection, Git hooks, MCP integration, AI hooks, migrations'. Falls short of the 5 anchor because the 'what' clause covers only linting/formatting without mentioning presets, rules, or framework support, and exceeds the 3 anchor which expects only 1-2 concrete actions.

4 / 5

Completeness

Explicitly answers both: what — 'Ultracite multi-provider linting/formatting (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' — with concrete trigger phrases, matching the anchor-5 exemplar structure. Not 4 because the 'when' clause is highly explicit and enumerates nine specific trigger scenarios rather than being vague or only weakly specific.

5 / 5

Trigger Term Quality

Good coverage of natural phrases users would say: 'setup', 'Git hooks', 'migrations', 'monorepo', 'type-aware linting', plus tool names Biome/ESLint/Oxlint. Missing a few natural synonyms users say — notably 'prettier' (common migration source), 'lint', and file/config terms like 'biome.jsonc' — so it fits the 'good keyword coverage, a few natural terms missing' anchor rather than the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche: the Ultracite brand plus distinctive triggers (v6/v7 migration, MCP integration, AI hooks, provider selection) make it unlikely to fire for generic Biome or ESLint skills. It is not 4 because the branded, multi-provider, migration-focused triggers leave only minimal overlap risk with a dedicated Biome-only skill.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/ultracite/skills/ultracite/SKILL.md

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.