- I could maintain templates of resumes.

- Templates changing shouldn't affect the underlying contents of the resume

- and, wait, we can make JSON the underlying data struct, and be able to modify that for every job description, and templates render the JSON

Really enjoyed playing around with this, cause it got me thinking: if agents are automating the most mundane workflows, why are we still bottlenecked with tools like Google doc, Word, etc to create and maintain resumes; why cant we reliably see a job description and re-render a resume fitted to that job while not compromising the templates? Why not let Claude maintain the JSON files for each job, or each of your own profiles, and render those JSON's in to your templates?

I'm open sourcing this, and I'd love if you all give it a try. Drop the Skill in in your .claude/skills/ dir, take your existing resume, and build something cool.

The starter template today is inspired from: https://blog.pragmaticengineer.com/the-pragmatic-engineers-r.... I plan to add some more starter templates in the coming days. Feel free to recommend which resume templates you want me to ship.