agentleFS
aiagentwithdhruvaiagentwithdhruv/skills/onboarding-kickoff/SKILL.md

onboarding-kickoff

Skill16 starsChanged 9 months agoMITView on GitHub

Automated client onboarding after kickoff call - generates leads, creates email campaigns, sets up auto-reply. Use when user asks to onboard a new client, set up campaigns for client, or run post-kickoff automation.

  • Reads credentials

3 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 1 is common, 0 are distinctive, and 0 are very specific to this project.

  • 1

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Add entry to auto-reply knowledge base sheet for intelligent response handling.

    line 70

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Post-Kickoff Client Onboarding

Goal

Automated onboarding workflow that runs after kickoff call. Generates leads, creates campaigns, and sets up auto-reply system.

Inputs (from kickoff call)

Required:

  • client_name: Company name
  • client_email: Primary contact email
  • service_type: What service they provide
  • target_location: Geographic area
  • offers: Three offers (pipe-separated)
  • target_audience: Who they're targeting
  • social_proof: Credentials/results

Optional:

  • lead_limit: Number of leads (default: 500)
  • value_proposition: Additional context

Scripts

  • ./scripts/gmaps_lead_pipeline.py - Lead generation
  • ./scripts/casualize_company_names_batch.py - Name casualization
  • ./scripts/instantly_create_campaigns.py - Campaign creation
  • ./scripts/onboarding_post_kickoff.py - Full orchestration
  • ./scripts/update_sheet.py - Sheet updates

Process

Step 1: Generate Lead Search Query

Format: {service_type} in {target_location} Example: "plumbers in Austin TX"

Step 2: Scrape and Enrich Leads

python3 ./scripts/gmaps_lead_pipeline.py \
  --search "{service_type} in {target_location}" \
  --limit {lead_limit} \
  --sheet-name "{client_name} - Leads" \
  --workers 5

Step 3: Casualize Company Names

python3 ./scripts/casualize_company_names_batch.py \
  --sheet-url "{sheet_url}" \
  --column "business_name" \
  --output-column "casualCompanyName"

Step 4: Create Instantly Campaigns

python3 ./scripts/instantly_create_campaigns.py \
  --client_name "{client_name}" \
  --client_description "..." \
  --offers "{offers}" \
  --target_audience "{target_audience}" \
  --social_proof "{social_proof}"

Step 5: Upload Leads to Campaigns

Distribute leads evenly across 3 campaigns via Instantly API.

Step 6: Add Knowledge Base Entry

Add entry to auto-reply knowledge base sheet for intelligent response handling.

Step 7: Send Summary Email

Send completion email to client with:

  • Campaign links and leads counts
  • Lead spreadsheet URL
  • Auto-reply configuration details
  • Next steps

Output

{
  "status": "success",
  "client_name": "...",
  "sheet_url": "...",
  "lead_count": 50,
  "campaigns": [...],
  "leads_uploaded": true,
  "knowledge_base_updated": true,
  "summary_email_sent": true
}

Timing

  • Full workflow: ~10-15 minutes for 50 leads
  • Lead scraping uses 5 workers by default

Error Handling

  • < 10 leads found: Warn but continue
  • 0 leads found: Error (bad search query)
  • Instantly API error: Capture, note for manual fix
  • Sheet/email failures: Log but complete workflow

Schema

Inputs

NameTypeRequiredDescription
client_namestringYesCompany name
client_emailstringYesPrimary contact email
service_typestringYesWhat service they provide
target_locationstringYesGeographic area
offersstringYesThree offers (pipe-separated)
target_audiencestringYesWho they're targeting
social_proofstringYesCredentials/results
lead_limitintegerNoNumber of leads (default: 500)

Outputs

NameTypeDescription
statusstringsuccess/failure
sheet_urlstringLead spreadsheet URL
lead_countintegerNumber of leads generated
campaignsarrayCampaign IDs created
summary_email_sentbooleanWhether summary was emailed

Credentials

NameSource
APIFY_API_TOKEN.env
ANTHROPIC_API_KEY.env
INSTANTLY_API_KEY.env

Composable With

Skills that chain well with this one: gmaps-leads, casualize-names, instantly-campaigns, welcome-email

Cost

~$5-10 for 500 leads + campaigns

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.