No skills match your search.
Git & Deploy 5 skills
/push
Git
Commit, push, and deploy — smart. Detects what changed (dashboard, src, store, config) and runs only the required deploy steps. Handles stash/rebase to avoid rejection on diverged branches.
When After any logical unit of work that changed files. Most-used command in the session lifecycle.
/push
/pull
Git
Pull the latest commits for the current repo using --ff-only. Shows what changed if new commits were pulled. Stops if branches have diverged — never merges or force-ops.
When Start of any resumed or forked session. SessionStart hook only fires on new sessions.
/pull
/sync
Git
Pull-then-push in a single command. Detects diverged branches and stops safely. Best when another chat may have pushed since your last pull and you also have local changes to ship.
When Concurrent sessions active. Combines /pull + /push safely.
/sync
/ops-sync
GitSystem
Sync completed work to the ops dashboard and GitHub issues. Creates or updates GitHub issue for the work, PATCHes ops project status, and outputs a confirmation summary. Reads DASHBOARD_SECRET from .env.
When After a feature batch ships. NOT after every commit. Run: /push → /update-tracking → /ops-sync.
/ops-sync
/update-tracking
Git
Update internal docs after a feature batch: CHANGELOG, PROGRESS.md, and .claude/context/ files. Runs before /ops-sync. Captures what was built in session memory, not external tracking.
When After meaningful feature batch. Order: /push → /update-tracking → /ops-sync.
/update-tracking
Bounty Hunting 6 skills
/bounty-preval
BountySonnet
10-block pre-validation gate that must pass before any finding is marked SUBMIT-READY. Checks: program status, placeholders, OOS placement, duplicate, audit grep, PoC validation (EVM gas / web2 response body / RPC), TVL, source reachability, defense baseline, governance precondition, and public gist verify.
When After forge test passes. After full report is written. After any major PoC revision. Non-negotiable gate.
/bounty-preval <finding-id> # e.g. /bounty-preval lombard-1
/bounty-submit
Bounty
Atomically update all bounty tracking files when a finding is submitted or status-changes. Updates store/bounty-log.json, SUBMIT-NEXT.md, SUBMISSIONS.md, and the report file status line in one response. Commits and pushes on completion.
When Finding is SUBMIT-READY and you've submitted to the platform. Also for status changes (rejected, duplicate).
/bounty-submit lombard-1 Immunefi high "Title here" /bounty-submit berachain-2 Cantina critical "MEV path" rejected_disputed
/risk-check
BountySystem
Classify risk before acting. Assigns Low / Medium / High tier with safeguards, rollback path, and assumptions. High = stop and ask user. Covers production data, destructive commands, and broad-scope refactors.
When Before any action with production data, deployment commands, migrations, or broad code changes.
/risk-check # run before risky operation
/verify
BountyDev
Structured verification of a code change. Selects tier (Quick Smoke / Targeted Regression / Deep Verification), runs explicit checks with verbatim command output, and reports coverage gaps. Every PASS must be backed by executed output — not code inspection.
When After implementation. Before marking a change done. Pairs with /verification-specialist for delegated adversarial pass.
/verify
/verification-specialist
BountySonnet
Sub-agent prompt for adversarial verification. Spawns an independent worker that tries to break the implementation (not rubber-stamp it). Probes concurrency, boundary values, idempotency, and orphan operations. Returns PASS / FAIL / PARTIAL with verbatim evidence.
When Implementation touches auth, payments, data integrity, or shared infra. Use via /create-team after implementation is complete.
/verification-specialist # paste into /create-team worker prompt
/companion-close
System
Session close hook. Rewrites Continuity.md (dated block: what changed, what's open, gotchas), updates CONVERGEHERE.md (last session state + next action), and appends to session-journal.md via script. Run before ending any session.
When End of every session. Ensures the next session boots with accurate context.
/companion-close
Agents & Teams 4 skills
/create-sub
Agents
Spawn a single sub-agent for a one-off task. Always use this instead of the bare Agent tool. Keeps lead context clean for coordination. For any task that takes >2 minutes or >5 tool calls, delegate via create-sub.
When Single focused task that would pollute lead context. Research, report writing, file analysis, implementation of a defined spec.
/create-sub "Write the lombard-2 report draft using the hypothesis file at groups/bounty-team/targets/lombard-finance/H-002.json"
/create-team
Agents
Spawn parallel sub-agents for independent tasks. Specify model per teammate to control cost. Haiku for lookup/search, Sonnet for implementation, never Opus for teammates. Cap: 3-5 typical, 15 max. Each worker prompt must be fully self-contained.
When Multiple independent tasks that can run in parallel. Research sweeps, multi-target analysis, implementation + testing simultaneously.
/create-team "3 Sonnet teammates: T1: run bounty-preval on berachain-1 T2: run bounty-preval on chainlink-2 T3: fetch audit PDFs for origin-protocol"
/coordinator
AgentsOpus
Orchestration protocol for multi-agent work with 3+ workers or multi-phase pipelines (Research → Synthesis → Implementation → Verification). Lead directs, synthesizes, and verifies. Never delegates comprehension. Worker prompts must be self-contained with file paths and success criteria.
When Complex multi-phase work requiring coordination across 3+ workers. Architecture decisions, large refactors, full bounty pipelines.
/coordinator # load protocol before spawning team
team-orchestration
Agents
Rules for spawning and managing Claude Code teams efficiently. Defines model tiers (Haiku=1x cost, Sonnet=10x, Opus=60x), spawn caps (15 max), team patterns (research/implementation/mixed), and cost controls. Never use Opus for teammates.
When Reference before spawning any team. Contains templates for research teams (2-3 Haiku), implementation teams (2-3 Sonnet), and mixed teams.
# Always specify model in spawn prompt "Create a team with 3 teammates using claude-sonnet-4-6 for each"
Autonomous Loops 5 skills
/auto-dev
LoopBounty
Autonomous anytime development loop for the bounty team. Runs the full pipeline continuously: pick target → clone → recon → hypothesis → PoC → preval gate → report. Self-paces using ScheduleWakeup. Can run unattended for hours.
When Leaving Claude Code running to work autonomously. Good for weekday day runs with active oversight available.
/auto-dev
/auto-night
LoopBounty
Overnight bounty hunting run. Extended autonomous loop optimized for unattended execution — longer sleep intervals, conservative gas estimates, skips anything requiring human confirmation. Runs full pipeline while you sleep.
When End of day, leaving Claude Code running overnight. Start before bed, check results in the morning.
/auto-night
/loop
Loop
Run a prompt or slash command on a recurring interval using ScheduleWakeup. Omit the interval to let the model self-pace. Cache-aware: stays under 300s to keep context warm. Use for polling, repeated checks, or any task needing periodic execution.
When Any task that needs to repeat: checking build status, polling a pipeline, running a preval sweep every 30 minutes.
/loop 5m /gsd:next /loop 30m /bounty-preval berachain-1 /loop # self-paced (model picks interval)
/schedule
LoopSystem
Create, update, list, or run scheduled remote agents (triggers) that execute on a cron schedule. Manages persistent schedules that survive session restarts. Use for recurring tasks that need to run even when Claude Code is not active.
When Setting up recurring autonomous tasks: nightly bounty run, daily dependency scan, weekly ops-sync.
/schedule create "0 2 * * *" "/auto-night" # 2am nightly /schedule list /schedule delete <id>
/init-project
LoopDev
Bootstrap a self-improving agent kit for a new project. Sets up the .claude/ directory structure, CLAUDE.md, learnings/, and companion context files. Creates the foundation for autonomous development loops on a new codebase.
When Starting work on a new project or repo that doesn't yet have the agent scaffolding in place.
/init-project
Research & Analysis 3 skills
/research
ResearchSonnet
Decompose a topic into 2-3 search queries, cross-validate across 2+ sources, and output a structured knowledge entry with confidence level (High/Medium/Low) and expiry date. Optionally appends to 06-RAGFILE.md or a specified knowledge base section.
When Before implementing integrations, when memory-check reveals a gap, before architectural decisions about unfamiliar tech.
/research "LayerZero V2 executor trust model" /research "EigenLayer withdrawal queue" --update-ragfile /research "Uniswap V4 hooks" --section "DeFi Protocols"
/ollama-hunt
ResearchBounty
Process handoff files from Pi + Ollama scout/reason passes. Reads hypothesis JSON (confidence > 0.7, rejection_risk < 8), writes Foundry fork tests, runs them, and converts passing tests into Cantina-format reports. Logs failures with root-cause analysis.
When After Pi + Ollama have run their scout pass on a target and written a HANDOFF.md to the ollama-findings/ directory.
/ollama-hunt process berachain /ollama-hunt process lombard-finance
/deps-scan
ResearchSystem
Scan all package.json and requirements.txt files against the OSV.dev vulnerability database (no API key required). Filters to CRITICAL/HIGH severity. 50ms rate limiting. With --alert, appends findings to .learnings/ERRORS.md.
When Weekly (Monday recommended). Before major releases. After adding new dependencies.
/deps-scan /deps-scan --alert
Dev Tools 7 skills
/gsd:quick
Dev
Run a single described task with full GSD guarantees: execute completely, verify all files updated, commit via /push, report back in one sentence. Applies all CLAUDE.md rules including ACL gate and 3-file atomic updates for bounty reports.
When Ad-hoc one-off task that needs full quality guarantees without a full loop session.
/gsd:quick write the capyfi-001 report and add it to SUBMIT-NEXT.md /gsd:quick run bounty-preval on lombard-1
/gsd:next
Dev
Auto-detect and begin the highest-priority incomplete task. Reads tasks.md and HANDOFF.json. Priority: active task from HANDOFF → carry_forward → unchecked tasks.md → SUBMIT-NEXT rows → hunt a new target. No asking, no planning — just execute.
When Starting a session or after completing a task and wanting to auto-advance to the next thing.
/gsd:next
/gsd:pause
Dev
Save session state before stopping. Writes HANDOFF.json with active task, last completed step, next steps, and carry_forward items. Appends a row to LEDGER.md. Runs /push to commit everything including HANDOFF.json for pickup by another session.
When Stopping mid-task and want to resume cleanly later or hand off to another session.
/gsd:pause
/gsd:resume
Dev
Restore from last session by reading HANDOFF.json and resuming at next_steps[0]. If loop_state is complete, falls through to /gsd:next. Appends resumed row to LEDGER.md. Falls back to cold-start /gsd:next if no HANDOFF.json exists.
When Starting a resumed session. Replaces having to re-read all context manually.
/gsd:resume
self-improvement
DevSystem
Log learnings, errors, and corrections to .learnings/ for continuous improvement. Recurring patterns (3+ occurrences) get promoted to CLAUDE.md as permanent rules. Covers LRN (learning), ERR (error), and FEAT (feature request) entry types.
When Command fails, user corrects you, knowledge is outdated, better approach is found, or a feature is missing.
# Entry types: # LRN-YYYYMMDD-XXX — learnings / corrections # ERR-YYYYMMDD-XXX — errors / failures # FEAT-YYYYMMDD-XXX — feature requests
/simplify
Dev
Review changed code for reuse, quality, and efficiency, then fix any issues found. A post-implementation quality pass that catches over-engineering, missed reuse opportunities, and unnecessary complexity introduced during fast implementation.
When After implementing a feature. Before /push if the change was complex.
/simplify
/init-project
Dev
Bootstrap a self-improving agent kit for a new project. Sets up the .claude/ directory, CLAUDE.md, learnings/ structure, and companion context files needed for autonomous development loops.
When New project or repo that doesn't yet have the agent scaffolding.
/init-project
I/O & Comms 5 skills
/speak
Comms
Reads text aloud using edge-tts (Microsoft Aria Neural, high quality) or macOS `say` as fallback. Speak specific text or speak Claude's last response. No API key required for either method. edge-tts sends text to Microsoft TTS servers.
When Hands-free monitoring of long autonomous runs. Auditory alerts on completion or errors.
/speak # speak last response /speak "Preval complete" # speak specific text /speak last # alias for no-args
/speak-toggle
Comms
Toggle automatic text-to-speech on or off. When enabled, Claude speaks every response aloud after replying. State persisted in ~/.claude/.voice-speak. Runs a test speak when enabling to confirm audio works.
When Starting an unattended run where you want audio alerts. Toggle off when back at desk.
/speak-toggle # on ↔ off
/voice
Comms
Record microphone audio on macOS and transcribe it into your next prompt using Whisper (offline) or OpenRouter fallback. Records for 10 seconds by default. Audio saved to /tmp only, deleted immediately after transcription.
When Hands are busy. Dictating long instructions faster than typing. Voice-driven task queuing.
/voice # 10 second default /voice 20 # 20 second capture /voice 5 # quick 5 second
/telegram:configure
Comms
Set up the Telegram channel — save the bot token and configure review access policy. Use when pasting a Telegram bot token, asking to configure Telegram, setting up @Drake (@drakemayebot), or checking channel status.
When First-time setup or reconfiguring the Telegram bot integration for the @Drake persona channel.
/telegram:configure
/telegram:access
Comms
Manage Telegram channel access — approve pairings, edit allowlists, set DM/group policy. Use when approving someone, checking who's allowed, or changing the access policy for the @Drake Telegram channel.
When Someone needs access to the @Drake channel. Managing who can reach you via Telegram bot.
/telegram:access
Bounty-Team Hunter Skills 26 skills
skill-active-hunter
HunterOpus
Master orchestration skill. Given a target, runs the full discovery pipeline: repo verification → recon → static analysis → protocol classification → grep patterns → hypothesis generation → PoC stubs. Outputs structured JSON hypothesis files ready for analyze-logic and write-poc.
When Starting work on a new bug bounty target from scratch. The entry point for full automated hunting.
Target name: lombard-finance Deployed addresses: 0x...
skill-hypothesis-generator
HunterSonnet
Generate scored, prioritized vulnerability hypothesis JSON records from source code. Input: contract file path + protocol type (DEX/lending/vault/oracle/bridge/staking/governance). First extracts full function signatures with modifiers before reading function bodies.
When After cloning and mapping a target repo, before fork testing. Never generate hypotheses without checking audit-index.md first.
contract_path: contracts/LombardStaking.sol protocol_type: staking
skill-pattern-grep
Hunter
Automated vulnerability detection patterns covering all 27 bug classes + Class 28 ACL gate. Exact ripgrep commands for positive indicators (vulnerability present), negative indicators (guard absent = vulnerable), false positive filters, and confidence scoring. Run ACL gate FIRST.
When Before any manual review of a target. Run pattern-grep against the entire repo to triage which bug classes are worth investigating.
# Class 28 ACL gate — run before all others rg "onlyOwner|onlyRole|onlyAdmin|requiresAuth" contracts/
skill-audit-fetcher
Hunter
Automates downloading and cataloguing all publicly available audit reports for a target. Creates audit-index.md as a master record (cached, gated, blocked). Run at target-setup time — BEFORE hypothesis generation to avoid proposing already-documented issues.
When Always run before writing any hypothesis. Never generate a hypothesis without first checking audit-index.md.
mkdir -p groups/bounty-team/targets/lombard-finance/audits # Then invoke skill to scrape + download all audit PDFs
skill-quality-gate
HunterOpus
Independent second-model review of PoC + report before SUBMIT-READY status. Catches false positives and submission errors missed by the writing agent. Run AFTER forge test is green AND Superpowers code review is clean. Final gate before preval.
When Before marking any hypothesis SUBMIT-READY, CANTINA_READY, or status: validated with intent to submit.
# Activate before marking: # SUBMIT-READY / CANTINA_READY / status: validated
skill-web-recon
Hunter
Structured reconnaissance pipeline for web2 bug bounty targets (HackerOne, SaaS, fintech, marketplace) with no source code. Maps external attack surface before testing. Output feeds directly into skill-idor-access-control and skill-auth-bypass.
When Any live web application target. Read this first — do not test anything until recon is complete.
# Phases: asset discovery → tech stack → auth flow mapping # → endpoint enumeration → JS analysis → auth flow → API
skill-auth-bypass
Hunter
Systematic methodology for auth bypass: OAuth misconfigurations (redirect_uri, state parameter), JWT attacks (alg:none, key confusion), session management failures, MFA bypasses. Second-highest yield web2 bug class. Requires skill-web-recon Phase 6-7 as input.
When After recon Phase 6-7 has mapped the auth flow. Any web2 HackerOne target with OAuth, JWT, or session auth.
# Input: auth flow map from skill-web-recon Phase 6-7 # Test proxy + OAuth domain control configured
skill-idor-access-control
Hunter
Systematic IDOR and access control testing methodology. Highest-yield web2 bug class. Tests horizontal privilege escalation (access other users' resources) and vertical escalation (access admin functionality). Requires recon output as input.
When After web-recon maps endpoints. Any web2 target with user-scoped resources or role-based access.
# Pattern: capture user A request → replay as user B # Check: IDs, UUIDs, email params, role headers
Bug Class Library (Classes 1–27)
Hunter
27-class vulnerability taxonomy covering: component mismatch, array index invariant, async withdrawal race, callback state pollution, cross-chain race, deposit ordering, fee-on-transfer, flash governance, proxy storage collision, read-only reentrancy, reward dilution, MEV protocol damage, multi-hop precision loss, EIP-2612 permit replay, keeper griefing, self-scaling DoS, permit frontrun DoS, and more.
When After cloning target. Read the relevant class file before writing any hypothesis for that bug type.
# Each class file: archetype • checklist • key insight • test vector # File naming: skill-<class-name>.md
skill-session-ledger
Hunter
Track bounty session state: hypotheses opened, tested, closed, and deferred. Maintains pipeline visibility across multi-session investigations. Pairs with HANDOFF.json for session-to-session continuity.
When During active bounty hunting sessions. Log hypothesis state changes as they happen.
LEDGER.md row format: | timestamp | action | hypothesis_id | status | notes |
skill-repo-setup
Hunter
Bootstrap a target repo for bounty hunting: clone, install dependencies, configure Foundry, set up fork test environment with RPC URLs, verify forge test runs cleanly. Creates the working directory structure under groups/bounty-team/targets/.
When First step when starting work on any new bounty target. Run before any analysis or hypothesis work.
mkdir -p groups/bounty-team/targets/lombard-finance/repo cd groups/bounty-team/targets/lombard-finance/repo git clone <url> protocol && cd protocol && forge install
Additional Specialist Skills
Hunter
Specialized skills: skill-mev-protocol-damage, skill-twap-window-manipulation, skill-keeper-griefing, skill-flash-governance, skill-zk-circuit-under-constrained, skill-zk-evm-l2-state-transition, skill-trusted-input-branching, skill-upstream-spec-diff, skill-error-type-propagation, skill-fuel-gas-asymmetry, skill-governance-timelock-packing, skill-eip2612-permit-replay, skill-partial-signature-replay, skill-proxy-storage-collision, skill-read-only-reentrancy.
When After pattern-grep identifies a likely bug class. Read the specific class skill file for checklist + test vector.
groups/bounty-team/skills/skill-<class>.md
skill-hackerone-submission
Hunter
Report format and submission template for HackerOne (web2) bug bounty submissions. Covers title format, severity/CVSS/CWE fields, description structure, steps to reproduce, impact statement, and supporting materials. Used for H1 Critical/High findings only (program-level constraint).
When Writing any HackerOne submission. Only Critical/High to H1 per signal constraint.
# Title: [COMPONENT] Short impact description # Severity: Critical | High # CWE: CWE-XXX # Steps: numbered, exact, reproducible
Support Skills
Hunter
Supporting reference skills: pre-submission-gate.md (preval runner), kiln-web-redteam.md (Kiln web app testing), building-secure-contracts.md (secure coding patterns), protocol-type-mapping.md (map protocol to bug class priority), red-team-tools.md (tooling reference), submission-psychology.md (framing + triage psychology).
When Referenced during specific phases of the pipeline. Not invoked directly — read as needed.
groups/bounty-team/skills/<skill-name>.md
Container Skills (Planned / Stubs) 25 stubs
agdp-acp
agdp-testing
agent-browser
agent-orchestration
auto-polymarket
auto-quant
automated-researcher
bounty
bounty-discovery
bounty-pipeline
bounty-submit
clawtasks
defi
dependency-watchdog
drake-ops
dropship
leia
memory-manager
moltbook
overnight-dev
polymarket-maker
process-auditor
prompt-engineer
trading
xpr-metal