Archive metadata
Read and validate metadata on an archive document. Use when checking, fixing, or reporting on metadata fields.From its SKILL.md
npx -y skills add m4tice/the-archive --skill archive-metadataAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, 419 tokens by cl100k_base, as published. Nobody here has run it
Archive Metadata
Purpose
Read, validate, and correct metadata on an existing archive document. Ensure ID format matches the document's category directory.
ID System (5-digit format: XNNNN)
| Prefix | Category | Directory |
|---|---|---|
| 1 | Policy | /archive/design |
| 2 | Projects | /archive/projects |
| 3 | Academic | /archive/academic |
| 4 | Technical | /archive/technical |
| 5 | Personal Interests | /archive/personal-interests |
Procedure
- Open the target document in
/archive/<category>/slug.md. - Parse metadata fields in fixed order as bold inline fields:
**ID:**,**Title:**,**Author:**,**Date:**,**Tags:**. - Validate ID format:
- Must be 5 digits (XNNNN, e.g., 10001, 20001, 40001).
- ID prefix (first digit) must match the document's category:
- 1xxxx → must be in
/archive/design - 2xxxx → must be in
/archive/projects - 3xxxx → must be in
/archive/academic - 4xxxx → must be in
/archive/technical - 5xxxx → must be in
/archive/personal-interests
- 1xxxx → must be in
- Report any missing or malformed fields:
- Missing metadata fields
- ID format violations (not 5 digits or prefix mismatch)
- Invalid date format (should be YYYY-MM-DD)
- Offer corrections if needed — only modify these metadata lines, never the document body.
Constraints
- Never modify the document body when fixing metadata.
- Metadata lines must appear in fixed order at the top of the file, using bold inline labels (not YAML frontmatter).
- ID corrections should reassign based on category if the prefix doesn't match the current directory.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most docs writing skills give in 419 tokens
Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-07
- Announce the skill at startin 54 of 1637, across 26 files
- Convert legacy doc files before editingin 45 of 1637, across 7 files
- Predict questions readers might askin 42 of 1637, across 4 files
- Generate clarifying questions for initial contextin 42 of 1637, across 3 files
- Create document scaffold with placeholder textin 42 of 1637, across 3 files
- Brainstorm content options for each sectionin 42 of 1637, across 3 files
- Test the document with a fresh context-less instancein 42 of 1637, across 3 files
- Include exact file paths in every taskin 42 of 1637, across 15 files
- Ask interview questions one at a timein 42 of 1637, across 27 files
- Apply surgical edits during refinementin 41 of 1637, across 2 files
- Offer structured workflow or freeformin 40 of 1637, across 1 file
- Ask for document meta-contextin 40 of 1637, across 2 files
Said here and by no other author read
- parse metadata fields in fixed order
- validate ID prefix matches document category
- offer metadata corrections when needed
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.