Extension README as a skill?

[andrewpbray]

Just an idea:

I'm using LLMs to help me work on a repo that has many different quarto extensions that I've written. I was starting to write a skill for each one, then I realized I'm pretty much writing the README for that extension.

If quarto add also copied in the README, then I could add a skill that's just a pointer: go read the README. That skill would stay valid even after quarto update.

I'm not sure how much you want to tune the behavior of quarto add to this particular LLM workflow, but figured I'd throw the idea out there.

[cscheid]

Do you mean "copy the main README at the root of the git repo into the extension directory"? Yeah, we could consider that, but if that's the goal, couldn't we encourage people to have an actual readme in the right place already to begin with?

I might be misunderstanding you, though!

[andrewpbray]

Yes, I guess that's what I mean.

an actual readme in the right place

Do you mean having users author a second _extensions/README in addition to /README?

[cscheid]

Either that, or a symlink, or a straight-up copy that's manually managed. But yes.