afk-setup

Original：🇺🇸 English

Translated

1 scripts

Register a repo in the AFK board registry (~/.claude/afk.json) so engineer, triage, and reviewer can resolve its tracker and board. Generates the per-repo entry idempotently with a script, resolving the repo path itself so it works on any machine (laptop, VPS). Use when a repo is not yet on the board ("this repo has no afk.json entry", "set up afk", "register this repo", /afk-setup), or it runs automatically as part of startup.

11installs

Sourcedividendsolo/skills

Added on2026-07-07

NPX Install

npx skill4agent add dividendsolo/skills afk-setup

SKILL.md Content

View Translation Comparison →

AFK Setup

Register a repo in the AFK board registry so

engineer

,

triage

, and

reviewer

can find its board. The registry is a single JSON file at

$CLAUDE_CONFIG_DIR/afk.json

(default

~/.claude/afk.json

) that maps an absolute repo path to that repo's board coordinates.

It is per-machine and NOT source-controlled. It keys on absolute paths, which differ between your laptop and the VPS, so each machine generates its own with the bundled script. That is why a freshly-cloned checkout (e.g. on the VPS) has no entry: you generate it there.

The schema

json

{
  "repos": {
    "/abs/path/to/repo": {
      "tracker": "linear",
      "linear": { "team": "Engineering", "project": "Docket phase 1: ingest, feed, reader" },
      "readyStatus": "Ready for Agent",
      "humanStatus": "Ready for Human",
      "shipMode": "pr"
    }
  }
}

```
tracker
```
:
```
linear
```
,
```
github
```
, or any future tracker.

Coordinates:

linear: { team, project }

, or

github: { repo: "owner/name", project? }

.

```
readyStatus
```
/
```
humanStatus
```
: the board's two triage-output columns (canonical
```
Ready for Agent
```
/
```
Ready for Human
```
). The other statuses (
```
Triage
```
,
```
In Review
```
,
```
Changes Requested
```
,
```
Done
```
) are matched by their canonical names verbatim.
```
shipMode
```
:
```
pr
```
(branch and open a PR) is the default.

Generate the entry

Run the bundled script from the repo root (it resolves the path itself):

bash

# Linear board (the DEFAULT). Team defaults to "Engineering"; only the project
# is required (it cannot be inferred):
bash <path-to-this-skill>/scripts/init-afk.sh --linear-project "Skills"

# Linear with a non-default team:
bash <path-to-this-skill>/scripts/init-afk.sh \
  --tracker linear --linear-team "Design" \
  --linear-project "Docket phase 1: ingest, feed, reader"

# GitHub board (opt-in; owner/repo inferred from the origin remote):
bash <path-to-this-skill>/scripts/init-afk.sh --tracker github

Defaults:

--tracker linear

,

--linear-team "Engineering"

,

--ready "Ready for Agent"

,

--human "Ready for Human"

,

--ship pr

. The script is idempotent: an existing entry is left untouched unless

--force

. It edits the JSON with

node

(or

bun

), preserving every other repo's entry.

Interactive use (/afk-setup)

When the maintainer runs

/afk-setup

, do the figuring-out, then call the script:

Resolve the repo (
```
git rev-parse --show-toplevel
```
). If it already has an entry, show it and stop unless they want to change it (
```
--force
```
).
Determine the tracker. Linear is the default (team defaults to
```
Engineering
```
); use GitHub only when the maintainer explicitly wants GitHub issues/Projects. For Linear you still need a project (it cannot be inferred): list projects with the Linear MCP (
```
list_projects
```
for the team), then reuse an existing one or create a new project, and confirm with the maintainer. Do not guess a Linear project.
Confirm the values (tracker, coordinates, statuses, ship mode), then run
```
init-afk.sh
```
with the resolved flags.
Read the file back and show the maintainer the entry you wrote.

Pairs with

```
startup
```
calls this in its meta layer, so a new repo is registered as it is created. The default is a Linear board (team
```
Engineering
```
); since the Linear project cannot be inferred, startup does not auto-register it. Finish it by running
```
/afk-setup
```
(determine the project, reusing or creating one via the Linear MCP). GitHub is used only when explicitly chosen (
```
--tracker github
```
).
```
engineer
```
/
```
triage
```
/
```
reviewer
```
read the entry this writes; if they find none, they point the user here.