This innovative solution empowers users to unlock seamless outcomes.
The guide gives first-time facilitators a checklist they can use before the room opens.
Working Tools by J. Kyle Hobson
A public library for writing, research, design, building, career work, teaching, and games with AI. Every item here opens to a resource you can read, install, or download.
01 / Start
You do not need the whole system. Pick the work in front of you; the library will narrow itself.
Choose the job, not the brand
Featured collection / Humanizer
Humanizer checks a draft for vague claims, borrowed confidence, citation problems, and voice drift. It keeps the useful irregularities and asks for evidence where the draft has not earned certainty.
This innovative solution empowers users to unlock seamless outcomes.
The guide gives first-time facilitators a checklist they can use before the room opens.
02 / Library
Search by task or narrow the list. Every result opens a public page, guide, example, or download that a visitor can actually use.
Loading the library…
No tools match those filters. Clear a filter or try a different word.
The full library did not load. The featured tools and public links above still work.
03 / Boundary
This library is a public resource shelf, not an inventory of my private setup.
A public release file, paired with installation guidance and checksums where the product publishes them.
A complete public resource you can read now, with sources and limits kept beside the advice.
A plain-language explanation of the work, what is included, an example prompt, and the actual download.
Private systems, account-bound connectors, unfinished previews, and tools without a public resource stay out.
04 / Install
Use each product page as the authority for current files and checksums. These screenshots document tested Claude paths; Codex collections install from extracted skill folders.



.mcpb release asset.


.skill file.


05 / Builder
I’m Jonathan Kyle Hobson, a UX researcher, product strategist, teacher, game master, and AI-tool builder. I make these tools when a repeated task needs a clearer boundary, a better handoff, or proof that the work actually finished.
The library will change. The rule stays the same: one tool should have one bounded job, a visible limit, and a result a person can inspect.