ai-pair
SolidAI Pair Collaboration Skill. Coordinate multiple AI models to work together: one creates (Author/Developer), two others review (Codex + Gemini). Works for code, articles, video scripts, and any creative task. Trigger: /ai-pair, ai pair, dev-team, content-team, team-stop
Install
Quality Score: 87/100
Skill Content
Details
- Author
- axtonliu
- Repository
- axtonliu/ai-pair
- Created
- 2 months ago
- Last Updated
- 2 months ago
- Language
- N/A
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
ai-collab-bridge
A collaboration protocol for Claude, Codex, and other CLI-capable AI models to review each other's code via CLI handoffs. Use this skill whenever the user mentions AI-to-AI collaboration, Claude-Codex bridge, peer review between AI models, "let Claude check what Codex did", "have Codex verify Claude's work", multi-agent code review, AI handoff, two AIs reviewing each other, or wants two different AI models to verify each other's output before completing a task. Also use whenever you (the running AI) want a second opinion from another model and need a structured way to request that review, even if the user did not explicitly ask for it.
pair-agent-harness
Harness two AI agents (typically Claude + OpenAI Codex, or two Claudes, or an agent + human reviewer) into a Reviewer / Implementor pair that collaborate asynchronously through a shared markdown thread. One agent reviews / critiques / asks pointed questions; the other implements / responds / drives the code changes; the file mediates. Use when the user says "pair another agent on this", "harness Codex on this", "review this with Codex", "open a Codex thread", "respond to Codex", "open a peer review", "monitor this review file", names a *-review-thread.md or *-dialogue-thread.md, or wants to coordinate structured async back-and-forth between two AI agents on a code or design question. Seeds the file from a template if missing, appends a numbered Claude response under its own section header, arms a file-mtime monitor so each peer append triggers a fresh read + response, drives the pyramid-principle response shape (position first, justification second), detects consensus markers like "Final ACK" / "No further ob
reviewing-code-multi-ai
Orchestrates multiple AI tools (Claude, Codex, Gemini, Droid) for comprehensive code review from multiple perspectives. Use for "멀티 AI 리뷰", "코드 리뷰", "종합 리뷰" requests or when thorough multi-agent review is needed.
ai-team-orchestration
Multi-agent dev team — parallel AI agents, roles, coordination, project kickoff
ai-team-workflow
Organize AI agents as a structured team — role assignment, proposal/vote/ review/ship cycle, cross-agent code review, consensus mechanisms, and escalation to human for deadlocks. Use when asked about "AI team", "agents working as a team", "multi-agent workflow", "agent roles", "agent review", "agents vote", "Hivemoot", "AI proposes and votes", "agent consensus", "agents reviewing each other's work", "define agent roles", "AI standup", or "autonomous team of agents". Do NOT use for: git-based task coordination — see git-native-agent-protocol. Do NOT use for: safety gates — see agent-safety-patterns.