Claude-skill-registry client-handoff

Project handover process for lead generation websites. Documentation, training, credentials, maintenance. Use when project complete.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/client-handoff" ~/.claude/skills/majiayu000-claude-skill-registry-client-handoff && rm -rf "$T"
manifest: skills/data/client-handoff/SKILL.md
source content

Client Handoff Skill

Purpose

Produces handoff package for completed lead generation website. Documentation + training + access transfer.

Scope

✅ Supported❌ Out of Scope
Lead gen sitesE-commerce/webshops
Static Astro sitesCMS with multi-editor
Single clientAgency white-label
Cloudflare PagesCustom hosting

Skill Output

This skill produces:

ArtefactFormatRequired
Site DocumentationPDF/Notion
Credentials DocumentSecure doc
Training RecordingLoom video
Analytics AccessGA4 Admin invite
Maintenance AgreementPDF

Core Rules

  1. Documentation before handoff — Nothing verbal-only
  2. Training session required — Screen-recorded minimum
  3. Client sets all passwords — Never store client passwords
  4. 30-day support included — Post-launch bug fixes
  5. Analytics access = Admin — Client owns their data
  6. Search Console = Owner — Full control to client

Blocking Conditions (STOP)

Handoff BLOCKED if any:

ConditionCheck
Site not approvedWritten client approval
Documentation missingAll 5 artefacts ready
Training not doneRecording exists
Analytics not sharedClient has Admin
Search Console not sharedClient has Owner
No maintenance termsAgreement signed

If blocked → FIX first, do not handoff.

Credentials Responsibility

ItemWho Sets PasswordWho Stores
CloudflareClientClient
Domain registrarClientClient
GA4Google accountClient
Search ConsoleGoogle accountClient
CookieYesClientClient

Rule: Developer NEVER stores client passwords. Client sets own passwords during handoff.

Checklists

Before Handoff Meeting

  • Site fully tested and approved
  • All content finalized
  • Analytics confirmed working
  • Documentation prepared
  • Training agenda ready
  • Loom/recording ready

During Meeting

  • Walk through site live
  • Test form submission together
  • Show analytics dashboard
  • Explain maintenance terms
  • Record entire session
  • Client sets their passwords

After Meeting (Same Day)

  • Send documentation package
  • Share recording link
  • Add client to GA4 (Admin)
  • Add client to Search Console (Owner)
  • Send final invoice
  • Schedule 30-day check-in

Training Session

Duration: 30-45 minutes
Format: Video call + screen share + recording

TopicTimeCovers
Site tour5 minLive site, mobile, key pages
Forms5 minTest submit, where leads go
Analytics10 minGA4 dashboard, key metrics
Search Console5 minIndexing, common issues
Content updates5 minHow to request, what's included
Q&A10 minQuestions, next steps

30-Day Support Period

IncludedNot Included
Bug fixesNew features
Form issuesDesign changes
Analytics setup fixesContent writing
Broken linksSEO campaigns

After 30 days → Maintenance agreement terms apply.

Forbidden

  • ❌ Verbal-only handoff
  • ❌ No documentation
  • ❌ Storing client passwords
  • ❌ Locking client out of accounts
  • ❌ Unclear maintenance terms
  • ❌ No training recording
  • ❌ Handoff with blocking conditions

References

Definition of Done

  • All 5 artefacts delivered
  • Training recorded and shared
  • Client has GA4 Admin access
  • Client has Search Console Owner
  • Client set own passwords
  • Maintenance agreement signed
  • 30-day check-in scheduled