CtrlK
BlogDocsLog inGet started
Tessl Logo

landing-page-generator

Generate complete, deploy-ready landing pages from any repository. Use when creating a homepage for an open-source project, building a project website, converting a README into a marketing page, or standardizing landing pages across multiple repos.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./examples/skills/landing-page-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 thorough, well-structured guide with concrete commands, an extraction map, output structure, and a validation checkpoint. Its main weaknesses are moderate verbosity from inlined reference material that duplicates existing bundle files and progressive-disclosure gaps where bulk content could be moved to references/assets.

Suggestions

Move the CSS variables and component-class reference into assets/styles-base.css or references/landing-pattern.md and replace the inline blocks with a one-line pointer to keep SKILL.md lean.

Condense the 12-item Section Generation list into the essential ordering rules and delegate per-section markup details to the section-snippet files in assets/section-snippets/.

Turn Step 5's validation checklist into an explicit feedback loop (e.g., 'If a link or contrast check fails, fix and re-verify before finalizing') to strengthen workflow clarity for a batch-generation skill.

DimensionReasoningScore

Conciseness

Mostly efficient and task-specific, but the inlined CSS variables block (~25 lines) and full component-class listing duplicate material that lives in assets/styles-base.css and could be trimmed or referenced.

3 / 5

Actionability

Concrete commands, an options table, a file-structure tree, a README-to-section extraction map, and a real GitHub Actions workflow in assets give mostly executable guidance with only minor gaps.

4 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced and Step 5 provides an explicit validation checkpoint covering rendering, links, responsiveness, and accessibility, though it is a checklist rather than a fix-and-retry feedback loop.

4 / 5

Progressive Disclosure

Sections are well organized and references/landing-pattern.md plus assets/ are real and signaled at the end, but substantial reference material (CSS variables, component classes, the full 12-section spec) is inlined in SKILL.md rather than offloaded to the existing reference/assets files.

3 / 5

Total

14

/

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 strong, third-person description that clearly states what the skill does and gives multiple explicit 'Use when' triggers. It is concrete and comprehensive, with only minor gaps in trigger synonym coverage and a small overlap risk with adjacent site-generation skills.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'Generate complete, deploy-ready landing pages', 'converting a README into a marketing page', 'building a project website' — with only minor gaps (no mention of search/deploy specifics).

4 / 5

Completeness

Explicitly answers both 'what' ('Generate complete, deploy-ready landing pages from any repository') and 'when' ('Use when creating a homepage... building a project website, converting a README...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural phrases users would say — 'homepage', 'project website', 'README into a marketing page', 'landing pages' — though a few common variants like 'project site' are absent.

4 / 5

Distinctiveness Conflict Risk

Repo-to-landing-page niche is mostly distinct with clear triggers, though there is minor overlap risk with general static-site or documentation-site 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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
FlorianBruniaux/claude-code-ultimate-guide
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.