agentleFS
psyducklerpsyduckler/aeo-skills/aeo-init/SKILL.md

aeo-init

Skill13 starsChanged 6 months agoMITView on GitHub

Initialize an AEO workspace by writing aeo.config.json — the workspace configuration file that every other v2 skill (aeo-baseline, aeo-track, aeo-report, aeo-optimize) reads. Captures the brand name and domain, aliases, competitors, the prompts to track, and spend limits. Supports both interactive prompts (for first-time setup) and flag-driven invocation (for agents). The output conforms to schemas/aeo-config-v1.json and validates against it when jsonschema is available. Use when a user wants to: start a new AEO tracking project, scaffold the config that aeo-baseline reads, regenerate a workspace config from scratch, or add prompts to an existing setup.

  • Reads credentials
  • Installs packages

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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
  1. Distinctive:

    No API keys (this skill never calls a provider)

    line 27
  2. Very specific:

    When you pass --prompt "Best CRM for small business", the prompt is auto-assigned prompt_id = "best_crm_for_small_business".

    line 97
  3. Distinctive:

    After building the config, two validation layers run:

    line 101
  4. Distinctive:

    If validation fails, the script prints the errors and exits with a non-zero code without writing.

    line 106

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

AEO Init

Source: github.com/psyduckler/aeo-skills Part of: AEO Skills Suite Output schema: aeo-config-v1

The workspace bootstrapper. One command, one config file, then aeo-baseline knows what to measure.

Requirements

  • Python 3.9+
  • No API keys (this skill never calls a provider)
  • Optional: pip install jsonschema for full schema validation at write time

Usage

# Interactive — walks through every field
python3 scripts/init.py

# Flag-driven — best for agent use
python3 scripts/init.py \
  --brand Tabiji --domain tabiji.ai \
  --alias tabiji \
  --competitor tripadvisor.com --competitor lonelyplanet.com \
  --prompt "best travel planning tools" \
  --prompt "AI travel apps for itineraries" \
  --prompt-intent commercial --prompt-intent commercial

# Print the would-be config without writing
python3 scripts/init.py --brand X --domain x.com --prompt "best X" --dry-run

# Overwrite an existing config (safety: refuses unless --force)
python3 scripts/init.py --brand NewName --domain new.com --force

# Custom output path
python3 scripts/init.py --output /path/to/aeo.config.json ...

Interactive mode triggers automatically when neither --brand nor a useful flag combination is provided. Pass --interactive to force it even with flags.

Options

OptionDescription
--brandBrand/company name to track (required for non-interactive mode)
--domainBrand's primary domain (e.g. example.com)
--alias (repeatable)Alternate spellings/abbreviations
--competitor (repeatable)Competitor domains to track
--prompt (repeatable)Prompts to track for visibility
--prompt-intent (repeatable)Intent for each --prompt, paired by position
--localeBCP-47 locale (default: en-US)
--personaOptional persona prefix used by some downstream skills
--output PATHWhere to write the config (default: ./aeo.config.json)
--data-dir PATHWhere baselines should write evidence files
--forceOverwrite an existing config without prompting
--interactiveForce interactive prompts even when flags are set
--dry-runPrint the config to stdout instead of writing

What gets written

A JSON file conforming to aeo-config-v1.json. The default skeleton includes:

  • One Gemini provider (model gemini-3-flash-preview, env var GEMINI_API_KEY, grounding enabled)
  • Sampling: 20 runs default, 5 concurrency, 3 retries per sample
  • Limits: $25/day cap, $5 confirm-over threshold, 100 runs per campaign
  • Scoring: aeo-v1 methodology
  • Empty prompts list if none were provided (add later with --force or edit the file)

Domain normalization

Competitor and brand domains are normalized before writing:

  • Lowercased
  • https:// / http:// prefixes stripped
  • Literal www. prefix stripped (using startswith, not the lstrip('www.') footgun that would corrupt world.com)
  • Trailing / stripped

So https://WWW.TripAdvisor.com/ becomes tripadvisor.com.

Prompt IDs

When you pass --prompt "Best CRM for small business", the prompt is auto-assigned prompt_id = "best_crm_for_small_business". IDs are snake_case, deduplicated by truncation to 64 chars. Override by editing the JSON post-hoc.

Validation

After building the config, two validation layers run:

  1. Built-in: required fields, api_key_env shape (^[A-Z][A-Z0-9_]*$), prompt_id shape (^[a-z0-9_]+$), intent enum membership.
  2. JSON Schema (if jsonschema is importable): full structural validation against aeo-config-v1.json.

If validation fails, the script prints the errors and exits with a non-zero code without writing.

Pairs With

  • aeo-baseline — reads the config this skill writes
  • aeo-track — schedules aeo-baseline runs from this config
  • Future prompt packs (e.g. aeo-pack-b2b-saas) will populate the prompts array

Notes

  • This skill never calls a provider API and never reads secrets.
  • The output is editable JSON — re-running with --force regenerates; editing in place is also fine.
  • For a starter prompt list, run the (future) aeo-prompt-research-free skill first and feed its suggestions back into init via --prompt flags.

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.