aeo-pack-b2b-saas
Skill13 starsChanged 6 months agoMITView on GitHub
Curated prompt pack for B2B SaaS AEO visibility tracking. 20 vertical-specific prompts covering category discovery, vendor comparison, alternatives, pricing, integrations, and trust signals. Designed to be merged into an existing aeo.config.json before running aeo-baseline. Template variables (category, problem, vendor, integration, company_size) are filled in per workspace. Use when a user is setting up AEO tracking for a B2B SaaS product, wants a starter prompt set for software-category visibility, or asks for prompt ideas for a SaaS company.
In this repository22 other files it gives its agents.
- aeo-ai-overview-simulatorSkill
- aeo-analytics-freeSkill
- aeo-baselineSkill
- aeo-cannibalization-detectorSkill
- aeo-citation-gap-finderSkill
- aeo-competitor-monitorSkill
- aeo-content-freeSkill
- aeo-entity-extractorSkill
- aeo-freshness-decay-trackerSkill
- aeo-grounding-query-mapperSkill
- aeo-initSkill
- aeo-multi-prompt-strategySkill
- aeo-optimizeSkill
- aeo-pack-ai-toolsSkill
- aeo-pack-local-servicesSkill
- aeo-prompt-frequency-analyzerSkill
- aeo-prompt-question-finderSkill
- aeo-prompt-research-freeSkill
- aeo-reportSkill
- aeo-schemaSkill
- aeo-source-authority-profilerSkill
- aeo-trackSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 84
If you want to add custom prompts, just edit your aeo.config.json directly.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AEO Pack: B2B SaaS
Source: github.com/psyduckler/aeo-skills Part of: AEO Skills Suite (v2 prompt packs) Schema: prompt-pack-v1
20 ready-to-track prompts for B2B SaaS visibility, covering the full purchase journey from category discovery to vendor evaluation.
What's in the pack
| Intent | # of prompts | Example |
| Category discovery | 7 | "Top {{category}} software in 2026" |
| Vendor comparison | 1 | "{{vendor}} vs alternatives: which is best?" |
| Alternatives | 4 | "Alternatives to {{vendor}}" |
| Pricing | 2 | "How much does {{vendor}} cost?" |
| Integration | 2 | "Best {{category}} that integrates with {{integration}}" |
| Trust / security | 1 | "Is {{vendor}} secure? SOC 2 / GDPR / HIPAA compliance" |
| Research / evaluation | 3 | "Is {{vendor}} worth it for {{company_size}}?" |
Full prompt list lives in prompts.json.
Template variables
Each prompt may contain {{variable}} placeholders. Fill them in with values specific to the workspace:
| Variable | Required | Example |
category | yes | project management, CRM, analytics, content optimization |
problem | yes | tracking customer support tickets, managing remote team standups |
vendor | no | Your brand or a key competitor — used in vendor-specific prompts |
integration | no | Slack, Salesforce, Notion, etc. |
company_size | no | startup, SMB, mid-market, enterprise |
How to use this pack
This pack is read-only data. To use it:
- Install alongside the v2 core skills:
npx skills add psyduckler/aeo-skills --skill aeo-pack-b2b-saas - Open
prompts.jsonin the installed pack folder. - Pick the prompts that apply to your workspace — you usually don't need all 20. A focused set of 8–12 prompts gives better signal than 20 noisy ones (and is cheaper to run).
- Substitute variables for your brand. For example, with
category = "content optimization"andvendor = "Surfer":- "Top {{category}} software in 2026" → "Top content optimization software in 2026"
- "Alternatives to {{vendor}}" → "Alternatives to Surfer"
- Merge into your
aeo.config.jsonby adding the filled-in prompts to thepromptsarray. The agent doing this should preserve any existing prompts the user already had. - Run
aeo-baselineto start tracking.
Why these prompts
B2B SaaS visibility splits into roughly five clusters:
- Discovery — buyers who don't yet know which vendor they want; they search for the category. This is where the highest acquisition leverage lives, and where hub pages compete.
- Comparison/alternatives — buyers who've narrowed to 2–3 vendors and want differentiation. Citation rate here drives bottom-of-funnel conversion.
- Pricing — late-stage; signals readiness to buy. Pages cited here matter for sales-cycle acceleration.
- Integration — power users with existing stacks. Citation here drives expansion / cross-sell.
- Trust — compliance / security signal. Often where enterprise deals get blocked.
The pack covers each cluster with 2–7 prompts so a workspace can see balanced visibility data without 50+ prompt overhead.
Notes
- Variables are unescaped JSON strings — keep them brand-safe (no
{{or}}in your substitutions). - If you want to add custom prompts, just edit your
aeo.config.jsondirectly. The pack is a starting point, not a constraint. - Suggested first-baseline scope: 10 prompts × 20 samples = ~$0.06 estimated Gemini cost.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.