Supporting external tools

[aaronpowell]

As this repo has grown, discoverability is a critical challenge that we need to tackle; I talked about it in this discussion.

While we could build tooling ourselves, the community is already out there building awesome experiences and we want to make it easier for them.

One way to support this is we're looking to add a workflow to the repo that will support invoking a webhook when changes are merged to main. Here is the PR that I'm iterating on.

If you have a tool that you want to have notified when the repo is updated, reach out with the webhook that you want to have invoked, and we'll add it to the list.

Note - the webhooks are going to be kept in a secret in the repo, rather than the workflow file, so that we can better ensure the privacy of others platforms, meaning you can have an authentication key in the URL and it will be hidden in the job run.

[VamshiVerma]

Nice workflow! GitHub Pages would be perfect for this - could auto-update when main changes and showcase all the customizations with search/filtering. I like a simple search index and it would make it easy for us to find specific instructions/prompts by category or language.
Maybe we can start with GitHub Pages? since it's built-in and easy to set up? Could be a quick win for discoverability.

[aaronpowell]

Building a website, even something as simple as a GitHub Pages site, is something we're discussing, but we're already seeing the community starting to build out cool tools.

Today, I merged in a chat mode from @OrenMe that will search for chat modes/prompts/instructions, you can see the video here: https://x.com/OrenMe/status/1943400896316031120

We also have prompts for chat modes and promptfiles from @PlagueHO.

I'm also aware of people building their own website/indexes, and part of the goal of this bit of work is to support them, because this repo is for the community and you're all building stuff that's cooler than we could!