landing-page-generator
Generate complete, deploy-ready landing pages from any repository. Use when creating a homepage for an open-source project, building a project website, converting a README into a marketing page, or standardizing landing pages across multiple repos.
84
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
100%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 is a well-crafted skill description that clearly communicates what the skill does and when to use it. It provides specific, concrete actions and includes natural trigger terms that users would actually say. The explicit 'Use when...' clause with multiple scenarios makes it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate complete, deploy-ready landing pages', 'creating a homepage for an open-source project', 'building a project website', 'converting a README into a marketing page', 'standardizing landing pages across multiple repos'. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate complete, deploy-ready landing pages from any repository) and 'when' with an explicit 'Use when...' clause listing four distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'landing pages', 'homepage', 'open-source project', 'project website', 'README', 'marketing page', 'repository', 'repos'. These cover a good range of natural variations for this use case. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around landing page generation from repositories, with specific triggers like 'README into a marketing page' and 'open-source project homepage' that are unlikely to conflict with general web development or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%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 clear workflow sequencing and a solid validation checkpoint. Its main weaknesses are that it's somewhat verbose for a SKILL.md (the 12-section generation guide and CSS patterns could be in referenced files), and the actionability is limited by relying on a custom slash command without providing the underlying implementation code. The content extraction mapping table and output structure are strong practical elements.
Suggestions
Move the detailed 12-section generation guide and CSS patterns into a separate reference file (e.g., references/section-guide.md) and link to it from the main skill, keeping only a summary inline.
Add executable code snippets or script references that show how the repository analysis and content extraction actually work, rather than describing the process abstractly.
Consider providing a minimal working example showing the actual HTML output for at least one section (e.g., Hero) so Claude has a concrete template to follow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly detailed and well-structured, but includes some content that could be tightened. The extensive section generation list (12 sections with sub-bullets) and the CSS patterns section add bulk that could be referenced externally. Some descriptions are slightly verbose but not egregiously so. | 2 / 3 |
Actionability | The skill provides concrete output structures, CSS variable definitions, and content extraction mappings, which are useful. However, the core workflow relies on a custom slash command (`/landing-page-generator`) without providing the actual executable code or scripts that implement it. The CSS snippets are class names without implementations, and the extraction methods are described rather than implemented with executable code. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced across 5 explicit steps (Repository Analysis → Content Extraction → Section Generation → Output Structure → Validation Checkpoint). Step 5 includes explicit validation criteria covering rendering, links, responsive design, and accessibility. The progression is logical and includes a clear feedback checkpoint before finalizing. | 3 / 3 |
Progressive Disclosure | The skill references external files (`references/landing-pattern.md`, `assets/`) at the end, which is good. However, the main body is quite long with detailed section-by-section generation instructions and CSS patterns that could be split into separate reference files. The content extraction map and 12-section generation guide would benefit from being in a referenced document rather than inline. | 2 / 3 |
Total | 9 / 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 | |
- Commit
4ef3dec
- 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.