diff --git a/.agents/skills/aeo_crosslink_audit/SKILL.md b/.agents/skills/aeo_crosslink_audit/SKILL.md index d8d48447..8a27adeb 100644 --- a/.agents/skills/aeo_crosslink_audit/SKILL.md +++ b/.agents/skills/aeo_crosslink_audit/SKILL.md @@ -27,7 +27,7 @@ Do not: ## Source data Use the smallest reliable set of source data needed to justify link changes: -- **Peec MCP** - Review recent prompts, recommendations, source URLs, and query vocabulary related to agents, cloud agents, and orchestration. +- **Peec snapshot** - Read the snapshot file at `/workspace/buzz/aeo-snapshots/docs/agents-orchestration/latest.json`. This file is generated by a separate workflow and contains recent Peec prompts, query clusters, recommendations, source URLs, candidate docs areas, and open questions for the agents/cloud-agents/orchestration topic area. Use the `prompts`, `query_clusters`, `recommendations`, and `candidate_docs_areas` fields to identify user language and link opportunities. If the snapshot file does not exist or is older than 30 days (check `generated_at`), fall back to Peec MCP if available, or note that Peec data could not be loaded. - **Google Search Console** - When available, use the environment's `GSC_SERVICE_ACCOUNT_CREDENTIALS_JSON` secret to inspect recent queries and pages related to agents, cloud agents, and orchestration. Never print, log, commit, or include the secret value in reports. If a GSC client requires a credentials file path, write the secret to a restricted temporary file, use it for the run, and remove it before finishing. - **Docs repo** - Search existing pages under `src/content/docs/` for relevant source pages, link targets, and related terminology. @@ -35,7 +35,7 @@ If Peec or Google Search Console data is unavailable, say what could not be veri ## Workflow -1. **Gather source signals.** Use Peec MCP and Google Search Console data, when available, to identify relevant user language, prompts, recommendations, or pages. +1. **Gather source signals.** Read the Peec snapshot file and Google Search Console data, when available, to identify relevant user language, prompts, recommendations, or pages. 2. **Search existing docs.** Look for pages under `src/content/docs/` that already mention or imply related concepts in agents, cloud agents, or orchestration. 3. **Identify link opportunities.** Find up to 5 internal cross-link opportunities where: - The source page already mentions or implies the related concept.