fd-firm-onboard
Skill1 starsChanged 4 months agoMITView on GitHub
Stand up a Forward Deploy firm's internal team Slack channel during the internal-kickoff / pod-assignment phase. For one firm or a batch, it reconciles the firm's #fd-<firm>-team channel (handling name variants and the Slack Connect workspace trap), pulls readiness + prior demos + the firm's agents from the program sources, crawls your DMs with the firm's PDM + the FD approver for the internal team and firm-side contacts, and creates an ATTACHED Slack draft (never sent) with a readiness+context+team post plus an add-list. Use when you say "onboard <firm>," "stand up <firm>'s channel," "kick off <firm>," "build the context post for <firm>," "who do I add to <firm>," or "onboard my firms" (batch). It drafts and researches; it never creates channels, adds members, or sends messages — those stay your click.
In this repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- fd-blocker-sweepSkill
- fd-onsite-availabilitySkill
- fd-portfolio-rollupSkill
- fd-reconcileSkill
- full-sweepSkill
- intakeSkill
- process-meetingsSkill
- safe-mvSkill
- slack-recapSkill
- steSkill
- sweep-binderSkill
- sweep-jiraSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 36
Search for #fd-<firm>-team, trying the firm name AND its nicknames.
- Very specific: line 38
Workspace trap: if the channel is on intuit-slack-connect, the draft app often can't write there (channel_not_found).
- Distinctive: line 41
Don't retry a 404.
- Distinctive: line 45
Read existing messages. If substantive context is already posted, produce a gap-fill, not a duplicate.
- Very specific: line 79
Draft, never send: Only write is an attached draft.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
FD Firm Onboard — internal kickoff / pod-assignment helper
Automates the repeatable motion when a firm enters the early Forward Deploy phase: reconcile the firm's internal team channel, gather its context and agents, figure out the pod, and post a readiness briefing. It produces an attached Slack draft you review and send, plus an add-list of people. It does the research + drafting; you do channel creation and membership (no tool can do those).
Setup (first run): the skill needs to know who you are (name, Slack handle) and where the program sources live. On first run it asks once and remembers: (a) your identity, (b) the FDE Resourcing Priorities tab, (c) the demo-recordings repository, (d) the per-firm agent-library binder. If your team keeps firm nicknames (CBH = Cherry Bekaert, PAG = Platform, etc.), record those too so channel-name matching works.
When to run
- One firm: "onboard
<firm>", "stand up<firm>'s channel", "kick off<firm>", "who do I add to<firm>". - Batch: "onboard my firms", "onboard all my commits", "do the resourcing-tab firms" — fan out the per-firm flow over the list.
Step 0 — Resolve firm list + sources
- One named firm → just that. Batch → read the FDE Resourcing Priorities tab for the firm rows; for "my firms," filter to rows where you're the DM/temp owner.
- Confirm the program sources (resourcing tab, demo repo, agent-library binder). State the firm(s) + sources in one line and proceed.
Step 1 — Reconcile the channel (per firm)
Load Slack tools (one call):
select:mcp__claude_ai_Slack__slack_search_channels,mcp__claude_ai_Slack__slack_read_channel,mcp__claude_ai_Slack__slack_search_public_and_private,mcp__claude_ai_Slack__slack_search_users,mcp__claude_ai_Slack__slack_send_message_draft,mcp__claude_ai_Slack__slack_read_thread
- Search for
#fd-<firm>-team, trying the firm name AND its nicknames. - Report state, don't fix:
- Workspace trap: if the channel is on
intuit-slack-connect, the draft app often can't write there (channel_not_found). These are meant to be INTERNAL pod channels — flag that it should live in the internal workspace, and that the fix is to recreate/switch it there. Don't retry a 404. - Duplicates: surface both with IDs; recommend which to use + archive the other.
- Missing: give the exact name to create (
#fd-<firm>-team, internal/private, NOT Slack Connect) — the skill can't create it.
- Workspace trap: if the channel is on
- Read existing messages. If substantive context is already posted, produce a gap-fill, not a duplicate.
Step 2 — Gather context + agents (per firm)
Dispatch a research specialist. Pull: readiness/status (resourcing tab), prior demos/deep-dives
(demo repo — dates, recording/Gong links, attendees labeled Intuit-vs-firm-side), and the firm's
agents from the agent-library binder (canonical name, ID, scope, status; quote the binder's own
flags, don't resolve them). Mark [Unverified]; thin firm → honest stub, never invented readiness.
Step 3 — Crawl for the pod + contacts (per firm)
Dispatch a people-crawl specialist to mine your DMs with the firm's PDM/partner manager and the FD handoff approver (on nearly every firm), plus firm-name searches. Return:
- Internal team to add — PM/SME/DM/PDM + any product/eng SMEs, each name + role + why + date.
- Firm-side (external) contacts — clearly LABELED external; surfaced for you to judge per channel (default: internal-pod-only, so listed separately, not auto-added). The 1:1 DM with a PDM may be empty with the real thread in a group DM including the approver — check both. Keep look-alike firms distinct.
Step 4 — Draft the context post (per firm) — attached draft, never sent
Assemble and create via slack_send_message_draft into the reconciled internal channel:
Header (+ siren if a demo/scoping date is imminent) · Status · Team to add (internal) · Firm-side
contacts (external, separate) · Prior demo discussions · The agents (binder names/IDs/status +
flags) · Desired use cases (or "not yet scoped") · Next steps (owners+dates) · Blockers/risks +
verify line · Sources.
One attached draft per channel — if one exists, tell the user, don't clobber. If the channel
can't take a draft (Connect 404), deliver as pasteable text + the workspace fix; don't loop. Run
humanizer on the body.
Step 5 — Deliver + add-list
Per firm: the draft link (or pasteable text), full-vs-gap-fill, the add-list (internal to add + firm-side to decide), and channel flags (workspace trap / duplicate / missing). Batch → one summary table.
Guardrails (hard rules)
- Draft, never send. Only write is an attached draft. Never send/react/mark-read/add members/create/rename/archive channels — all yours. Say so.
- Internal vs external —
#fd-<firm>-teamis internal; firm-side contacts listed separately, never auto-added. - No fabrication — thin firm → honest stub;
[Unverified]; preserve the binder's flags; keep look-alike entities distinct. - No new documents unless asked — briefs live as Slack drafts.
- Don't retry a 404 channel — surface the workspace fix.
Install
Drop the fd-firm-onboard/ folder into .claude/skills/fd-firm-onboard/ (project) or
~/.claude/skills/fd-firm-onboard/ (everywhere). Requires the Slack connector; the program
sheets are read via your Google Drive connector. Then: "onboard <firm>"
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.

