onboard-project
Skill7 starsChanged 3 months agoMITView on GitHub
Safely register a local project with or without Git, attach an existing repository, or relink a registered repository in Agent OS without moving it. Use when the user asks to connect, register, onboard, rename, or repair the path of a project from any folder; verify topology first and never move repositories or change remotes as part of onboarding.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Sn4kyGit/qa-agent-blueprinttheir own version, first seen Nov 16, 2026
- Recluse/HyperMnesiatheir own version, first seen Nov 5, 2026
- BenaliHQ/paxus-skillstheir own version, first seen Oct 30, 2026
- qu1r0ra/skillstheir own version, first seen Oct 20, 2026
- crissmoldovan/agent-skillstheir own version, first seen Oct 15, 2026
- xiaolongnk/SuperHarnesstheir own version, first seen Sep 26, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Recluse/HyperMnesia★ 17same name
- BenaliHQ/paxus-skills★ 4same name
- xiaolongnk/SuperHarness★ 4same name
- crissmoldovan/agent-skills★ 2same name
- Sn4kyGit/qa-agent-blueprint★ 2same name
- qu1r0ra/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 7 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create or repair one registered project while preserving all existing repositories and external state.
- Very specific: line 21
Use unknown for missing optional facts.
- Very specific: line 27
When the user wants a suggested channel linked, run a second apply: false preview with the exact returned slackChannelIds, or repeat …
- Very specific: line 29
If an already registered repository was moved separately by the user, preview agent_os_relink_project (or bin/agent-os relink-project) …
- Very specific: line 33
If the registry contains obsolete layout or wrapper fields, preview agent_os_upgrade_project_registry.
- Very specific: line 37
Run ruby tools/validate-agent-os only when working from a full Agent OS source checkout.
- Distinctive: line 41
Use this shape and omit empty optional collections only when the schema permits:
- Distinctive: line 69
Do not move, delete, clone, fetch, pull, commit, push, or modify remotes as part of onboarding.
- Distinctive: line 70
Do not invent source-of-truth, provider project, Slack channel, task tracker, or Codex project IDs.
- Distinctive: line 71
Do not overwrite existing project or repository instructions without a targeted merge.
- Distinctive: line 72
Do not store credentials, raw conversations, or provider logs.
- Distinctive: line 73
Keep external integrations read-only unless the user separately authorizes a write action.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Onboard Project
Create or repair one registered project while preserving all existing repositories and external state.
Inputs
Obtain or derive only from verified local evidence:
- lowercase kebab-case project key;
- display name and useful aliases;
- absolute existing local project root from any folder;
- optional absolute paths to existing Git repositories;
- repository role, source of truth, primary branch, and publication target when known;
- optional Slack channel IDs returned as safe suggestions by the onboarding preview.
Use unknown for missing optional facts. Stop the affected mutation if an unknown fact changes repository topology or publication destination; continue independent safe work.
Workflow
- List current projects and resolve the exact local root. For a project without Git, preview
bin/agent-os sync-codex-projects --directory /absolute/project --jsonfrom the active runtime; this is the same deterministic operation used by app launch and the task-start hook. For an existing Git repository or Slack reconciliation, preferagent_os_onboard_projectwithapply: false; from a source checkout, usebin/agent-os onboard-project --repository /absolute/repository --json. - For a local-only project, review the proposed root, stable key, exact private registry file, and empty repository collection. For Git onboarding, also review the returned repository root, remote, current branch,
HEAD, worktree state, and any conservative Slack channel suggestions. A suggestion is not selected automatically. - When the user wants a suggested channel linked, run a second
apply: falsepreview with the exact returnedslackChannelIds, or repeat--slack-channel CHANNEL_IDin the CLI. Report the selected mappings and every open unassigned outcome that would gain the project; channel labels remain on those cards. - Apply only after the user approves that exact selected preview. Use the same MCP arguments with
apply: true, or add--applyto that reviewed CLI command. Automatic task-start synchronization is already authorized only for the current deterministiccwd; it does not require a separate onboarding invocation. - If an already registered repository was moved separately by the user, preview
agent_os_relink_project(orbin/agent-os relink-project) instead of onboarding a duplicate. Verify the same Git root and origin identity, then apply only the reviewed private metadata change. - If the registry contains obsolete
layoutorwrapperfields, previewagent_os_upgrade_project_registry. Apply the one-way migration only after reviewing every new root and recovery-backup path. - List projects again and read the registered project root
AGENTS.mdbefore substantive work. - Run
ruby tools/validate-agent-osonly when working from a full Agent OS source checkout; packaged runtime users validate the resulting MCP response and registry listing.
Registry entry
Use this shape and omit empty optional collections only when the schema permits:
project-key:
display_name: Project Name
status: active
aliases: []
root: /absolute/path/to/project
slack_channels:
- id: CEXAMPLE
name: "#project-name-int"
repositories: []The registry is the only Agent OS metadata owner. slack_channels contains only
reviewed stable channel IDs and their current display names. Applying a selected
mapping assigns only unfinished outcomes that are still unassigned; it never
replaces another project's attribution, merges outcomes by title, or removes the
channel label from a task card. A project may keep repositories: []
indefinitely. If Git later gains a first commit at the exact project root,
automatic synchronization attaches a primary repository to the same entry; a
remote discovered later fills only previously unknown metadata. Relink preserves
root equality for a single-repository project after a separate user-controlled
move. Nested and multi-repository entries require manual review; Agent OS does
not create a project container folder.
Boundaries
- Do not move, delete, clone, fetch, pull, commit, push, or modify remotes as part of onboarding.
- Do not invent source-of-truth, provider project, Slack channel, task tracker, or Codex project IDs. Channel-name matching may produce a preview suggestion only; stable IDs and explicit approval own the mapping.
- Do not overwrite existing project or repository instructions without a targeted merge.
- Do not store credentials, raw conversations, or provider logs.
- Keep external integrations read-only unless the user separately authorizes a write action.
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
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.

