CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-font-grab-ext

Ship a professional Chrome extension that identifies fonts, extracts CSS, and finds Google Font matches. Use when: Extract CSS and Tailwind font styles from any website instantly; Identify paid fonts and find their closest free Google Font alternatives; Fork a production-ready Manifest V3 overlay extension archetype.

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-font-grab-ext/SKILL.md

The canonical home for this skill is nex-font-grab-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 operating instructions: it promotes a codebase it explicitly does not include, and every reference to extension source files is broken because no bundle files exist. A Claude invoking this skill would have nothing concrete to execute, only descriptive copy and a generic Chrome loading walkthrough.

Suggestions

Include the actual Manifest V3 extension source in assets/ (or scripts/) so the referenced paths (assets/extension/, fontmatch.js, content.js) resolve, and replace the fictional 'Result' dialog with real instructions for using those files.

Replace the FAQ and promotional sections ('Why use this skill', 'Questions', footer links) with actionable guidance: manifest structure, how to modify the font-mapping JSON, and concrete export-format examples (CSS, shorthand, Tailwind).

Add a real workflow with validation checkpoints, e.g. load unpacked -> verify the overlay activates on a test page -> confirm font match output, so failures have a recovery path.

DimensionReasoningScore

Conciseness

The FAQ section ('What exactly is included...', 'How does this skill differ...') restates the 'What you get' section, and promotional links to nex-ai.be, slopsome.com, and a paid catalog are pure padding. Several sections add no instructional value, matching anchor 2 rather than 1 since it doesn't explain concepts Claude already knows.

2 / 5

Actionability

No code or commands beyond generic chrome://extensions loading steps, and the core deliverable is explicitly absent ('Scripts, extension source, and templates from the original package are not in this folder'). References to assets/extension/, fontmatch.js, and content.js point to files that do not exist in the bundle, so there is nothing executable to act on.

2 / 5

Workflow Clarity

Only a loose implied sequence (generate source, then load unpacked) inside a fictional Example dialog, with no validation steps; the first step depends on files missing from the bundle. This matches anchor 2 (rough sequence, many gaps, validation absent) and is not a destructive/batch skill so the cap-3 rule is not binding.

2 / 5

Progressive Disclosure

Scored against the actual bundle structure: no references/, scripts/, or assets/ directories exist, so the body's references to assets/extension/, fontmatch.js, and content.js are all dangling. Structure is minimal with broken references, fitting anchor 2 rather than 3 (references are not merely unclear, they resolve to nothing).

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 strong: it states concrete capabilities and provides an explicit 'Use when:' clause with natural trigger phrases, giving it excellent completeness and distinctiveness. Its only weaknesses are light marketing fluff and a few missing user-side synonyms for font identification.

DimensionReasoningScore

Specificity

Names concrete actions ('identifies fonts, extracts CSS, and finds Google Font matches') with qualified triggers, but carries minor fluff ('professional', 'production-ready... archetype') and an unqualified 'extracts CSS'. Fits anchor 4 (several specific actions, minor gaps) rather than 5 (comprehensive without padding).

4 / 5

Completeness

Explicitly answers both 'what' (identify fonts, extract CSS, find Google Font matches in a Chrome extension) and 'when' via a concrete 'Use when:' clause with three trigger phrases, matching anchor 5 exactly.

5 / 5

Trigger Term Quality

Good natural coverage: 'Chrome extension', 'fonts', 'Tailwind font styles', 'Google Font', 'paid fonts'. Missing common user phrasings like 'what font is this' or 'font detector', so anchor 4 fits better than 5.

4 / 5

Distinctiveness Conflict Risk

Clear font-identification niche, but the bare 'extracts CSS' in the what-clause invites minor overlap with generic CSS-extraction or scraping skills, matching anchor 4 rather than 5.

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-font-grab-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.