shared

Shared reference documents for multi-agent skills (not directly invocable)

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "shared" with this command: npx skills add boshu2/agentops/boshu2-agentops-shared

Shared References

This directory contains shared reference documents used by multiple skills:

  • validation-contract.md - Verification requirements for accepting spawned work
  • references/claude-code-latest-features.md - Claude Code feature contract (slash commands, agent isolation, hooks, settings)
  • references/backend-claude-teams.md - Concrete examples for Claude native teams (TeamCreate + SendMessage)
  • references/backend-codex-subagents.md - Concrete examples for Codex CLI and Codex sub-agents
  • references/backend-background-tasks.md - Fallback: Task(run_in_background=true)
  • references/backend-inline.md - Degraded single-agent mode (no spawn)
  • references/claude-cli-verified-commands.md - Verified Claude CLI command shapes and caveats
  • references/codex-cli-verified-commands.md - Verified Codex CLI command shapes and caveats
  • references/cli-command-failures-2026-02-26.md - Dated failure log and mitigations from live runs

These are not directly invocable skills. They are loaded by other skills (council, crank, swarm, research, implement) when needed.


CLI Availability Pattern

All skills that reference external CLIs MUST degrade gracefully when those CLIs are absent.

Check Pattern

# Before using any external CLI, check availability
if command -v bd &>/dev/null; then
  # Full behavior with bd
else
  echo "Note: bd CLI not installed. Using plain text tracking."
  # Fallback: use TaskList, plain markdown, or skip
fi

Fallback Table

CapabilityWhen MissingFallback Behavior
bdIssue tracking unavailableUse TaskList for tracking. Note "install bd for persistent issue tracking"
aoKnowledge flywheel unavailableWrite learnings to .agents/learnings/ directly. Skip flywheel metrics
gtWorkspace management unavailableWork in current directory. Skip convoy/sling operations
codexCLI missing or model unavailableFall back to runtime-native agents. Council pre-flight checks CLI presence (which codex) and model availability for --mixed mode.
cassSession search unavailableSkip transcript search. Note "install cass for session history"

Required Multi-Agent Capabilities

Council, swarm, and crank require a runtime that provides these capabilities. If a capability is missing, the corresponding feature degrades.

CapabilityWhat it doesIf missing
Spawn subagentCreate a parallel agent with a promptCannot run multi-agent. Fall back to --quick (inline single-agent).
Agent-to-agent messagingSend a message to a specific agentNo debate R2. Workers run fire-and-forget.
BroadcastMessage all agents at oncePer-agent messaging fallback.
Graceful shutdownRequest an agent to terminateAgents terminate on their own when done.
Shared task listAgents see shared work stateLead tracks manually.

Every runtime maps these capabilities to its own API. Skills describe WHAT to do, not WHICH tool to call.

After detecting your backend (see Backend Detection below), load the matching reference for concrete tool call examples:

BackendReference
Claude feature contractskills/shared/references/claude-code-latest-features.md
Claude Native Teamsskills/shared/references/backend-claude-teams.md
Codex Sub-Agents / CLIskills/shared/references/backend-codex-subagents.md
Background Tasks (fallback)skills/shared/references/backend-background-tasks.md
Inline (no spawn)skills/shared/references/backend-inline.md

Backend Detection

Use capability detection at runtime, not hardcoded tool names. The same skill must work across any agent harness that provides multi-agent primitives. If no multi-agent capability is detected, degrade to single-agent inline mode (--quick).

Selection policy (runtime-native first):

  1. If running in a Claude session and TeamCreate/SendMessage are available, use Claude Native Teams as the primary backend.
  2. If running in a Codex session and spawn_agent is available, use Codex sub-agents as the primary backend.
  3. If both are technically available, pick the backend native to the current runtime unless the user explicitly requests mixed/cross-vendor execution.
  4. Only use background tasks when neither native backend is available.
OperationCodex Sub-AgentsClaude Native TeamsOpenCode SubagentsInline Fallback
Spawnspawn_agent(message=...)TeamCreate + Task(team_name=...)task(subagent_type="general", prompt=...)Execute inline
Spawn (read-only)spawn_agent(message=...)Task(subagent_type="Explore")task(subagent_type="explore", prompt=...)Execute inline
Waitwait(ids=[...])Completion via SendMessageTask returns result directlyN/A
Retry/follow-upsend_input(id=..., message=...)SendMessage(type="message", ...)task(task_id="<prior>", prompt=...)N/A
Cleanupclose_agent(id=...)shutdown_request + TeamDelete()None (sub-sessions auto-terminate)N/A
Inter-agent messagingsend_inputSendMessageNot availableN/A
Debate (R2)SupportedSupportedNot supported (no messaging)N/A

OpenCode limitations:

  • No inter-agent messaging — workers run as independent sub-sessions
  • No debate mode (--debate) — requires messaging between judges
  • --quick (inline) mode works identically across all backends

Backend Capabilities Matrix

Prefer native teams over background tasks. Native teams provide messaging, redirect, and graceful shutdown. Background tasks are fire-and-forget with no steering — only a speedometer and emergency brake.

CapabilityCodex Sub-AgentsClaude Native TeamsBackground Tasks
Observe outputwait() resultSendMessage deliveryTaskOutput (tail)
Send message mid-flightsend_inputSendMessageNO
Pause / resumeNOIdle → wake via SendMessageNO
Graceful stopclose_agentshutdown_requestTaskStop (lossy)
Redirect to different tasksend_inputSendMessageNO
Adjust scope mid-flightsend_inputSendMessageNO
File conflict preventionManual git worktree routingNative isolation: worktree + lead-only commitsNone
Process isolationYES (sub-process)Shared worktreeShared worktree

When to use each:

ScenarioBackend
Quick parallel tasks, coordination neededClaude Native Teams
Codex-specific executionCodex Sub-Agents
No team APIs available (last resort)Background Tasks

Skill Invocation Across Runtimes

Skills that chain to other skills (e.g., /rpi calls /research, /vibe calls /council) MUST handle runtime differences:

RuntimeToolBehaviorPattern
Claude CodeSkill(skill="X", args="...")Executable — skill runs as a sub-invocationSkill(skill="council", args="--quick validate recent")
CodexN/ASkills not available — inline the logic or skipCheck if Skill tool exists before calling
OpenCodeskill tool (read-only)Load-only — returns <skill_content> blocks into contextCall skill(skill="council"), then follow the loaded instructions inline

OpenCode skill chaining rules:

  1. Call the skill tool to load the target skill's content into context
  2. Read and follow the loaded instructions directly — do NOT expect automatic execution
  3. NEVER use slashcommand syntax (e.g., /council) in OpenCode — it triggers a command lookup, not skill loading
  4. If the loaded skill references tools by Claude Code names, use OpenCode equivalents (see tool mapping below)

Cross-runtime tool mapping:

Claude CodeOpenCodeNotes
Task(subagent_type="...")task(subagent_type="...")Same semantics, different casing
Skill(skill="X")skill tool (read-only)Load content, then follow inline
AskUserQuestionquestionSame purpose, different name
TaskCreate, TaskUpdate, TaskList, TaskGettodoTask tracking (Claude uses 4 tools, OpenCode uses 1)
Read, Write, Edit, Bash, Glob, GrepSame namesIdentical across runtimes

Rules

  1. Never crash — missing CLI = skip or fallback, not error
  2. Always inform — tell the user what was skipped and how to enable it
  3. Preserve core function — the skill's primary purpose must still work without optional CLIs
  4. Progressive enhancement — CLIs add capabilities, their absence removes them cleanly

Reference Documents

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

council

No summary provided by upstream source.

Repository SourceNeeds Review
-1.5K
boshu2
Automation

swarm

No summary provided by upstream source.

Repository SourceNeeds Review
-281
boshu2
Automation

bug-hunt

No summary provided by upstream source.

Repository SourceNeeds Review
-258
boshu2