Start with the result you need
The Recipes library is the main discovery surface. A recipe names its intended result, the information it needs and the checks to apply afterward. Its ID remains the same whether you use the website or a connected assistant.
Choose the delivery that fits your assistant
Copy lets you prepare a prompt on this device and paste it into your chosen assistant. MCP retrieves public instructions through get_recipe. Connecting an assistant is optional; neither path completes the work just by copying or retrieving.
Keep private facts in the place you choose
Filled recipe inputs stay in your browser unless you choose to paste them into an assistant. Public MCP arguments are for catalog identifiers and public keywords. Do not put personal documents, conversation transcripts or final drafts into a catalog search.
Check identity, then check the actual draft
A starter names the selected recipe version and publication. Confirm those match before creating a result. After generation, check the draft itself against the recipe promise and your facts. A tool connection is not evidence of result quality.