Generate complete landing pages from repositories. Analyzes README, features, and structure to create static sites following established patterns. Use for new project landings, open-source showcases, documentation portals.
Install with Tessl CLI
npx tessl i github:FlorianBruniaux/claude-code-ultimate-guide --skill landing-page-generator77
Quality
70%
Does it follow best practices?
Impact
86%
2.20xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/skills/landing-page-generator/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description adequately covers the core purpose and provides explicit use cases, earning good marks for completeness. However, it could be more specific about concrete actions and include more natural trigger terms users would actually say. The description is functional but not optimally distinctive from other web/documentation generation skills.
Suggestions
Add more natural trigger terms users would say, such as 'homepage', 'project website', 'marketing page', 'GitHub pages', or 'repo to website'.
Increase specificity by listing concrete outputs or actions like 'generates HTML/CSS, creates hero sections, feature grids, installation instructions, and call-to-action buttons'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (landing pages from repositories) and some actions (analyzes README, features, structure; creates static sites), but lacks comprehensive detail on specific capabilities like what patterns are followed or what output formats are supported. | 2 / 3 |
Completeness | Clearly answers both what (generate landing pages by analyzing repo content) and when ('Use for new project landings, open-source showcases, documentation portals') with explicit trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'landing pages', 'README', 'static sites', 'open-source', 'documentation portals', but misses common variations users might say like 'homepage', 'project page', 'website from repo', or 'marketing page'. | 2 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to landing page generation from repos, but could overlap with general website generation skills, documentation skills, or static site generator skills without clearer differentiation. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability and good progressive disclosure. The workflow is clear but would benefit from explicit validation steps before deployment. Some content redundancy between the overview and detailed workflow sections could be tightened.
Suggestions
Add a validation checkpoint after Step 4 (e.g., 'Verify: Open index.html in browser, check all links resolve, confirm responsive layout')
Remove or consolidate the 'What This Skill Does' section since it duplicates the detailed workflow steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., the 'What This Skill Does' section largely duplicates the detailed workflow). The CSS patterns section is useful but could be trimmed or moved to a reference file. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific file paths, command examples, complete CSS variable definitions, and clear output structure. The extraction mapping table and section generation order are highly actionable. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (Steps 1-4) with good structure, but lacks explicit validation checkpoints. No verification step to confirm the generated landing page is valid HTML/CSS or that all referenced assets exist before deployment. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate use of tables for options and mappings, and proper references to external files (references/landing-pattern.md, assets/). Content is appropriately structured without deep nesting. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Table of Contents
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.