offboarding-checklist

Automates employee offboarding across Okta, Google Workspace, Google Drive, and GitHub with approval gates.

20.2k|3.4k|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/kortix-ai/suna --skill offboarding-checklist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: offboarding-checklist
Source: https://github.com/kortix-ai/suna/tree/main/packages/starter/templates/marketplace/runtime/skills/offboarding-checklist
Command: npx skills add https://github.com/kortix-ai/suna --skill offboarding-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Employee departures require revoking access and transferring assets across many systems, and steps are easy to miss under time pressure. This Skill runs the full offboarding checklist for each newly detected departure, in the right order, without skipping steps or blocking one case on another.

Core Features & Use Cases

  • Departure Detection: Polls the designated Okta group for newly marked departures and treats each person as an independent case.
  • Access Revocation: Deactivates Okta accounts, removes app assignments, suspends Google Workspace accounts, removes GitHub org and team membership, and reclaims paid licenses.
  • Human Approval Gate: Holds irreversible Google Drive ownership transfers for human approval before executing, and never deletes accounts.
  • Use Case: An IT admin schedules a daily run; the agent finds two new departures, revokes their access across Okta, Google, and GitHub, queues the Drive ownership transfers for approval, and posts the completed checklist to the notification channel.

Quick Start

Run the offboarding checklist for any employees newly added to the departures group in Okta and post the results to the notification channel.

Frequently Asked Questions about offboarding-checklist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate employee offboarding across Okta and Google Workspace?

Detect departures via a designated Okta group, then deactivate the Okta account, remove app assignments, suspend the Google Workspace account, and release licenses. This Skill runs that checklist per departure and posts results to a notification channel.

How to transfer Google Drive ownership when an employee leaves?

List the documents and shared drives the person owns in Google Drive, then reassign ownership to their manager's Workspace email. Because this transfer is irreversible, the Skill holds it at a human approval gate before executing.

Can this offboarding workflow delete user accounts?

No, account deletion is never performed by this agent. It only deactivates Okta accounts and suspends Google Workspace accounts, which are reversible; actual deletion is a human decision made outside the workflow.

What happens if one offboarding case fails or is pending approval?

Each departure is handled as an independent case, so a failure or pending approval on one person never blocks the others found in the same run. Pending items are reported as pending, not as done.

How does offboarding handle a departing GitHub org owner?

If the person is the sole owner of a repository or last admin on a team, the Skill flags it instead of removing them, since a human must name a new owner first. Otherwise it removes org and team membership and reclaims the paid seat.