Load with: base.md + ui-web.md
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionweb-contentExecute the skills CLI command in your project's root directory to begin installation:
Fetches web-content from alinaqi/claude-bootstrap and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate web-content. Access via /web-content in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
570
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
570
stars
Load with: base.md + ui-web.md
For creating web content optimized for both traditional SEO and AI discovery (ChatGPT, Perplexity, Claude, Gemini).
Sources: GEO Complete Guide | AI Search SEO | LLM Optimization | Generative Engine Optimization
SEO gets clicks. GEO gets citations.
Traditional SEO optimizes for Google rankings. Generative Engine Optimization (GEO) optimizes for being cited by AI assistants. Modern content needs both:
AI traffic grew 1,200% between July 2024 and February 2025. Google's search share dropped below 90% for the first time in a decade. Optimize for both.
Write for humans, structure for machines.
AI systems prefer:
## Homepage Structure
### Above the Fold
- **Headline**: Clear value proposition (what you do + for whom)
- **Subheadline**: How you deliver that value
- **Primary CTA**: One clear action
- **Trust signals**: Logos, testimonials, stats
### Content Sections
1. **Problem Statement**: Pain point you solve
2. **Solution Overview**: How you solve it (3-4 key features)
3. **Social Proof**: Testimonials, case studies, logos
4. **How It Works**: 3-step process (simple)
5. **Pricing Preview**: Or link to pricing page
6. **FAQ Section**: 5-7 common questions (GEO gold)
7. **Final CTA**: Repeat primary action
### Schema Required
- Organization schema (name, logo, founding date, social links)
- WebSite schema with SearchAction
- FAQ schema for questions section
## Product Page Structure
### Hero Section
- **Product Name**: Clear, descriptive
- **One-line Description**: What it does in 10 words or less
- **Key Benefit**: Primary value proposition
- **CTA**: Buy/Try/Demo
### Content Sections
1. **TL;DR Box**: 3-5 bullet summary (AI-quotable)
2. **Problem → Solution**: What problem, how solved
3. **Features Grid**: 4-6 features with icons
4. **Comparison Table**: vs. alternatives (GEO loves these)
5. **Use Cases**: Who uses it and how
6. **Testimonials**: Real names, photos, companies
7. **Pricing**: Clear tiers if applicable
8. **FAQ**: Product-specific questions
### Schema Required
- Product schema (name, description, price, availability)
- Review schema (aggregate rating)
- FAQ schema
- BreadcrumbList schema
## Blog Post Structure
### Opening (First 100 words)
- **TL;DR**: Direct answer to the title's question
- **What you'll learn**: Bullet list of takeaways
- This section should be quotable standalone
### Body Structure
- **H2 sections**: Main topics (5-7 per article)
- **H3 subsections**: Supporting points
- **Bullet lists**: For scanability
- **Stat boxes**: Highlight key numbers
- **Comparison tables**: When comparing options
### Content Elements
- Definition boxes ("What is X?")
- Step-by-step instructions
- Code examples (if technical)
- Original statistics/research
- Expert quotes with attribution
### Closing
- **Summary**: Key takeaways (bulleted)
- **Next steps**: What reader should do
- **Related content**: Internal links
### Metadata Required
- Author name + bio + photo
- Publication date
- Last updated date (visible!)
- Reading time
- Article schema with author
## FAQ Page Structure
### Organization
- Group questions by category
- Most common questions first
- Direct, concise answers
- Link to detailed pages for more info
### Question Format
Q: [Exact question users ask]
A: [Direct answer in first sentence, then elaboration]
### Schema Required
- FAQPage schema (critical for AI discovery)
- Each Q&A as Question/Answer schema
## Landing Page Structure
### Single Focus
- One offer
- One audience
- One CTA (repeated)
### Sections
1. **Headline**: Benefit-focused, specific
2. **Problem Agitation**: Pain points
3. **Solution**: Your offer
4. **Proof**: Testimonials, stats, logos
5. **Features**: 3-5 key benefits
6. **Objection Handling**: FAQ or guarantee
7. **CTA**: Clear, urgent
### No Navigation
- Remove header nav (reduce exits)
- Single path: read → convert
<div class="tldr-box">
<h3>TL;DR</h3>
<ul>
<li>Key point 1 with specific detail</li>
<li>Key point 2 with number/stat</li>
<li>Key point 3 with actionable insight</li>
</ul>
</div>
Place at top of articles. AI systems extract these for summaries.
## What is [Term]?
[Term] is [concise definition in one sentence]. It [what it does] by [how it works].
**Key characteristics:**
- Characteristic 1
- Characteristic 2
- Characteristic 3
Start with "What is X?" - AI systems look for this pattern.
| Feature | Product A | Product B | Our Product |
|Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
sickn33/antigravity-awesome-skills
supercent-io/skills-template
hvpandya/stop-slop
emilkowalski/skills
skillcreatorai/ai-agent-skills
jwynia/agent-skills
Keeps context tight: web-content is the kind of skill you can hand to a new teammate without a long onboarding doc.
web-content is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added web-content from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: web-content is the kind of skill you can hand to a new teammate without a long onboarding doc.
web-content is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
web-content reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend web-content for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
web-content is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: web-content is the kind of skill you can hand to a new teammate without a long onboarding doc.
web-content is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 57