Bug Description
The skill-creator skill hardcodes author: gentleman-programming in its template and documentation, which causes every skill created by any user to be attributed to gentleman-programming instead of the actual author.
This means that when a user creates skills using the skill-creator, all their skills end up with someone else's name in the metadata.author field.
Where the problem is
The file skills/skill-creator/SKILL.md has the hardcoded author in three places:
1. The skill's own frontmatter (line ~8)
metadata:
author: gentleman-programming
version: "1.0"
2. The SKILL.md template shown to the AI (line ~52)
metadata:
author: gentleman-programming
version: "1.0"
3. The Frontmatter Fields documentation table (line ~114)
| `metadata.author` | Yes | `gentleman-programming` |
Impact
When the AI uses this skill to create new skills for a user, it copies the template verbatim and sets author: gentleman-programming in every generated skill. The user doesn't notice until they review the frontmatter later — by that point they may have dozens of skills with the wrong author.
In my case, I had 17 skills all attributed to gentleman-programming before I noticed and had to batch-replace them.
Suggested fix
The template should not hardcode an author name. Options:
Option A: Use a placeholder
metadata:
author: "{your-github-username}"
version: "1.0"
Option B: Instruct the AI to ask or infer
Add a note in the skill-creator instructions like:
"The metadata.author field should be set to the user's name or GitHub username. Ask the user if not known, or infer from git config or system username."
Option C: Use a variable reference
metadata:
author: $USER # or infer from git config user.name
Reproduction
- Use the
skill-creator skill to create any new skill
- Check the generated
SKILL.md frontmatter
- Observe
author: gentleman-programming regardless of who is creating the skill
Environment
- Claude Code (claude-opus-4-6 1M context)
- macOS Darwin 25.3.0
- Skills installed at
~/.claude/skills/
Bug Description
The
skill-creatorskill hardcodesauthor: gentleman-programmingin its template and documentation, which causes every skill created by any user to be attributed togentleman-programminginstead of the actual author.This means that when a user creates skills using the skill-creator, all their skills end up with someone else's name in the
metadata.authorfield.Where the problem is
The file
skills/skill-creator/SKILL.mdhas the hardcoded author in three places:1. The skill's own frontmatter (line ~8)
2. The SKILL.md template shown to the AI (line ~52)
3. The Frontmatter Fields documentation table (line ~114)
Impact
When the AI uses this skill to create new skills for a user, it copies the template verbatim and sets
author: gentleman-programmingin every generated skill. The user doesn't notice until they review the frontmatter later — by that point they may have dozens of skills with the wrong author.In my case, I had 17 skills all attributed to
gentleman-programmingbefore I noticed and had to batch-replace them.Suggested fix
The template should not hardcode an author name. Options:
Option A: Use a placeholder
Option B: Instruct the AI to ask or infer
Add a note in the skill-creator instructions like:
Option C: Use a variable reference
Reproduction
skill-creatorskill to create any new skillSKILL.mdfrontmatterauthor: gentleman-programmingregardless of who is creating the skillEnvironment
~/.claude/skills/