Is my understanding correct that the "skill creator" skill from Claude, cannot be edited by the user?

[imex-git]

It just says "skill name already in use", whereas for other skills, it gives me an option to update.

Also, when new versions of the system plugins come out, for e.g. Claude recently launched a new version of the skill-creator plugin, does claude automatically update them? If so, how does that impact your customizations?

Thanks

[mj-deving]

Short answer: you can't edit the bundled one, but you can override it completely. And no, updates won't touch your override.

Why you're hitting "skill name already in use"

The skill creator ships inside Claude Code's plugin-dev bundled plugin. Bundled skills are read-only — they're baked into the binary. That's why you get the "already in use" error instead of the update prompt you see with your own skills. This is intentional, not a bug.

The override trick

Claude Code resolves skills with a priority chain:

1. Enterprise settings (if your org has them)
2. ~/.claude/skills/<name>/SKILL.md — personal, all projects
3. .claude/skills/<name>/SKILL.md — project-level, this repo only
4. Plugin skills (namespaced like plugin:skill)
5. Bundled skills (lowest priority)

Personal beats bundled. So if you create a skill with the same name at ~/.claude/skills/skill-creator/SKILL.md, yours wins. The bundled one still exists, it just never gets loaded.

mkdir -p ~/.claude/skills/skill-creator

Then write your own SKILL.md with whatever conventions you want:

---
name: skill-creator
description: Create and scaffold new Claude Code skills with custom conventions.
---

# My Skill Creator

When creating skills, follow these rules:
- Always include a description with trigger phrases
- Keep SKILL.md under 500 lines, move details to references/
- Use imperative voice
- (your rules here)

Now /skill-creator loads your version instead of the bundled one.

On updates

When Claude Code updates, only the bundled skill-creator changes. Your personal skills in ~/.claude/skills/ are never touched — they're your files on your filesystem. And since personal skills have higher priority, your override keeps winning even after the bundled version updates underneath it.

So: no, you don't lose customizations on update.

Frontmatter fields you can use

Since you're customizing the creator, here's what you can put in the frontmatter — some of these aren't obvious from the docs:

Field	What it does
name	The /slash-command name. Lowercase + hyphens.
description	How Claude decides when to auto-trigger. Front-load keywords.
disable-model-invocation	true = only manual /slash invocation, Claude won't auto-trigger.
user-invocable	false = hidden from / menu, only Claude invokes it internally.
allowed-tools	Pre-approve tools so Claude doesn't ask permission during the skill.
context	fork = runs in an isolated subagent (good for heavy skills).
agent	Which subagent type (Explore, Plan, etc.) when forked.
model	Override which model runs this skill.
paths	Glob patterns — only auto-trigger when working in matching paths.

I run about 30 custom skills myself. The override pattern works reliably — been doing it since skills shipped.

[imex-git]

Thanks, that is very helpful. two quick follow-ups:

1. How do you track and use updates to the original "skill-creator".
2. I notice that the original "skills creator" does not show a last updated date in the customize tab (co-work), so wonder how do you track when it was last updated?