client-delivery-auditor
Skill3 starsChanged 6 months agoMITView on GitHub
Audit final client deliverables against the agreed scope, verify files and links, and prepare a clear handoff with an unsent delivery message. Use when a user asks to check a delivery package, find missing or unverified items, prepare final files, create a client handoff, draft a delivery email, separate private evidence from public proof, or confirm that a project is ready to send.
In this repository47 other files it gives its agents.
- agents-md-writerSkill
- ai-image-run-pacingSkill
- automation-state-reconcilerSkill
- backup-readiness-auditorSkill
- brand-voice-linterSkill
- case-study-writerSkill
- client-intake-builderSkill
- client-workspace-scaffolderSkill
- code-deduplicatorSkill
- cold-outreach-writerSkill
- demo-animationSkill
- demo-animation-v2Skill
- discovery-briefSkill
- em-dash-removerSkill
- etsy-listing-optimizerSkill
- follow-up-radarSkill
- github-profile-proof-updaterSkill
- github-safe-publisherSkill
- idea-inboxSkill
- implement-client-feedbackSkill
- lead-scorerSkill
- llms-txt-generatorSkill
- local-app-public-demoSkill
- media-spec-checkerSkill
- obsidian-daily-noteSkill
- ops-status-reportSkill
- outreach-pipeline-designerSkill
- php-form-mailerSkill
- proposal-writerSkill
- release-announcement-writerSkill
- remove-ai-image-metadataSkill
- research-brief-curatorSkill
- research-to-articleSkill
- screen-recorderSkill
- session-handoffSkill
- skill-builderSkill
- skill-reviewerSkill
- social-campaign-proof-trackerSkill
- skill-nameSkill
- thumbnail-legibility-checkSkill
- thumbnail-set-designerSkill
- vault-janitorSkill
- verify-public-claimsSkill
- web-scraperSkill
- website-change-verifierSkill
- windows-reinstall-plannerSkill
- write-evidence-backed-profileSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Read the latest brief, proposal, feedback, approval notes, and existing handoff material.
- Distinctive: line 14
Use the latest explicit decision when it changes earlier scope.
- Distinctive: line 15
Do not infer pricing, rights, approval, deadlines, or included deliverables.
- Distinctive: line 29
Check filenames, formats, dimensions, variants, links, versions, accessibility needs, and usage instructions relevant to the project.
- Distinctive: line 34
Follow an existing delivery structure when one is already established.
- Distinctive: line 37
Do not delete, rename, archive, upload, or change access permissions unless requested.
- Distinctive: line 38
Keep client-facing instructions separate from internal continuation notes.
- Distinctive: line 44
Keep the message concise, warm, and easy to act on.
- Distinctive: line 48
Never send the message or record it as sent.
- Distinctive: line 53
Keep a public-proof brief separate from the delivery handoff.
- Distinctive: line 59
Verify links, downloads, routes, dimensions, document pages, archive contents, or builds as appropriate.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Client Delivery Auditor
Turn completed project work into a checked delivery package with clear status, instructions, and communication.
1. Reconstruct the agreed delivery scope
- Confirm the project root, delivery milestone, recipient, and intended delivery channel.
- Read the latest brief, proposal, feedback, approval notes, and existing handoff material.
- Use the latest explicit decision when it changes earlier scope.
- Do not infer pricing, rights, approval, deadlines, or included deliverables.
- Preserve exact project names, links, dates, formats, and file requirements supplied by the user.
2. Audit every promised item
Classify each deliverable as:
present and verified: exists, opens correctly, and matches the agreed formatpresent but unverified: exists but still needs an appropriate checkpartial: identifiable work remainsmissing: promised but not foundexcluded: explicitly removed from scopeawaiting client: depends on approval, content, access, or another client action
Check filenames, formats, dimensions, variants, links, versions, accessibility needs, and usage instructions relevant to the project. Do not report the delivery as ready while required items are missing or unverified.
3. Prepare the handoff
- Use assets/client-delivery-handoff-template.md.
- Follow an existing delivery structure when one is already established.
- Include only final or intentionally shared files in the client package.
- Exclude scratch work, backups, raw prompts, logs, databases, account exports, and internal notes.
- Do not delete, rename, archive, upload, or change access permissions unless requested.
- Keep client-facing instructions separate from internal continuation notes.
4. Draft the delivery message
- Include
To:only when the recipient is known and always includeSubject:. - Lead with what is complete and where the client can access it.
- Keep the message concise, warm, and easy to act on.
- State missing or follow-up items plainly.
- Offer future support as an option, not a sales push.
- Request portfolio permission only when useful and include a clear opt-out.
- Never send the message or record it as sent.
5. Separate delivery from public proof
- Name a client, show work, quote feedback, or publish outcomes only when public use is confirmed.
- Keep a public-proof brief separate from the delivery handoff.
- Generalize or omit private correspondence, unpublished metrics, implementation details, account data, and internal paths.
6. Verify and report
- Open or inspect representative deliverables rather than checking only filenames.
- Verify links, downloads, routes, dimensions, document pages, archive contents, or builds as appropriate.
- Report complete, partial, blocked, and awaiting-client items separately.
- Return the handoff location, package status, checks performed, unsent message draft, and remaining action.
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
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.

