Optimization for AI-powered search engines.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongeo-fundamentalsExecute the skills CLI command in your project's root directory to begin installation:
Fetches geo-fundamentals from davila7/claude-code-templates 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 geo-fundamentals. Access via /geo-fundamentals 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
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
Optimization for AI-powered search engines.
GEO = Generative Engine Optimization
| Goal | Platform |
|---|---|
| Be cited in AI responses | ChatGPT, Claude, Perplexity, Gemini |
| Aspect | SEO | GEO |
|---|---|---|
| Goal | #1 ranking | AI citations |
| Platform | AI engines | |
| Metrics | Rankings, CTR | Citation rate |
| Focus | Keywords | Entities, data |
| Engine | Citation Style | Opportunity |
|---|---|---|
| Perplexity | Numbered [1][2] | Highest citation rate |
| ChatGPT | Inline/footnotes | Custom GPTs |
| Claude | Contextual | Long-form content |
| Gemini | Sources section | SEO crossover |
How AI engines select content to cite:
| Factor | Weight |
|---|---|
| Semantic relevance | ~40% |
| Keyword match | ~20% |
| Authority signals | ~15% |
| Freshness | ~10% |
| Source diversity | ~15% |
| Element | Why It Works |
|---|---|
| Original statistics | Unique, citable data |
| Expert quotes | Authority transfer |
| Clear definitions | Easy to extract |
| Step-by-step guides | Actionable value |
| Comparison tables | Structured info |
| FAQ sections | Direct answers |
| Action | Purpose |
|---|---|
| Google Knowledge Panel | Entity recognition |
| Wikipedia (if notable) | Authority source |
| Consistent info across web | Entity consolidation |
| Industry mentions | Authority signals |
| Crawler | Engine |
|---|---|
| GPTBot | ChatGPT/OpenAI |
| Claude-Web | Claude |
| PerplexityBot | Perplexity |
| Googlebot | Gemini (shared) |
| Strategy | When |
|---|---|
| Allow all | Want AI citations |
| Block GPTBot | Don't want OpenAI training |
| Selective | Allow some, block others |
| Metric | How to Track |
|---|---|
| AI citations | Manual monitoring |
| "According to [Brand]" mentions | Search in AI |
| Competitor citations | Compare share |
| AI-referred traffic | UTM parameters |
| ❌ Don't | ✅ Do |
|---|---|
| Publish without dates | Add timestamps |
| Vague attributions | Name sources |
| Skip author info | Show credentials |
| Thin content | Comprehensive coverage |
Remember: AI cites content that's clear, authoritative, and easy to extract. Be the best answer.
| Script | Purpose | Command |
|---|---|---|
scripts/geo_checker.py |
GEO audit (AI citation readiness) | python scripts/geo_checker.py <project_path> |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
davila7/claude-code-templates
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
geo-fundamentals has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in geo-fundamentals — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: geo-fundamentals is focused, and the summary matches what you get after install.
geo-fundamentals has been reliable in day-to-day use. Documentation quality is above average for community skills.
geo-fundamentals reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added geo-fundamentals from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
geo-fundamentals fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend geo-fundamentals for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
geo-fundamentals is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
geo-fundamentals is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 75