How do I install the Cgpt Backup skill?

Run npx skillmds@latest add pvsundar/cgpt-backup 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.

Is Cgpt Backup safe to use?

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.

Which AI agents work with Cgpt Backup?

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.

Is Cgpt Backup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cgpt Backup?

pvsundar (@pvsundar) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cgpt Backup by pvsundar — Agent Skill

Name: Cgpt Backup
Author: pvsundar

Cgpt Backup

Create timestamped backup copies of important files or folders before editing, formatting, bulk replacement, risky automation, or user-requested backup work. Use when the user says backup, create a checkpoint, copy before editing, preserve the current version, or when a MEMORY/HANDOFF note marks a file as frozen or critical.

pvsundar Updated Sep 21, 2026

File contents

CGPT Backup

Use this skill before changing anything that needs a recoverable checkpoint: manuscripts, submission packages, decks, reports, data files, app configs, or entire project folders.

Workflow

Identify the exact source path.
- Prefer -LiteralPath on Windows.
- If the user did not name a path, inspect the active project context and ask only if multiple targets are plausible.
Choose the backup location.
- Default: same parent folder as the original.
- File pattern: <stem>_backup_YYYY-MM-DD<ext>.
- Directory pattern: <name>_backup_YYYY-MM-DD.
- If that name exists, append _2, _3, etc.
Create the backup.
- Use scripts/make_backup.py when available.
- Otherwise use native PowerShell copy commands end to end.
- Do not use Git as a substitute for a requested backup.
Verify before continuing.
- Confirm the destination exists.
- Confirm file size matches for a single file.
- For directories, confirm recursive file count and total bytes are nonzero.
Report the result.
- Include the original path, backup path, size, and whether verification passed.

Rules

Never edit the backup after creating it.
Never delete old backups unless the user explicitly asks.
Do not overwrite an existing backup.
When backing up before edits, finish the backup first, then make the requested edits.
If the source is inside a Git repo, do not treat a dirty worktree as a blocker; just report it if relevant.

Helper Script

Run from PowerShell:

python C:\Users\sundar\.codex\skills\cgpt-backup\scripts\make_backup.py --source "C:\path\to\file-or-folder"

Optional destination parent:

python C:\Users\sundar\.codex\skills\cgpt-backup\scripts\make_backup.py --source "C:\path\to\file.docx" --dest-dir "C:\path\to\backups"

---name: cgpt-backupdescription: Create timestamped backup copies of important files or folders before editing, formatting, bulk replacement, risky automation, or user-requested backup work. Use when the user says backup, create a checkpoint, copy before editing, preserve the current version, or when a MEMORY/HANDOFF note marks a file as frozen or critical.---# CGPT BackupUse this skill before changing anything that needs a recoverable checkpoint: manuscripts, submission packages, decks, reports, data files, app configs, or entire project folders.## Workflow1. Identify the exact source path. - Prefer `-LiteralPath` on Windows. - If the user did not name a path, inspect the active project context and ask only if multiple targets are plausible.2. Choose the backup location. - Default: same parent folder as the original. - File pattern: `<stem>_backup_YYYY-MM-DD<ext>`. - Directory pattern: `<name>_backup_YYYY-MM-DD`. - If that name exists, append `_2`, `_3`, etc.3. Create the backup. - Use `scripts/make_backup.py` when available. - Otherwise use native PowerShell copy commands end to end. - Do not use Git as a substitute for a requested backup.4. Verify before continuing. - Confirm the destination exists. - Confirm file size matches for a single file. - For directories, confirm recursive file count and total bytes are nonzero.5. Report the result. - Include the original path, backup path, size, and whether verification passed.## Rules- Never edit the backup after creating it.- Never delete old backups unless the user explicitly asks.- Do not overwrite an existing backup.- When backing up before edits, finish the backup first, then make the requested edits.- If the source is inside a Git repo, do not treat a dirty worktree as a blocker; just report it if relevant.## Helper ScriptRun from PowerShell:```powershellpython C:\Users\sundar\.codex\skills\cgpt-backup\scripts\make_backup.py --source "C:\path\to\file-or-folder"```Optional destination parent:```powershellpython C:\Users\sundar\.codex\skills\cgpt-backup\scripts\make_backup.py --source "C:\path\to\file.docx" --dest-dir "C:\path\to\backups"```

Frequently asked questions