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.

72

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 skill body: concrete code, exact values, explicit validation with an error-recovery loop, and real one-level-deep bundle files. The main deductions are duplicated brand/FOUC rules across sections, two stub keyframe definitions, and heavy inlining of material that the references already cover.

Suggestions

State the brand-override derivation rules (lighten 15% / darken 8% / 0.12 alpha) once — in the Override Pattern section — and have the Q3 section and Error Handling table reference it instead of repeating it, cutting ~10 lines of duplication.

Replace the '@keyframes floatB/floatC { /* different duration + rotation */ }' stubs with two concrete, differing keyframe definitions (or a one-line parameterization rule like 'duration 9–15s, rotation 6–12deg, unique per shape') so all required patterns are executable.

Trim the five inlined animation patterns to the two most failure-prone ones (hero entrance with gsap.set FOUC prevention, ScrollTrigger batching) and defer the remaining three plus the CSS keyframes to references/gsap_animation_patterns.md, which already exists as their stated canon.

DimensionReasoningScore

Conciseness

The body is dense with earned tokens (exact CSS variables, px values, CDN URLs, executable GSAP snippets) and includes a deliberate 'Anti-Patterns To Reject' list rather than concept explanations. Not score 5 because there is real duplication: the brand-derivation rule ('derive accent algorithmically (lighten 15% / darken 8%)') is stated in the Q3 section, the Override Pattern section, and again in the Error Handling table, and the gsap.set FOUC rationale is repeated in the Animation Patterns, Validation, and Anti-Patterns sections. Not score 3 because the padding is limited to these repeats — no section explains concepts Claude already knows.

4 / 5

Actionability

Mostly copy-paste-ready guidance: complete hero-entrance GSAP timeline, mouse-parallax handler, ScrollTrigger.batch call, exact CDN link/script tags, exact command 'Run scripts/html_validator.py --file ${OUTPUT_DIR}/<slug>.html', and a kebab-case filename rule with a worked example ('Quill AI' → quill-ai.html). Not score 5 because two required keyframes are literal comment stubs ('@keyframes floatB { /* different duration + rotation */ }') — pseudocode where executable CSS was expected, and no sample HTML skeleton ties the section specs into one runnable whole.

4 / 5

Workflow Clarity

Clear dependency-ordered sequence: Phase 0 intake with per-question rationale, explicit stop condition ('After Q4, commit and generate. No follow-up questions during generation'), content extraction with fallback strategy, build spec, then a post-generation validation step with a feedback loop ('html_validator returns FAIL → Regenerate ONLY the failing sections in one targeted pass; do NOT abandon the file') and an Error Handling table covering edge cases like duplicate output paths. Matches the score-5 anchor: explicit validation, error-recovery loop, and checklists.

5 / 5

Progressive Disclosure

Good structure with well-signaled one-level-deep references: all three referenced files (references/brand_system_design.md, gsap_animation_patterns.md, single_file_html_discipline.md) and all three scripts exist and are linked in context, plus a References section and Tooling table. Not score 5 because the body inlines complete material that the references also canonize — the full five animation patterns are inlined right after 'See references/gsap_animation_patterns.md for the canon', and the entire default palette spec is inlined while deferring color theory — leaving SKILL.md a ~330-line hybrid of overview and detail rather than a clean overview pointing to depth.

4 / 5

Total

17

/

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.

An exemplary description: concrete multi-action capability statement, explicit trigger phrases with strong synonym coverage, and clear output-format declaration in third person. The only weakness is that a few broad triggers ('web page for Y', 'web presence') slightly raise conflict risk with general web-building skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage: '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)', 'Outputs a single self-contained HTML file (Claude Code) or HTML artifact (Claude.ai)', and 'Supports configurable brand colors via CSS custom property overrides'. Not score 4 because coverage spans generation, input handling, output format, and configuration without gaps; 'premium' borders on buzzword but is backed by enumerated concrete capabilities.

5 / 5

Completeness

Explicitly answers both questions: 'what' via 'Generates a premium single-page HTML landing page with 3D CSS animations, GSAP scroll effects, and mouse-parallax depth' and 'when' via 'Use whenever the user says...'. Matches the score-5 anchor (concrete what + explicit trigger phrases) exactly; not score 4 because the 'when' clause is fully explicit with quoted trigger phrases rather than merely present.

5 / 5

Trigger Term Quality

Comprehensive natural-phrase coverage including 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'. These are phrasings a user would naturally say. Not score 4 because the synonym set ('one-pager', 'sales page', 'web presence') covers variations most descriptions miss; file extensions are not applicable to this task domain.

5 / 5

Distinctiveness Conflict Risk

The landing-page niche with GSAP/self-contained-HTML output is mostly distinct from general web-dev skills, but broad triggers like 'I need a web page for Y' and 'web presence' create minor overlap risk with generic site-building skills. Not score 5 because those broad triggers could plausibly fire for non-landing web requests; not score 3 because the dominant trigger set ('landing page', 'one-pager', 'sales page') is specific to this skill's niche.

4 / 5

Total

19

/

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

alirezarezvani/claude-skills

Path

marketing/landing/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.