kookr-skill-naming-conventionlisted

# Kookr skill + agent naming + placement convention ## When to use - Creating a new skill or agent in the Kookr repo. - Promoting a skill/agent from `.claude/` to `plugin/` (or the reverse). - Renaming an existing artifact that violates the convention below. - Reviewing a PR that adds or renames a skill or agent. ## The two locations ``` ~/git/kookr/ ├── .claude/ │ ├── skills/ ← KOOKR REPO-LOCAL skills: dirs MUST start with `kookr-` │ └── agents/ ← KOOKR REPO-LOCAL agents: files MUST start with `kookr-` └── plugin/ ├── skills/ ← DISTRIBUTED skills for plugin-backed agents in any cwd └── agents/ ← DISTRIBUTED agents for plugin-backed agents in any cwd ``` `.claude/` artifacts are invisible to other projects — they only load when Claude Code is opened inside `$HOME/git/kookr/`. Use this tier only for skills and agents whose natural working directory is the Kookr repository itself: editing Kookr source, maintaining Kookr tests, or inspecting Kookr repo-local state. `plugin/` is the distributed Kookr Toolkit. Kookr injects it into spawned agents regardless of cwd, and non-spawned Claude Code sessions can also see it when the plugin is installed or synced into Claude's skill/plugin directories. It is the right home for both: - Kookr-specific operational skills that agents need while working in other repositories, such as spawning, supervising, or coordinating Kookr tasks. - General-purpose engineering skills that are useful