{"skill":{"slug":"metadata-naming","displayName":"Metadata Naming","summary":"Define, apply, or review a reusable metadata-based filename standard for files, folders, inventories, archives, and generated catalogs. Use when the user wan...","description":"---\nname: metadata-naming\ndescription: Define, apply, or review a reusable metadata-based filename standard for files, folders, inventories, archives, and generated catalogs. Use when the user wants to extract a naming convention into a standard, normalize filenames, choose between human-readable and machine-friendly naming, or create naming rules for repositories, skills, software inventories, snapshots, and long-lived records.\n---\n\n# Metadata Naming\n\nTurn loose filename habits into a stable naming standard that is easy to read, sort, parse, and reuse.\n\n## Use This Standard\n\nFollow this split by file purpose:\n- Use stable identity naming for long-lived entries that are updated in place.\n- Use timestamp naming for snapshots, archives, exports, and reports.\n- Prefer ASCII, no spaces, and fixed separator rules when filenames will be processed by scripts or moved across systems.\n\n## Core Metadata Blocks\n\nUse these blocks in a fixed order when a filename needs richer metadata:\n- time\n- prefix\n- title\n- version\n- tags\n- source_or_author\n- note\n\nNot every block is required. Keep only the fields that improve retrieval or automation.\n\n## Two Modes\n\n### Relaxed mode\n\nUse for human-managed documents where readability matters more than strict parsing.\n\nConventions:\n- Chinese or mixed-language titles are allowed.\n- Spaces are allowed when the surrounding system tolerates them.\n- Typical visual markers:\n  - time: `(2026-03-11)` or `(20260311-093500)`\n  - version: `(v1.2.0)`\n  - tags: `#tag`\n  - source or author: `@name`\n  - note: `&note`\n\nExample:\n```text\n(2026-03-11)Favorites Curator(v0.1.0)#skill#favorites@workspace&initial publish\n```\n\n### Strict mode\n\nUse by default for standards, skills, inventories, generated files, syncable folders, and anything a script will read.\n\nConventions:\n- ASCII only\n- no spaces\n- top-level separator: `__`\n- intra-block separator: `-` or `.`\n- lowercase slug-style titles unless there is a strong reason not to\n\nGeneral template:\n```text\nYYYYMMDD[-HHMMSS]__prefix__title__version__tags__source__note.ext\n```\n\nExamples:\n```text\n20260311__skill__favorites-curator__v0.1.0__favorites.catalog__workspace.md\n20260311__repo__openclaw-backup-tool__v0.1.0__backup.tool__github.md\n20260311__app__codex__v0.112.0__cli.ai__brew.md\n```\n\n## Default Rule For Long-Lived Entries\n\nFor catalogs, inventories, and canonical records, prefer stable filenames over timestamped filenames.\n\nUse this template:\n```text\n<data_type>__<source_name>__<slug>.md\n```\n\nExamples:\n```text\nskill__workspace__favorites-curator.md\nrepo__github__openclaw-backup-tool.md\napp__brew__codex.md\n```\n\nUse this rule when the content is refreshed in place and the filename should not drift over time.\n\n## Default Rule For Snapshots And Reports\n\nUse timestamp-first filenames for time-series artifacts.\n\nTemplates:\n```text\nYYYYMMDD__report__topic.md\nYYYYMMDD-HHMMSS__snapshot__topic.json\n```\n\nExamples:\n```text\n20260311__report__favorites-digest.md\n20260311-095914__snapshot__favorites.json\n```\n\n## Block Rules\n\n### Time\n- Use `YYYYMMDD` for day-level tracking.\n- Use `YYYYMMDD-HHMMSS` for run-level uniqueness.\n- Put time first when sort order matters.\n\n### Prefix\n- Use short taxonomy values such as `repo`, `skill`, `app`, `doc`, `snapshot`, `report`.\n- Keep the vocabulary stable once chosen.\n\n### Title\n- Make this the main identity.\n- Prefer short, stable, searchable slugs.\n- Move extra description into tags or notes.\n\n### Version\n- Use semver when available: `v0.1.0`, `v2.3.4`.\n- Omit the block when versioning is irrelevant.\n\n### Tags\n- Use compact, low-noise tags.\n- Join multiple tags with `.` or `-` inside the same block.\n\n### Source Or Author\n- Use the source system, publisher, owner, or author when it improves retrieval.\n- Examples: `github`, `brew`, `workspace`, `openclaw`, `vendor-name`.\n\n### Note\n- Keep it short.\n- Do not put long prose into filenames.\n- Use only when the note materially changes retrieval value.\n\n## Standard Principle\n\nUse fixed-order metadata blocks. Use stable identity filenames for long-lived entries and timestamped filenames for snapshots. Default to ASCII, no spaces, `__` between blocks, and `-` or `.` inside blocks so names stay sortable, parseable, and portable.\n\n## References\n\nRead `references/standard.md` when you need the normalized standard, examples, and decision rules in a reference-friendly format.\n","tags":{"latest":"0.1.0"},"stats":{"comments":0,"downloads":540,"installsAllTime":20,"installsCurrent":1,"stars":0,"versions":1},"createdAt":1773292800000,"updatedAt":1778491848315},"latestVersion":{"version":"0.1.0","createdAt":1773292800000,"changelog":"Initial publish","license":"MIT-0"},"metadata":null,"owner":{"handle":"luw2007","userId":"s179d7fsn1et1b9mz7ef9cez8583zwf0","displayName":"luw2007","image":"https://avatars.githubusercontent.com/u/1415541?v=4"},"moderation":null}