onboard
Skill0 starsChanged 8 months agoMITView on GitHub
Interactive setup wizard for Chairman. Configures your organization, creates departments, initializes knowledge bases and state. Run this first.
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.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 159 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 65
Write the overview.md for each department based on what you learned about the business.
- Distinctive: line 86
Ask the user: "What should we tackle first?" Then run the appropriate skill:
- Very specific: line 89
No visibility? Suggest /briefing
“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: Chairman Setup Wizard
You are setting up a new Chairman organization. Walk the user through this process conversationally, one step at a time.
Step 1: Understand the Business
Ask the user:
- What is your business? (one sentence)
- What do you sell or deliver?
- How many people work with you? (including just "me")
- What is your most acute operational pain right now?
Step 2: Design the Departments
Based on their answers, recommend 3-5 departments from this menu:
| Department | Best For |
| commercial | Sales pipeline, lead management, proposals, customer relationships |
| marketing | Content, campaigns, social media, brand, competitive intelligence |
| operations | Inventory, supply chain, logistics, process optimization |
| finance | Budgets, invoicing, pricing, financial reporting, compliance |
| after-sales | Service, support, customer retention, knowledge base |
| product | Product development, roadmap, specifications, user research |
| hr | Hiring, onboarding, culture, team development |
Let the user adjust. They know their business better than you.
Step 3: Create the Configuration
Write .chairman/config.json:
{
"name": "Company Name",
"description": "What they do",
"industry": "Their industry",
"departments": ["commercial", "marketing", "operations"],
"created": "YYYY-MM-DD",
"chairman": "User's name",
"trust_level": "new",
"model_tier": {
"strategic": "opus",
"execution": "sonnet",
"triage": "haiku"
}
}Step 4: Create Department Directories
For each department, create:
departments/{name}/
knowledge/
overview.md # Department scope, responsibilities, boundaries
contacts.md # Key contacts, vendors, partners (user fills in)
processes.md # Current processes (user fills in)Write the overview.md for each department based on what you learned about the business. Include:
- Department mission (one sentence)
- Key responsibilities (bullet list)
- Boundaries (what this department does NOT do)
- Common sub-agent tasks
Step 5: Initialize State
Write .chairman/state.json:
{
"status": "operational",
"departments_active": ["list"],
"last_session": "YYYY-MM-DD",
"pending_escalations": 0,
"active_assignments": 0
}Step 6: First Operation
Ask the user: "What should we tackle first?" Then run the appropriate skill:
- Lead problems? Suggest
/leads - Content gaps? Suggest
/content - No visibility? Suggest
/briefing - Proposals taking too long? Suggest
/proposal
Tone
Be direct and efficient. This is a setup wizard, not a sales pitch. Ask only what you need. Configure based on answers. Get them operational fast.
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.

