Free OpenClaw Config Audit
Most Claude Code setups I review are running at maybe 30% of what the platform can do. Not because people are lazy, but because the config surface area is huge and poorly documented. I know it cold.
12 Production Primitives
What I check.
These are the building blocks of a well-configured Claude Code environment. If any of them are missing or misconfigured, you're leaving performance on the table.
01CLAUDE.md structure
Is your project identity file well-organized, scoped, and actually useful to the model?
02Hook architecture
Are you using pre/post hooks to enforce standards, or relying on the model to remember?
03Skill definitions
Do you have reusable skills, or are you re-explaining workflows every session?
04Memory system
Is your memory structured and retrievable, or a graveyard of stale notes?
05Session context
Do sessions pick up where you left off, or start cold every time?
06Feature tracking
Are features and progress tracked in a structured format the agent can read?
07Model selection
Are you routing the right tasks to the right models, or burning Opus tokens on formatting?
08Branch workflow
Is your git workflow designed for AI-assisted development, or fighting against it?
09Debug logging
Can you trace what happened when something breaks, or are you guessing?
10Error handling patterns
Does your UI surface failures to users, or swallow them into the void?
11Permission model
Is the agent scoped to what it should touch, or does it have free reign to break things?
12Development framework
Do you have a repeatable spec-to-ship process, or is every task ad hoc?
The Deliverable
What you get back.
A structured assessment covering all 12 primitives, scored and annotated.
Specific, actionable fixes. Not vague advice. Actual config changes with code.
A priority list so you know what to fix first for the biggest impact.
Optional follow-up if you want help implementing the changes.
Process
How it works.
Send your config
Email penny@pennywiseops.com with your CLAUDE.md, settings.json, and any hook or skill files. Zip it up or paste it inline. I don't care about formatting.
I run the audit
I review your config against the 12 production primitives. This isn't a checklist. I read the actual content and evaluate whether it's doing what you think it's doing.
You get the report
Within 48 hours, you get a written assessment with scores, findings, and specific fixes. Usually 2-4 pages depending on your setup's complexity.
First 10 audits are free.
No catch. I'm building a portfolio of real-world audits and you get a better config out of it. After that, audits are part of the Operating System Kit.
Send your config