CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-brand-palette-lite

Extract brand color hex codes from a website's CSS variables into a portable Python script. Use when: Identify primary and accent brand colors from a live URL; Generate a reusable Python script for color audits; Speed up UI development by matching existing design tokens.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/nex-brand-palette-lite/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a marketplace listing repurposed as a skill: it markets capabilities convincingly but delivers no executable content — no code, no steps, and a generated-script example pointing at a file the body itself admits is absent. The FAQ, purchase-oriented questions, and promotional footer consume the token budget without instructing Claude on how to perform the extraction.

Suggestions

Ship the actual extraction logic: either inline a complete, standard-library-only Python script that fetches a URL and filters --primary/--accent/--brand variables, or include assets/palette_lite.py in the bundle and reference it accurately.

Replace the promotional sections ("Why this beats prompting it yourself", the six-question FAQ, and the footer links) with a concrete workflow: fetch the URL → parse CSS custom properties → filter brand-token conventions → emit the script, with a validation step (e.g., check that at least one matching variable was found and warn on login-walled or shadow-DOM sites).

Fix or remove the dangling assets/palette_lite.py reference, since the body states the scripts are not in this folder.

DimensionReasoningScore

Conciseness

The body is noticeably padded: the six-question FAQ (e.g., "What specific assets are included in this purchase?"), "Why this beats prompting it yourself", and the storefront footer are marketing copy that adds no instructional value Claude needs — anchor 2. Not 1: it does not explain basic concepts Claude already knows; not 3: the padding is substantial sections, not minor trimming.

2 / 5

Actionability

Only high-level hints are given — "Filters for specific naming conventions like --primary, --accent, and --brand", "Operates using only standard libraries" — with no executable code, commands, or extraction logic anywhere, and the referenced script is explicitly absent ("Scripts... are not in this folder") — anchor 2. Not 1: the naming conventions and stdlib-only constraint are concrete, specific hints; not 3: there is no code or step a reader could execute.

2 / 5

Workflow Clarity

A rough implied sequence exists in the "What it does" bullets (scrape URL → filter variables → generate script), but there are many gaps: no ordered steps, no commands, and no validation or error handling for the scraping/generation flow — anchor 2. The simple-skill exception does not apply because the action itself is never specified unambiguously.

2 / 5

Progressive Disclosure

Sections are well-organized with clear headers and the skill is short, but the example result cites "assets/palette_lite.py" which does not exist in the bundle (no references/, scripts/, or assets/ directories), and storefront FAQ content that belongs outside the skill is inlined — anchor 3. Not 2: the structure is genuinely clear and navigable; not 4: the dangling file reference and misplaced marketing content are real organization problems.

3 / 5

Total

9

/

20

Passed

Description

75%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 well-formed: it uses third person, states a concrete what, and includes an explicit "Use when:" clause with mostly relevant triggers. It falls just short of the top anchors because one trigger is a benefit statement, the trigger list lacks common synonyms like "palette" or "theme colors", and coverage is narrowly focused on extraction.

Suggestions

Rewrite the 'Use when' items as user-mention triggers (e.g., 'Use when the user mentions brand colors, a site's color palette, or design tokens') instead of restating capabilities or benefits like 'Speed up UI development'.

Add natural synonyms such as 'color palette', 'theme colors', or 'CSS custom properties' to improve trigger term coverage.

DimensionReasoningScore

Specificity

"Extract brand color hex codes from a website's CSS variables into a portable Python script" names several concrete actions (extract hex codes, target CSS variables, generate a portable script), matching anchor 4. Not 5: coverage is extraction-only and "Speed up UI development by matching existing design tokens" is a generic benefit rather than a specific action; not 3: multiple concrete actions are listed beyond a minimal 1-2.

4 / 5

Completeness

Both parts are explicit: a clear "what" ("Extract brand color hex codes... into a portable Python script") and an explicit "Use when:" clause with three trigger scenarios, matching anchor 4. Not 5: the first two triggers largely restate the what and the third ("Speed up UI development...") is a benefit statement rather than a concrete trigger phrase like "when the user mentions...".

4 / 5

Trigger Term Quality

Good natural keyword coverage: "brand colors", "hex codes", "CSS variables", "color audits", "design tokens", "live URL" — terms users would actually say. Not 5: common synonyms and variations like "color palette", "theme colors", "color scheme", or ".css" are missing; not 3: coverage goes well beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

"Brand color hex codes from a website's CSS variables" is a clear niche with distinct triggers (CSS variables, brand colors, color audits), so it is mostly distinct with only minor overlap risk against general web-scraping or design-token skills — anchor 4. Not 5: "Speed up UI development" broadens it into territory shared with general UI/design skills.

4 / 5

Total

16

/

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: 1 missing

Warning

Total

15

/

16

Passed

Repository

NexaiGuy/nex-ai-skills

Path

skills/nex-brand-palette-lite/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.