agentleFS
Sign inStart free
OneWave-AIOneWave-AI/claude-skills/onboarding-checklist/SKILL.md

onboarding-checklist

Skill378 starsChanged 55 days agoMITView on GitHub

Generates customized client onboarding checklists with phased tasks, ownership assignments, dependencies, acceptance criteria, and email templates. Adapts to consulting, SaaS, or agency engagement models.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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
  1. Very specific:

    Verify the result against the quality checklist and common pitfalls in references/scaling-and-pitfalls.md.

    line 39
  2. Distinctive:

    Write the file to the current working directory using the Write tool.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Onboarding Checklist Generator

Generate a comprehensive, customized client onboarding checklist saved as onboarding-checklist.md in the current working directory. The checklist is actionable, phase-structured, and tailored to the specific engagement type.

Contents

  • references/output-template.md -- Full output structure: header block, four phases, handoff criteria, formatting rules.
  • references/engagement-types.md -- How to classify Consulting vs SaaS vs Agency, and per-type adaptation guidelines.
  • references/task-banks.md -- Reference task pools per engagement type and phase.
  • references/email-templates.md -- The five required email templates, their structure, and content guidelines.
  • references/scaling-and-pitfalls.md -- Timeline and team-size scaling rules, common pitfalls, and the final quality checklist.

Required Inputs

Gather these before generating. If any are missing, ask for them explicitly:

  1. Client Type: Industry, company size, maturity (e.g., "Series B fintech startup").
  2. Services Purchased: Exact scope of work or product tiers.
  3. Team Size: Number of people on both provider and client sides.
  4. Tech Stack: Relevant technologies, platforms, tools, integrations.
  5. Timeline: Total onboarding duration and any hard deadlines.

Workflow

  1. Collect all five required inputs from the user.
  2. Classify the engagement type (Consulting, SaaS, or Agency) using references/engagement-types.md. This classification drives the structure and tone of the entire checklist.
  3. Select and customize tasks from references/task-banks.md, adapting language, deadlines, and owners to the specific engagement. Reflect tech-stack items in relevant tasks.
  4. Apply timeline scaling rules from references/scaling-and-pitfalls.md based on the specified duration.
  5. Apply team-size scaling rules from references/scaling-and-pitfalls.md based on team composition.
  6. Generate all five email templates with full body content per references/email-templates.md.
  7. Compile the complete onboarding-checklist.md following references/output-template.md. Apply the per-type adaptations in references/engagement-types.md.
  8. Verify the result against the quality checklist and common pitfalls in references/scaling-and-pitfalls.md.
  9. Write the file to the current working directory using the Write tool.
  10. Confirm completion and summarize key stats (total tasks, timeline, engagement type, file location).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free