Skip to content

fix: point AEO cross-link audit skill at Peec snapshot files #185

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rachaelrenk wants to merge 1 commit into from
+2 −2
Closed

fix: point AEO cross-link audit skill at Peec snapshot files #185

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .agents/skills/aeo_crosslink_audit/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,15 +27,15 @@ 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.

If Peec or Google Search Console data is unavailable, say what could not be verified and proceed only with repo-grounded recommendations. Do not invent source signals.

## 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.
Expand Down
Loading