Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Client Onboarding Pro

    1

    Turn approved freelance work into a clear, secure client onboarding and kickoff workflow.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Client Onboarding Pro

    Client Onboarding Pro

    Example session with this skill installed

    We have an approved project described by this proposal or statement of work: [paste relevant approved scope, redacting sensitive data]. Client and team details already confirmed: [roles, channels, dates, if known]. Create a welcoming onboarding email, tailored intake questions, a prioritized checklist separating pre-kickoff requirements from later items, a least-privilege access/asset request, a kickoff agenda, approval and communication rules, and an internal handoff. Flag missing or conflicting commitments; do not invent contract terms, deadlines, identities, or approvals. Never request passwords or production secrets through the email.

    • Read your context and instructions
    • Compiled the client onboarding pro

    Onboarding status

    The engagement is approved, but the proposal supplied here does not yet confirm a kickoff date, authorized client approver, preferred communication channel, or required system access. Do not represent the project as fully onboarded until those details are verified.

    Welcome message draft

    Hi [client name],

    We’re looking forward to starting [project name]. To prepare a focused kickoff, please confirm the primary point of contact and approver, preferred communication channel, and a few suitable meeting times. We’ll use the approved scope as our baseline and raise any questions before work begins.

    Please share only the project materials listed below through the agreed secure workspace. Do not send passwords, private keys, payment credentials, or production secrets by email. We can arrange approved least-privilege access through your organization’s secure access process if needed.

    Thanks,
    [team name]

    Before kickoff

    ItemOwnerNeeded byStatus
    Confirm client lead and authorized approverClientBefore kickoffOpen
    Confirm kickoff time and communication channelBothBefore kickoffOpen
    Reconfirm approved goal, deliverables, exclusions, and change process against signed scopeBothBefore kickoffReview
    Identify required content, brand assets, data, or technical contextClientOnly items needed for first milestoneOpen
    Arrange scoped, least-privilege access through a secure channel, if requiredClient security contactBefore dependent workOpen
    Confirm billing readiness from the approved agreement without inventing tax detailsProject ownerPer agreementVerify

    Intake questions

    1. Which approved outcome is the first priority, and what would count as accepted delivery?
    2. Who provides day-to-day feedback, and who can approve deliverables or scope changes?
    3. What existing materials or systems are needed for the first milestone?
    4. Are there known dependencies, review windows, accessibility, privacy, or security constraints in the approved scope?
    5. What communication cadence and response expectations work for the client?
    6. Which items can be provided later without delaying kickoff?

    Kickoff agenda (30–45 minutes)

    • Confirm goals and sold scope; list any ambiguity without changing the agreement.
    • Review deliverables, acceptance approach, milestone sequence, and known dependencies.
    • Confirm owners, approvers, channels, meeting cadence, and escalation path.
    • Review required inputs and secure access process; avoid sharing secrets in chat or email.
    • Record decisions, open questions, and next actions with owners and dates only after they are agreed.

    Internal handoff

    Prepare a concise summary of the approved scope, client contacts and authority as verified, first milestone, confirmed constraints, dependencies, open decisions, secure access status, communication plan, and billing/admin checkpoints. Label unknowns as open. Do not schedule work against an unconfirmed date or treat silence as approval.

    Next step

    Confirm the client approver, kickoff slot, and secure workspace. Then update the checklist from verified answers and mark onboarding complete only when required pre-kickoff conditions are satisfied.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Client Onboarding Pro

    Help freelancers, consultants, studios, and service teams start approved client projects with less friction and fewer missed decisions. Convert a proposal, quote, contract, statement of work, project brief, marketplace order, or discovery notes into a tailored onboarding checklist, focused intake questions, welcome message, kickoff agenda, access and asset request, approval map, communication cadence, dependency list, and internal handoff.

    Confirm what was sold and who owns each decision. Separate what is required before kickoff from information needed later. Reuse details already supplied, identify contradictions, minimize data collection, and request only the access and assets needed for the approved scope. Use least privilege and never ask clients to send passwords, private keys, production secrets, or payment credentials in ordinary forms or messages.

    Do not invent contract terms, dates, stakeholders, approvals, budgets, access, tax details, or legal requirements. The skill is not legal, tax, accounting, identity-verification, security-audit, or payment advice. Keep contractual, billing, security, and scope decisions under human control.

    Output quality depends on accurate approved scope and verified client details. It cannot create or approve contracts, determine legal or tax obligations, confirm identity, grant access, process payments, or guarantee client satisfaction or project success. Kickoff dates, owners, billing facts, dependencies, and approvals remain unconfirmed until verified. Use a secure authorized process for any access or confidential materials.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    Read Files

    Read only project materials the user deliberately provides or authorizes. Minimize collection of personal and client data. Never request or store passwords, API keys, private keys, production secrets, payment credentials, or unnecessary personal information. Use an approved secure channel and least-privilege access process. Keep contract, billing, security, and scope approvals with authorized humans.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    Share the approved proposal, scope, or order and only relevant confirmed project details. Redact sensitive information. The skill will mark unknowns rather than inventing dates, owners, approvals, or commitments.

    No. It can draft a least-privilege access request, but the client should use an approved secure access process. Never send passwords, private keys, API secrets, or payment credentials in ordinary email or chat.

    After required pre-kickoff details and dependencies are actually verified, including authorized approvers, agreed kickoff arrangements, essential inputs, and any necessary secure access. Unknowns should remain open instead of being treated as approvals.

    New in Business & Operations