agentleFS
Sign inStart free
orrgal1orrgal1/manager-skill/register-builder/SKILL.md

register-builder

Skill0 starsChanged 2 months agoMITView on GitHub

Ask the project's manager session to adopt this pane as a builder. Use when the operator says 'register this session with the manager', 'register as a builder', 'become a builder', 'hand this tab to the manager', or names the issue number this session should be registered under. Do not use to act as the manager yourself, and do not use to resume or continue builder work — that starts only after the manager sends a brief.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Stop and wait: Do not load builder.md, do not run any other mgr command, and do not resume whatever work this session was doing.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Register as a builder

You are a session in a herdr tab that wants the manager to adopt it. This skill's entire job is to make the request, then stop.

  1. Resolve mgr. ~/.claude/skills/manager/bin/mgr is the installed path. If it is not there, try $MGR paths (when MGR is already exported) or command -v mgr.

  2. Run the request.

    <mgr> register [N]

    Pass N only when this session already knows which issue it is working on. Omit it otherwise — the manager fills it in later.

  3. Relay the result. On success mgr register prints one JSON object mapping this pane, the manager it registered with, and the issue (if any). Report that mapping to the operator in one short line.
  4. Stop and wait. Do not load builder.md, do not run any other mgr command, and do not resume whatever work this session was doing. mgr bind in particular is not yours to run yet: it is a step the manager's brief will tell you to take, and only on the branch where no issue exists yet. The manager will send that brief; only when it arrives do you start under builder.md, at its second or third opener.
  5. A refusal ends this skill too. Exit 3 means the request was refused — relay the message verbatim and stop. Exit 1 or 2 are the same: report the message, do not retry on your own.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free