CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

css-best-practices

Regras e boas práticas para organização e uso de CSS

Quality

57%

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 ./skills/frontend/css/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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.

The content is a well-structured, largely actionable rulebook with concrete code examples for CSS organization, minification, per-page loading, and Django deployment. Its main weaknesses are duplicated sections that pad the token budget and missing validation steps for the batch build/minification workflow.

Suggestions

Merge the duplicated file-responsibility lists ('Estrutura de Pastas' and 'Organização' repeat the same mapping) and fold 'Carregamento' into 'Versões Minificadas Obrigatórias' to remove redundant sections.

Add an executable minification command (e.g., `npx cssnano styles/app.css styles/app.min.css`) and a post-build verification step (confirm each .min.css exists and is smaller) to close the workflow validation gap for batch operations.

Remove the 'why minified files are better' bullets (larger files, slower loading) — Claude already knows minification benefits — or move the Django production/collectstatic/nginx detail into a reference file.

DimensionReasoningScore

Conciseness

The body is mostly terse rules with code, but it has redundant padding: the file-responsibility mapping is duplicated across 'Estrutura de Pastas' and 'Organização', 'Carregamento' restates the 'Versões Minificadas Obrigatórias' rules, and 'Impacto negativo no carregamento / Arquivos maiores / Performance reduzida' explains minification benefits Claude already knows. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') — below 4 due to the duplicated sections, above 2 because the per-line style is lean.

3 / 5

Actionability

Concrete, executable guidance dominates: a folder tree, explicit .min.css naming, HTML <link> examples for per-page loading, an executable Django urls.py snippet, and the collectstatic command. It sits at anchor 4 ('mostly executable guidance with minor gaps') rather than 5 because the minification tools (cssnano, clean-css, csso) are named without a runnable command, and nginx configuration is mentioned without an example.

4 / 5

Workflow Clarity

Sequences are present (criar arquivo legível → minificar → carregar .min.css; manter legível → minificar no build) and an end Checklist exists, but batch operations (build-time minification of all CSS files, collectstatic) have no validation or verification steps and no feedback loops. Per the guideline capping batch workflows without validation at 3, this matches anchor 3 ('sequence present but checkpoints missing or implicit') rather than anchor 4.

3 / 5

Progressive Disclosure

The body is well-organized with clear section headers and a 'Referências' section signaling one-level-deep references (Django skill, templates path). It matches anchor 4 ('good structure; most content appropriately placed; minor organization gaps') rather than 5 because the 163-line body keeps everything inline — the Django static-file/production deployment detail would fit a reference file — and no reference files exist to justify the under-50-line exception.

4 / 5

Total

14

/

20

Passed

Description

36%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.

The description is a vague domain label rather than a capability statement: it says CSS rules and best practices but lists no concrete actions, no use-when trigger clause, and no natural keyword variations. Most of the skill's actual scope (minification pipeline, per-page loading, Django static files) is invisible from the description alone.

Suggestions

Rewrite the description to list concrete capabilities, e.g., 'Organizes CSS into per-type files under styles/, generates .min.css production versions, configures per-page stylesheet loading, and sets up Django static files (collectstatic/nginx)' — this moves specificity from anchor 2 toward 4-5.

Add an explicit trigger clause: 'Use when creating or organizing CSS files, configuring asset builds, minifying stylesheets, or setting up Django static file serving' — the missing 'when' currently caps completeness at 3 and the vague 'what' drops it to 2.

Fold natural trigger keywords into the description itself (CSS, .css files, stylesheet, minify, minification) instead of relying solely on the separate triggers field, and drop the generic 'boas práticas' framing.

DimensionReasoningScore

Specificity

The description 'Regras e boas práticas para organização e uso de CSS' names the domain (CSS) but the actions are generic ('organização e uso') with no concrete capabilities stated, matching the anchor 'Names the domain but actions are minimal or generic'. It falls below anchor 3 because no specific actions (e.g., minify files, structure folders, configure Django static files) are listed.

2 / 5

Completeness

The 'what' is vague ('Regras e boas práticas' is buzzword framing without saying what the skill actually does) and the 'when' is entirely absent — no 'Use when...' clause or equivalent. This matches anchor 2 ('Has a vague what and no when') and is below anchor 3, whose example lists concrete actions; the missing 'when' would cap the score at 3 regardless.

2 / 5

Trigger Term Quality

The description itself contains only the keyword 'CSS'; natural variations such as 'stylesheet', 'styles', 'minify', and the '.css' extension appear only in the separate triggers field, not in the description. This matches 'Some relevant keywords but missing common variations or synonyms' rather than anchor 4's good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

The description is scoped to CSS, which is somewhat specific, but 'uso de CSS' (use of CSS) is broad within the domain and could overlap with any frontend or styling skill. It matches anchor 3 ('Somewhat specific but could still overlap with similar skills') rather than anchor 4, since the niche is not tightly defined.

3 / 5

Total

10

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/cursor-multiagent-system

Path

skills/frontend/css/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.