[jhgaylor]

I think I feel ya on some level but I also think that when the process is refined it will be much less exhausting to update our resumes with the help of an LLM. Underneath this tool is just consuming the data I already present to the world through my website, resume, linkedin, and github.

[babyshake]

Once there is a "one click connect to an MCP server" workflow this type of thing will make more sense for this type of use case, but right now how would you say this improves on the status quo of a resume PDF you can upload to your AI chatbot and ask questions about? Aside from demonstrating your own proficiency with MCP tech, that is. I ask because the current amount of work and tech knowledge required is greater than it would be for the PDF-based workflow, but I might be missing something.

Edit: there was an example in another answer, "I offer a contact tool when you use the hosted server because I can hide away my email credentials and expose a way for the LLM to send me an email."

[jhgaylor]

The standard PDF resume is optimized for the human to read. The information density there is pretty low. Take a look at https://ai.jakegaylor.com/llms.txt and compare that to https://jakegaylor.com/JakeGaylor_resume.pdf

Now we can spend our time more on the content and less on the presentation.

You can already use claude desktop, upload your resume, point it to your website, paste in some stuff from linkedin and output an llms.txt. You can get 80% of the way with just a couple of clicks.

[stavros]

> I offer a contact tool when you use the hosted server because I can hide away my email credentials and expose a way for the LLM to send me an email.

Yeah, but this is the modern equivalent of the "Stavros at Gmail dot com", it's basically antispam by obscurity. Just wait for one spammer to send three seconds writing something that will parse emails from all your MCP commands and that's defeated.

[DonHopkins]

It's the modern version of "Have your answering machine call my answering machine!"