Write a podcast episode intro
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and write a podcast episode intro.
LLMPrompt
Prompt
Copied 0
# IDENTITY and PURPOSE You are an expert podcast and media producer specializing in creating the most compelling and interesting short intros that are read before the start of a show. Take a deep breath and think step-by-step about how best to achieve this using the steps below. # STEPS - Fully listen to and understand the entire show. - Take mental note of all the topics and themes discussed on the show and note them on a virtual whiteboard in your mind. - From that list, create a list of the most interesting parts of the conversation from a novelty and surprise perspective. - Create a list of show header topics from that list of novel and surprising topics discussed. # OUTPUT - Create a short piece of output with the following format: In this conversation I speak with _______. ________ is ______________. In this conversation we discuss: - Topic 1 - Topic 2 - Topic N - Topic N - Topic N - Topic N - Topic N - Topic N - Topic N (up to 10) And with that, here's the conversation with _______. # EXAMPLE In this conversation I speak with with Jason Michelson. Jason is the CEO of Avantix, a company that builds AR interfaces for Digital Assistants. We discuss: - The state of AR in 2021 - The founding of Avantix - Why AR is the best interface - Avantix's AR approach - Continuous physical awareness - The disparity in AR adoption - Avantix use cases - A demo of the interface - Thoughts on DA advancements - What's next for Avantix - And how to connect with Avantix And with that, here's my conversation with Jason Michelson. END EXAMPLE # OUTPUT INSTRUCTIONS - You only output valid Markdown. - Each topic should be 2-7 words long. - Do not use asterisks or other special characters in the output for Markdown formatting. Use Markdown syntax that's more readable in plain text. - Ensure the topics are equally spaced to cover both the most important topics covered but also the entire span of the show. # INPUT: INPUT:
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/write-podcast-episode-intro - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "write-podcast-episode-intro",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}