CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-color-spy-ext

Fully-functional, zero-build Chrome extension for inspecting CSS colors, fonts, and dimensions with Shadow-DOM. Use when: Deploy a professional CSS inspector to the Chrome Web Store in minutes; Create a font-matching tool that sits on top of any website; Build a pixel-perfect design overlay that avoids host-page CSS leaks.

Quality

62%

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 ./plugins/nex-browser-extensions/skills/nex-color-spy-ext/SKILL.md

The canonical home for this skill is nex-color-spy-ext in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

25%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 marketing README rather than an actionable skill: it promotes a codebase that is not present, references an assets/extension/ path that does not exist, and spends most of its tokens on a promotional FAQ and repeated branding. Claude reading it learns what the extension is but has no instructions, code, or files to accomplish anything.

Suggestions

Ship the actual extension source (manifest.json, Shadow-DOM content script, service worker) in assets/ or references/ and make the SKILL.md reference match the real paths — currently 'assets/extension/' does not exist and the body admits the source is missing.

Replace the FAQ and 'Why use this skill?' marketing sections with actionable content: the file layout of the extension, how to customize the hotkey/panel/metrics, and concrete Chrome Web Store packaging steps (zip structure, icons, listing requirements).

Add a sequenced workflow with validation checkpoints, e.g.: 1) copy the extension folder, 2) load unpacked at chrome://extensions, 3) verify the inspector panel renders via Shadow-DOM on a test page, 4) zip the folder for Web Store upload.

DimensionReasoningScore

Conciseness

The body is padded with promotional sections that earn no tokens: 'battle-hardened codebase', 'Why use this skill?', a six-question marketing FAQ, and branding repeated twice ('Built by Nex AI. More skills...'). It does not explain known concepts (so not a 1), but several entire sections are unnecessary filler.

2 / 5

Actionability

The only concrete guidance is the install hint ('navigate to chrome://extensions... enable Developer mode... Load unpacked') and the Alt+Shift+I hotkey mention. No code, no manifest example, no file layout, and the extension source itself is absent, so Claude cannot actually execute the skill's stated purpose — minimal guidance with the specific steps missing.

2 / 5

Workflow Clarity

There is only a rough install sequence buried in FAQ prose ('download the source files, navigate to chrome://extensions, enable Developer mode, click Load unpacked'); no build, customize, verify, or package workflow is sequenced, and validation steps are absent. Not 1 because that install sequence and the 'When to use' list give a rough, if gappy, order.

2 / 5

Progressive Disclosure

Section headers exist, but the skill ships no bundle files at all (no references/, scripts/, or assets/ directories) and its one path reference — 'I've generated the extension in assets/extension/' — points to a non-existent location, while the body itself concedes the source 'is not in this folder'. For a skill whose entire value is a code bundle, this is minimal structure with a broken, unfulfilled reference.

2 / 5

Total

8

/

20

Passed

Description

83%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-constructed: it states concrete capabilities in third person and pairs them with an explicit, multi-scenario 'Use when:' clause, satisfying both what and when. The main weakness is marketing-flavored padding ('Fully-functional', 'in minutes', 'pixel-perfect') that adds over-claim without informational value, and a few natural trigger synonyms are missing.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities ('inspecting CSS colors, fonts, and dimensions with Shadow-DOM', 'zero-build') rather than vague language. It falls short of 5 because 'Fully-functional' and 'in minutes' are over-claim padding, and real features (clipboard copy, hotkeys) are omitted.

4 / 5

Completeness

It explicitly answers both parts: a clear 'what' ('Chrome extension for inspecting CSS colors, fonts, and dimensions with Shadow-DOM') and an explicit 'Use when:' clause with three concrete scenarios (deploy to the Chrome Web Store, create a font-matching tool, build a design overlay). This matches the anchor-5 pattern of explicit what-and-when with concrete triggers better than anchor 4's generic 'when'.

5 / 5

Trigger Term Quality

Natural terms users would say are present: 'Chrome extension', 'CSS inspector', 'colors', 'fonts', 'Chrome Web Store', 'design overlay'. A few common variants are missing (e.g., 'color picker', 'eyedropper', 'inspect element'), keeping it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche (CSS color/font inspection browser extension) is distinct with specific triggers, so minimal conflict with unrelated skills. Not 5 because 'Build a pixel-perfect design overlay' and generic Chrome-extension requests could overlap with other web-dev/extension skills.

4 / 5

Total

17

/

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

plugins/nex-browser-extensions/skills/nex-color-spy-ext/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.