agentleFS
BenaliHQBenaliHQ/paxus-skills/skills/onboard-client-admin/SKILL.md

onboard-client-admin

Skill4 starsChanged 16 days agoNo licenceView on GitHub

Admin-side client onboarding for Paxus CPA. Phase 1 ingests the prospective-client quote, creates the client + primary contact in Financial Cents via API, spins up the New Client Onboarding project (Firm Admin Tasks auto-assigned to Jennifer), and drafts proposal content. Phase 2 (post-signing) copies the standard template into a new client Shared Drive, files the signed engagement PDF, moves the client from Prospective to Active, POSTs the Shared Drive link to FC's Resources section, creates an "Engagement Letters" folder in FC's Files tab with the engagement uploaded for client-portal access, attaches the 8 standard project templates (weekly bookkeeping, month-end review, month-end close, cleanup, post cleanup, kick-off call, client training manual, tax returns) with per-role task reassignment, and attaches the FC 1099 project templates for Full Service / Premium clients (Basic clients skip 1099). Phase 3 generates a personalized welcome packet in Canva, saves the PDF to the client's Shared Drive, and drafts the warm welcome email to the client. Phase 4 produces the internal Onboarding Dossier handoff file (Discovery, Pre-Kickoff Readiness, billing, cleanup scope, volumes/complexity, and Kickoff-Call reference notes) in the client's Perm File for the lead, then drafts the internal team handoff email pointing the team at the Dossier. Phase 5 drafts the day-before-kickoff email to the client with a reminder of the meeting time and the outstanding items on the FC Onboarding Checklist. Phase 6 completes the FC client-dashboard "About" section — the firm-wide custom fields (Entity Type, EIN, Package, monthly billing, budgeted hours, tax accountant, etc.) — sourcing values from the Perm File, recurring invoice, Taxes folder, and budgeted-hours tracker, writing each via PATCH /clients/{id}/about-fields/{field_id}, and also updates the separate Master Client Tracker Google Sheet. Run when a new client engages Paxus, when a signed engagement needs to be filed, the day before a client's kickoff call, or to fill in a client's FC About section.

  • Deletes or force-pushes
  • Sends data out

The file

Show its rules and text

We split this skill into the rules it gives an agent

53 rules. About 0 are common, 27 are distinctive, and 26 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈27

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 26

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.