CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tailwind-4-docs

Comprehensive Tailwind CSS v4 documentation snapshot and workflow guidance. Use when answering Tailwind v4 questions, selecting utilities/variants, configuring Tailwind v4, or migrating projects from v3 to v4 with official docs and gotcha checks.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 body is a well-structured, highly actionable overview with excellent workflow gating and verified one-level-deep references. The main flaw is localized redundancy: the snapshot-staleness rule and the licensing note are each repeated multiple times and could be consolidated into a single authoritative statement.

Suggestions

State the staleness rule (missing or older than one week) once — in Initialization — and have Quick start step 2 reference it with a single sentence instead of restating the full gate and its rationale.

Consolidate the source-available licensing explanation into the Initialization section and drop the duplicate framing in Overview, keeping only a brief pointer (the --accept-docs-license flag already carries the operational reminder).

Use one consistent invocation path for the sync script (the Update workflow's bare `scripts/sync_tailwind_docs.py` differs from the fully qualified path in Initialization) so the command is unambiguous.

DimensionReasoningScore

Conciseness

Mostly efficient, but the snapshot staleness rule ("missing or older than one week... do not proceed") is repeated nearly verbatim in both Quick start and Initialization, and the source-available licensing note appears three times (Overview, Initialization, and the command flag). This redundancy is more than the minor trimming of the anchor above.

3 / 5

Actionability

Provides a copy-paste-ready initialization command with the exact flag, concrete file paths to check for snapshot state, specific entry-point docs for each task type, and named tooling packages. All referenced bundle files and script flags (e.g., --local-repo, --accept-docs-license) were verified to exist.

5 / 5

Workflow Clarity

The Quick start is a clear 7-step sequence with an explicit existence/staleness checkpoint and a hard gate ("Do not answer the user's question until the snapshot is initialized"), plus error-recovery paths: asking the user to run the command manually, a blocked-initialization fallback to gotchas.md, and a migration checklist. This is a doc-lookup skill with no destructive or batch operations, so no cap applies.

5 / 5

Progressive Disclosure

The body is a lean overview with a References map that signals each file's purpose and a Common entry points section for navigation. References are one level deep, and the actual bundle structure checks out: engineering-playbook.md, gotchas.md, and docs-source.txt exist, while references/docs/ and docs-index.tsx are clearly documented as runtime-generated.

5 / 5

Total

18

/

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 strong description that clearly states what the skill provides and when to use it, with version-specific trigger phrases that make it highly distinguishable. The only weaknesses are the slightly abstract capability phrasing and a few missing natural synonyms such as "upgrade" or "styling".

DimensionReasoningScore

Specificity

Lists several concrete tasks ("answering Tailwind v4 questions, selecting utilities/variants, configuring Tailwind v4, or migrating projects from v3 to v4"), but the core capability statement "documentation snapshot and workflow guidance" is a noun-phrase abstraction rather than a concrete action, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both parts: the "what" ("Comprehensive Tailwind CSS v4 documentation snapshot and workflow guidance") and a concrete "Use when..." clause with four specific trigger scenarios, matching the top anchor's pattern of what + explicit trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say such as "Tailwind v4 questions", "selecting utilities/variants", "configuring Tailwind v4", and "migrating projects from v3 to v4". A few natural terms are missing (e.g., "upgrade", "classes", "styling", "CSS"), so it falls short of the comprehensive synonym coverage of the top anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche by pinning the framework and version ("Tailwind CSS v4", "migrating projects from v3 to v4") with domain-specific triggers, so it is unlikely to fire for unrelated skills.

5 / 5

Total

18

/

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

referenced_paths_exist

Referenced path issues: 11 possibly missing (references/docs-index.tsx, references/docs/, references/docs/adding-custom-styles.mdx, references/docs/compatibility.mdx, references/docs/detecting-classes-in-source-files.mdx, +6 more), 9 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.claude/cloud-profile/skills/tailwind-4-docs/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.