--- name: aeo-daily-standup description: Turn yesterday's AEO work and open actions into a short daily standup, with a weekly priorities thread on Mondays and evidence-based tracker updates. --- # AEO Daily Standup Bring shipped content, technical fixes, outreach status and citation changes into one daily action list. Marketing teams get an evidence-backed recap and a Monday thread that the weekly AEO and SEO report can later join. Part of the [Answer Engine Optimization (AEO) skillset](https://type.com/library/skills/answer-engine-optimization). ## When it runs - Recommended schedule: daily at 7:00am in `timezone`, after the crawler monitor and lost-citation alert. - Tuesday–Sunday: one daily post to `report_channel` about the previous calendar day, 00:00–23:59 in `timezone`. - Monday: a standalone weekly title and a thread reply covering the prior Monday–Sunday. The weekly AEO and SEO report can reply there later, after owner approval. - No DMs. ## Inputs | Input | What it is | Example | |---|---|---| | `brand_name`, `brand_exclusions` | Exact brand spelling and excluded look-alikes | `example.com`, `example.ai` | | `content_repo` | Read-only repository for public-site PR evidence | `example-org/website` | | `master_doc` | Shared AEO master doc | Workspace doc | | `work_threads` | AEO marketing work threads to read | Your marketing space/project | | `listings_tracker` | Current directory/MCP listing status, for Mondays | Shared tracker | | `report_channel`, `owner`, `timezone` | Report destination, owner label and reporting timezone | `#aeo`, `@owner`, `America/Los_Angeles` | ## Before you start - Connect GitHub read-only, the report channel and shared workspace docs/threads. - Find the AEO master doc and listings tracker. Create missing named docs on first run and tell the owner where they are; never invent historical status. - A new master doc should contain Status at a glance, This week, Decisions needed, Changelog, Alert log and Action tracker. Create a missing `## Action tracker` with action, owner, created date, evidence link, Status and Done columns. Leave unknown history empty. - Existing docs are read-only except scoped Status and Done cell updates in Action tracker. Docs may be type.com docs, Google Docs or Notion pages. ## Steps ### 1. Determine the day and window Use `timezone`. Mondays use the prior full Monday–Sunday week; all other days use yesterday's calendar day. Do not mix a rolling 24 hours with a calendar-day report. ### 2. Gather the evidence For both windows: 1. Read merged PRs in `content_repo` touching marketing pages, blog posts, guides, comparisons, docs, llms.txt, schema, crawl access, IndexNow, sitemaps, the skills library or trust/security pages. Ignore unrelated product and engineering PRs. 2. Read the master doc's Status at a glance, This week, Decisions needed, Action tracker and Alert log, plus relevant changelog entries. 3. Read `work_threads` active in the window concerning tracker/citations, directory or MCP listings, review sites, social AEO content, trust center, comparison pages, indexing, outreach and Reddit AEO. Distinguish completed, submitted/pending and owner-blocked work. 4. Read `report_channel` posts in the window for human updates and automated lost-citation, crawler, Reddit, entity-audit and publish-to-index results. For the daily report, also read PRs opened yesterday that remain open. For Monday, check current status of every listing in `listings_tracker`. ### 3. Classify honestly Call an item "published" or "live" only when a merged PR or source confirms that status. Drafts, open PRs, pending submissions and filled forms awaiting the owner belong under Waiting. A merged PR is shipping evidence; do not infer a successful deployment when the deployment is known to be pending. Never invent items. Omit empty categories. If yesterday was empty, say so in one line. ### 4. Maintain the Action tracker For each open row, check whether yesterday's merged PRs, live pages, listing-status changes or Alert log WIN entries demonstrate that exact action is done. Only then set Status to "done" and Done to yesterday's date, anchored on that row only. Never delete or reorder rows; never mark unrelated actions done. The source defines this upkeep for the daily workflow. Monday reads tracker status for the weekly counts; do not infer completion from a weekly summary alone. ### 5. Choose actions Daily: start with open tracker rows by owner and age, then merged pages needing indexing, PRs awaiting the owner, owner blockers and yesterday's lost-citation fix proposals. Keep at most 3, ordered. Monday: start with open tracker rows by age, then gaps; order at most 6 by impact on AI citations. Review sites with real reviews, Brave/Bing indexing fixes, machine-readable content and content for high-volume buyer questions rank highest. ### 6. Post Daily: post one message. Monday: post the title first and use its returned message/thread identifier for the content reply. Confirm the required post(s) succeeded before finishing. Do not post a weekly report draft on another skill's behalf. ## What it posts Daily, maximum 12 lines: ```text *AEO daily — * · shipped yesterday · open actions ( on ) *Do today* 1. : · 2. Eng: · 3. agent: · *Yesterday* • shipped: • site/technical: • outreach & listings: • tracking: lost, takeovers (), wins • waiting on : Details → ``` Include only populated categories; at most 5 Yesterday bullets. Monday standalone title: ```text *AEO weekly — Mon, * ``` Monday thread reply, maximum 20 lines: ```text *This week's priorities* 1. : · *Last week in numbers* • PRs shipped: • listings live: • tracker: done / added / open >14 days • daily alerts: lost, takeovers (), wins • crawler regressions: caught / fixed • tracker configuration changes: *Biggest gaps* • Details → ``` At most 6 priorities, 6 numeric recap bullets and 3 gap bullets. Full listings enumerations and structural analysis belong in the master doc, maintained by its owning workflow; this skill does not edit those sections. ## Output rules - Lead with action; Do today/priorities precede evidence. Every action is one line with owner, verb, exact object and link. - Use numbers, not adjectives. No preamble, "I checked", restating the task or caveats unless they change an action. - Details live in the master doc, linked once as "Details →". - Hard caps: daily 12 lines; weekly thread reply 20 lines. One idea per line. - Write `brand_name` exactly. Use plain owner labels, never channel @-mentions. ## Safety - Read-only on every third party, repo, social site and tracker. Never submit forms, send email/outreach, sign up, or comment, vote or post on Reddit, X, LinkedIn or any social/community site. - Never change tracker prompts, monitors, personas, models or schedules. - Only writes: posts to `report_channel`, initial creation of missing named docs/Action tracker, and scoped Status and Done cell updates with shipping evidence. - No DMs; any workflow that does send a DM must address only its configured owner. - Never @-mention anyone or put credentials, tokens or passwords in posts, docs or DMs. ## Example configuration How type.com configures this skill (example). - Brand: type.com, excluding type.ai; daily at 7:00am America/Los_Angeles; report channel #b-aeo; owner Sam. - It reads marketing-space threads about Promptwatch, listings, review sites, LinkedIn/YouTube AEO, the trust center, indexing, comparison pages and Reddit. - Example tracked work includes the AgentCore alternatives page, docs indexing, G2 reviews, MCP directory listings and the public skills library. - Oct 2026 panel changes and Codex collection dates are historical evidence for that week's report, not enduring schedule or baseline assumptions.