CLSkills Hub
← Back to the blog
April 15, 2026Claude Skills Hub

Claude Prompt

Optimize podcast show notes with Claude prompt codes L99 and /trim

claudepromptspodcastshownotes

Struggling to Create Engaging Podcast Show Notes

If you're searching for a Claude prompt for podcast show notes, you're likely trying to automate the process of generating notes for your podcast episodes. Manually writing show notes can be a time-consuming task, and it's easy to end up with notes that are either too brief or too lengthy. Your current approach might involve listening to the entire episode, taking notes by hand, and then attempting to organize them into a coherent summary. However, this method can be tedious and may not result in the engaging show notes you need to attract and retain listeners.

The Pattern that Works

To create effective podcast show notes using Claude, you can use a combination of the L99 and /trim prompt codes. The L99 code helps Claude understand the context and tone of your podcast, while /trim enables the model to condense the episode into a concise summary. By stacking these codes together, you can generate show notes that capture the key points and essence of your episode. For example, your prompt might look like this: L99 /trim Generate show notes for the following podcast episode: [episode transcript].

Concrete Before/After Example

Let's consider an example of a podcast episode about entrepreneurship. Without using the L99 and /trim codes, Claude might generate show notes that are too lengthy or unfocused: Before: Generate show notes for the following podcast episode: Our guest today is John Smith, a successful entrepreneur who has founded several startups. He shares his journey, from struggling to find funding to eventually selling his company for millions. John also discusses the importance of perseverance and adaptability in the entrepreneurial world. Claude's response might be a lengthy summary that includes unnecessary details. However, by using the L99 and /trim codes, you can get a more concise and engaging summary: After: L99 /trim Generate show notes for the following podcast episode: Our guest today is John Smith, a successful entrepreneur who has founded several startups. He shares his journey, from struggling to find funding to eventually selling his company for millions. John also discusses the importance of perseverance and adaptability in the entrepreneurial world. Claude's response might be: John Smith, founder of multiple startups, shares his entrepreneurial journey, highlighting the importance of perseverance and adaptability. Key takeaways include the need to pivot when necessary and the value of learning from failure.

Anti-Patterns that Don't Work

Some users might try using the /skeptic code, thinking that it will help Claude generate more critical or analytical show notes. However, this code is better suited for evaluating arguments or claims, rather than summarizing podcast episodes. Others might attempt to use the /voice code, hoping to inject a more conversational tone into their show notes. While this code can be useful for generating content that mimics a particular voice or style, it may not be the best choice for creating concise and informative show notes. Another anti-pattern is using the /deepthink code, which can lead to overly complex or philosophical show notes that may not resonate with listeners.

When NOT to Use this Approach

While the L99 and /trim codes can be effective for generating podcast show notes, there are situations where this approach may not be the best fit. For example, if your podcast episodes are highly technical or specialized, you may need to use more specific prompt codes, such as /mirror or /hook, to generate show notes that accurately capture the key concepts and terminology. Additionally, if you're looking to generate show notes that are more creative or humorous, you may want to experiment with other codes, such as /punch or /simplify.

Next Steps

To learn more about the different prompt codes and how to use them effectively, see all 120 codes tested over 3 months in the Cheat Sheet. This comprehensive resource will help you unlock the full potential of Claude and generate high-quality content, including engaging podcast show notes, with ease.

The Cheat Sheet is where the rest of this lives

160+ prompt patterns, each with the temperature, top_p, and system prompt we actually use, why we picked it, and what breaks when you get it wrong. If a lookup table is what you needed, this is the same thing at 20x the depth.

Get the Cheat Sheet, from $10 →Free 75-page guide first
More reading

Recent posts

Jul 12, 2026
Claude Fast Mode Removed July 24: What Breaks and Fix

Claude Opus 4.7 fast mode is deleted July 24, 2026. Requests error, no fallback. Here is the exact migration path to Opus 4.8 and the 3x price cut you get.

Read post →
Jul 10, 2026
Claude Prompt Caching: The Real Setup Guide (Cut API Costs Up to 90%)

How Claude's prompt caching actually works, when it saves you money, when it costs you more, and the exact break-point pattern that gets a 90% discount. Verified against Anthropic's official spec.

Read post →
Jul 9, 2026
Claude Fable + Token Monitoring: How to Cut Your Claude Code Bill Without Cutting Quality

Fable is the fast light Claude 5 model built for cost efficiency. Here is when to use Fable vs Sonnet vs Opus, how to monitor tokens live inside VS Code, and the honest math on what each saves.

Read post →