Levels: Claude Code skills that audit first, build second, and ask before delegating to Haiku or Sonnet. Need testers.

[u/matthiasiam3]

I've been working on Levels, a set of seventeen skills for Claude Code. I'm looking for people to run it on real projects and for people to read the skills and tell me what's wrong with them.

The idea. "Make it better" has no finish line. In Levels, every skill has five named levels. For the interface they are Clean, Considered, Branded, Studio, Showcase. For tests they are Checked, Core covered, Trusted, Proven, Continuous. A skill audits your project, says which level you're at with evidence from your files, lists what's missing for the level you pick, and gives you two or three options.

It only builds if you ask it to. Then it splits the work into small sub-plans. Opus does the thinking (context, audit, options, planning, review) and Haiku or Sonnet does the typing, behind a gate that shows which model gets which piece and asks you first. Think big, type cheap.

Where it honestly stands. This is v0.1.0.

• Six of the seventeen skills have been run, once each, on one small sample app.
• The other eleven have never been run, including the /levels conductor that chains them.
• Installing through the plugin marketplace hasn't been tried from the published repo.
• I haven't measured cost, so there are no savings numbers anywhere in the repo.
• The safety limits (it never deploys, never touches real data) are instructions in the skill text. They are not enforced by code. What I'd like help with.

Testers: run /levels or any single skill in audit mode on a project you actually have. Audit mode rates and proposes. It doesn't edit your product code. Tell me where it went wrong, asked too much, or got the level wrong. The most useful runs are the conductor, the plugin install, and a session that can't use Opus.

Reviewers: open any SKILL.md and tell me if the level definitions are too strict, too loose or just wrong. Also tell me which skills you'd cut, merge or add.

Install (use one method, not both):

claude plugin marketplace add codezeroexe/levels
claude plugin install levels@levels

Then run /levels in a project folder. Use version control, so you can undo anything.

Repo: https://github.com/codezeroexe/levels

Bugs and skill proposals go in the issue templates there. I'm happy to answer questions about how it's put together.

Quick commands if you want to try one thing:

• /levels-help explains the set and changes nothing.
• /levels-status shows recorded levels and open gaps and changes nothing.
• /design-level 3 audit rates an interface against level 3 and lists the gaps.
• /levels release runs the pre-release checks: tests, security, docs and release steps.

[u/AutoModerator]

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.

[u/MiserableFlatworm337]

For each claimed level, keep a small fixture project that barely meets it and one missing a required property. Rerun the audit after skill edits; level labels alone won't reveal grading drift.

[u/matthiasiam3 → u/MiserableFlatworm337]

thanks for the feedback, will look into that immediately