subagent

podcast-editor — Claude Code subagent: features and setup

Q: How do I install podcast-editor in Claude Code?

Run `npx claude-code-templates@latest --agent podcast-creator-team/podcast-editor`, then use `.claude/agents/podcast-editor.md`.

Plans podcast post-production and prepares show notes with chapters and timestamps. Useful when getting an episode ready to publish.

Install into Claude Code · claude-code-templates All methods and platforms ↓

npx claude-code-templates@latest --agent podcast-creator-team/podcast-editor

Open on GitHub

What podcast-editor does

This subagent helps break an episode into sections and plan post-production, including noise reduction, transitions, and quality checks. It can draft timestamped show notes and chapter markers, plus checklists and formatting guidance for publication.

Its listed tools are Read, Write, and Edit; outputs can also include workflow templates and automation scripts. For audio work, it offers recommendations rather than processing sound files itself, so you’ll still need an audio editor for the actual changes.

What it helps with

plan post-production for an episode
draft show notes with timestamps and chapters
prepare a podcast publishing checklist
outline noise-reduction and quality-control steps

Example prompts for the agent

Draft show notes for this episode with chapter markers and timestamps.
Plan post-production steps for noise reduction, transitions, and quality checks.
Create a checklist for preparing this podcast episode for publication.

How to install podcast-editor

1claude-code-templates

npx claude-code-templates@latest --agent podcast-creator-team/podcast-editor

2Manually: put the files in place

.claude/agents/podcast-editor.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Manually: put the files in place

.codex/agents/podcast-editor.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Manually: put the files in place

.cursor/agents/podcast-editor.md

Cursor also reads .claude/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about podcast-editor

How do I install podcast-editor in Claude Code?

Run npx claude-code-templates@latest --agent podcast-creator-team/podcast-editor, then use .claude/agents/podcast-editor.md.

What does podcast-editor do?

It helps plan podcast post-production and draft timestamped show notes and chapter markers. It can also prepare publishing checklists and formatting guidance.

Does podcast-editor edit audio files directly?

It provides audio improvement and noise-reduction guidance. Its listed tools are Read, Write, and Edit.

Similar subagents

All subagents for Writing and docs →

prompt-engineer VoltAgent Community This subagent designs, tests, and improves prompts for LLM production systems. Use it when prompts need evaluation, metrics, or cost tracking. 16,078installs context-manager VoltAgent Community Organizes shared context for multi-agent projects in files, including state, task history, and decisions. Use it when agents need a clear shared workspace. 10,638installs code-explorer official Anthropic This subagent traces existing features from entry points to data storage, mapping the code paths and architecture. Use it before extending unfamiliar code. 1,172installs search-specialist Seth Hobson A web research subagent that filters sources and cross-checks facts. Use it for deep research, competitive analysis, and trend work. CX Codex 6,886installs api-documenter VoltAgent Community Drafts OpenAPI 3.1 specs, code examples, and integration guides for REST or GraphQL APIs. Helpful when documenting endpoints and standardizing schemas. 6,451installs technical-writer VoltAgent Community This subagent creates and maintains API references, user guides, and SDK docs. Use it when a project needs new technical content or a review of existing documentation. 4,345installs

From the same set804

The whole set →

troubleshooting-guide Writes a troubleshooting document with diagnostic steps, common failures and shell commands for checking a system. Useful when a service needs a runbook. 397installs fastapi-endpoint Guides you through planning and coding async FastAPI endpoints with Pydantic v2 schemas, SQLAlchemy 2.0, auth checks, and pytest suites. Gathers requirements before writing code. 393installs performance-budget-guard A Claude hook that measures your Next.js JS bundle after a build and blocks the deploy when it goes over the performance budget. 393installs best-practices Checks web code against Lighthouse standards, patches dependency vulnerabilities, and sets up browser security headers. 392installs memory-spring-cleaning Walks through CLAUDE.md and markdown docs, checks the rules written there against the actual code, and drops what no longer holds. 391installs create-prp Builds a Product Requirement Prompt by reading your docs and code, searching the web for examples, and writing an implementation guide. 387installs neon-auth-specialist Configures Stack Auth integration with Neon database synchronization. Helps set up user management, protected routes, and safe query patterns. 387installs fix-github-issue This command takes a GitHub issue number, investigates the related code, and works through a fix with tests. Use it to carry an issue from its report to a commit. 386installs