dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
38,472 Skills
Search uses this published catalog; rankings and counts are snapshots.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when implementation on a branch is complete and it is about to be merged or PR'd — or when finishing-a-development-branch reaches its docs-audit gate — and after code changes are committed, to ensure all project documentation accurately reflects shipped code. Covers README, A
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use at session-close when a session captured several new memories, or on-demand, to consolidate, deduplicate, prune, and structure the beads memory store. Triggers on "curate memories", "clean up memories", "memory sweep".
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
A human-invoked utility that writes a grounded session-handoff document (plus a continuation pointer memory) so a fresh agent can resume in-progress work. Not auto-invoked; a human runs it deliberately.
Use when a design, plan, or decision needs adversarial scrutiny before proceeding. Interrogates every branch of the decision tree, providing recommended answers and forcing explicit agreement or pushback. Triggers on "grill me", "stress test this", "poke holes", "challenge this d
Use when implementing any feature or bugfix, before writing implementation code
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Structure a scientific paper section by section — tables and figures, Results, Methods, Introduction, Discussion, Abstract — following Stanford's Writing in the Sciences. Use this skill whenever someone is writing, drafting, planning, restructuring or reviewing any part of a rese
Communicate science to non-specialists: lay summaries, plain-language abstracts, press releases, science news stories, talking to journalists, presenting risk numbers honestly, interviewing a scientist, and using social media. Based on Stanford's Writing in the Sciences. Use this
Plan and run the writing process for a scientific paper or thesis chapter — pre-writing and organisation, drafting fast without perfectionism, revision, and the final pre-submission checklist — following Stanford's Writing in the Sciences. Use this skill whenever someone is stuck
Write the documents an academic career runs on besides papers: narrative review articles, grant and fellowship applications (specific aims, research plan), letters of recommendation, and personal statements. Based on Stanford's Writing in the Sciences. Use this skill whenever som
Navigate publication: choosing a journal, the submission process, responding to reviewers after a revise-and-resubmit, performing a peer review yourself, authorship decisions and order, plagiarism and self-plagiarism, and spotting predatory journals. Based on Stanford's Writing i
Catalog captured:2026-11-21