.agents/skills/clawdstrike-workstream-orchestrator/SKILL.md
Use when specs are mature enough to split work into parallel ClawdStrike lanes with explicit ownership, dependency graphs, verification gates, merge order, and agent briefs.
npx skillsauth add backbay-labs/clawdstrike clawdstrike-workstream-orchestratorInstall 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 is near and the missing artifact is coordination: workstreams, lane boundaries, dependencies, verification, and merge discipline.
Produce:
.codex/swarm/lanes.tsv and .codex/swarm/waves.tsv.codex/swarm/lanes.tsv and .codex/swarm/waves.tsv so execution metadata matches the docs.ORCH, P1A, or A3.docs/plans/multi-agent/overview.mddocs/plans/multi-agent/isolation-boundaries.mddocs/plans/multi-agent/coordination-protocols.mdapps/terminal/docs/dispatch-*.md.codex/swarm/lanes.tsv.codex/swarm/waves.tsvDo not launch workers from this skill unless the user explicitly asks. The job here is to make the execution topology real and unambiguous.
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