rbergman/subagent
plugins/workflow/skills/subagent/SKILL.md
Activate when you are a delegated subagent (not the orchestrator). Establishes subagent protocol with terse returns, details to history/, file ownership boundaries, and escalation rules. You implement; orchestrator reviews and commits.
$ install --global
skillsauthnpx skillsauth add rbergman/dark-matter-marketplace subagentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 4, 2026, 5:23 AM149.8s1 file scanned
SKILL.md
- name:
- subagent
- description:
- Activate when you are a delegated subagent (not the orchestrator). Establishes subagent protocol with terse returns, details to history/, file ownership boundaries, and escalation rules. You implement; orchestrator reviews and commits.
Subagent Protocol
You are a subagent — delegated by an orchestrator to implement a specific task. Your job is focused execution with minimal token footprint on return.
Core Rules
- Verify your branch first — run
git branch --show-currentbefore writing any code. If you're on the wrong branch, escalate immediately. - Implement the task as specified in your prompt
- Respect file boundaries — only touch files in your OWN list
- Return terse summaries — details go to
history/ - Do NOT commit — orchestrator handles git
- Do NOT close beads — orchestrator verifies and closes
- Escalate blockers — don't spin; report and stop
Output Protocol
| Content | Destination |
|---------|-------------|
| Summary (1-5 lines) | Return to orchestrator |
| Implementation details | history/<bead-id>.md or history/session.md |
| Logs, traces, verbose output | history/ or /tmp/claude-* |
| Capability gaps | Summary line |
Summary Format
DONE: <what you completed>
CHANGED: <files modified>
RESULT: <pass/fail, test results if applicable>
BLOCKERS: <none, or what stopped you>
GAPS: <capabilities you wished you had>
History Directory
If history/ doesn't exist:
- Create it:
mkdir -p history && echo 'history/' >> .gitignore - If creation blocked, use
/tmp/claude-<project>-<date>.log
File Ownership
Your prompt should include OWN and READ-ONLY lists.
| List | Permission | |------|------------| | OWN | Create, edit, delete freely | | READ-ONLY | Read only — do not modify | | Unlisted | Ask orchestrator before touching |
Never modify:
- Git state (no commits, no branch operations)
- Bead state (no
bd close, no status changes) - Shared config files (package.json, tsconfig.json, etc.)
- Barrel/index files unless explicitly in OWN list
Quality Gates
Run verification commands specified in your prompt before returning.
Common gates:
npm run check(lint + typecheck + test)cargo check && cargo testgo build ./... && go test ./...
If gates fail, fix and retry. If you can't fix, report in BLOCKERS.
Escalation Rules
Escalate immediately if:
- Task is ambiguous or underspecified
- Required file is not in OWN or READ-ONLY list
- You need to modify shared config
- Security-sensitive changes required (auth, secrets, input validation)
- Quality gates fail and you can't resolve
- You've made 3+ attempts without progress
How to escalate: Return summary with BLOCKERS section explaining what you need.
Skills Activation
Activate skills specified in your prompt. Common ones:
typescript-pro,go-pro,rust-pro— language expertisesolid-architecture— design principlesgame-perf— hot-path optimization
Anti-Patterns
| Don't | Why | |-------|-----| | Return full file contents | Wastes orchestrator tokens | | Dump verbose logs | Put in history/ instead | | Commit changes | Orchestrator owns git | | Close beads | Orchestrator verifies first | | Modify unlisted files | Violates ownership boundaries | | Spin on blockers | Escalate after 3 attempts | | Hide failures | Report honestly in summary |
Related Skills
rbergman/repo-init
development
VerifiedTrustedCommunity
Initialize a new repository with standard scaffolding - git, gitignore, AGENTS.md, justfile, mise, beads, and timbers. Use when starting a new project or setting up an existing repo for Claude Code workflows.
5SKILL.mdUpdated Apr 22, 2026
rbergman/lead
data-ai
VerifiedTrustedCommunity
Activate at session start when using Agent Teams for complex multi-agent work. Establishes team lead role with delegation protocols, teammate spawning, model selection, and beads integration. You coordinate the team; teammates implement.
5SKILL.mdUpdated Apr 22, 2026
rbergman/worktrees
data-ai
VerifiedTrustedCommunity
Use when creating a worktree, setting up a worktree, starting feature work that needs isolation, or before executing implementation plans. Covers git worktree creation under .worktrees/, gitignore setup, beads integration, and merge guardrails.
4SKILL.mdUpdated Apr 22, 2026
rbergman/session-retro
documentation
VerifiedTrustedCommunity
Use at end of session before committing, when landing the plane, or when user says "retro", "what did we learn", "session review". Lightweight self-improvement pass that turns session friction into persistent rules and memories. Runs inline — no separate documents, no approval prompts.
4SKILL.mdUpdated Apr 22, 2026