CtrlK
BlogDocsLog inGet started
Tessl Logo

landing-page-generator

Generates high-converting Next.js/React landing pages with Tailwind CSS. Uses PAS, AIDA, and BAB frameworks for optimized copy/components (Heroes, Features, Pricing). Focuses on Core Web Vitals/SEO.

59

Quality

68%

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/AI-Agents-Safe-Coding-Skills-claude/skills/landing-page-generator/SKILL.md

The canonical home for this skill is landing-page-generator in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 content is actionable and well-sequenced with a validation checkpoint, but it underuses its own bundle: detailed reference files exist yet their content is duplicated inline rather than linked, hurting progressive disclosure.

Suggestions

Replace the inlined Copy Frameworks and SEO Checklist sections with brief summaries that link to references/frameworks.md and references/seo-checklist.md, keeping only essential points inline.

Move the full Other Section Patterns into references/landing-page-patterns.md and reference it, so the body stays an overview.

Add an explicit re-validation step to the SEO workflow loop ('after fixing gaps, re-run the checklist until all items pass').

DimensionReasoningScore

Conciseness

The body is efficient — tables, a full code example, and checklists with no concept over-explanation, assuming Claude's competence. Not a 5 due to minor marketing-flavored prose ('Not lorem ipsum — actual copy that converts') and lightly padded intro lines.

4 / 5

Actionability

Provides a copy-paste Hero TSX component, concrete Tailwind class tables, and a specific char-count SEO checklist. Not a 5 because the other section patterns (Features, Pricing, FAQ) are described in prose rather than as full executable code.

4 / 5

Workflow Clarity

A clear 7-step numbered generation workflow includes an explicit validation step and an SEO checklist with a fix-inline feedback loop. Not a 5 because there is no explicit re-validate-after-fix checkpoint in the loop.

4 / 5

Progressive Disclosure

The body has good section structure but inlines the SEO checklist, copy frameworks, and page patterns that already exist as unreferenced bundle files in references/ (frameworks.md, seo-checklist.md, landing-page-patterns.md, conversion-patterns.md). Not a 4 because those references are never signaled or linked from the body.

3 / 5

Total

15

/

20

Passed

Description

66%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 specific and keyword-rich, clearly conveying a distinct landing-page generation niche. Its main weakness is the absence of an explicit 'Use when…' trigger clause, which caps completeness.

Suggestions

Append a 'Use when…' clause naming concrete trigger phrases (e.g., 'Use when generating landing pages, marketing pages, or when the user asks for high-converting Next.js pages').

Add natural synonyms/format extensions a user might say (e.g., 'sales page', 'squeeze page', '.tsx') to broaden trigger coverage.

Tighten the parenthetical '(Heroes, Features, Pricing)' into a fuller action list to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain plus several concrete actions (PAS/AIDA/BAB frameworks, Heroes/Features/Pricing components, Core Web Vitals/SEO), with only minor coverage gaps. Not a 5 because the listed actions are somewhat high-level feature names rather than an exhaustive action set.

4 / 5

Completeness

Clearly states what the skill does, but provides no 'Use when…' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guidelines. The 'when' is only weakly implied by the domain.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('landing pages', 'Next.js', 'React', 'Tailwind', 'SEO', 'Core Web Vitals') that users would actually say. Not a 5 because synonyms and file/format extensions are absent.

4 / 5

Distinctiveness Conflict Risk

The marketing/conversion-focused landing-page niche with named copy frameworks is mostly distinct from generic web-dev skills. Not a 5 because of minor overlap risk with general Next.js/React component-generation skills.

4 / 5

Total

15

/

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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.