Sponsored by

Find leads on Reddit on auto pilot

Agent skills
autonomous-agent

Topic: autonomous-agent

188 skills in this topic.

flow-next-impl-review John Carmack-level implementation review via RepoPrompt or Codex. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.
gmickel/flow-next 567
flow-next-interview Interview user in-depth about an epic, task, or spec file to extract complete implementation details. Use when user wants to flesh out a spec, refine requirements, or clarify a feature before building. Triggers on /flow-next:interview with Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2) or file paths.
gmickel/flow-next 567
flow-next-plan Create structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation. Triggers on /flow-next:plan with text descriptions or Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).
gmickel/flow-next 567
flow-next-plan-review Carmack-level plan review via RepoPrompt or Codex. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.
gmickel/flow-next 567
flow-next-prime Comprehensive codebase assessment for agent and production readiness. Scans 8 pillars (48 criteria), verifies commands work, checks GitHub settings. Reports everything, fixes agent readiness only. Triggers on /flow-next:prime.
gmickel/flow-next 567
flow-next-ralph-init Scaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.
gmickel/flow-next 567
flow-next-rp-explorer Token-efficient codebase exploration using RepoPrompt CLI. Use when user says "use rp to..." or "use repoprompt to..." followed by explore, find, understand, search, or similar actions.
gmickel/flow-next 567
flow-next-setup Optional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.
gmickel/flow-next 567
flow-next-sync Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.
gmickel/flow-next 567
flow-next-work Execute a Flow epic or task systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan or working through a spec. Triggers on /flow-next:work with Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).
gmickel/flow-next 567
flow-next-worktree-kit Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
gmickel/flow-next 567
flow-impl-review John Carmack-level implementation review via rp-cli for current branch changes. Use when reviewing code changes, PRs, or implementations. Triggers on mentions of code review, implementation review, or PR review.
gmickel/flow-next 567
flow-interview Interview user in-depth about a spec, bead, or feature idea to extract complete implementation details. Use when user wants to flesh out a spec, refine requirements, discuss technical details, clarify a feature before building, or asks to be interviewed about their idea. Triggers on "interview me", "ask me questions about", "flesh out this spec", "refine requirements", "help me think through".
gmickel/flow-next 567
flow-plan Create structured build plans from feature requests, bug reports, or Beads issue IDs. Use when planning features, designing implementation, preparing work breakdown, or when given a bead/issue ID to plan. Triggers on /flow:plan with text descriptions or issue IDs (e.g., bd-123, gno-45, app-12).
gmickel/flow-next 567
flow-plan-review Carmack-level plan review via rp-cli context builder + chat. Use when reviewing implementation plans, architecture docs, or design specs. Triggers on mentions of plan review, design review, or architecture review.
gmickel/flow-next 567
flow-work Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executing a Beads issue ID (e.g., bd-123, gno-45, app-12).
gmickel/flow-next 567
rp-explorer Token-efficient codebase exploration using RepoPrompt CLI. Use when user says "use rp to..." or "use repoprompt to..." followed by explore, find, understand, search, or similar actions.
gmickel/flow-next 567
worktree-kit Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
gmickel/flow-next 567
auto-experiment Launch an autonomous THINK→EXECUTE→REFLECT experiment loop on a GPU project
Xiangyue-Zhang/auto-deep-researcher-24x7 302
conf-search Search papers from top AI/ML conferences
Xiangyue-Zhang/auto-deep-researcher-24x7 302
daily-papers Daily arXiv paper recommendations with automatic deduplication
Xiangyue-Zhang/auto-deep-researcher-24x7 302
experiment-status Check status of running autonomous experiment loops
Xiangyue-Zhang/auto-deep-researcher-24x7 302
gpu-monitor Check GPU status, running experiments, and available resources
Xiangyue-Zhang/auto-deep-researcher-24x7 302
paper-analyze Deep analysis of a single paper with figure extraction from arXiv source
Xiangyue-Zhang/auto-deep-researcher-24x7 302