This directory contains shared reference documents used by multiple skills:
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsharedExecute the skills CLI command in your project's root directory to begin installation:
Fetches shared from boshu2/agentops and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate shared. Access via /shared in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
260
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
260
stars
This directory contains shared reference documents used by multiple skills:
validation-contract.md - Verification requirements for accepting spawned workreferences/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-agentsreferences/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 caveatsreferences/codex-cli-verified-commands.md - Verified Codex CLI command shapes and caveatsreferences/cli-command-failures-2026-02-26.md - Dated failure log and mitigations from live runsThese are not directly invocable skills. They are loaded by other skills (council, crank, swarm, research, implement) when needed.
All skills that reference external CLIs MUST degrade gracefully when those CLIs are absent.
# 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
| Capability | When Missing | Fallback Behavior |
|---|---|---|
bd |
Issue tracking unavailable | Use TaskList for tracking. Note "install bd for persistent issue tracking" |
ao |
Knowledge flywheel unavailable | Write learnings to .agents/learnings/ directly. Skip flywheel metrics |
gt |
Workspace management unavailable | Work in current directory. Skip convoy/sling operations |
codex |
CLI missing or model unavailable | Fall back to runtime-native agents. Council pre-flight checks CLI presence (which codex) and model availability for --mixed mode. |
cass |
Session search unavailable | Skip transcript search. Note "install cass for session history" |
| Model tier config | .agentops/config.yaml missing |
Use built-in defaults (quality=opus, balanced=sonnet, budget=haiku). Tier resolution falls through to "balanced". |
Council, swarm, and crank require a runtime that provides these capabilities. If a capability is missing, the corresponding feature degrades.
| Capability | What it does | If missing |
|---|---|---|
| Spawn subagent | Create a parallel agent with a prompt | Cannot run multi-agent. Fall back to --quick (inline single-agent). |
| Agent-to-agent messaging | Send a message to a specific agent | No debate R2. Workers run fire-and-forget. |
| Broadcast | Message all agents at once | Per-agent messaging fallback. |
| Graceful shutdown | Request an agent to terminate | Agents terminate on their own when done. |
| Shared task list | Agents see shared work state | Lead 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:
| Backend | Reference |
|---|---|
| Claude feature contract | skills/shared/references/claude-code-latest-features.md |
| Claude Native Teams | skills/shared/references/backend-claude-teams.md |
| Codex Sub-Agents / CLI | skills/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 |
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):
TeamCreate/SendMessage are available, use Claude Native Teams as the primary backend.spawn_agent is available, use Codex sub-agents as the primary backend.| Operation | Codex Sub-Agents | Claude Native Teams | OpenCode Subagents | Inline Fallback |
|---|---|---|---|---|
| Spawn | spawn_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 |
| Wait | wait(ids=[...]) |
Completion via SendMessage |
Task returns result directly | N/A |
| Retry/follow-up | send_input(id=..., message=...) |
SendMessage(type="message", ...) |
task(task_id="<prior>", prompt=...) |
N/A |
| Cleanup | close_agent(id=...) |
shutdown_request + TeamDelete() |
None (sub-sessions auto-terminate) | N/A |
| Inter-agent messaging | send_input |
SendMessage |
Not available | N/A |
| Debate (R2) | Supported | Supported | Not supported (no messaging) | N/A |
OpenCode limitations:
--debate) — requires messaging between judges--quick (inline) mode works identically across all backendsPrefer 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.
| Capability | Codex Sub-Agents | Claude Native Teams | Background Tasks |
|---|---|---|---|
| Observe output | wait() result |
SendMessage delivery |
TaskOutput (tail) |
| Send message mid-flight | send_input |
SendMessage |
NO |
| Pause / resume | NO | Idle → wake via SendMessage |
NO |
| Graceful stop | close_agent |
shutdown_request |
TaskStop (lossy) |
| Redirect to different task | send_input |
SendMessage |
NO |
| Adjust scope mid-flight | send_input |
SendMessage |
NO |
| File conflict prevention | Manual git worktree routing |
Native isolation: worktree + lead-only commits |
None |
| Process isolation | YES (sub-process) | Shared worktree | Shared worktree |
When to use each:
| Scenario | Backend |
|---|---|
| Quick parallel tasks, coordination needed | Claude Native Teams |
| Codex-specific execution | Codex Sub-Agents |
| No team APIs available (last resort) | Background Tasks |
Skills that chain to other skills (e.g., /rpi calls /research, /vibe calls /council) MUST handle runtime differences:
| Runtime | Tool | Behavior | Pattern |
|---|---|---|---|
| Claude Code | Skill(skill="X", args="...") |
Executable — skill runs as a sub-invocation | Skill(skill="council", args="--quick validate recent") |
| Codex | N/A | Skills not available — inline the logic or skip | Check if Skill tool exists before calling |
| OpenCode | skill tool (read-only) |
Load-only — returns <skill_content> blocks into context |
Call skill(skill="council"), then follow the loaded instructions inline |
OpenCode skill chaining rules:
skill tool to load the target skill's content into context/council) in OpenCode — it triggers a command lookup, not skill loadingCross-runtime tool mapping:
| Claude Code | OpenCode | Notes |
|---|---|---|
Task(subagent_type="...") |
task(subagent_type="...") |
Same semantics, different casing |
Skill(skill="X") |
skill tool (read-only) |
Load content, then follow inline |
AskUserQuestion |
question |
Same purpose, different name |
TaskCreate, TaskUpdate, TaskList, TaskGet |
todo |
Task tracking (Claude uses 4 tools, OpenCode uses 1) |
Read, Write, Edit, Bash, Glob, Grep |
Same names | Identical across runtimes |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
shared is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
shared has been reliable in day-to-day use. Documentation quality is above average for community skills.
shared reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added shared from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for shared matched our evaluation — installs cleanly and behaves as described in the markdown.
shared fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for shared matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in shared — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
shared reduced setup friction for our internal harness; good balance of opinion and flexibility.
shared is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 46