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.
87
85%
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 strong, well-crafted description that clearly communicates what the skill does and when to use it. It provides specific concrete actions, natural trigger terms users would actually say, and occupies a distinct niche. 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. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche: landing page generation specifically from repositories. The combination of 'landing pages', 'repository', 'README to marketing page' creates a distinct trigger profile unlikely to conflict with general web development or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%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 excellent workflow clarity and progressive disclosure. Its main weakness is actionability—it describes what to do at a high level but lacks executable code for the core generation logic, relying on a custom command interface. The content is moderately concise but could benefit from moving the detailed CSS patterns and 12-section specification to reference files.
Suggestions
Add executable code snippets or pseudocode showing how to actually parse README.md and extract content (e.g., regex patterns for H1 extraction, badge detection), rather than just describing the mapping in a table.
Move the detailed CSS patterns/variables and the 12-section specification to a reference file (e.g., references/landing-pattern.md) and keep only a summary in the main skill, improving conciseness.
| 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 command (`/landing-page-generator`) without providing the actual implementation code. The CSS snippets show class names but not full implementations. The extraction methods are described at a high level rather than with executable code. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced across 5 steps with explicit validation checkpoints in Step 5 (browser rendering, link validation, responsive testing, accessibility checks). The progression from analysis → extraction → generation → output → validation is logical and well-structured with clear deliverables at each stage. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-organized sections, and appropriately references external files ('references/landing-pattern.md' for detailed patterns, 'assets/' for templates). Content is structured with headers, tables, and collapsible-friendly patterns. The main file serves as a comprehensive but navigable overview without deeply nested references. | 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 | |
- Commit
746adc8
- 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.