.agents/skills/clawdstrike-swarm-supervisor/SKILL.md
Use when it is time to create worktrees, launch Codex worker lanes, monitor background jobs, resume finished or stalled sessions, run review, and advance a ClawdStrike swarm through its waves.
npx skillsauth add backbay-labs/clawdstrike clawdstrike-swarm-supervisorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when execution should move from docs and plans into live Codex worker orchestration.
Drive toward:
Prefer the repo-local command suite:
scripts/codex-swarm/setup-worktrees.shscripts/codex-swarm/bootstrap-lane.shscripts/codex-swarm/launch-lane.shscripts/codex-swarm/launch-wave.shscripts/codex-swarm/status.shscripts/codex-swarm/resume-lane.shscripts/codex-swarm/review-lane.shUse plain git worktree and codex exec only when you need to inspect or patch
the orchestration flow itself.
.codex/swarm/*.tsv metadata are current..codex/swarm/lanes.tsv.codex/swarm/waves.tsvDo not treat "workers are running" as success. Success is controlled progress: bounded lane execution, review, merge, and wave advancement.
testing
A simple skill demonstrating clawdstrike security
tools
# Hello Skill A simple greeting skill that demonstrates secure agent operation. ## Description This skill allows the agent to greet users and perform basic file operations within the allowed workspace. ## Capabilities - Generate personalized greetings - Read files from the workspace - Write greeting logs to the output directory ## Usage Ask the agent: - "Say hello to Alice" - "Read the welcome message from data/welcome.txt" - "Log a greeting for Bob" ## Examples ### Basic Greeting **Us
testing
# bb-edr: Triage Skill Use this skill to turn clawdstrike audit logs into an incident report and a minimal response plan. ## Inputs - `.hush/audit.jsonl` (JSONL) — clawdstrike audit events (allowed/denied, guard, reason). - `policy.yaml` — the active security policy. ## Task 1. Read and summarize the last ~50 audit events. 2. Focus on **denied** events first: - Group by `guard` (e.g., `forbidden_path`, `egress`, `patch_integrity`) - Identify likely intent (misconfiguration vs. suspici
tools
Threat hunting and security event investigation