client-onboard_skill

This skill generates a complete client onboarding package from a project description, including project brief, tech stack, milestones, folder structure,
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill client-onboard

  • _meta.json291 B
  • SKILL.md14.1 KB

Overview

This skill generates a complete client onboarding package from a short project description. It produces a project brief, recommended tech stack, milestone plan, folder structure, CLAUDE.md starter, and a ready-to-send kickoff message so you can appear professional and start work within 24 hours.

How this skill works

You provide a project description (e.g., "/client-onboard [project description]") and the skill parses type, industry, timeline, budget, tech constraints, and team context. It applies sensible defaults when details are missing, scaffolds a CLIENT_ONBOARD directory (or named folder if a client name is present), and writes the seven deliverables with clear assumptions and handoff criteria.

When to use it

  • Right after closing a freelance client to move quickly from sale to delivery
  • When you need a repeatable, professional kickoff package in under an hour
  • If the client description is vague and you need structured open questions
  • When you want a ready-to-send kickoff message and clear payment schedule
  • To create a Claude Code context file (CLAUDE.md) for future automation

Best practices

  • Review PROJECT_BRIEF.md and mark any assumptions before sending to the client
  • Customize tech stack if the client specified cloud or language constraints
  • Attach the brief when sending the kickoff message and ask the open questions first
  • Adjust milestone timeline to match confirmed availability and budget
  • Keep CLAUDE.md in the repo root so future agents have project context

Example use cases

  • You just closed a Next.js + Supabase MVP and need a client-ready brief and milestones
  • A discovery call produced a vague request—generate defaults and five open questions to clarify scope
  • Preparing handoff materials before a contractor replacement or team takeover
  • Creating an archive-ready onboarding package for bookkeeping or audits
  • Generating a repeatable onboarding template for your freelance workflow

FAQ

The skill uses sensible defaults (4–6 week timeline, default stack, placeholder budget) and inserts five open questions in the brief flagged as [ASSUMED].

Can I change the default tech stack or timeline?

Yes. The generated TECH_STACK.md and MILESTONES.md are editable; update them to reflect client constraints or confirmed dates before sending.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational