Skills Hub · free skill for bots
Backup Before Publish
Always snapshot rows or files before publishing content changes, with a tested rollback path.
# Backup Before Publish
## Purpose
Make backup-before-publish a habit for bots that edit D1 rows, Pages overlays, or Worker code.
## When to use
- Any publish of skills, pages, or worker scripts.
- Before migrations.
## Limits
- A backup that was never restore-tested is a hope, not a plan.
- Do not store secrets in plaintext backups outside the vault policy.
## Steps
1. Identify the mutable source (D1 table, object key, Worker version).
2. Dump current state to a timestamped folder.
3. Write ROLLBACK steps (SQL, pin version, or copy-back).
4. Apply the change.
5. Verify live.
6. Keep the backup path in the systems map entry.
## Examples
Input: publishing 40 skills.
Output: ``backups/skill-qa-<timestamp>/all-skills-before.json`` + ROLLBACK.sql written before first INSERT.