shadow-handover
Skill1 starsChanged yesterdayMITView on GitHub
Client Project Delivery & Handover. Use when preparing BAST (Berita Acara Serah Terima), source/SBOM inventory, credential transfer, Admin/Operator/User manuals, and Training of Trainers (ToT). Do NOT use for AI session memory handoff (/handoff).
- Reads credentials
In this repository51 other files it gives its agents.
- antislop-codeSkill
- antislop-copywritingSkill
- antislop-humanSkill
- antislop-layoutmobileSkill
- antislopSkill
- antislop-uiSkill
- context7Skill
- handoffSkill
- shadow-accessibilitySkill
- shadow-apiSkill
- shadow-architectSkill
- shadow-authSkill
- shadow-bootstrapSkill
- shadow-browserSkill
- shadow-cacheSkill
- shadow-compatSkill
- shadow-concurrencySkill
- shadow-dataSkill
- shadow-dbSkill
- shadow-debugSkill
- shadow-designSkill
- shadow-discoverySkill
- shadow-docSkill
- shadow-domainSkill
- shadow-eaSkill
- shadow-evalSkill
- shadow-finopsSkill
- shadow-gitSkill
- shadow-grcSkill
- shadow-integrateSkill
- shadow-maintainSkill
- shadow-mobileSkill
- shadow-modernizeSkill
- shadow-monarchSkill
- shadow-observeSkill
- shadow-opsSkill
- shadow-perfSkill
- shadow-planSkill
- shadow-pmoSkill
- shadow-presalesSkill
- shadow-privacySkill
- shadow-qualitySkill
- shadow-realtimeSkill
- shadow-refactorSkill
- shadow-releaseSkill
- shadow-resilienceSkill
- shadow-searchSkill
- shadow-secSkill
- shadow-supplychainSkill
- shadow-testSkill
- shadow-uatSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
When preparing a project for final client handover / BAST (Berita Acara Serah Terima), verify and generate all 7 packages (using …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Shadow Handover (/shadow-handover) — Client System Delivery, BAST & Operational Independence
[!IMPORTANT] Distinction of Purpose:
/handoff= Transfers AI agent session context when conversation memory is full./shadow-handover= Transfers the completed software system, documentation, credentials, and operational ownership to the client/employer so they can run and maintain the system independently.
1. The 7 Mandatory Client Handover Deliverables (Gate 8)
When preparing a project for final client handover / BAST (Berita Acara Serah Terima), verify and generate all 7 packages (using /shadow-doc for .docx/.xlsx/.pdf outputs):
1. Berita Acara Serah Terima (BAST) & Deliverable Checklist
- Formal handover document mapping every contract scope item (KAK/TOR/SPK) to its verified deliverable artifact, UAT sign-off reference (
/shadow-uat), and repository/archive location.
2. Source Code & Technical Asset Inventory
- Clean repository state (
git statusclean, release tagv1.0.0created, zero dead files or temporary debug scripts). - Complete inventory table of:
- Source code repositories (Frontend, Backend, Mobile, ETL/Warehouse scripts, Infrastructure/Docker configs).
- Database schema (
schema.dbml,ERD.md, migration files, and reference seed scripts from/shadow-db&/shadow-data). - API specifications (
openapi.yamlandpostman_collection.jsonfrom/shadow-api). - Third-party licenses & SBOM (Software Bill of Materials) confirming zero prohibited/unlicensed dependencies.
3. Secure Credential & Secret Transfer Protocol
- NEVER put plain-text production passwords or private keys inside
.docxreports, Git repos, or unencrypted emails/chats! - Deliver a Credential Inventory Matrix listing what credentials exist (Server SSH, DB Admin, DB Read-Only, Redis, S3/MinIO, SMTP, Payment Gateway, Domain/DNS, SSL) and where they are stored (Password Manager Vault / Encrypted
.kdbx/ Secret Manager), along with instructions for the client's IT team to rotate passwords upon receipt.
4. System Administrator & DevOps Runbook (Buku Panduan Administrator / Teknis)
Step-by-step copy-pasteable guide enabling a new sysadmin/developer to operate the system without the original author:
- Server topology, IP/Port matrix, and firewall rules.
- Fresh installation & deployment commands (
docker compose,systemd,nginx,.env.exampleexplanation). - How to check service status, view logs, restart services, run database migrations, and trigger/restore backups (
/shadow-ops&/shadow-resilience). - Troubleshooting decision tree for common operational issues (
502 Bad Gateway, disk full, expired SSL, locked user account).
5. End-User & Operator Manual (Buku Panduan Pengguna / Manual Book)
Task-oriented guide grouped by User Role (Operator, Verifikator, Pimpinan, Admin):
- Numbered step-by-step workflows accompanied by real annotated application screenshots (
bukti/*.png). - FAQ and common validation error explanations in plain Bahasa Indonesia.
6. Training & Knowledge Transfer (ToT) Package
- Training agenda, attendance/BA Pelatihan template, and hands-on training scenarios for Operators and IT Administrators.
7. Warranty / Masa Pemeliharaan (Garansi) Handover Checklist
- Support escalation contacts, SLA response tiers (
/shadow-maintain), and scope boundaries distinguishing Warranty Bug Fixes (Covered) from New Feature Requests (Out of Warranty Scope).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

