Bench onboarding
First-run orientation for a new BenchAGI teammate or pilot customer. Walks through what the Bench Crew is, who the agents are, and how to use them. Use when a new user just installed the plugin or is asking "what is this" / "how do I use this".From its SKILL.md
npx -y skills add BenchAGI/bench-cowork --skill bench-onboardingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.2 KB, as published. Nobody here has run it
Bench Onboarding (Tier D)
First-run orientation for someone who just installed the Bench Cowork plugin.
When to trigger
- Right after
/bench-logincompletes for the first time (the login command can point at this) - When the user asks "what is this", "how do I use this", "what can you do"
- When the user sees
@aureliusor@baileymentioned and asks who they are
Onboarding script
Deliver this in 3 short beats. Don't dump it all at once — pace it.
Beat 1 — What this is
You just installed Bench Cowork — Tier D of the BenchAGI harness. It adds 7 specialist agents and 7 skills to your Claude Code session, plus MCP servers that read and write BenchAGI canon (shared knowledge) and canvas tiles (the launch-readiness dashboard).
Everything talks to benchagi.com over HTTPS. No local daemons, no background processes. You can uninstall cleanly at any time.
Beat 2 — Meet the agents
The Bench Crew:
- Aurelius — coordinator, drafts external email, runs fleet coordination
- Bailey — your personal-space agent (Gmail triage, reminders, notes)
- Cole — morning briefing + sales-pipeline anomalies
- Sage — customer-success voice (calm, specific, professional)
- Ember — internal field-ops rally voice (WoW-style; never customer-facing)
- Piper — product + UX research (PRDs, call summaries)
- Kestrel-Coder — engineering (code review, implementation)
Invoke any with
@<name>or/<name>, e.g./aurelius draft a follow-up to Jimor@bailey triage my inbox.
Beat 3 — What to try first
Three starter tasks:
/bench-login <your-email>— if you haven't already.@bailey hi— say hi to your personal agent. She'll ask what you'd like help with./wiki-captureon a recent decision or PR — feed the agent canon so future sessions know about it.Things to know:
- Every outbound email goes through
aurelius-emailand carries a named human approver. You'll always review before it sends.- Agents refuse harmful or out-of-charter requests. That's a feature.
- If something's missing or wrong,
/wiki-capturea canon entry explaining the gap — the next session inherits it.
Handoff
After this onboarding, the user will likely want to:
- Triage their inbox → hand off to Bailey
- Draft a follow-up → Aurelius (via
aurelius-email) - Review a PR → Kestrel-Coder (with
reviewskill) - Understand pipeline state → Cole
- Customize the app or workspace → use
customize-experienceand link/app/wiki/customize-your-experience
Adaptive notes
- If the user is a pilot customer (non-BenchAGI staff), emphasize Sage. Skip Ember and internal rally references.
- If the user is a BenchAGI teammate, mention Ember and Storm XP.
- If the user mentions they're an engineer, lead with Kestrel-Coder + the engineering skills (review, security-review, simplify, hammer-anvil).