CtrlK
BlogDocsLog inGet started
Tessl Logo

preline-theme-generator

Generate, preview, save, or validate Preline theme CSS using the bundled local generator in this skill. Use when the user asks to create a new Preline theme, match a brand color, translate a mood into a theme, generate light and dark theme CSS, preview theme output without writing files, or review and fix generated theme tokens. Do not use for generic non-Preline CSS work or arbitrary command execution.

68

Quality

85%

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

71%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 concise, well-structured, and gives a clear sequenced workflow with named scripts and a validation step. The decisive weakness is bundle completeness: the entire workflow depends on six referenced doc files that are absent from the skill, breaking navigation.

Suggestions

Ship the missing referenced docs (docs/workflow.md, docs/palette-guidance.md, docs/final-output-style.md, docs/validation-checklist.md, docs/token-reference.md, examples.md) or remove the references and inline the essential instructions.

Add at least one concrete example invocation of scripts/run-theme-generator.js (with normalized inputs) so generation is copy-paste ready without opening the missing docs.

Add an explicit validate→fix→re-validate feedback loop in the Workflow section rather than only a single "Validate" step pointing to an external checklist.

Drop the redundant "Key References" section or fold it into "Read Order" to remove duplication.

DimensionReasoningScore

Conciseness

Lean, imperative body with no conceptual padding about CSS/Preline, but the "Key References" list duplicates files already cited in "Read Order" and "Follow docs/workflow.md" restates Read Order step 1 — minor trim opportunities.

4 / 5

Actionability

Concrete, specific guidance: names exact scripts (scripts/find-themes-dir.js, scripts/run-theme-generator.js) and a numbered 7-step workflow with per-step doc reads. Minor gap: no inline sample command invocation for the generator.

4 / 5

Workflow Clarity

Clear sequenced process (Read Order 1-6, Workflow 1-7) with an explicit validation checkpoint (step 6: "Validate with docs/validation-checklist.md"). Not a 5 because no inline validate→fix→retry feedback loop is shown in the body itself.

4 / 5

Progressive Disclosure

The SKILL.md itself is well-organized with clearly signaled one-level-deep references, but scored against the actual bundle: 6 of the 7 referenced docs (docs/workflow.md, palette-guidance.md, final-output-style.md, validation-checklist.md, token-reference.md, examples.md) do not exist, so most navigation links lead nowhere.

3 / 5

Total

15

/

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 well-crafted description: third-person voice, concrete actions, an explicit "Use when" trigger clause, and a clear negative boundary. The only gap is the absence of synonyms and file extensions in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Generate, preview, save, or validate Preline theme CSS", "match a brand color", "translate a mood into a theme", "generate light and dark theme CSS", "review and fix generated theme tokens" — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both "what" (generate/preview/save/validate Preline theme CSS) and "when" with a concrete "Use when the user asks to..." clause enumerating trigger scenarios, matching the 5-anchor.

5 / 5

Trigger Term Quality

Strong natural trigger phrases ("create a new Preline theme", "match a brand color", "translate a mood into a theme", "preview theme output") that users would actually say, but lacks synonyms and file extensions (.css), which the 5-anchor requires.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Preline theme CSS via a bundled local generator) reinforced by an explicit negative boundary ("Do not use for generic non-Preline CSS work or arbitrary command execution"), giving minimal conflict risk.

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
htmlstreamofficial/preline
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.