aeo-init

Generate aeo.config.json workspace configurations with interactive or flag-driven modes.

9|2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/psyduckler/aeo-skills --skill aeo-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aeo-init
Source: https://github.com/psyduckler/aeo-skills/tree/main/aeo-init
Command: npx skills add https://github.com/psyduckler/aeo-skills --skill aeo-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Write aeo.config.json to initialize an AEO workspace, enabling the rest of the v2 skills to read and operate on a brand's tracking configuration.

Core Features & Use Cases

  • Interactive setup prompts for brand, domain, aliases, competitors, and prompts to generate a ready-to-run aeo.config.json.
  • Flag-driven invocation for automation and agent use, producing the config without interactive prompts.
  • Validation against the aeo-config-v1 schema (when jsonschema is available) to ensure the generated config is correct and ready for downstream skills.

Quick Start

Run the interactive init to create or regenerate aeo.config.json for your project, or use the flag-driven flow to produce the config directly.

Frequently Asked Questions about aeo-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an aeo.config.json workspace configuration for project initialization?

You can create an aeo.config.json workspace configuration by using the interactive setup prompts for brand and domain details, or by using flag-driven invocation for automation. The generated config is validated against the aeo-config-v1 schema and written to disk to enable downstream AEO tracking skills.

What is the best way to validate a workspace config against the aeo-config-v1 schema?

Validating a workspace config against the aeo-config-v1 schema happens automatically during initialization if the jsonschema package is available. This process ensures your aeo.config.json file is structurally correct and ready for downstream AEO tracking skills to operate on.

Can I generate a workspace config automatically without interactive prompts?

Yes, you can generate a workspace config automatically by using flag-driven invocation. This mode bypasses the interactive walkthrough and directly produces the aeo.config.json file, making it suitable for automation and agent use within your project.

Does the initialization process support a dry-run mode to preview the workspace config?

Yes, the initialization process supports a dry-run mode to preview the generated workspace config. This allows you to review the aeo.config.json output and schema validation results without actually writing the configuration file to disk.

Do I need jsonschema installed to write a valid aeo.config.json?

You do not need jsonschema installed to generate an aeo.config.json file, but it is required for validation. The skill writes the workspace config regardless, yet schema validation against aeo-config-v1 only occurs when the jsonschema package is available.