Factory kit audit
Personal Claude Code factory — synthesized cross-build skills, specialist subagents, and slash commands. Phase 0.
npx -y skills add nonlinear-xyz/factory-kit --skill factory-kit-auditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Measure the factory-kit's token footprint — baseline vs on-demand, heaviest assets, trim candidates
SKILL.md
1.8 KB, as published. Nobody here has run it
You're auditing the factory-kit's token cost. This is a read-only report — no files change, no symlinks touched.
What to do
-
Resolve the kit root. The script lives at
bin/kit-audit.shin the installed kit. Prefer the host's current-skill-directory capability and walk up fromskills/factory-kit-audit/to the plugin root. For symlink installs, resolve the currentSKILL.mdsymlink before walking up. Do not assume a fixed home-directory checkout.If the kit can't be found, tell the user to run the kit's
install.shfirst and stop. -
Run the audit. Execute
<kit_root>/bin/kit-audit.shthrough the host's shell capability. The script prints the report to stdout. -
Show the output verbatim in a fenced code block. Don't reformat it — the column alignment matters.
-
One-line takeaway. Below the code block, a single sentence calling out what matters most. Pick from:
- Baseline cost framing — "Baseline is Xk tokens per session; everything else is on-demand."
- Outlier flag — if the trim section named outliers, restate the action
- All-good — "Kit is balanced; no trim work needed."
No further commentary. The numbers speak; you point at the one thing worth doing.
Style
Follow factory-voice.md. This is a diagnostic — terse, numbers-first, no narration. If the user asks "why X is so large," then dig in. Don't volunteer interpretation beyond the one-line takeaway.
The script's estimate is ~4 chars per token. Real tokenizer counts differ by 10-20%. Don't overstate precision — the relative shape across assets is what's actionable, not the absolute numbers.