aeo-track

Automate recurring aeo-baseline scheduling across macOS and Linux workspaces.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Scheduling recurring aeo-baseline runs typically requires manual setup of cron/launchd, scaffolding wrapper scripts, and tracking installation state. This skill automates that lifecycle across workspaces so you can maintain consistent visibility tracking without manual infra.

Core Features & Use Cases

  • Generates platform-appropriate schedulers (launchd on macOS, cron on Linux) to invoke aeo-baseline --yes.
  • Produces a wrapper script that sources workspace .env and runs the baseline with logs under aeo-data.
  • Maintains per-workspace state under ~/.aeo-track to support multiple projects and easy removal.
  • Supports install, status, and remove workflows for end-to-end lifecycle.

Quick Start

Run aeo-track --install --workdir /path/to/workspace --baseline-script /path/to/aeo-baseline/scripts/baseline.py to generate a dry-run, then re-run with --apply to activate.

Frequently Asked Questions about aeo-track

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

FAQPage Schema
How do I schedule recurring aeo-baseline runs to track visibility automatically?

You can automate aeo-baseline scheduling by generating platform-appropriate launchd or cron jobs. This tool creates wrapper scripts that source workspace environments and run daily, weekly, hourly, or custom interval visibility tracking without manual setup.

Do I need an aeo.config.json file to automate baseline tracking across workspaces?

Yes, each workspace requires an aeo.config.json file and a baseline script to automate tracking. The scheduler wrapper loads environment keys from these workspace configurations before executing the visibility baseline run.

Can I manage multiple scheduled baseline runs on macOS and Linux?

Yes, you can maintain multiple per-workspace schedules across macOS and Linux. The tool stores installation state under ~/.aeo-track, allowing you to install, inspect status, and remove separate recurring visibility tracking jobs for different projects.

What's the best way to remove or inspect automated visibility tracking schedules?

You can inspect or remove automated tracking schedules using dedicated status and remove workflows. The tool maintains per-workspace state under ~/.aeo-track, making it easy to manage and delete recurring launchd or cron baseline jobs without manual infrastructure cleanup.

How do I install a recurring baseline schedule without immediately activating it?

You can perform a dry-run installation by running the install command with your workspace and baseline script paths. Re-running the same command with the apply flag activates the generated launchd or cron schedule for actual visibility tracking.