Turn a role and start date into an owner-bound preboarding, Day 1, Week 1, 30/60/90, access, learning, and handoff plan with honest readiness states.
Most onboarding plans are long checklists with no proof that accounts work, managers are ready, or the first task teaches the role. This skill starts with the approved role, start boundary, owners, source systems, access authority, and the outcomes the new hire should be able to perform.
The workflow separates requested, scheduled, completed, and verified work. It maps dependencies, limits access to the approved role need, keeps sensitive employee records in authorized systems, and gives delayed equipment, missing accounts, inaccessible training, changed starts, and absent managers explicit recovery paths. Formal employment, payroll, benefits, immigration, accommodation, background-check, and legal decisions stay with their authorized owners.
The final pack includes the onboarding contract, role-readiness model, evidence register, dependency map, preboarding plan, first-week schedule, 30/60/90 learning path, access register, owner matrix, checkpoint log, and an evidence-matched verdict. It does not create accounts, send invitations, invent policies, or call a hire ready because a checklist was assigned.
Input
A backend engineer starts in nine days across a six-hour time-zone gap. The laptop is ordered, but delivery is unconfirmed. Email and chat were requested; production, customer-data, and repository access have no approved scope. The manager has a first task but no review criteria. Security training and payroll forms live in separate systems.
Output
An onboarding contract, role-outcome map, dependency and evidence registers, least-privilege access requests, device-delay fallback, privacy-safe owner handoffs, a time-zone-aware first week, supervised first-task criteria, 30/60/90 checkpoints, open gates, and a preboarding-ready or blocked verdict tied to the remaining evidence.
Input
Provide the approved role, team, manager, start date, location or remote arrangement, source systems, required tools or training, known owners, current requests, and any deadlines or exceptions. Ask the agent to build a new plan, review an existing checklist, prepare a specific starter, or reconcile onboarding already in progress. Unknown policies, access, documents, and completion stay visibly unknown until an authorized source confirms them.
The supplied role, team, manager, location or remote arrangement, start date, employment boundary as recorded by the organization, and the role outcomes this onboarding should support.
The accountable manager or onboarding owner plus the HR, IT, security, payroll, facilities, accessibility, training, or compliance sources relevant to the case.
Known account, equipment, document, schedule, training, policy, access, accessibility, privacy, or exception states. Missing evidence is allowed and remains explicit.
SKILL.md; onboarding state, privacy, least-privilege access, exception, and readiness controls; reusable onboarding contract, role-readiness, dependency, schedule, learning-path, access, owner, checkpoint, and verdict templates; OpenAI interface metadata
No reviews yet.
A contractor may start tomorrow, but the agreement and classification decision are unresolved. The manager is away. A teammate suggests sharing an admin login and sending customer exports to a personal email so work can begin. The start date changed twice, and no one owns the access or training exceptions.
Output
A blocked decision for the affected work, explicit refusal of shared credentials and personal-data workarounds, reserved employment decisions routed to authorized owners, a revised dependency map, safe orientation-only options if approved, escalation owners, expiries, evidence needs, and the smallest action that can unblock the start.
Input
The tracker marks every item complete because invitations were sent. The new hire missed security training, still cannot access one source system, has broader analytics access than the role needs, and completed two tasks without review. The manager says onboarding succeeded because 30 days elapsed. Reconcile the record and prepare the handoff.
Output
A preserved planned-versus-observed checkpoint log, corrected states for invitations, training, access, and reviewed work, a least-privilege correction path, owner-bound recovery actions, evidence-based 30/60/90 decisions, open risks, and an in-progress-with-limits or blocked verdict rather than a success claim.
Trebuh
Updated Jul 13, 2026
Automated scan passed. It found 1 finding; highest severity info.
Scanned Aug 3, 2026.
Automated scanning reduces risk but cannot guarantee a package is safe for every environment.
Creator
Zzalrio0
