Offered by Dead Brands
Every saved snapshot findable later — one naming pattern, one index, no more lost zips.
Use it over MCP: connect to https://mcp.deadbrands.co/hub/mcp and call skills_get with slug archival-snapshot-naming.
# Archival Snapshot Naming
## Purpose
Concrete use case — Used by: the archivist bot. Task: name and index archival snapshots — zips, reports, and fix waves dropped for the team — so that any file can be found months later from its name alone, without opening it. A snapshot with a vague name ('fixes.zip', 'final2.zip') is a snapshot lost: the team redoes work it already did because nobody can prove the file exists. The skill's product is not the file, it is the findability of the file: name, date, contents, and index line, all consistent.
## Superpower
Every saved snapshot findable later — one naming pattern, one index, no more lost zips.
## When to use
- Whenever a snapshot, zip, report, or fix wave is archived for the team.
- When tidying an archive folder, to rename and index what is already there.
## When NOT to use
- Do not rename a file the team is currently using without telling its owner, and do not delete an old snapshot to make room.
- Do not use it to hide or bury a snapshot that corrects an earlier one; corrections are indexed beside the original.
## Tools & APIs
The archive folder and its existing files (existing, real); the team's naming pattern as already used (date, topic, version). No new tool is required; the index file is the working artifact.
## Inputs
The snapshot file; its date, topic, and version; its contents summary; the archive folder's existing index, if one exists.
## Outputs
A renamed file following the pattern (date-topic-version), an index line naming its contents, and a confirmation that the old name still resolves (a note, not a duplicate file).
## Example invocation
> "Name and index today's fix-wave zip: apply the date-topic-version pattern, write its index line with contents, and confirm the team's old reference still resolves."
## Steps
1. Read the snapshot's contents summary: what it is, its date, and its version.
2. Apply the naming pattern (date, topic, version) and check the name against the existing index for collisions.
3. Rename the file, and note the old name in the index line so old references still resolve.
4. Write the index line: new name, date, contents, and who it is for.
5. Confirm the file opens under its new name and the index line matches it.
## Safety limits
Never delete an old snapshot to make room, and never rename a file in active use without telling its owner. Never bury a correction: corrections are indexed beside the original, not over it. No credentials or personal data are involved. Bots and house archives only.
## Failure modes
- **Name collision:** two snapshots get the same name and one overwrites the other. Mitigation: the index is checked before any rename.
- **Broken references:** a rename orphans every note that cited the old name. Mitigation: old names are recorded in the index line.
- **Buried corrections:** a fixed version hides the original it corrects. Mitigation: corrections are indexed beside, never over, the original.
## Test checklist
- [ ] Every archived file follows the date-topic-version pattern.
- [ ] Every index line names the file's contents and its audience.
- [ ] Old names are recorded so old references still resolve.
- [ ] No snapshot was deleted or buried by this skill.
---
*Trademarks and copyrights mentioned belong to their respective owners. Educational reference only; not affiliated with or endorsed by them.*