Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Produces a complete client onboarding workflow including discovery call agenda, contract checklist, kickoff document, communication expectations, and first deliverable timeline. Creates a reusable onboarding process document.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
Each of these library teams gives its bots this skill. Import one and look inside first.
The whole file, exactly as it downloads. Read it before you rely on it.
SKILL.md
303 lines · 2,201 words
User has signed a new freelance or consulting client and needs to set up the engagement
User wants to create a standardized client onboarding process
User asks how to kick off a new client relationship with clear expectations
User needs a checklist for what to cover before starting project work
Produces a complete client onboarding workflow including discovery call agenda, contract checklist, kickoff document, communication expectations, and first deliverable timeline. Creates a reusable onboarding process document.
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
Paste it into your agent's instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add it to a bot in Murage.
Ask Ember for the bot, then switch the skill on in its settings.
Step 1
Send your Chief of Staff this message. It proposes the bot and its role first, and creates it when you say go.
Send this to Ember
“Create a bot that uses the Client Onboarding Checklist skill, and show me the plan first.”
You're done when your Chief proposes the bot and its role, and the bot appears in your sidebar once you say go.
Step 2
You're done when you see the bot’s skills and the library.
Step 3
You're done when the skill shows as on for that bot.
Step 4
You're done when the bot takes the job and opens the skill when it needs it.
Prefer to do it yourself? Choose + in the sidebar, then New Bot.Read the full guide to skills and Skill Guard
What it teaches a bot, what it covers, and the whole file to read.
What it covers
When to Use
Process
Output Format
Rules
Edge Cases
Example
Client Onboarding Document: TaskFlow - Onboarding Flow Redesign
User wants to avoid scope creep and miscommunication at the start of an engagement
Do NOT use when: user is onboarding a new employee (use HR skills), user needs an internal project kickoff (use project management skills), user wants to write a client proposal (use freelance-proposal-writer)
Gather engagement context. Collect the details of the new client:
Client name, company, and primary contact person
Project type and scope (from the signed proposal or agreement)
Contract status (signed/pending)
Agreed timeline and key milestones
Communication preferences (email, Slack, phone, meeting frequency)
Billing structure (hourly, project-based, retainer, payment terms)
What the client needs to provide (assets, access, content, feedback)
Build the pre-kickoff checklist. Before the first meeting:
Contract signed and countersigned
Initial payment received (if required before work begins)
Client contact information documented (primary contact, billing contact, technical contact if different)
Project management or collaboration tools set up (shared folder, project board, communication channel)
Internal project brief created (user's own notes on scope, risks, timeline)
Welcome email sent with kickoff meeting details and agenda
Create the discovery call agenda. Structure the first conversation:
Introductions and roles (who does what on both sides)
Project goals review (confirm understanding of objectives from the proposal)
Success criteria definition (how will both parties know the project succeeded?)
Brand guidelines, style preferences, or technical requirements review
Content and asset inventory (what the client has vs. what needs to be created)
Communication plan (preferred channels, response time expectations, meeting cadence)
Timeline walkthrough (key dates, milestones, review points)
Questions and concerns from either side
Next steps and action items with owners and dates
Build the kickoff document. Create a shared reference:
Project summary (1-2 paragraphs restating scope and goals)
Team directory (names, roles, contact information for both sides)
Communication plan (channels, frequency, escalation process)
Timeline with milestones and review dates
Client responsibilities and deadlines for their deliverables
Revision process (how feedback is submitted, how many rounds)
Change request process (how scope changes are handled)
File sharing and access information
Set communication expectations. Define the operating rhythm:
Status update frequency (weekly email, bi-weekly call, etc.)
Response time expectations (business hours, same-day, next-day)
Preferred feedback format (in-document comments, email, meeting)
Meeting cadence and duration
Escalation path (who to contact if something goes wrong)
Out-of-scope request handling (how to raise additional needs)
Define the first deliverable milestone. Set the initial target:
What will be delivered first and when
What feedback is needed from the client and by when
How the first deliverable review will be conducted
Success criteria for the first milestone
Adjustment point: review process and communication after the first deliverable to calibrate expectations
## Client Onboarding Document: [Client Name] - [Project Name]
**Date:** [Date]
**Client:** [Client name], [Company]
**Primary contact:** [Name], [Email], [Phone]
**Project:** [Project name / brief description]
**Timeline:** [Start date] to [End date]
---
### Pre-Kickoff Checklist
- [ ] Contract signed by both parties
- [ ] Initial payment of $[X] received
- [ ] Client contact information documented
- Primary: [Name], [Email], [Phone]
- Billing: [Name], [Email]
- Technical (if applicable): [Name], [Email]
- [ ] Project folder created and shared with client
- [ ] Communication channel set up ([Tool name])
- [ ] Welcome email sent with kickoff agenda
- [ ] Internal project brief completed
### Discovery Call Agenda
**Date:** [Scheduled date and time]
**Duration:** [X] minutes
**Attendees:** [Names from both sides]
1. **Introductions and roles** (5 min)
- Who is who on both sides
- Decision-making authority (who approves deliverables?)
2. **Project goals review** (10 min)
- Confirm objectives from proposal
- Define success criteria: [What does success look like for this project?]
3. **Requirements and preferences** (15 min)
- Brand guidelines and style direction
- Technical requirements or constraints
- Content and assets: what exists vs. what needs to be created
4. **Communication plan** (10 min)
- Preferred channels: [Email / Slack / Phone / Other]
- Response time expectation: [Same day / Next business day]
- Meeting cadence: [Weekly / Bi-weekly / As needed]
- Feedback format: [How the client will provide feedback on deliverables]
5. **Timeline walkthrough** (10 min)
- Key milestones and dates
- Client deliverable deadlines
- Review and feedback windows
6. **Questions and next steps** (10 min)
- Open questions from either side
- Action items with owners and deadlines
### Kickoff Document (Shared Reference)
**Project summary:**
[1-2 paragraph restatement of what is being built/delivered and why]
**Team directory:**
| Name | Role | Contact | Response Time |
|------|------|---------|--------------|
| [User name] | [Role] | [Email] | [Same day / Next business day] |
| [Client contact] | [Role] | [Email] | [Response time agreed] |
**Communication plan:**
| Channel | Purpose | Frequency |
|---------|---------|-----------|
| [Email] | [Status updates, formal communication] | [Weekly] |
| [Slack/Chat] | [Quick questions, async coordination] | [As needed] |
| [Video call] | [Milestone reviews, feedback sessions] | [Bi-weekly] |
**Project timeline:**
| Milestone | Date | Deliverable | Client Action Needed |
|-----------|------|------------|---------------------|
| Kickoff | [Date] | Discovery call completed | Provide assets by [date] |
| [Milestone 1] | [Date] | [Deliverable] | Review and feedback by [date] |
| [Milestone 2] | [Date] | [Deliverable] | Review and feedback by [date] |
| Final delivery | [Date] | [Final deliverable] | Final approval by [date] |
**Client responsibilities:**
| Item | Due Date | Notes |
|------|----------|-------|
| [Asset/content 1] | [Date] | [Format or specification needed] |
| [Asset/content 2] | [Date] | [Format or specification needed] |
| [Feedback on milestone 1] | [Date] | [How to submit: email, comments, meeting] |
**Revision process:**
- [X] rounds of revisions included per deliverable
- Feedback submitted via [method] within [X] business days of delivery
- Revisions completed within [X] business days of receiving feedback
- Additional revisions beyond included rounds: $[X]/hour or per-revision quote
**Change request process:**
- Any work outside the original scope requires a written change request
- Change requests include: description of new work, timeline impact, cost impact
- Work on change requests begins only after written approval from [client contact]
### Communication Expectations
| Expectation | Details |
|------------|---------|
| Status updates | [Frequency, format, who sends to whom] |
| Response time (user) | [X business hours / same day / next business day] |
| Response time (client) | [X business days for feedback and approvals] |
| Meeting cancellation | [X hours notice required] |
| After-hours communication | [Not expected / Emergency only / Specific hours] |
| Escalation path | [Who to contact if the project is off track] |
### First Deliverable Milestone
**What:** [First deliverable description]
**Due:** [Date]
**Client feedback needed by:** [Date]
**Success criteria:** [How both parties will know this deliverable is on track]
**Process check:** After the first deliverable review, both parties will assess whether the communication, feedback, and revision process is working and make adjustments if needed.Always produce a complete onboarding document with checklists, agenda, and shared reference -- never generic advice about client management
Every checklist item must have a checkbox (- [ ]) for the user to track completion
The discovery call agenda must include specific time allocations for each section -- vague agendas waste client time
Client responsibilities must include specific due dates, not vague references to "as soon as possible"
Include a change request process in every onboarding document -- this is the primary defense against scope creep
Communication expectations must include response time commitments from BOTH sides, not just the user
Include a process check after the first deliverable -- this is the adjustment point for the entire engagement
NEVER assume the client knows how the user's process works -- explain everything, even things that seem obvious
The revision process must specify the number of included rounds and the cost of additional rounds
The kickoff document becomes the single source of truth for the engagement -- everything agreed upon should be in this document
Client is a repeat engagement (returning client): Simplify the onboarding by referencing the previous engagement. Skip introductions and basic process review. Focus on what is different about this project: new scope, updated timeline, any process changes from last time.
Multiple stakeholders on the client side: Add a RACI (Responsible, Accountable, Consulted, Informed) matrix to the kickoff document. Identify who provides feedback, who approves deliverables, and who makes final decisions. This prevents conflicting feedback from multiple client contacts.
Very small project (under 1 week): Collapse the onboarding to a single email. Include: confirmed scope, delivery date, what you need from the client, payment terms. Skip the formal discovery call -- a 15-minute alignment call or email exchange is sufficient.
Client has no process experience (first time hiring a freelancer): Add extra explanation to every section. Define terms like "revision round," "scope change," and "milestone." Include a brief "how this works" section at the top of the onboarding document that explains the typical freelance engagement flow.
Remote client in a different time zone: Add time zone information to every meeting reference. Identify a shared working hours window (e.g., "Both parties are available 10 AM - 2 PM EST"). Emphasize async communication with clear written documentation over real-time meetings.
Input: "I just signed a freelance UX design project with a startup called TaskFlow. The project is redesigning their onboarding flow for new users. The client contact is Jamie Park, Head of Product. The project is 4 weeks, $8,000 fixed fee (50/50 payment split). I include 2 rounds of revisions. We'll communicate via Slack and have weekly check-in calls."
Output:
Date: [Current date] Client: Jamie Park, TaskFlow Primary contact: Jamie Park, [email], [phone] Project: Redesign of new user onboarding flow Timeline: [Start date] to [Start date + 4 weeks]
Contract signed by both parties
Initial payment of $4,000 (50%) received
Client contact information documented
Primary: Jamie Park, [email], [phone]
Billing: [Name if different], [email]
Shared project folder created (Google Drive or Figma workspace)
Slack channel created and Jamie invited
Welcome email sent with kickoff meeting details and agenda
Internal project brief completed (current onboarding flow review, competitive analysis notes)
Date: [Scheduled date and time] Duration: 45 minutes Attendees: [User name], Jamie Park
Introductions and roles (5 min)
Who approves designs? Jamie or another stakeholder?
Who provides technical constraints? Engineering contact needed?
Project goals review (10 min)
What is the primary goal of the onboarding redesign? (Activation rate, time to value, drop-off reduction?)
What metrics define success? (e.g., "Reduce onboarding drop-off from 40% to 20%")
What is working in the current onboarding? What is not?
Requirements and preferences (15 min)
Existing design system or component library?
Brand guidelines, typography, color palette
Technical constraints (what can engineering build in the current stack?)
User research or analytics data available (where do users drop off today?)
Communication plan (5 min)
Slack for day-to-day, weekly video call for milestone reviews
Feedback turnaround: 2 business days after each deliverable
Jamie is the single point of feedback (consolidated, not multiple reviewers)
Timeline walkthrough (5 min)
Week 1: Research and wireframes
Week 2-3: High-fidelity design
Week 4: Revisions and final delivery
Questions and next steps (5 min)
Jamie to share current onboarding flow screenshots and analytics by Day 2
[User] to deliver wireframes by end of Week 1
[Remaining sections follow the template above with TaskFlow-specific details filled in, including timeline milestones, client responsibilities with dates, and the post-first-deliverable process check.]
SKILL.md
303 lines · 2,201 words
The text of SKILL.md is shown as it downloads, under the Apache-2.0 license, by Ferrox Labs. The license is the one in the file's own frontmatter.
Your new bot
Client Onboarding Checklist bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for