CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-single-section-html

Generate a zero-dependency, single-file HTML hero section for rapid prototyping and placeholder pages. Use when: Spin up a "coming soon" page in seconds; Prototype hero layouts without a build step; Create lightweight, single-file landing pages for domain parking.

Quality

64%

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-single-section-html/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%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 reads as a product marketing page rather than operational instructions: it promotes the skill, answers sales-style questions, and links to a paid catalog, but never provides the template or specification needed to generate the hero section consistently. Structure and headers are reasonable, but the substance is missing.

Suggestions

Include the actual hero-section HTML template (or a precise structural spec: tag hierarchy, centered-layout CSS approach, and the full list of {{PLACEHOLDER}} tokens) so the output is deterministic instead of invented.

Replace the FAQ, 'Why this beats prompting it yourself', and purchase/footer promo sections with a short workflow: where to write the file (e.g., assets/hero.html), how to fill placeholders, and how to verify the result renders in a browser.

State the output convention explicitly (filename, placeholder naming, zero-dependency constraint) in a single 'Output' section, cutting the body to the essentials Claude needs to execute.

DimensionReasoningScore

Conciseness

Multiple sections are padding that Claude does not need: 'Why this beats prompting it yourself', a five-question FAQ that largely restates the description, 'What exactly is included in my purchase', and a promotional footer. It does not hit level 1 because it never explains basic concepts Claude already knows.

2 / 5

Actionability

No HTML template, code, or placeholder inventory is ever shown; the only concrete hints are 'Generated assets/hero.html' and the '{{PLACEHOLDER}}' syntax, leaving the actual output to be invented. It rises above level 1 only because the file path, placeholder convention, and 'clean, centered hero layout' target are stated.

2 / 5

Workflow Clarity

The single task (generate a hero section file) is identifiable from the description and example, but the expected output is never specified — no template, structure, or file-writing convention — so the action is not unambiguous enough for the simple-skill score of 5.

3 / 5

Progressive Disclosure

The body has clear section headers and needs no external references for a skill this simple, but most of the inline content (FAQ, marketing, purchase information) is material that does not belong in a skill at all, which is worse than the 'minor organization gaps' of level 4.

3 / 5

Total

10

/

20

Passed

Description

78%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 strong description: third-person, concise, with an explicit 'Use when:' clause containing concrete, natural trigger phrases. Its main gaps are limited action coverage (one action) and some missing common synonyms.

DimensionReasoningScore

Specificity

The description names the domain ('zero-dependency, single-file HTML hero section') with one concrete action and qualifiers, but does not list several distinct actions like the level-4 anchor requires.

3 / 5

Completeness

It explicitly answers both 'what' ('Generate a zero-dependency, single-file HTML hero section for rapid prototyping and placeholder pages') and 'when' with three concrete 'Use when:' trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like '"coming soon" page', 'hero layouts', 'landing pages', 'domain parking', and 'placeholder pages' cover common user phrasings well, but a few natural synonyms (e.g., 'one-pager', 'static page', 'simple website') are missing.

4 / 5

Distinctiveness Conflict Risk

The niche (single-section hero, coming soon, domain parking) is clear with distinct triggers, but generic landing-page or web-page generation requests could overlap with broader web development 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-single-section-html/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.