SKILLEMALL.ai
RU Sign in

BF phy-css-dead-code

Unused CSS detector and dead selector auditor. Scans your stylesheet files against all HTML, JSX, TSX, Vue, and template files to find selectors that are defined but never referenced anywhere in your codebase. Detects CSS framework (Tailwind, Bootstrap, CSS Modules, vanilla CSS, Sass/SCSS) and applies the right analysis strategy for each. Reports estimated byte savings per dead rule, finds !important overuse, duplicate selectors, and orphaned media-query blocks. Generates a safe-deletion plan with exact grep verification commands. Works with PostCSS, Sass, Less, and raw CSS. Zero external API — uses npx and grep only. Triggers on "unused CSS", "dead CSS", "CSS bloat", "remove unused styles", "CSS cleanup", "what CSS can I delete", "/css-dead-code".

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 2 files body ≈ 4 386 tokens Open the sourcegithub.com↗ analyzed 20 h ago

Unused CSS detector and dead selector auditor.

As a process F 37/100 · Will not run — References files that are not bundled: [^"\']+, [a-z][a-z0-9-_]+

AnalyzerSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
F
37/100
Will not run
References files that are not bundled: [^"\']+, [a-z][a-z0-9-_]+
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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 description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: [^"\']+
  • warning missing-ref reference to a missing file: [a-z][a-z0-9-_]+
  • note edit-residue the text marks something as outdated (lines 48, 351, 395, 396, 397, 411): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 37/100

Will not run. References files that are not bundled: [^"\']+, [a-z][a-z0-9-_]+
  • 0Tools and files. 2 referenced file(s) missing: [^"\']+, [a-z][a-z0-9-_]+
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 11 mutating operations with no state check
  • 70When it triggers. States when to use, but not when not to
  • 70Execution cost. Instruction body is 4386 tokens
  • 100Steps. 10 steps
  • 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

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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +5Description quotes 7 example trigger phrases
  • +3Description length 758: enough signal without eating the budget
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 10 items
  • +4Has examples (18 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.