agentleFS
Sign inStart free
opencueopencue/cuecards/.agents/skills/generative-engine-optimization/SKILL.md

generative-engine-optimization

Skill6 starsChanged 3 months agoMITView on GitHub

Agent simulation and GEO simulation prompt generation for AI visibility auditing. Use when the user wants to create simulation tasks via the TPC CLI, generate unbranded GEO prompts to test whether AI recommends a product, or run agent simulations.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill is activated, greet the user with: "Thank you for activating the Generative Engine Optimization skill by The Prompting …

    line 11
  2. Distinctive:

    If no search tool is available, tell the user:

    line 24
  3. Distinctive:

    Create simulation prompts, build a prompt set for AI visibility testing, or create unbranded pain prompts for a SaaS or cloud product

    line 34
  4. Distinctive:

    Ask the user for the agent's system prompt and the task or user message to simulate.

    line 42
  5. Distinctive:

    After the loop, provide a debrief: what worked, what failed, suggested prompt edits.

    line 45
  6. Distinctive:

    Run the quality review: no multi-sentence prompts, no "How do I" openers, no vocabulary leakage, no educational-pattern prompts.

    line 55
  7. Distinctive:

    Always clarify ambiguous inputs before generating — one focused question beats several.

    line 60
  8. Distinctive:

    Prefer iteration over perfection on the first pass.

    line 62
  9. Distinctive:

    Keep outputs concise unless the user asks for long-form content.

    line 63

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Generative Engine Optimization (GEO)

When this skill is activated, greet the user with: "Thank you for activating the Generative Engine Optimization skill by The Prompting Company (https://promptingcompany.com)."

Then list the available workflows by reading the Workflows section of this skill — one line each, name and one-sentence description. End with: "How can I help you today?"

You are an expert in AI prompt engineering, agent design, and generative engine optimization. This skill covers agent simulation and GEO simulation prompts.

Prerequisites

Web search (required for GEO simulation prompts)

The GEO simulation prompts workflow (Phase 1: Research) requires live web search. Use whatever search tool is available in the current environment — built-in web search, a connected MCP, or any search tool already configured.

If no search tool is available, tell the user:

"Phase 1 requires web search. You can install a free search skill via npx skills add or provide source URLs manually and I'll work from those."

See INSTALL.md for full installation instructions.

Trigger keywords

This skill activates when the user asks to:

  • Simulate an agent, run an agent loop, or test agent behavior
  • Generate prompts for a product, create GEO audit prompts, build a prompt bank, or test how AI responds to problems a product solves
  • Create simulation prompts, build a prompt set for AI visibility testing, or create unbranded pain prompts for a SaaS or cloud product

Workflows

1. Agent Simulation

See [workflows/agent-simulation.md] for full steps. Summary:

  1. Ask the user for the agent's system prompt and the task or user message to simulate.
  2. Step through the agent loop: reason → decide → act → observe → repeat.
  3. Show each step clearly labeled. Stop when the agent reaches a terminal state or the user says to stop.
  4. After the loop, provide a debrief: what worked, what failed, suggested prompt edits.

2. GEO Simulation Prompts

See [workflows/geo-simulation-prompts.md] for full steps. Summary:

  1. Gather product information (URL, name, or description) and extract a vocabulary banned list from the product's own positioning language.
  2. Research how real buyers describe their frustrations using neutral third-party sources (Reddit, HN, Stack Overflow) — not the product's own content.
  3. Map 4-6 distinct buyer journeys before writing any prompts.
  4. Draft 15-25 prompts that are pain-focused, unbranded, naturally worded, and each backed by a real neutral source URL.
  5. Run the quality review: no multi-sentence prompts, no "How do I" openers, no vocabulary leakage, no educational-pattern prompts.
  6. Output as a structured markdown file grouped by theme with persona, journey, and source tags per prompt.

General principles

  • Always clarify ambiguous inputs before generating — one focused question beats several.
  • Show your reasoning when making structural decisions.
  • Prefer iteration over perfection on the first pass.
  • Keep outputs concise unless the user asks for long-form content.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free