AF skill-tailwind
Write, configure, migrate, and review modern Tailwind CSS v4 (CSS-first) in any stack or none — framework-agnostic, examples are plain HTML + CSS/SCSS. Use whenever setting up Tailwind, doing a v3->v4 migration (@tailwind->@import, JS config->@theme), defining a reusable design-token / color system + dark mode via @theme, choosing between the two organizing approaches — (A) utility-first classes in markup and (B) BEM + @apply in SCSS grouped by property type — wiring responsive @variant and states, debugging @apply / @reference in component styles, or reviewing Tailwind code. Not for: choosing brand color VALUES or palettes, JS theme libs, cn()/clsx/tailwind-merge glue, vanilla-JS component behavior, non-Tailwind CSS frameworks, general CSS Q&A, or build/CI and generic postcss tooling.
Write, configure, migrate, and review modern Tailwind CSS v4 (CSS-first) in any stack or none — framework-agnostic, examples are plain HTML + CSS/SCSS.
As a process F 39/100 · Will not run — References files that are not bundled: references/v4-rules.md, references/gotchas.md, references/build-integration.md
The same skill appears in 1 more place: ClawHub
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/v4-rules.md - warning
missing-refreference to a missing file: references/gotchas.md - warning
missing-refreference to a missing file: references/build-integration.md - warning
missing-refreference to a missing file: references/tokens.md - warning
missing-refreference to a missing file: references/approaches.md - warning
missing-refreference to a missing file: references/components.md - warning
missing-refreference to a missing file: references/plugins.md - warning
missing-refreference to a missing file: references/editor-setup.md - warning
missing-refreference to a missing file: references/review.md - warning
missing-refreference to a missing file: examples/README.md - warning
missing-refreference to a missing file: scripts/check-v3-antipatterns.mjs - warning
missing-refreference to a missing file: scripts/lint-dynamic-classes.mjs - warning
missing-refreference to a missing file: scripts/README.md
Process rating: all ten parameters 39/100
- 0Tools and files. 13 referenced file(s) missing: references/v4-rules.md, references/gotchas.md, references/build-integration.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Steps. 47 steps, 4 vague phrases
- 70Execution cost. Instruction body is 4879 tokens
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 796: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 47 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.