clous-ai/hreng-offboard
skills/hreng-offboard/SKILL.md
Use when the user is planning an exit or handoff for a departing team member; produce exit checklist (access, docs, knowledge transfer, last day), handoff doc, and access-revoke list.
testing
Updated Apr 4, 2026
$ install --global
skillsauthnpx skillsauth add clous-ai/agents hreng-offboardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 4, 2026, 3:06 PM3.8s5 files scanned
SKILL.md
- name:
- hreng-offboard
- description:
- Use when the user is planning an exit or handoff for a departing team member; produce exit checklist (access, docs, knowledge transfer, last day), handoff doc, and access-revoke list.
- version:
- 1.0.0
- license:
- MIT
Offboard / Exit
Produce an exit checklist, handoff plan, and access-revoke list to close the employee lifecycle cleanly.
When to Use
Use this skill when:
- An employee is leaving (resignation, end of contract, termination) and you need a structured handoff.
- You want an exit checklist (access revoke, docs, knowledge transfer, last day).
- You need a handoff doc for continuity (owner, status, contacts).
Do not use this skill when:
- The focus is onboarding a new hire → use
hreng-onboard-306090. - The focus is performance or PIP → use
hreng-perf-diagnose/ pip command.
Inputs Required
- Person, role, last day (if known).
- Systems they use, docs they own, key contacts (AskUserQuestion or Read).
- Handoff recipient(s) (manager, teammate, backup).
Outputs Produced
- Exit checklist: access revoke list, doc ownership transfer, knowledge transfer items, final day logistics (equipment, badge, offboarding meeting).
- Handoff doc: projects/artifacts, status, next owner, contacts; use
templates/handoff-doc.mdwhen present. - Reminder: coordinate with HR/IT for access and equipment; do not store passwords or sensitive access in the doc.
Using Supporting Resources
Templates
templates/exit-checklist.md– Exit checklist (access, docs, knowledge transfer, last day).templates/handoff-doc.md– Handoff document (owner, status, contacts).
References
- None in-repo; coordinate with HR/IT and onboarding (e.g.
hreng-onboard-306090) for continuity.
Scripts
- No validation script; rely on HR/IT workflows for access and equipment.
Core Pattern
- List systems and access (code, infra, SaaS, docs, keys).
- List deliverables and docs they own; assign next owner per item.
- Knowledge transfer: what only they know; suggest sessions or docs.
- Last day: equipment return, access cut, final conversation, exit survey if applicable.
- Output checklist + handoff doc; remind HR/IT coordination.
Common Mistakes
- Listing credentials or secrets in the handoff doc; only list systems and owners.
- Skipping knowledge-transfer sessions when the leaver is the only expert.
- Not aligning with HR/IT on access cut timing and equipment return.
Legal disclaimer
This skill supports exit and handoff logistics only; it is not legal advice. Termination, final pay, benefits, and restrictive covenants vary by jurisdiction and contract. Consult HR/legal for terminations and sensitive exits.
Tips
- Prefer MCP for org/access data if available; do not exfiltrate credentials.
- Keep handoff doc in a shared, access-controlled location.
Related Skills
clous-ai/webhook-operations
development
VerifiedTrustedCommunity
Use when an AI agent needs to inspect, create, update, delete, or troubleshoot Clous webhook subscriptions and events.
SKILL.mdUpdated May 11, 2026
clous-ai/platform-operation
tools
VerifiedTrustedCommunity
Use when an external AI agent needs to operate Clous safely across MCP, SDK, CLI, and API surfaces while preserving user/company context and avoiding unsafe mutations.
SKILL.mdUpdated May 11, 2026
clous-ai/object-management
tools
VerifiedTrustedCommunity
Use when reading, creating, updating, or deleting Clous objects such as employees, candidates, jobs, reviews, skills, and forms.
SKILL.mdUpdated May 11, 2026
clous-ai/mcp-use
tools
VerifiedTrustedCommunity
Use when an AI agent can call Clous remote MCP tools to inspect or operate the Clous platform, HR, or employee surfaces.
SKILL.mdUpdated May 11, 2026