afk-setuplisted

Scaffold the per-repo .afk/ orchestrator (config, labels, prompts, scripts, templates) and wire it into the repo's agent rules file. Use after installing the afk-agent skill bundle, when the user says "set up afk", "install afk in this repo", "/afk-setup", or wants to start using the AFK orchestrator on a new project.
Mo-Tamim/afk-agent · ★ 0 · AI & Automation · score 72

Install: claude install-skill Mo-Tamim/afk-agent

# Skill: afk-setup Scaffold the AFK orchestrator into the **current repository** by: 1. Detecting the repo's tracker, default branch, and existing agent rules file. 2. Walking three guided decisions one at a time. 3. Running `install.sh` (or copying `template/` by hand if you don't have it on disk) to create `.afk/` with the right config baked in. 4. Appending an `## AFK orchestrator` section to the repo's `AGENTS.md` (or `CLAUDE.md` / `.cursorrules` / `GEMINI.md`, whichever exists) so future agents pick it up. This is **prompt-driven**, not a silent script. Explore, present what you found, confirm one decision at a time, then write. ## Process ### 1. Explore the current repo Read whatever exists; don't assume. In parallel: - `git config --get remote.origin.url` — extract host (`github.com` / `gitlab.com` / self-hosted) and `<owner>/<repo>` slug. - `git symbolic-ref refs/remotes/origin/HEAD` — derive default branch (fall back to `main` if absent). - Check for an existing agent rules file in this order: `AGENTS.md`, `CLAUDE.md`, `.cursor/rules/` directory, `.cursorrules`, `GEMINI.md`, `.github/copilot-instructions.md`. The first one that exists is the primary; if none exist, default to `AGENTS.md`. - Check whether `.afk/` already exists. If it does, **stop** and ask the user whether to overwrite, abort, or only refresh a subset (config / scripts / prompts). Present a one-screen summary of what you found before asking anything. ### 2. Three gu