Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+21 moreClaude CodeCursorCodex CLIMuseDots
Manus
Grok
Grok Bot+18 agentsAI Automation Client Closeout Pack
Turn messy AI automation project evidence into a sign-off verdict, precise blocker chase, and—when ready—a client handoff page.
$9
AI Automation Client Closeout Pack
Example session with this skill installed
I need to close out this n8n project before the final client call. Review the attached approved scope, change log, sanitized workflow export, test results, UAT notes, and ownership handoff. Check each promised outcome against the build, proof, and receiving owner. Tell me whether it is ready for client sign-off. If blocked, give me only the smallest evidence or decision chase. If ready, create the private closeout check and a separate client-facing handoff page. Do not assume anything that is not supported by the files.
- Read your context and instructions
- Compiled the ai automation client
AI AUTOMATION CLOSEOUT CHECK — PRIVATE
Assessment boundary
Supplied-evidence review only. No live execution performed.
Target: CRM Lead Intake v1.4 / Production
Verdict: BLOCKED
Decision summary
3 of 5 promised outcomes have attributable build and proof. Two material gaps prevent client sign-off.
Blockers
-
Retry safety — Duplicate-write prevention is represented in the workflow, but no exact-target retry result identifies release v1.4.
Smallest next action: Supply one expected-versus-actual retry record for v1.4 showing a single CRM record. -
Recovery ownership — Failed-write recovery is described, but no receiving owner or escalation path is named.
Smallest next action: Record the post-handoff recovery owner and escalation route.
Ready evidence
- Accepted webhook creates one CRM lead — proven by test T-01.
- Rejected payload is logged — proven by test T-03.
- Client UAT decision — approved with the two gaps above still open.
Outputs
- Private closeout check: CREATED
- Internal evidence chase: CREATED
- Client sign-off and handoff page: WITHHELD until blockers are cleared
Connects securely to your tools. The creator never sees your data.
About this skill
Know whether the project is actually ready to close
An automation can look finished while scope, test evidence, retry or recovery proof, ownership, or support boundaries remain unclear. This skill audits the redacted project material you supply before the final demo, final invoice, client sign-off, or ownership transfer.
What you get
- A private agency closeout check covering every promised outcome.
- A clear BLOCKED, READY WITH DISCLOSED EXCEPTIONS, or READY verdict.
- For blocked projects, the smallest evidence or decision chase needed to move forward.
- For ready projects, a separate client-facing sign-off and handoff page with delivered outcomes, evidence references, exceptions, ownership, exclusions, and support boundaries.
How it decides
Every in-scope promise is traced through Promise → Build → Proof → Owner. Claims are separated from attributable evidence for the target release and environment. Missing, stale, conflicting, duplicated, or unreadable critical material is surfaced instead of guessed.
Built for
AI automation freelancers and small agencies delivering n8n, Make, Zapier, chatbot, AI-agent, or API-connected workflows.
Useful inputs
Approved scope and changes; sanitized workflow exports or build notes; expected-versus-actual test records; UAT decisions; and platform, billing, credential, alert, recovery, escalation, and support ownership records.
Important boundaries
This is a supplied-evidence review. It does not execute, observe, deploy, or test the live automation, and it does not prove production reliability, security, legal compliance, or contractual acceptance. It will not invent approvals, results, owners, thresholds, terms, exclusions, or production status. Use redacted files and never provide passwords, API keys, tokens, payment-card data, patient data, or unnecessary personal data.
Reviews only the redacted files you supply; it does not run, deploy, or observe the live automation. It cannot certify production reliability, security, legal compliance, or contractual acceptance. A meaningful verdict requires approved scope plus identifiable build evidence. Missing, stale, conflicting, or unreadable critical evidence can produce a BLOCKED verdict. Never include passwords, API keys, tokens, payment data, patient data, or unnecessary personal information.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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 3 months ago
Permissions
Reads only the project files the buyer supplies or selects. Writes the private closeout check and, when the verdict permits, the client handoff Markdown files to the buyer's chosen output folder. No terminal, browser, network, environment-variable, or external-service access.