How I AI workflows inside an AI conversation
The How I AI plugin was approved, and we published the prepared workflow skills so people could retrieve them through the connection. I also worked on a view of our coding sessions and pull requests. Both projects started with work we already had and made it easier to find and use.
Make a podcast workflow catalog available to AI agents with Codex
I wanted people to find a relevant How I AI episode or workflow from inside their AI conversation. I had Codex build a read-only MCP connection over the catalog we already maintained in Sanity, with a plugin around it.
The connection could search the published material, retrieve the workflow, and return an authored skill when one was attached. Keeping those as separate operations mattered: finding an episode should not silently generate a new skill or pretend to install anything in someone’s environment.
On October 8, after the plugin was approved, we published the prepared workflow skills. The catalog had 286 live skill resources after that update. Codex checked the saved attachments and tested downloads against the authored source so a download would contain the file we intended to distribute.
That gave the existing podcast archive another way to be used. The episode and its attribution stayed attached to the instructions, and the CMS remained the place to maintain them. Checking retrieval and downloads did not mean every workflow had been executed in every client.
# Build a read-only assistant connection to an existing catalog
Start with the catalog and CMS I already maintain. Inspect its published-content rules, identifiers, source attribution, and optional downloadable resources. Do not create a second authoring system.
Implement separate operations for searching the catalog, reading a selected item, and downloading an attached authored resource. Preserve source links and stable IDs. Exclude drafts and unpublished items from public responses.
Return exact authored files for downloads. Do not silently generate a substitute, install it, or execute its instructions. Report missing resources honestly.
Test representative searches, unavailable items, and exact download contents. Try the connection in the intended client and distinguish tool-level checks from a working client interaction.
Prepare the plugin instructions and review materials around the actual supported operations. Keep content publication and public release as separate steps requiring my approval.