CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-frame-it-ext

A production-ready, no-build Chrome Extension for creating professional device mockups from browser screenshots. Use when: Ship a professional screenshot-to-mockup tool with zero build configuration; Fork a working Manifest V3 "action-on-click" extension architecture; Create programmatic device frames using HTML5 Canvas instead of heavy assets.

Quality

56%

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 ./skills/nex-frame-it-ext/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

11%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 functions as a promotional landing page rather than skill instructions: it markets a paid package, explains Chrome basics Claude already knows, and contains no actionable guidance, code, or workflow. Critically, it admits the advertised source code is not included in the bundle, so the skill cannot accomplish its stated purpose.

Suggestions

Replace the marketing and FAQ sections with concrete instructions: loading the unpacked extension in chrome://extensions, where the manifest and frame-drawing code live, and how to add a new device frame.

Actually bundle the extension source (or at minimum a working manifest.json and one frame-drawing module) so referenced paths like assets/extension/ and frames/macbook.js exist and the Example section is achievable.

Provide a real dev-to-store workflow with sequenced steps and verification checkpoints (e.g., reload extension, test capture, validate zip structure) instead of only claiming a 'proven dev-to-store workflow' exists.

DimensionReasoningScore

Conciseness

The body is noticeably padded with marketing copy ('Unlike generic AI prompts that generate non-functional code snippets...'), repeated promotional links, and a five-question FAQ explaining concepts Claude already knows (Chrome Developer Mode loading, NPM/Webpack, Manifest V3 standards).

2 / 5

Actionability

There is no code, command, or executable instruction anywhere in the body; it only describes ('Includes a proven dev-to-store workflow and packaging guide') and the stated source is absent — 'Scripts, extension source, and templates from the original package are not in this folder'.

1 / 5

Workflow Clarity

No steps or sequence are provided; the 'Example' section is a fabricated dialogue claiming deployment to 'assets/extension/' and 'frames/macbook.js', paths that do not exist in the bundle.

1 / 5

Progressive Disclosure

Sections are clearly headed, but the only file references (assets/extension/, frames/macbook.js) point to nonexistent paths and the actual material is deferred to an external paid package rather than bundled reference files, leaving navigation broken.

2 / 5

Total

6

/

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.

A well-constructed description that explicitly states both capability and trigger conditions with mostly natural terminology. Its main weaknesses are a few missing synonyms for mockup framing and slight overlap risk with general Chrome extension development skills.

Suggestions

Add natural trigger synonyms users are likely to say, such as 'device frame', 'bezel', 'screenshot mockup', or named devices like 'MacBook' and 'iPhone'.

Narrow the 'Fork a working Manifest V3 extension architecture' trigger to screenshot/mockup-specific extension work to reduce overlap with generic Chrome extension development skills.

Mention the capture entry points (toolbar click, context menu, Alt+Shift+F) to round out capability coverage.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — 'creating professional device mockups from browser screenshots', 'programmatic device frames using HTML5 Canvas', forking a 'Manifest V3 action-on-click extension architecture' — with only minor gaps such as capture methods and specific device types.

4 / 5

Completeness

It clearly answers what ('a production-ready, no-build Chrome Extension for creating professional device mockups from browser screenshots') and explicitly provides when via a 'Use when:' clause with three concrete trigger scenarios, matching the top anchor.

5 / 5

Trigger Term Quality

Natural terms like 'Chrome Extension', 'browser screenshots', 'device mockups', and 'HTML5 Canvas' map well to what a user would say, though common variations ('bezel', 'device frame', named devices like MacBook) are missing.

4 / 5

Distinctiveness Conflict Risk

The screenshot-to-mockup niche is mostly distinct, but the 'Fork a working Manifest V3 extension architecture' trigger overlaps with generic Chrome-extension development skills, giving minor conflict risk rather than minimal.

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

skills/nex-frame-it-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.