package-backup
Skill1 starsChanged 5 months agoMITView on GitHub
Use when the user asks to package, back up, zip, restore, unzip, extract, or otherwise handle packaging and extraction with the package_backup.sh contract.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- backend-reliability-guidelinesSkill
- code-review-specSkill
- commitSkill
- dddSkill
- development-workflowSkill
- frontend-interaction-guidelinesSkill
- logging-boundariesSkill
- product-managerSkill
- story-lineSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read and follow this reference before performing any package or restore action:
- Distinctive: line 21
Treat the reference as mandatory before choosing archive names or running commands.
- Distinctive: line 22
Follow the script contract for backup naming, restore validation, and path safety.
- Distinctive: line 23
Do not invent alternate archive rules when this skill is triggered.
- Distinctive: line 24
If the reference cannot be read, stop and report that archive rules are unavailable.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Package Backup
This skill is a thin pointer to the repository's archive contract.
Canonical Source
Read and follow this reference before performing any package or restore action:
package-backup/references/package_backup.md
The reference is the local source of truth for behavior derived from
/Users/lvdaxianer/Downloads/shell-main/package_backup.sh.
Required Behavior
- Treat the reference as mandatory before choosing archive names or running commands.
- Follow the script contract for backup naming, restore validation, and path safety.
- Do not invent alternate archive rules when this skill is triggered.
- If the reference cannot be read, stop and report that archive rules are unavailable.
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.

