Menu
Use when optimizing a site or brand to show up in AI answers, LLM citations, AI search, product recommendations, and category answers.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when writing or rewriting website copy: homepages, landing pages, pricing pages, product pages, feature pages, hero sections, headlines, subheads, CTAs, value propositions, taglines, and above-the-fold messaging. Do not use for email sequences, blog posts, longform X articles, or platform-specific ad copy.
Use when planning a product launch, feature release, waitlist, beta, public announcement, relaunch, Product Hunt-style push, repeated feature launch system, launch-week checklist, or multi-channel GTM rollout.
Use when writing or rewriting longform X/Twitter articles, X Articles, founder essays, launch essays, growth teardowns, product breakdowns, build-in-public stories, or sharp startup takes that need X-native hooks, tone, pacing, and structure. Use for X Articles and long posts, not blog SEO posts, lifecycle emails, or landing page copy.
Use when turning a marketing, growth, CRO, pricing, onboarding, email, ad, or acquisition idea into a useful experiment or test plan.
Use when auditing, planning, or debugging marketing measurement, conversion tracking, GA4, GTM, UTMs, pixels, CRM attribution, funnel reporting, or dashboard trust.
Use when creating or improving B2B outbound, prospecting, cold email, LinkedIn outreach, account research, sales sequences, or founder-led direct outreach.
| name | ai-seo |
| description | Use when optimizing a site or brand to show up in AI answers, LLM citations, AI search, product recommendations, and category answers. |
Make the company, product, category, use cases, and proof easy for AI answer engines to understand and cite.
Inspect what the web can verify:
If live research is needed, use current sources and prefer primary pages.
Ask:
Inventory public evidence by claim:
Then recommend assets that make weak claims easier to verify: canonical explainer, use case page, public example, customer story, fair comparison, documentation, review surface, or reputable third-party mention.
AI answer presence read:
[one paragraph]
Entity clarity:
- Category:
- Audience:
- Use cases:
- Proof:
- Third-party corroboration:
Gaps:
1. [gap] -> [why it matters]
Evidence table:
| Claim | Official source | Third-party source | Query supported | Strength | Gap |
Assets to create:
| Asset | Query/job it supports | Proof required | Priority |
Schema and crawl fixes:
- [fix]
30-day presence plan:
1. [action]
2. [action]
3. [action]