docs: add AEO cross-links for agents and orchestration#232
Closed
rachaelrenk wants to merge 1 commit into
Closed
Conversation
Add monitoring cross-links from the triggers and integrations hub pages to Managing cloud agents, so readers who set up a trigger or integration can find where their runs are tracked and reviewed across the team. Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
rachaelrenk
added a commit
that referenced
this pull request
Jun 16, 2026
Transfer changes from PR #232 (docs/aeo-crosslinks-agents-orchestration-20260616): - integrations/index.mdx: add managing-cloud-agents cross-link - triggers/index.mdx: add managing-cloud-agents cross-link after trigger types Co-Authored-By: Oz <oz-agent@warp.dev>
Contributor
Author
|
Closing in favor of #228 — changes from this PR have been ported to that branch. |
rachaelrenk
added a commit
that referenced
this pull request
Jun 16, 2026
* docs: add AEO cross-links for agents and orchestration Add high-confidence internal cross-links for the agents, cloud agents, and orchestration topic area, grounded in Peec AEO signals (scheduling, managing and observing multiple agents) and existing docs: - Scheduled Agents reference now links to the Scheduled Agents quickstart for a guided, no-CLI setup path. - Run multiple agents at once guide now links to Agent notifications and the Agent Management Panel for notification setup and run observability. Co-Authored-By: Oz <oz-agent@warp.dev> * docs: add AEO cross-links for integrations and triggers pages Transfer changes from PR #232 (docs/aeo-crosslinks-agents-orchestration-20260616): - integrations/index.mdx: add managing-cloud-agents cross-link - triggers/index.mdx: add managing-cloud-agents cross-link after trigger types Co-Authored-By: Oz <oz-agent@warp.dev> --------- Co-authored-by: Oz <oz-agent@warp.dev>
rachaelrenk
added a commit
that referenced
this pull request
Jun 17, 2026
…skill (#234) * docs: add AEO cross-links for agents and orchestration Add high-confidence internal cross-links for the agents, cloud agents, and orchestration topic area, grounded in Peec AEO signals (scheduling, managing and observing multiple agents) and existing docs: - Scheduled Agents reference now links to the Scheduled Agents quickstart for a guided, no-CLI setup path. - Run multiple agents at once guide now links to Agent notifications and the Agent Management Panel for notification setup and run observability. Co-Authored-By: Oz <oz-agent@warp.dev> * docs: add AEO cross-links for integrations and triggers pages Transfer changes from PR #232 (docs/aeo-crosslinks-agents-orchestration-20260616): - integrations/index.mdx: add managing-cloud-agents cross-link - triggers/index.mdx: add managing-cloud-agents cross-link after trigger types Co-Authored-By: Oz <oz-agent@warp.dev> * feat: add run logging and Slack notifications to aeo_crosslink_audit skill - Add .agents/logs/aeo_crosslink_audit_runs.md as a durable run log committed to main after every scheduled run (PR or no-change) - Add Environment requirements section documenting SLACK_BOT_TOKEN and SLACK_CHANNEL_ID (same secrets already used by weekly-404-monitor) - Add workflow steps 7 and 8: write run log entry, then post simple text notification to #growth-docs; both fall back to run output gracefully - Add Run log format and Slack notification format reference sections - Update stale manual-sharing note in no-change report section Co-Authored-By: Oz <oz-agent@warp.dev> * fix: address PR review comments - Step 7: specify clean main checkout/worktree and path-limited staging to prevent accidentally pushing PR branch edits to main alongside log - Log file header: 'Appended' -> 'New entries are prepended' to match the skill's actual prepend instruction Co-Authored-By: Oz <oz-agent@warp.dev> --------- Co-authored-by: Oz <oz-agent@warp.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AEO cross-link audit: agents and orchestration
Small, high-confidence internal cross-link additions for the agents, cloud agents, and orchestration docs. Scope is limited to internal cross-linking; no new pages, rewrites, or broad SEO changes.
Goal
Identify small internal cross-link improvements for agents, cloud agents, and orchestration docs, focused on helping readers continue a real workflow.
Source signals
From the Peec snapshot at
buzz/aeo-snapshots/docs/agents-orchestration/latest.json(window 2026-05-05 to 2026-06-04), high-volume docs-adjacent prompts include:The snapshot's open questions also ask which page should be the canonical target for monitoring and reviewing cloud agent runs.
Managing cloud agents(the Agent Management Panel + Oz web app Runs page) is that canonical target, and both edited hub pages were missing a link to it.Google Search Console credentials were available in the environment, but the audit did not need GSC query data to justify these two links — the Peec prompts plus the repo-grounded gap on the hub pages were sufficient. No secret value was read, logged, or committed.
Pages touched
src/content/docs/agent-platform/cloud-agents/triggers/index.mdx— Thin hub page that listed trigger types but never pointed readers to where triggered runs are monitored.src/content/docs/agent-platform/cloud-agents/integrations/index.mdx— Integrations hub that explained setup but never linked to the run-monitoring surface for integration-triggered runs.Links added
triggers/index.mdx→managing-cloud-agents— Added a sentence after the trigger types list: after a trigger fires, track and review the resulting runs from the Agent Management Panel and Oz web app Runs page. Backed by the "track and observe in real time" and "scheduling and managing across a team" prompts.integrations/index.mdx→managing-cloud-agents— Added a "Managing cloud agents" item to the existing "Get started" list to monitor and review integration-triggered runs. Backed by the "track and observe in real time" and "trigger from Slack, Linear, or GitHub" prompts.Reader next step
A reader who just set up a trigger or an integration next wants to know where the resulting runs appear and how to review them across the team. Both pages previously dead-ended without pointing to the canonical monitoring surface; these links complete that workflow.
Open questions for human review
Managing cloud agentsis the preferred canonical monitoring target over the standaloneOz web apppage for these hub-page links (the snapshot raises this as an open question).Managing cloud agentswas chosen because it documents both the Agent Management Panel and the Oz web app Runs page in one place.Follow-up (out of scope for this cross-link pilot)
environmentspage. That is an accuracy/link-target fix rather than a cross-link addition, so it was left out of this audit.Conversation: https://app.warp.dev/conversation/45f77819-80e6-4961-9d2f-a6ac896d8621
Run: https://oz.warp.dev/runs/019ecfa8-b500-75cc-bd31-0056b8abb22a
This PR was generated with Oz.