Work with Hazeley
Standardize your skill library
Every engagement runs on the same pairing: the toolkit supplies the evidence, a named rule or gate behind each claim, and we supply the judgment about what to fix first. You keep the toolkit when we leave.
Packages
Engagement options
Assess
Your existing skill library, audited against every applicable rule family.
- Ecosystem audit: overlap matrix, hand-off graph, and gap map across the library
- Per-skill grades against the quality rubric, plus preflight and hygiene findings
- Security posture over prompts, tools, and subagent definitions
- A tiered fix plan, sequenced cheapest-first, with a rule id behind every finding
Placeholder · mcw-business-plan · price + timeline
State this package’s price and timeline once the business plan fixes them.
Build
New skills taken from a one-paragraph brief to a shipped GO verdict.
- A typed design plan per skill: anatomy, file list, eval shape, sister-skill bridges
- The six-stage build lifecycle, run with orchestrated worker agents
- Trigger evals and output benchmarks committed beside each skill
- The terminal gate on every deliverable: preflight, grade, and ship-check GO
Placeholder · mcw-business-plan · price + timeline
State this package’s price and timeline once the business plan fixes them.
Standardize
The discipline installed in your repos and your team, not a report on a shelf.
- The toolkit wired into your repos: plugin enrollment, MCP server, git-safety hooks
- CI gates: preflight on changed skills, drift guards on generated artifacts
- An eval ledger and grading bar your team runs without us
- Working sessions with the engineers who will own the library
Placeholder · mcw-business-plan · price + timeline
State this package’s price and timeline once the business plan fixes them.
Who it fits
Teams whose skills outgrew their review process
Platform teams
You own the internal Claude tooling and the skill library grew faster than the review bar. You need a grading standard the whole org can cite.
Consultancies
Skills are part of what you deliver to clients. A GO verdict with named rules behind it is a stronger handover than a demo.
Claude Code power users
Your personal toolkit became load-bearing for the team. Time to version it, grade it, and ship it like the software it is.