chore(skills): use Peec PAT for aeo_crosslink_audit cloud agent - #392
Conversation
Replace the snapshot-based Peec workflow with direct Peec MCP access via a Personal Access Token (PEEC_PAT). The scheduled cloud audit agent can now call Peec MCP directly without requiring a locally-generated snapshot to be committed to the buzz repo. Changes: - aeo_crosslink_audit: remove snapshot freshness check, stale-snapshot report, and buzz repo snapshot references; add PEEC_PAT environment requirement and Peec MCP config instructions; update source data section and workflow step 1 to call Peec MCP directly; remove snapshot stale outcome from run log format and Slack notification - improve-aeo-crosslink-skill: update 'Peec unavailable' pattern to reference expired/missing PAT instead of stale snapshot files Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR updates the AEO cross-link audit skill to use live Peec MCP access with PEEC_PAT instead of committed Peec snapshots, and adjusts the monthly improvement skill's Peec-unavailability remediation guidance.
Concerns
- The monthly improvement skill's Peec-unavailability pattern still looks for
Peec: unavailable, but the run log format records availability asPeec unavailableunderSource signals; this can prevent the outer-loop skill from detecting repeatedPEEC_PATor MCP outages.
Verdict
Found: 0 critical, 1 important, 0 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
Add step 0 to the improve-aeo-crosslink-skill workflow that merges the standing chore/aeo-crosslink-audit-log PR into main before reading the run log. This ensures all accumulated entries are visible on main at analysis time without requiring a manual merge step before each monthly run. Falls back to reading the log from the feature branch if merge fails. Co-Authored-By: Oz <oz-agent@warp.dev>
Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com>
|
/oz-review |
|
I'm re-reviewing this pull request in response to a review request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR updates the AEO cross-link audit skills to use Peec MCP through a PAT instead of committed snapshots, and adds a monthly improvement step that merges the standing audit-log PR before analysis.
Concerns
- The new monthly skill workflow automatically merges the standing log PR using write credentials without first verifying that the PR is log-only and safe to merge.
- The same workflow refreshes the checkout with
git reset --hard, which can discard uncommitted workspace changes.
Security
- The automated
gh pr mergestep should validate the PR contents/status or avoid merging entirely by reading the log from the branch; otherwise an unexpected change on the standing branch could be merged intomainby the agent.
Verdict
Found: 0 critical, 2 important, 0 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
- Fix log format mismatch: pattern now matches 'Peec unavailable' in the Source signals field (no colon), matching the actual run log format - Add file-safety check before auto-merging the log PR: only merges if the PR exclusively touches the expected log file; falls back to reading from the branch if unexpected files are present - Replace 'git reset --hard' with 'git merge --ff-only' to avoid silently discarding uncommitted workspace changes Co-Authored-By: Oz <oz-agent@warp.dev>
Summary
Replaces the snapshot-based Peec workflow with direct Peec MCP access via a Personal Access Token (PAT), so the scheduled cloud audit agent no longer requires a locally-generated snapshot committed to the buzz repo.
Background
The
aeo_crosslink_auditcloud agent previously couldn't call Peec MCP directly because cloud agents don't support OAuth-based MCP auth. The workaround was a two-step process: generate a Peec snapshot locally (where OAuth works), commit it to buzz, then have the cloud agent read from that file. When the snapshot went stale (>14 days), the agent would abort.Peec MCP now supports Personal Access Tokens as a non-OAuth alternative — designed specifically for headless/CI use. Warp's cloud agent MCP config supports custom HTTP headers. Together, these unblock direct Peec MCP access from the cloud agent.
Changes
aeo_crosslink_audit/SKILL.mdPEEC_PATto environment requirements, with instructions for configuring Peec MCP in the agent configimprove-aeo-crosslink-skill/SKILL.mdPEEC_PATexpiry/config issues instead of stale snapshot filesmainbefore analysis, so entries are visible without a manual merge stepFollow-up actions
oz secret create --team PEEC_PAT{ "peec-ai": { "url": "https://api.peec.ai/mcp", "headers": { "Authorization": "Bearer ${PEEC_PAT}" } } }The snapshot files in buzz are retained as historical artifacts but are no longer read by the cloud agent.
Oz conversation
Co-Authored-By: Oz oz-agent@warp.dev