It's understandable, I don't think most of us like getting to the actual documentation of our project and would rather keep coding and/or prompting.

I think this is a message more for everyone that feels this way than just you but...

I'd suggest having a model go through it using pstack's unslop skill and see if you like that copy better.

But in all honesty we should be proofreading readmes before sending instructions out to millions of people. I've tried setting up a few that just didn't work when following instructions because of incorrect info or just completely leaving necessary steps/info out... Usually totally useless info in its place.

There's a conundrum there where we're so excited to show off our project that we present it in this streamlined way that makes people unable (or unwilling) to even digest what it's for and how to properly set it up.

You know what they say about first impressions.

https://github.com/cursor/plugins/blob/main/pstack%2Fskills%...

https://github.com/michael-denyer/pstack-claude

Thanks for the honesty! I don't blame you, it's hard to write good copy.

Cheers and good luck!