Answer Engine Optimization - Optimize content for AI citations, not traditional search rankings.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbencium-aeoExecute the skills CLI command in your project's root directory to begin installation:
Fetches bencium-aeo from bencium/bencium-marketplace 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 bencium-aeo. Access via /bencium-aeo 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
146
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
146
stars
Answer Engine Optimization - Optimize content for AI citations, not traditional search rankings.
Use this skill when:
NOT for traditional SEO - This is specifically for AI/LLM citation optimization.
Full templates and guidelines: Read prd.md in this directory for complete implementation details.
LLMs extract self-contained sentences of ~18 tokens (~15-20 words). Key claims must be complete, quotable statements requiring zero surrounding context.
Good: "Eight-API synthesis reduces property analysis errors by 67%." (9 tokens) Bad: "Our system is incredibly fast and delivers amazing results." (vague)
Single-concept pages vastly outperform multi-topic content. Create focused URLs like domain.com/specific-concept rather than comprehensive guides.
Every major claim needs:
95% of AI citations come from content updated in last 10 months. Static content dies.
| Authority Level | Optimization Approach |
|---|---|
| Challenger (new sites, low authority) | Aggressive: 5-7 extraction points per page, heavy citations, weekly micro-updates |
| Established (top-ranked, well-known) | Light touch: 1-2 strategic points, trust existing credibility, avoid over-optimization |
Princeton finding: Rank-5 sites gained 115% visibility with aggressive optimization. Rank-1 sites that over-optimized lost 30%.
When user requests AEO content, generate:
datePublished and dateModifiedFor every important claim:
When analyzing content for AEO readiness, score (0-10):
| Dimension | What to Check |
|---|---|
| Extraction | How many citation-ready sentences under 18 tokens? |
| Focus | Single topic or sprawling multi-topic? |
| Authority | Expert attribution with credentials? Citations? |
| Freshness | Updated within 90 days? Dated content? |
Quick test: Can you copy-paste 3 sentences that fully answer a question without context?
<head>After implementation, test with:
Track: Mentioned? Linked? Accurate? Evidence quoted?
For complete templates, examples, and detailed guidelines, read:
prd.md - Full AEO content generation guide with HTML templatesstory-structured.md - Framework summary from Princeton studyMake 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.
bencium/bencium-claude-code-design-skill
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Keeps context tight: bencium-aeo is the kind of skill you can hand to a new teammate without a long onboarding doc.
bencium-aeo is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in bencium-aeo — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend bencium-aeo for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in bencium-aeo — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in bencium-aeo — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for bencium-aeo matched our evaluation — installs cleanly and behaves as described in the markdown.
bencium-aeo reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend bencium-aeo for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
bencium-aeo reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 44