docs: record skill name separator migration
Build and publish Corp v1 Board portal / build (push) Successful in 36s

This commit is contained in:
2026-09-04 13:13:46 +00:00
parent 10f3f5e669
commit 6b024593c3
@@ -0,0 +1,34 @@
---
title: Skill name separator migration
sidebar_position: 13
---
# Skill name separator migration
- **Improvement ID:** `GUILD-IMP-20260904-skill-name-separators`
- **Status:** Complete
- **Approved by:** RootAtSkic (`discord:1518725627845283888`)
- **Approval evidence:** Discord message `1545414655609016450`
- **Date:** 2026-09-04
## Decision
Corp v1 skill names use single hyphens only. Consecutive ASCII hyphens are not permitted in skill frontmatter names, installed package folders, project-adopted skill repository names, cross-skill references, automation attachments, portal records, or active channel guidance.
Project qualification now follows these forms:
```text
<source-skill>-<project-code>
corp-v1-channel-<channel>-<project-code>
```
Central examples include `corp-v1-main`, `corp-v1-guild`, `corp-v1-glossary`, and `corp-v1-presentation`.
## Applied scope
- Renamed and remotely verified 59 existing Gitea skill repositories across central Corp v1 governance and the 3D Architecture, AeroSim, E-Shop v1, and Maze Next Gen projects.
- Published the previously local-only `corp-v1-presentation` package as `home-v1-skills-code-agent/corp-v1-presentation`.
- Updated central channel references, project adoption manifests, supporting files, the active Hermes runtime packages, scheduled-job attachments and prompts, and pinned Discord guidance.
- Preserved project authorization overrides, source provenance, repository history, and inactive historical workspaces.
Legacy Gitea URLs may resolve through Gitea's rename alias, but organization repository inventories and all canonical links use the new single-hyphen names.