Turn scattered responsibilities and undocumented operational knowledge into a clear, actionable work handover pack.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install ym-work-handover-pack
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install ym-work-handover-pack using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is Work Handover Pack?
Work Handover Pack is an Openclaw Skills workflow for transforming fragmented duties, active projects, recurring tasks, system access details, contacts, risks, and operational tips into a structured Markdown handover document. It is designed for role changes, resignations, extended leave, project transfers, and any situation where another person must take over work quickly.
Its core value is capturing hidden knowledge: practical details that may not exist in formal documentation but are essential for successful execution. The skill does not invent missing facts; it identifies information gaps, asks targeted follow-up questions, preserves placeholders, avoids writing passwords, and flags sensitive content for desensitization before generation.
Work Handover Pack Use Cases
- Preparing a resignation, role-change, leave, or project-transfer handover
- Converting scattered responsibilities and recent work into a deliverable checklist
- Documenting active projects, blockers, deadlines, owners, and next steps
- Recording recurring tasks with previous and upcoming execution dates
- Mapping systems, account types, permission transfers, and approval paths without exposing passwords
- Capturing key internal and external contacts and the topics they handle
- Surfacing undocumented operational knowledge, workarounds, reporting caveats, and common pitfalls
- Creating a 30-day transition plan for shadowing, practice, independent execution, and review
- Starting an information-gap review when the user provides too little context to generate a reliable handover
How Work Handover Pack Works
- Collect the available work description, handover recipient, timeline, permission-transfer needs, and sensitivity status.
- Produce an information-gap checklist across eight dimensions: daily responsibilities, active items, recurring work, systems and accounts, document locations, contacts, pending decisions, and common pitfalls.
- Ask the user to fill critical gaps instead of inferring or fabricating responsibilities, people, systems, or operational details.
- Convert responsibilities into actionable entries ordered by frequency and importance, including triggers, operating steps, and completion criteria.
- Build an active-items table with current status, next action, milestone, related people, and deadline; use the statuses in progress, blocked, and not started.
- Build a recurring-task table containing the task, cadence, previous execution time, next expected execution time, and dependencies.
- Document systems and access assets using transfer status and the appropriate approval or request path; never include account passwords.
- Record key contacts with their role, name or alias, communication topic, and contact method when available.
- Ask targeted questions to uncover hidden knowledge. If an answer is unavailable, preserve an explicit placeholder such as
[To complete: Which report requires manual filtering?]. - Capture risks and unresolved decisions, then create a transition timeline. Use the supplied deadline when available; otherwise clearly label the default two-week assumption or use the standard 30-day four-stage plan.
- Run a self-check to confirm all nine sections exist, hidden knowledge contains real content or explicit follow-up placeholders, passwords are absent, and sensitive content is appropriately desensitized.
Work Handover Pack Setup
No third-party dependencies are required. The skill performs text-only processing, does not access local files unless the user provides a path, does not connect to the internet, and does not upload content.
- Make the
ym-work-handover-packskill available in the configured Openclaw Skills directory. - Preserve the package resources used by the workflow:
references/信息缺口八维度清单.mdfor gap discoveryreferences/隐性知识提问库.mdfor hidden-knowledge promptstemplates/交接包模板.mdfor the fixed nine-section output
- Invoke it with requests such as “prepare a work handover,” “organize a handover document,” “prepare a resignation handover,” or “handover.”
- Provide the work description and, when possible, the recipient, deadline, permission-transfer scope, and desensitized sensitive information.
- If you maintain a multi-session handover, optionally store supplementary material under
handover/within the skill directory. Cross-session storage is not enabled by default.
The skill must not receive raw passwords or other secrets. For sensitive material, provide a desensitized version before requesting document generation.
Work Handover Pack Data Schema & Taxonomy
The generated deliverable is Markdown with a fixed nine-section taxonomy:
| Section | Required content |
|---|---|
| 1. Information gaps | Missing details across eight dimensions, with follow-up questions |
| 2. Responsibility checklist | Trigger, operating steps, and completion standard; ordered by frequency × importance |
| 3. Active items | Item, current status, next step, milestone, related person, and deadline |
| 4. Recurring tasks | Task, cadence, previous execution time, next execution time, and dependencies |
| 5. Assets and permissions | System or platform, account type, transfer requirement, and request owner or path; no passwords |
| 6. Key contacts | Role, name or alias, communication topic, and contact method |
| 7. Hidden knowledge | Undocumented but necessary operational details, with explicit placeholders when unknown |
| 8. Risks and pending decisions | Unresolved approvals, budget issues, process uncertainties, and handover risks |
| 9. 30-day transition timeline | Week-one shadowing, week-two practice, week-three independent execution, and week-four review, adjusted to the supplied deadline |
Input metadata includes the work description as required data, while the handover recipient, deadline, permission-transfer scope, and sensitivity flag are optional. Missing recipients default to a “new colleague” perspective without omitting necessary context. Missing deadlines use a clearly labeled two-week assumption. Sensitive content must be desensitized before processing. Account credentials are represented only by transfer status and an approval route, such as “requires transfer,” never by secret values.
Package resources are organized under references/ and templates/; an optional handover/ directory may hold incremental working material when explicitly enabled.
Work Handover Pack Advanced Features
- Hidden-knowledge extraction using a dedicated question bank instead of generic documentation prompts
- Evidence-preserving completion behavior that uses explicit
[To complete: ...]placeholders rather than inventing facts - Information-gap-first workflow that prevents low-context requests from producing misleading handover documents
- Structured status taxonomy for active work: in progress, blocked, and not started
- Recurring-task tracking with both previous and next execution times plus operational dependencies
- Privacy-aware permission documentation that records transfer routes without storing passwords
- Sensitivity gate that stops generation when confidential content has not been desensitized
- Deadline-aware transition planning that replaces default assumptions with the user’s actual timeline
- Final self-check for section completeness, hidden-knowledge coverage, credential exclusion, and sensitive-data handling
- Optional incremental handover storage under
handover/for follow-up completion across sessions
SKILL.md
Loading
Related Openclaw Skills
Client Follow-up Plan
Convert client meeting notes, chat excerpts, and visit records into a structured, evidence-based follow-up plan with owners, deadlines, risks, and completion criteria.
Zhongkui Guard
Zhongkui Guard scans AI-related content for suspicious commands, redacts sensitive data, and evaluates configured model APIs with evidence-based reports.
AI Web Check
AI Web Check performs an evidence-first, non-mutating assessment of website usability and agent readiness.
Hermes Browser on Fedora Atomic
A practical troubleshooting and configuration skill that makes Hermes browser automation reliable on Fedora Atomic and bootc systems.
PDF Summary and Translation Install Check
A reliable preflight and dependency installer for PDF OCR, summarization, translation, and rendering pipelines.
Grilling
Grilling relentlessly stress-tests a plan, decision, or idea through structured, round-based questioning until every assumption is resolved.
Featured*
