client-onboarding

client-onboarding is a skill for Claude Code from indranilbanerjee/digital-marketing-pro. It costs 31 tokens per session (1,349 once invoked), scanned A, original, MIT.

A marketing-client onboarding package is a set of plans and templates for starting work with a new client. It covers the kickoff meeting, information gathering, responsibilities, account access, early goals, communication, and escalation.

In plain words
What is it for?
It helps prepare a kickoff agenda, discovery questionnaire, stakeholder map, RACI matrix, access checklist, 30-60-90 day plan, communication schedule, escalation process, and welcome email.
Why use it?
It prevents unclear responsibilities, missing account permissions, and mismatched expectations during the handover from signing a contract to starting active work.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths.

Part of the digital-marketing-pro plugin — 164 skills, 5 commands, 24 agents shipped together

Good fit It helps prepare a kickoff agenda, discovery questionnaire, stakeholder map, RACI matrix, access checklist, 30-60-90 day plan, communication schedule, escalation process, and welcome email.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/indranilbanerjee/digital-marketing-pro/client-onboarding
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add indranilbanerjee/digital-marketing-pro --skill client-onboarding
Clone the repo
git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro

Made for: Claude Code.

Or install digital-marketing-pro, the plugin that ships this one along with the rest of its 164 skills, 5 commands, 24 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for client-onboarding

README.md
[![agentmods](https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/client-onboarding/github.svg)](https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/client-onboarding)
Your own site
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/client-onboarding"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/client-onboarding/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for client-onboarding

Your own site · 80×15
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/client-onboarding"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/client-onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,349 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.01349
Opus 5.5 $0.00012 $0.00540
Sonnet 5.5 $0.00006 $0.00270
Haiku 4.5 $0.00003 $0.00135

Measured 18d ago against content hash 716136e36d12, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

client-onboarding scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 18d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/client-onboarding/SKILL.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/digital-marketing-pro:client-onboarding

Purpose

Generate a comprehensive client onboarding workflow for a new marketing engagement. Covers kickoff planning, discovery, stakeholder alignment, access provisioning, milestone setting, and communication protocols to ensure a smooth transition from signed contract to active account with clear expectations on both sides.

Input Required

The user must provide (or will be prompted for):

  • Client name and industry: The new client's business name, vertical, and market segment
  • Services contracted: Which marketing services are included in the engagement (SEO, PPC, social, content, email, analytics, etc.)
  • Engagement timeline: Contract duration and key dates — start date, first deliverable, first review, contract end
  • Team structure (agency side): Account lead, strategist, specialists, and any shared resources assigned to the account
  • Team structure (client side): Primary contact, marketing lead, approvers, and subject matter experts available
  • Account access needs: Platforms, tools, and accounts requiring credentials or permissions (Google Ads, Analytics, CMS, social accounts, CRM, etc.)
  • Client maturity level: Startup, SMB, or enterprise — determines complexity of onboarding, approval layers, and compliance requirements
  • Stakeholder list: All individuals involved in the engagement with roles, decision authority, and communication preferences
  • Communication preferences: Preferred channels (Slack, email, calls), timezone, meeting availability, and response time expectations
  • Success criteria: What the client considers a successful engagement at 30, 60, and 90 days — and contractual KPIs if defined

Process

  1. Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load restrictions and relevant category files. Check for custom templates at ~/.claude-marketing/brands/{slug}/templates/. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
  2. Research client industry onboarding best practices: Identify industry-specific onboarding considerations — regulatory requirements, seasonal timing, common data sources, and typical ramp-up periods for the client's vertical
  3. Build kickoff meeting agenda: Structure a 60-90 minute kickoff covering introductions, engagement overview, goals alignment, process walkthrough, access handoff, communication setup, and immediate next steps
  4. Create discovery questionnaire: Draft 20-30 questions covering business context, competitive landscape, past marketing efforts, brand guidelines, content assets, data access, approval workflows, and success definitions
  5. Map stakeholders and decision-makers: Build a stakeholder map with RACI matrix (Responsible, Accountable, Consulted, Informed) for key activities — content approval, budget changes, strategy shifts, reporting, and escalations
  6. Define access and permissions checklist: Create a platform-by-platform checklist of all accounts, tools, and systems needing access — with permission level, owner, and deadline for provisioning
  7. Set 30-60-90 day milestones: Define specific, measurable milestones for each phase — discovery and setup (30 days), optimization and early results (60 days), full operation and first performance review (90 days)
  8. Establish communication cadence: Design the recurring meeting and reporting schedule — weekly status calls, monthly performance reports, quarterly business reviews, and ad-hoc escalation triggers
  9. Create escalation protocol: Define severity tiers (informational, urgent, critical), response time expectations, escalation paths on both agency and client sides, and resolution tracking
  10. Build knowledge transfer checklist: List all assets, documents, logins, brand files, historical data, and institutional knowledge the client needs to provide for the agency to operate effectively
  11. Compile into unified onboarding document: Assemble all components into a single structured onboarding package with clear ownership, deadlines, and a first-week action plan for immediate momentum

Read the full file on GitHub · 61 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 18d ago Changed · -120 tokens per session 716136e36d12
  2. 1mo ago First seen · 61 lines · 151 tokens per session scan A 3819c9c9cde3

Subscribe to this mod's changes

client-onboarding is a skill published in the GitHub repository indranilbanerjee/digital-marketing-pro (912 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,349 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.