Explanation
Why is it built this way?
Why loops
Why skilldrop sequences skills in a separate primitive instead of letting skills call each other, and why there are five lifecycle loops rather than three.
Read →Operating model
Know which stage your work is in, which loop and pack help there, and where the agent stops for your decision.
Read →skilldrop, reviewed by its own skills
The site's performance and accessibility, checked with the catalogue's own web-performance-review and accessibility-audit skills, the findings, and what was fixed. Pull requests are reviewed by pre-merge-review.
Read →Does the agent invent your resume?
The same 14 resume and cover-letter requests run with the career pack's skills and with plain Claude Code - how often each put something in the document that the person never said, and what kind of thing it was.
Read →What the benchmark showed
Five days of measuring skills against the agent without them - a large gain on the skills' own checks, no blind preference at first, a gain that did not survive new evals, and what the skills that do win have in common.
Read →Contributing
How to add or change a skill, a pack, a loop or a subagent, what an RFC is needed for, and the checks a pull request must pass.
Read →