Generic guide for transferring project context and access without platform lock-in. Helps collaborators find code, data boundaries, and environment setup.
When to use
Handing work to another developer or agent session
Documenting where artifacts live (git, cloud, local)
Reducing "where do I start?" friction
When not to use
Security access reviews (use team IAM process)
Partner data agreements (use ds-partner-boundaries if available)
Handoff checklist
Code
Repo URL and default branch
Open PRs or WIP branches named
How to run tests and dev server
Access
Required accounts (CI, cloud, analytics) listed by name
Never paste tokens, passwords, or private URLs with embedded secrets
Use team secret managers for credential transfer
Related skills
interview-me — clarify recipient needs
dynamic-config-management — env documentation
verify-before-done — confirm handoff recipient can run project
Clean-room generic handoff workflow.
1---2name: work-access-handoff-23description: Work Access Handoff4---56# Work Access Handoff78Generic guide for transferring project context and access without platform lock-in. Helps collaborators find code, data boundaries, and environment setup.910## When to use1112- Handing work to another developer or agent session13- Documenting where artifacts live (git, cloud, local)14- Reducing "where do I start?" friction1516## When not to use1718- Security access reviews (use team IAM process)19- Partner data agreements (use `ds-partner-boundaries` if available)2021## Handoff checklist2223### Code2425- [ ] Repo URL and default branch26- [ ] Open PRs or WIP branches named27- [ ] How to run tests and dev server2829### Access3031- [ ] Required accounts (CI, cloud, analytics) listed by name32- [ ] Who grants access; no credentials in chat or repo33- [ ] `.env.example` documents required vars3435### Artifacts3637- [ ] Spec, ADR, or ticket links38- [ ] Model artifacts location (if ML)39- [ ] Design/mockup links4041### State4243- [ ] What is done vs in progress vs blocked44- [ ] Known risks and decisions already made45- [ ] Next recommended action4647## Handoff note template4849```markdown50## Handoff: [project/feature]51- **Repo:**52- **Branch/PR:**53- **Run locally:**54- **Access needed:** (request from X)55- **Key paths:**56- **Status:**57- **Next steps:**58```5960## Safety6162- Never paste tokens, passwords, or private URLs with embedded secrets63- Use team secret managers for credential transfer6465## Related skills6667- `interview-me` — clarify recipient needs68- `dynamic-config-management` — env documentation69- `verify-before-done` — confirm handoff recipient can run project7071*Clean-room generic handoff workflow.*
Run npx skillmds@latest add charlieviettq/work-access-handoff-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Work Access Handoff It is listed under Productivity on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
charlieviettq (@charlieviettq) published this skill. Their other Agent Skills are listed on their SkillMD profile.
charlieviettq