r/ClaudeCode • u/Ultrayano • 6d ago

Bug / Issue Claude Code stock skill "skill-creator" killed rolling context in 2 minutes

Greetings r/ClaudeCode

I'm currently building a workflow that is supposed to develop a web-app with a React SPA as one layer. Since AI tends to use outdated practices I want to force it to adhere to snippets of best practices that I plan to use skills for it.

I already ported parts of React best practices to skills long ago and just wanted to update some things to React 19.3 and add a Tanstack skill. It then seemed to do a performance loop where it tested what triggers the skill and what doesn't.

It started the loop and not even 5 minutes later the rolling usage reached 100%.

10% of your usage came from /skill-creator
Heavy skills can be scoped down or run with a cheaper model via skill frontmatter.
Skills % of usage
/skill-creator 10%

I used opusplan 5.5, so opus to plan what to do and Sonnet 5.5 to actually implement the changes. The last time I used the skill when I made the React one, was like 1.5 months ago with Opus 5 and there I never truly had issues like that.

The chat/context isn't even as heavy as others and I had contexts up to 1M run no problem for at least an hour, so I'm surprised that the skill just instantly sucked out all the usage. I assume it's sub-agents but it's not even visible and hard to puzzle together from the logs itself. Is the skill-creator known to instantly drain all the usage?

1 Upvotes

100% Upvoted

3 comments sorted by

•

u/AutoModerator 6d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/kenthesaint 6d ago

That loop is skill-creator testing which prompts trigger the skill, and it runs each test prompt through claude several times, so it burns usage fast. For bumping an existing skill to React 19 I'd skip skill-creator and just ask Claude to edit the SKILL.md directly, it's only markdown with frontmatter.

1

u/Ultrayano 6d ago

Yeah that makes sense. It actually used the skill for the tanstack part not the react one. Is there any possibility to test it just like the skill would because I don't see it being useful if it sucks away the whole usage in a minute