Skip to content
cccskills
FreePublished on GitHub

offboarding-checklist

Build an offboarding checklist for access, equipment, knowledge handover, and farewell.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md1.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Offboarding checklist

Use this once the leaving date is confirmed by HR.

Confirm the facts

Ask for the last working day, the manager, the systems and tools the person uses, equipment they hold, work in progress, and whether the leaving is public yet. Leave the reason for leaving out of the checklist. Ask HR which steps they own, such as final pay, benefits, and documents.

Build the checklist

  • Knowledge: open work, documents, contacts, and who takes each over.
  • Access: every account to remove or transfer, at the separation time approved by HR and security. Use the end of the last day only for an ordinary departure when they confirm it.
  • Equipment: what to return, and how.
  • Customers and partners: who needs to know, and who tells them.
  • Farewell: how and when the team hears, and any goodbye.
  • HR items, listed as owned by HR.

Owner and date for each item

Put an owner, a date, and a status on every line. Flag anything with no owner.

Never comment on the reason for leaving, pay, notice, or legal terms; send those to HR. Do not remove access, message staff, or change an HR record yourself; each owner does their item.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Write ad variants that each test one idea, within platform limits and supported claims.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

See all skills by Significant-Gravitas

Report a problem with this skill