CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-prompt-booster-ext

The complete Nex Prompt Booster Chrome extension (real shipped Manifest V3 source): turn short, lazy AI prompts into detailed, structured, expert-quality prompts instantly, right inside ChatGPT, Claude, Gemini, Perplexity and Grok, with no API calls. Ships the full extension plus the dev loop, customization guide, and Web Store packaging steps. No build step. Use when: Generate a production-ready site for a real estate agency or makelaar; Create a self-managed property portal using a Firebase backend; Inject RealEstateAgent JSON-LD schema for SEO and AI search visibility.

Quality

40%

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-prompt-booster-ext/SKILL.md

The canonical home for this skill is nex-prompt-booster-ext in NexaiGuy/nex-ai-skills

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 is a promotional README for a Chrome extension that ships none of its claimed materials: no source, no scripts, no guides, and no actionable steps. It reads as marketing copy with a redundant FAQ, and its 'When to use' and 'Example' sections describe an unrelated real-estate website skill, leaving Claude with nothing to execute.

Suggestions

Actually include the claimed bundle (extension source, dev loop, customization guide, packaging steps) as files under references/ or scripts/, and reference them explicitly from the body with clear navigation — currently the body admits they are absent.

Add executable guidance: the 'load unpacked' setup at chrome://extensions, the dev loop (edit → refresh → test on a target site), and the Chrome Web Store packaging steps the description promises.

Delete the FAQ section (it restates the overview) and replace the real-estate 'When to use' and 'Example' sections with a prompt-boosting example (short input prompt → boosted output) consistent with what the skill actually does.

DimensionReasoningScore

Conciseness

The six-question FAQ section largely restates the overview (e.g. 'no external API calls are made and no prompt data is sent to third-party servers' repeats the intro's 'no API calls, no servers, and no data leaving your browser'), and repeated promotional footers ('Built by Nex AI. More skills and info at https://nex-ai.be') add tokens without instructing anything. This matches anchor 2 ('noticeably verbose; several unnecessary explanations or padded sections'); it is not anchor 1 because most sentences at least convey a fact about the extension.

2 / 5

Actionability

The body contains no executable guidance at all — no commands, no code, no steps for loading the unpacked extension, customizing the booster logic, or packaging for the Web Store, despite the description promising 'the dev loop, customization guide, and Web Store packaging steps'. It only describes ('You receive the complete Manifest V3 source code...', 'you can easily modify the logic'), matching anchor 1 ('only describes rather than instructs') exactly; anchor 2's 'high-level hints' are not even present as steps.

1 / 5

Workflow Clarity

No multi-step process is sequenced anywhere in the body — there is no dev loop, no setup sequence, no validation or verification steps, only an 'Example' showing a past result for an unrelated real-estate task. This matches anchor 1 ('steps missing or incoherent; no sequence; no validation').

1 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and the body admits 'Scripts, extension source, and templates from the original package are not in this folder' — so the customization guide, dev loop, and packaging steps the skill is supposed to disclose are simply missing rather than one level deep. The inline FAQ padding and the claimed-but-absent split leave structure minimal, matching anchor 2; it avoids anchor 1 because section headers do exist and navigation of what little content there is remains possible.

2 / 5

Total

6

/

20

Passed

Description

38%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 communicates a clear 'what' (local, no-API prompt rewriting injected into AI chat sites) but is padded with promotional language. Its critical defect is that the 'Use when' triggers belong to a different skill (real-estate site generation), which both fails to guide correct usage and creates direct conflict risk with unrelated skills.

Suggestions

Replace the 'Use when:' clause with triggers matching the actual capability, e.g. 'Use when the user wants to improve, expand, or rewrite an AI prompt, or asks about the Nex Prompt Booster Chrome extension, prompt quality, or boosting prompts in ChatGPT/Claude/Gemini/Perplexity/Grok.'

Remove the real-estate site, Firebase portal, and JSON-LD schema trigger phrases entirely — they describe a different skill and create conflict risk with website-generation skills.

Trim marketing padding ('The complete', 'real shipped', 'instantly', 'expert-quality') and keep the concrete capability statements: local in-page rewriting, no API calls, Manifest V3 source, no build step.

DimensionReasoningScore

Specificity

Concrete actions are present — 'turn short, lazy AI prompts into detailed, structured, expert-quality prompts', 'no API calls', 'Ships the full extension plus the dev loop, customization guide, and Web Store packaging steps' — but they are wrapped in marketing fluff ('The complete', 'real shipped', 'instantly', 'expert-quality') that the guidelines say to penalize. It names the domain and a couple of real actions without comprehensive coverage, matching anchor 3 better than anchor 4's 'several specific actions with minor gaps'.

3 / 5

Completeness

The 'what' is clear and explicit ('turn short, lazy AI prompts into detailed, structured, expert-quality prompts... right inside ChatGPT, Claude, Gemini, Perplexity and Grok'), but although a 'Use when:' clause exists, its contents describe unrelated real-estate functionality, so the 'when' guidance is effectively invalid rather than merely imprecise. This sits between anchor 3 ('clear what, when missing or only weakly implied') and anchor 4 ('both present, when could be more specific') — the explicit-but-wrong when clause is weaker than anchor 4 requires.

3 / 5

Trigger Term Quality

The 'Use when' triggers are 'Generate a production-ready site for a real estate agency or makelaar; Create a self-managed property portal using a Firebase backend; Inject RealEstateAgent JSON-LD schema' — natural phrases, but for a website-generation skill, not this one; the phrases a user of this skill would say ('improve my prompt', 'rewrite this prompt', 'Chrome extension') are absent. Platform names (ChatGPT, Claude, Gemini) are the only relevant keywords, matching anchor 2's 'one or two generic keywords; missing the natural phrases users say' rather than anchor 1's pure jargon.

2 / 5

Distinctiveness Conflict Risk

The real-estate 'Use when' triggers would cause this skill to fire in direct conflict with any real-estate or website-generation skill, and the broad prompt-improvement framing overlaps any prompt-writing skill. This matches anchor 2 ('very broad; high overlap risk with many similar skills'); it avoids anchor 1 only because the Manifest V3 / browser-extension framing gives it some identity.

2 / 5

Total

10

/

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

NexaiGuy/nex-ai-skills

Path

plugins/nex-browser-extensions/skills/nex-prompt-booster-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.