public-copy-durability
Installation
SKILL.md
Public copy that survives releases
Public copy splits by one question: can an agent edit it later?
| surface | editable later | what belongs there |
|---|---|---|
| Platform-locked pages: Nexus Mods, Steam, itch, CurseForge, forum posts, store listings, app descriptions | No - a human re-types it in a web form | Durable prose only. No version numbers, dates, counts, or "latest". |
| Agent-editable surfaces: GitHub README, CHANGELOG, docs, release bodies, wikis | Yes | Anything, including per-release facts |
| The platform's structured fields: version field, changelog section, release title | Yes, per release | The version number, once |
A locked page cannot be fixed by the agent that notices the staleness. Every volatile fact written there is a manual edit someone will forget, a re-upload, or a wrong number aging in public. GitHub is forgiving because an edit is one tool call; treat that as the exception, not as permission to scatter versions everywhere.
The rule
Write locked copy so it is still true after ten releases: