onboard
Skill2 starsChanged 3 months agoMITView on GitHub
Onboard ANY company (or founder/freelancer/solo owner) into this AI OS. Interviews them about their business, tools, and APIs; researches available MCP servers and integrations; then GENERATES their custom entity notes, routing table, department agents, skills, and style guide. Use on first run after cloning, or when the user says "onboard", "set this up for my company", or "/onboard".
171 other projects use a version of this.
Adopted by
Most recently taken up by
- TsukiNi22/skillstheir own version, first seen Nov 16, 2026
- TsukiNi22/ai-utilstheir own version, first seen Nov 16, 2026
- akovfoj-lang/plainframetheir own version, first seen Nov 16, 2026
- chuckplayer/claude-agent-packtheir own version, first seen Nov 16, 2026
- jestatsio/codebase-mentortheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
Used with
Projects with it also use soak-test, team-live-ops and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
lilangMaxSkillsoak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Also in 10 projects that use this
lilangMaxSkillteam-live-ops
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Also in 10 projects that use this
HK-hubSkillteach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
Also in 18 projects that use this
CoralGameSkillteam-level
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Also in 12 projects that use this
CoralGameSkillplaytest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Also in 12 projects that use this
HK-hubSkillarrange
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Also in 13 projects that use this
- +5 more from lilangMax
- +1 more from CoralGame
Other versions171 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 171
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- nateherkai/AIS-OS★ 1.4ksame name
- poshan0126/dotclaude★ 871same name
- me2resh/apexyard★ 542same name
- nexmoe/DayBee★ 424same name
- nexmoe/eve★ 424same name
- kousen/claude-code-training★ 352same name
161 more not listed
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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- eodSkill
- lintSkill
- new-entitySkill
- session-handoffSkill
- session-startSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 159 edited versions we read keep these.
3
Distinctive
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
- Distinctive: line 14
Ask in small batches (3–5 questions at a time), adapt follow-ups to their answers:
- Very specific: line 65
Run /lint to verify the generated OS is consistent.
- Distinctive: line 76
Every integration claim is web-verified with a date.
- Distinctive: line 78
Delete sample content you replace.
“Common” is measured: kept by at least 6 in 10 of the 159 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 — turn this template into THEIR company's OS
You are the onboarding guide. The goal: a stranger clones this repo, runs /onboard,
answers questions, and walks away with a working OS custom-built for their business.
Work in four phases. Announce each phase as you enter it.
Phase 1 — Interview (ask, don't assume)
Ask in small batches (3–5 questions at a time), adapt follow-ups to their answers:
- Who are you? Company/personal brand name, what you do, team size (solo founder and freelancer are valid answers — the OS scales down fine).
- Functions. Which of these exist for you: HR/people, engineering/product, operations, marketing, finance, sales/clients, support — plus anything unusual (inventory, dispatch fleet, clinics, classrooms…). One entity note each.
- Tools per function. For each function, what do they run on? Examples to prompt them: Meta/Google Ads, social schedulers, CRM, payroll system, inventory/POS, accounting, e-commerce, helpdesk, WhatsApp Business, email.
- Where files live. Real folders (paths), drives, or "everything is in SaaS".
- Writing channels. Which do they write in — email/Gmail, WhatsApp, LinkedIn, Instagram? Ask for 1–2 real (non-sensitive) sample messages per channel to learn their voice.
- Boundaries. What's sensitive (salaries, customer PII, credentials)? Confirm the rule: referenced, never copied into the vault.
Phase 2 — Research integrations (never guess)
For EACH tool they named:
- Web-search for an official MCP server first, then an official API.
- Determine the connection path, best-first:
- MCP server exists → exact install command (
claude mcp add …) and what auth it needs - API only → where to get the API key (exact console URL), which scopes
- Neither → manual export/CSV workflow into
raw/
- MCP server exists → exact install command (
- Produce an Integration Plan table:
tool | function | connect via | steps to get access | date checked. Everything web-verified, nothing from memory — note the date. - Walk them through connecting ONE integration end-to-end as the proof; list the rest
as checklist items. API keys go in env vars / agent settings — never into vault files.
(Full patterns:
docs/INTEGRATIONS.md.)
Phase 3 — Generate their OS
With their answers, create (vault writes need no confirmation):
entities/Company.md— rewritten for them (delete Acme sample data).- One entity note per function they actually have (delete unused sample departments,
or repurpose them). Each carries real
path:, tools, and the integration plan rows. entities/Routing.md— rebuilt with their real names/aliases/paths.entities/Style Guide.md— their voice, learned from the samples they gave: rules + one worked example per channel (email, WhatsApp, LinkedIn…).- Custom agents in
.claude/agents/— one per major function, cloned from the shipped examples, rescoped to their entity note, tools, and boundaries. (Inventory company →inventory-manageragent wired to their POS MCP; marketing agency →ads-analystwired to Meta/Google APIs.) - Custom skills in
.claude/skills/— one per recurring ritual they described (weekly report, campaign launch checklist, stock reorder check…). - Update
index.mdandHome.md— their map, their checklist.
Phase 4 — Handoff
- Run
/lintto verify the generated OS is consistent. - Log:
## [date] ingest | onboarded <Company> → N entities, M agents, K skills, integration plan. - Show them the daily loop:
/session-start→ work →/eod→/session-handoff, and the learning loop (learnings.md/mistakes.md— see CLAUDE.md §7). - End with their personal "first week with the OS" plan: 3–5 concrete tasks (e.g. "ingest your price list", "connect the second integration", "first payroll checklist run").
Rules
- Interview before generating — never scaffold from assumptions.
- Every integration claim is web-verified with a date. Never guess an API or price.
- Scale to size: a freelancer might need 3 entities and 1 agent, not 6 and 4.
- Delete sample content you replace; the OS should contain only THEIR company when done.
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.

