vault: session notes 2026-07-04

cc-os-plugin-skill-naming-convention.md

@@ -8,7 +8,7 @@ tags:
   - project/cc-os
   - tool/claude-code
 scope: global
-last_updated: 2026-07-02
+last_updated: 2026-07-04
 date: 2026-07-02
 related:
   - vault-conventions
@@ -41,6 +41,18 @@ This convention ensures that cc-os plugins and skills are named consistently, un
 
 **Invocation readability: `/os-vault:query [tag]`** → "query the vault using a tag." `/os-vault:onboard-project`→ "onboard this project to the vault graph." The pattern reads naturally without requiring context.
 
+## Registration Mechanics (Claude Code)
+
+**Do NOT set a `name:` field in SKILL.md frontmatter.** The skill's directory name is the skill
+name, and Claude Code registers the slash command as the namespaced `/plugin:skill` form when
+`name:` is absent. Setting `name: find` explicitly overrides the registered command to the bare,
+unnamespaced `/find` — ambiguous in the command palette and inconsistent with sibling plugins.
+Discovered 2026-07-04: os-adr and os-doc-hygiene had explicit `name:` fields and registered as
+`/find`, `/check`, etc., while os-vault (no `name:` fields) correctly registered as
+`/os-vault:query`. Fixed by deleting the `name:` lines. After any SKILL.md edit, refresh the
+plugin cache (`cc-os/bin/refresh-plugins`) — installs copy files into
+`~/.claude/plugins/cache/`, so source edits don't reach sessions until refreshed.
+
 ## Anti-Patterns
 
 - **Plugin name without prefix** — `vault` instead of `os-vault` — loses the visual cc-os affiliation and risks collision with other tools that might use `vault` as a name.

journal/2026-07-04.md

@@ -359,3 +359,10 @@ tags: [scope/global, type/log]
 **Reason:** other
 **Vault notes touched:**
 (none)
+
+## Session — 2026-07-04T16:55:30Z
+
+**Project:** /tmp/adr-eval-b-grid-rerun/W2-haiku-r1
+**Reason:** other
+**Vault notes touched:**
+(none)