← Back to Skills Marketplace
merjua14

Client Onboarding Automator

by merjua14 · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
257
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install client-onboarding-automator
Description
Automates client onboarding from inquiry to project start, handling intake, contract creation, payment, welcome emails, and project setup.
README (SKILL.md)

Client Onboarding Automator Skill

Automate the entire client onboarding workflow — from initial inquiry to project kickoff. Handles intake forms, contract generation, payment collection, welcome sequences, and project setup.

What This Skill Does

  1. Intake Processing — Captures new client info from email/form submissions
  2. Contract Generation — Creates service agreements from templates
  3. Payment Collection — Sends Stripe payment links automatically
  4. Welcome Sequence — Sends onboarding email series (day 0, 1, 3, 7)
  5. Project Setup — Creates folders, tasks, and checklists for new clients
  6. CRM Update — Logs client details in your tracking system

Trigger

When a new inquiry arrives (email matching pattern, form webhook, or manual trigger):

New client: [name] | [email] | [service] | [budget]

Workflow

Step 1: Intake

Parse the incoming inquiry and extract:

  • Client name and email
  • Service requested
  • Budget/package selected
  • Timeline expectations
  • Special requirements

Step 2: Auto-Response (Immediate)

Send a personalized acknowledgment email:

Subject: Thanks for reaching out, [Name]! Here's what happens next

Hi [Name],

Thanks for your interest in [service]. I've received your inquiry and here's what to expect:

1. I'll review your requirements (within 2 hours)
2. You'll receive a proposal with pricing
3. Once approved, we kick off immediately

In the meantime, here's a quick questionnaire to help me prepare:
[Link to intake form]

Best,
[Your name]

Step 3: Proposal Generation

Create a proposal document with:

  • Scope of work (based on service selected)
  • Pricing (from your rate card)
  • Timeline
  • Terms

Step 4: Contract + Payment

Once proposal is accepted:

  • Generate contract from template
  • Create Stripe payment link for the agreed amount
  • Send contract + payment link to client

Step 5: Welcome Sequence

After payment:

  • Day 0: Welcome email + access credentials + kickoff questionnaire
  • Day 1: "Getting started" guide + calendar link for kickoff call
  • Day 3: Check-in + first deliverable preview
  • Day 7: Progress update + feedback request

Step 6: Project Setup

  • Create project folder in workspace
  • Generate task checklist from service template
  • Set up recurring check-in reminders

Configuration

{
  "business_name": "Your Business Name",
  "from_email": "[email protected]",
  "reply_to": "[email protected]",
  "stripe_key": "sk_live_...",
  "services": {
    "basic": { "name": "Basic Package", "price": 497, "description": "..." },
    "pro": { "name": "Pro Package", "price": 997, "description": "..." },
    "enterprise": { "name": "Enterprise", "price": 2497, "description": "..." }
  },
  "welcome_sequence_delays": [0, 1, 3, 7]
}

Requirements

  • Resend, SendGrid, or SMTP for email
  • Stripe for payments
  • OpenClaw with email/webhook channel configured
Usage Guidance
This skill appears to do what it says, but it's high-level and expects API/SMTP keys and a workspace/CRM connection. Before installing: 1) Do not paste live secret keys into public files — use environment variables or a secure secrets store and prefer test API keys (Stripe test keys) for initial setup. 2) Confirm which CRM/project workspace and email provider the agent will connect to and limit API key scopes where possible. 3) Understand and audit automated payment/contract flows (avoid auto-charging without an explicit approval step). 4) Require explicit consent and logging for any client data transmitted to external services. 5) Rotate keys after testing and monitor activity. If you want a safer test, ask the skill maintainer for a connector list and run with sandbox/test credentials first.
Capability Analysis
Type: OpenClaw Skill Name: client-onboarding-automator Version: 1.0.0 The skill bundle automates high-risk business processes including Stripe payment collection, email communication, and filesystem management for project setup. While these capabilities (network and file access) are aligned with the stated purpose in SKILL.md and config.json, they constitute significant risk surfaces according to the analysis criteria. Furthermore, the documentation explicitly instructs the user to provide a live Stripe secret key ('sk_live_...') in the configuration, which is a sensitive credential handling practice.
Capability Assessment
Purpose & Capability
The name/description (client onboarding: intake, contracts, Stripe payments, emails, project setup, CRM logging) aligns with the SKILL.md steps. Required capabilities (email provider, Stripe, workspace/CRM) are expected for this purpose.
Instruction Scope
The SKILL.md stays within onboarding tasks but is high-level and leaves unspecified which CRM/workspace/project system to use and how files/credentials are stored. That vagueness can cause the agent to request additional access/credentials at runtime (reasonable for integration but worth attention). The instructions do not ask to read unrelated system files or exfiltrate data, but they do instruct sending client data to external services (email, Stripe, CRM) which is inherent to the feature.
Install Mechanism
Instruction-only skill with no install spec or code files — lowest install risk. Nothing is downloaded or written by an installer in the manifest.
Credentials
No required env vars or primary credential are declared in the registry metadata, but the SKILL.md example config includes a Stripe secret (stripe_key) and references SMTP/SendGrid/Resend. Requesting those service credentials is proportionate to the feature, but storing live secret keys in a config file (as shown) is risky. The skill does not ask for unrelated credentials.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent system-level privileges or install hooks. Autonomous invocation is allowed but is the platform default and not by itself a concern.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install client-onboarding-automator
  3. After installation, invoke the skill by name or use /client-onboarding-automator
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of Client Onboarding Automator. - Automates end-to-end client onboarding: intake, contract, payment, welcome emails, and project setup. - Processes inquiries via email or forms and updates your CRM with client details. - Generates proposals, contracts, and Stripe payment links automatically. - Sends a sequenced onboarding email series (day 0, 1, 3, 7) after payment. - Sets up client project folders, tasks, and recurring reminders.
Metadata
Slug client-onboarding-automator
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Client Onboarding Automator?

Automates client onboarding from inquiry to project start, handling intake, contract creation, payment, welcome emails, and project setup. It is an AI Agent Skill for Claude Code / OpenClaw, with 257 downloads so far.

How do I install Client Onboarding Automator?

Run "/install client-onboarding-automator" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Client Onboarding Automator free?

Yes, Client Onboarding Automator is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Client Onboarding Automator support?

Client Onboarding Automator is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Client Onboarding Automator?

It is built and maintained by merjua14 (@merjua14); the current version is v1.0.0.

💬 Comments