CtrlK
BlogDocsLog inGet started
Tessl Logo

saas-landing

Single-page SaaS landing with hero, features, social proof, pricing, and CTA. Respects the active DESIGN.md color/typography/layout tokens. Trigger keywords: "saas landing", "marketing page", "product landing".

64

Quality

76%

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 ./design-templates/saas-landing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tight, well-sequenced workflow with an explicit validation checklist and concrete design-token constraints. It is highly actionable and well-structured, with only minor conciseness and feedback-loop gaps keeping it just below top marks.

DimensionReasoningScore

Conciseness

The workflow body is lean and assumes Claude's HTML/CSS competence (e.g. "All CSS inlined in a <style> block", "No external JS") without padding; only the trailing "For skill authors" appendix adds meta-commentary not needed for execution, keeping it just below 5.

4 / 5

Actionability

Gives concrete, executable guidance — ordered sections with constraints, parameter wiring ("Use the hero_density parameter as vertical padding in px"), and specific output rules (data-od-id tagging, semantic HTML); no raw code snippet keeps it at 4 rather than 5, though as an instruction-only skill this is acceptable.

4 / 5

Workflow Clarity

A clear 6-step sequence with an explicit validation checkpoint (the step-5 self-check checklist) before "Done"; minor gap is that failures are not paired with a retry loop, so it does not fully reach the 5 anchor's feedback-loop standard.

4 / 5

Progressive Disclosure

A single, well-organized file under ~70 lines with no bundle files needed and a clearly signaled one-level reference (docs/skills-protocol.md); the simple-skill exception applies and structure is clean, matching the 5 anchor.

5 / 5

Total

17

/

20

Passed

Description

75%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 clear, specific description that names concrete deliverables and explicit trigger keywords, with both "what" and "when" present. It is strong but stops just short of fully comprehensive coverage and perfectly natural trigger phrasing.

DimensionReasoningScore

Specificity

Lists concrete sections (hero, features, social proof, pricing, CTA) and concrete actions ("Respects the active DESIGN.md color/typography/layout tokens"), covering several specific capabilities with only minor gaps — between the 4 and 5 anchors, closer to 4 because coverage is good but not exhaustive.

4 / 5

Completeness

Has a clear "what" (single-page SaaS landing with listed sections) and an explicit "when" ("Trigger keywords: ..."), but the when could be slightly more specific/contractive; matches the 4 anchor better than 5.

4 / 5

Trigger Term Quality

Provides three explicit natural triggers ("saas landing", "marketing page", "product landing") a user would plausibly say; a few synonyms (e.g. "landing page", "product page") are missing, so it sits between 4 and 5 but not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (SaaS/marketing/product landing pages) with distinct triggers and minimal conflict risk; mostly distinct with only minor overlap risk with closely related design skills.

4 / 5

Total

16

/

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository
nexu-io/open-design
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.