git
git workflows for agents: ship (stage → commit → push), worktree (parallel branches), hunks (selective staging). never force push, never git add -A, conventional commits. triggers on: commit, push, stage, ship,...
Browse published AI skills maintained by bdsqqq. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
14Repository stars across indexed skills
197Repository forks
30Average repository stars per indexed skill
14Repository stars may repeat across skills from the same repository.
git workflows for agents: ship (stage → commit → push), worktree (parallel branches), hunks (selective staging). never force push, never git add -A, conventional commits. triggers on: commit, push, stage, ship,...
adversarial review via spawned antithesis agent. use to prune false positives from EXISTING findings. NOT for discovery or when claim is verifiable against single source.
apply documentation philosophy — explain why, not what. use for jsdocs, READMEs, inline comments.
manage background processes in tmux windows. use when running dev servers, build watchers, or any long-running process that shouldn't block the agent. check window before spawning.
iterate with spawned agents until stable. use for verification with BOUNDED scope and explicit exit criteria. NOT for generating opinions to reconcile.
systematic investigation and debugging methodology. hypothesis-driven analysis with verification agents. use for incident response, codebase archaeology, dependency mapping, root cause analysis, or any investig...
message coordinator as a spawned agent. use when you were spawned by coordinate/spawn and need to report progress, completion, or blockers back to the coordinator.
prose style guide. use when your output includes ANYTHING other than a code snippet. use during conversation, and every time you write to a file, commit, PR. enforces academish voice: supported claims, precise...
orchestrate multiple amp agents with bidirectional tmux communication. use for multi-hour autonomous runs with INDEPENDENT parallel tasks. NOT for review courts or generating opinions to reconcile.
epistemic standards for evaluation and analysis. load before reviewing code, debugging, reporting findings, or any task where claims must be defensible. enforces trace-or-delete, confidence labeling, falsificat...
watchdog for autonomous runs that will exhaust context and need handoffs. supervises tmux agents, respawns on death, orchestrates handoffs. NOT for single-session tasks.
record context that would help in future sessions. use after learning something, discovering a gotcha, or making a decision worth preserving. test: would a future agent starting fresh benefit from knowing this?
write in amp's voice — direct, technical, opinionated, honest. use for technical writing that should feel authoritative without being academic. derived from analysis of amp's content patterns.
spawn parallel amp agents in tmux with thread linkage. use for INDEPENDENT side-quests discovered during main work. NOT for spawning multiple agents to review/evaluate the same thing.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.