AGENTKIT/WORKS

template · core tier

Client Ops Autopilot

Every account runs like your best account — onboarding, reports, invoices, scope, health, offboarding.

PRICE$99$69
Buy now — $69

Seven skills cover the full client lifecycle so the operational work between the billable work — status updates, meeting action items, invoice reminders, scope conversations — is drafted, tracked, and consistent, while you stay the human on the relationship. Built for freelancers and agencies who lose billable hours to account admin.

$ tree client-ops-autopilot/✓ actual contents
client-ops-autopilot/
├── README.md · INSTALL.md · LICENSE (commercial)
├── skills/               ← 7 lifecycle skills:
│   ├── client-onboarding · status-report-generator
│   ├── meeting-to-action-items · invoice-chaser
│   ├── scope-creep-sentinel · client-health-score
│   └── offboarding-handoff
└── templates/            ← 6 copy-paste templates
    ├── onboarding-checklist · status-report · action-items-log
    └── invoice-ladder · change-request · offboarding-checklist

Why it's different

  • The agent drafts, you approve — nothing client-facing sends itself
  • Everything leaves a dated, findable record — awkward conversations get short
  • Tool-agnostic: works against plain files, any PM tool, any invoicing tool

Runs unattended

The recurring skills in this kit ship with a scheduling procedure — not a guide for you to follow, but a file your agent reads and executes. Paste one line; it installs to the right directory for your platform, creates the schedule, and proves the first run actually wrote something.

paste into your agent

Read RUN-UNATTENDED.md in this folder and put this kit's recurring skills on a schedule for my platform, verifying each step.

Unattended execution support by agent platform
PlatformRuns with your laptop closedHow
Claude CodeYes — Anthropic's cloudRoutines, hourly or slower
HermesOnly while its host stays upcron, any interval
CodexNeeds a scheduler you owncodex exec + launchd or CI

Every scheduled run has to name the file it must write, and records a result either way. A run that finishes cleanly having produced nothing is recorded as a failure — which is the difference between automation you can leave alone and automation that has quietly stopped working.

Questions, answered

Will clients know an agent wrote the reports?+

The templates read like a competent operator wrote them, and the rule is built in: the agent drafts, a human approves. You edit the voice once and it sticks.

Does it integrate with my PM / invoicing tool?+

It works against plain files out of the box. If your tool has an API your agent can reach, point the skills at it — the workflow is identical either way.

Add tool connectors

Workflow kits teach the job. Integration kits handle the tools. They stack.