Employee Offboarding Manager

PassAudited by ClawScan on May 1, 2026.

Overview

This is a simple instruction-only offboarding checklist skill with no code or credentials, but users should avoid oversharing access details and verify the generated plan.

This skill appears safe to install as an instruction-only checklist generator. Use it as a planning aid, do not provide passwords or tokens, limit employee/access details to what is necessary, and have HR, legal, and IT review the final offboarding plan.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

A user could share sensitive employee and access information with the agent while preparing the checklist.

Why it was flagged

The example encourages including privileged account-access information as context for the offboarding plan. This is purpose-aligned, but access inventories are sensitive and should not include passwords, tokens, or unnecessary details.

Skill content
She owns the Q2 roadmap, runs weekly stakeholder syncs, and has admin access to Jira, Figma, and Amplitude.
Recommendation

Use only the minimum access details needed, avoid secrets or credentials, and handle outputs according to company HR and IT security policies.

What this means

A user might over-rely on the generated checklist and miss company-specific legal, HR, or access-revocation steps.

Why it was flagged

The skill uses broad assurance language for a generic checklist. Offboarding requirements can vary by company, jurisdiction, role, and system inventory, so the output should be treated as a draft rather than authoritative.

Skill content
The agent returns a full offboarding package with nothing missed.
Recommendation

Review the generated plan against internal HR, legal, compliance, and IT offboarding procedures before acting on it.