CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

landing

Generates a premium single-page HTML landing page with 3D CSS animations, GSAP scroll effects, and mouse-parallax depth. Forcing intake (product + elevator pitch, audience register, brand overrides, tone) locks down positioning before any copy or markup is written, so the page reflects the actual product rather than generic boilerplate. Use whenever the user says 'landing for X', 'create a landing page', 'build a landing page', 'make a landing page for X', 'I need a web page for Y', or provides product/service details and wants a polished website. Also triggers on 'promotional page', 'product page', 'one-pager', 'web presence', 'sales page'. Outputs a single self-contained HTML file (Claude Code) or HTML artifact (Claude.ai). Supports configurable brand colors via CSS custom property overrides.

70

Quality

88%

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

The canonical home for this skill is landing in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

A highly actionable, well-sequenced generation spec with real feedback loops and no filler — the core workflow would score near the top. The dominant defect is the bundle: six referenced files (3 references, 3 scripts) are missing, which breaks progressive disclosure entirely and makes the prescribed validation step non-executable as written.

Suggestions

Ship the referenced bundle files (references/brand_system_design.md, gsap_animation_patterns.md, single_file_html_discipline.md and scripts/html_validator.py, brand_palette_validator.py, kebab_slug_generator.py), or remove the references and inline whatever guidance is essential.

Replace the '@keyframes floatB/floatC { /* different duration + rotation */ }' placeholder comments with concrete keyframe examples so the animation block is fully copy-paste ready.

Deduplicate the repeated rules (single-file/CDN-only discipline, accent-derivation) into one authoritative section each to tighten token budget.

DimensionReasoningScore

Conciseness

Largely prescriptive spec with complete code — no tutorials on concepts Claude already knows. Minor redundancy keeps it off anchor 5: the single-file/CDN-only rule appears three times (Required CDN Dependencies, Output Spec, Anti-Patterns), the 'derive accent algorithmically' rule appears three times (Q3, Override Pattern, Error Handling), and the CDN URLs are re-listed in the Validation section.

4 / 5

Actionability

The GSAP timelines, mouse-parallax, ScrollTrigger.batch, CDN snippet, exact px/type scales, and error-handling table are copy-paste ready. Two gaps keep it off 5: the validation step ('Run scripts/html_validator.py') and the palette/slug helpers reference scripts that do not exist in the bundle, and '@keyframes floatB { /* different duration + rotation */ }' is placeholder pseudocode rather than executable code.

4 / 5

Workflow Clarity

Dependency-ordered Phase 0 (Q1→Q4) with explicit stop condition ('After Q4, commit and generate'), content extraction, build spec, then a post-generation validation step with a true feedback loop: 'html_validator returns FAIL → Regenerate ONLY the failing sections in one targeted pass; do NOT abandon the file'. Error handling is tabulated. Matches anchor 5's validate→fix→retry pattern.

5 / 5

Progressive Disclosure

The body is well-sectioned and reference links are clearly signaled one level deep (references/brand_system_design.md, gsap_animation_patterns.md, single_file_html_discipline.md), but none of the three reference files or three scripts exist in the bundle — every referenced path is dead, so the disclosure structure cannot actually be navigated. Not anchor 4 ('most content appropriately placed') because the split the skill itself describes is broken; not anchor 2 because the body is well-structured and self-sufficient for the core task.

3 / 5

Total

16

/

20

Passed

Description

96%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, concrete capabilities, explicit 'Use whenever...' triggers with rich synonym coverage, and a clearly stated output contract. The only weakness is that its most natural triggers overlap with other landing-page-generator skills, with the differentiation deferred to the body rather than the description.

DimensionReasoningScore

Specificity

Multiple concrete actions in third person voice: 'Generates a premium single-page HTML landing page with 3D CSS animations, GSAP scroll effects, and mouse-parallax depth', 'Outputs a single self-contained HTML file (Claude Code) or HTML artifact (Claude.ai)', 'Supports configurable brand colors via CSS custom property overrides'. Coverage is comprehensive with no generic filler.

5 / 5

Completeness

Explicitly answers both what ('Generates a premium single-page HTML landing page... Outputs a single self-contained HTML file') and when ('Use whenever the user says...') with concrete trigger phrases. Anchor 5 matches directly; anchor 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Extensive natural trigger phrases with synonyms: 'landing for X', 'create a landing page', 'build a landing page', 'make a landing page for X', 'I need a web page for Y', 'promotional page', 'product page', 'one-pager', 'web presence', 'sales page' — all phrasings a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

The single self-contained HTML output format is a distinct niche, but the primary triggers ('create a landing page', 'build a landing page') are exactly the phrases a Next.js/conversion-optimized landing page skill would also match; the description itself doesn't differentiate from that sibling (the differentiation lives in metadata/body, not the description). Not the level below: the output-format pin ('single self-contained HTML file') prevents overlap with broad web-building skills.

4 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 missing

Warning

referenced_paths_exist

Referenced path issues: 18 missing

Warning

Total

14

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/landing/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.