CtrlK
BlogDocsLog inGet started
Tessl Logo

bestax-theming

Customize colors, branding, dark mode, and visual tokens of an app built with @allxsmith/bestax-bulma. Use when changing the primary/brand color, recoloring components, overriding Bulma --bulma-* CSS variables, setting fonts/radius/spacing tokens, adding light/dark mode, or configuring the app-wide icon library / class prefix via ConfigProvider.

72

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 high-quality, information-dense body: executable code, package-specific facts Claude cannot infer, explicit decision rules, and a verification checklist. Two issues hold it back: the Examples section references files that are missing from the bundle, and a key dark-mode parenthetical is repeated three times, adding tokens without new information.

Suggestions

Fix the dangling references: either ship examples/theme-config.tsx and examples/dark-mode.tsx in the bundle or remove/inline the Examples section — every cited path should resolve.

State the 'data-<prefix>theme inside a ConfigProvider with classPrefix' detail once (Approach or a footnote) and reference it elsewhere; it currently appears verbatim three times.

Split the longest Contrast-rules sentences (e.g. the Both-modes bullet) into shorter steps or a small snippet block to reduce re-reading cost.

DimensionReasoningScore

Conciseness

The body is dense with package-specific facts Claude cannot know (HSL trios, prop unions, scheme-flipping rules) and wastes nothing on generic CSS/React background. The trimmable parts are repetition and syntax, not padding: the parenthetical '(plus `data-<prefix>theme` inside a `ConfigProvider` with a `classPrefix`, which the prefixed flavors read)' appears three times (Approach, Contrast rules, Checklist), and some Contrast-rules sentences chain multiple clauses that could be split. Fits anchor 4 ('minor instances ... that could be trimmed') better than 3, since there is no over-explanation of known concepts — only local redundancy.

4 / 5

Actionability

Copy-paste-ready Quick start and ConfigProvider code, exact prop names ('primaryH="265" primaryS="65%" primaryL="55%"', 'iconLibrary="fa"'), a concrete Sass line ('@use \'bulma/sass\' with ($primary: #1e6b99)'), and precise CSS selectors ('[data-theme=\'dark\']' and '@media (prefers-color-scheme: dark)' scoped to ':root:not([data-theme])'). Common cases (recolor, dark mode, icons) are each covered concretely; the few ellipsis snippets (':root { --bulma-primary-h: …; }') are justified flexibility for token values, not pseudocode.

5 / 5

Workflow Clarity

The skill is structured as an explicit decision guide: choose one of three override paths, 'Apply exactly one of these rules' for dark-mode contrast, and a closing Checklist that functions as verification — checkpoints are present, not implicit. However there is no ordered multi-step sequence with feedback loops (e.g. verify the rendered contrast after theming), matching anchor 4 ('clear sequence with most checkpoints present; minor validation gaps') rather than 5. No destructive/batch operations, so the validation cap does not apply.

4 / 5

Progressive Disclosure

The overview is well-split: two real, one-level-deep references (references/css-variables.md, references/themeable-components.md) are signaled with accurate one-line summaries, and no file is buried. But the Examples section cites 'examples/theme-config.tsx' and 'examples/dark-mode.tsx' — and no examples/ directory exists in the bundle, so both links are dangling. That is a genuine navigation defect that keeps it at anchor 4 ('minor organization gaps') rather than 5 ('easy navigation'); not 3, since the structure and existing references are clearly signaled and appropriately split.

4 / 5

Total

17

/

20

Passed

Description

92%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 strong description: concrete capabilities, an explicit 'Use when...' trigger clause, and firm anchoring to a specific package. The only weakness is that the natural vocabulary of the task itself — 'theme'/'theming' — is absent from the trigger terms, so a user asking to 'change the theme' may not match it.

Suggestions

Add 'theming', 'custom theme', or 'change the theme' to the 'Use when' clause — the skill's own subject vocabulary is the most likely user phrasing but never appears in the description.

Consider adding 'brand colors' / 'palette' as trigger synonyms to widen natural-term coverage toward anchor 5.

DimensionReasoningScore

Specificity

The description lists multiple concrete, package-specific actions — 'Customize colors, branding, dark mode, and visual tokens', 'overriding Bulma --bulma-* CSS variables', 'setting fonts/radius/spacing tokens', 'configuring the app-wide icon library / class prefix via ConfigProvider' — with comprehensive coverage of the skill's scope. It exceeds anchor 4 ('minor gaps in coverage'): every capability in the body (recolor, tokens, dark mode, icons/prefix) is named.

5 / 5

Completeness

Explicitly answers both parts: what ('Customize colors, branding, dark mode, and visual tokens of an app built with @allxsmith/bestax-bulma') and when ('Use when changing the primary/brand color, recoloring components, overriding Bulma --bulma-* CSS variables, ... via ConfigProvider') with concrete trigger phrases. This is a direct match to the anchor-5 example pattern; not 4, since the 'when' clause is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Good natural-phrase coverage: 'changing the primary/brand color', 'recoloring components', 'adding light/dark mode', 'fonts/radius/spacing', 'icon library'. However the most natural user words for this skill — 'theme' / 'theming' / 'custom theme' — never appear in the description, nor do synonyms like 'palette' or 'skin'. This matches anchor 4 ('good keyword coverage; a few natural terms missing') rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description is pinned to a specific package ('@allxsmith/bestax-bulma') and specific mechanisms ('--bulma-* CSS variables', 'ConfigProvider'), giving it a clear niche with minimal overlap risk against generic styling or CSS skills. Distinct triggers; anchor 5.

5 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
allxsmith/bestax
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.