podcraft-episode-creation

Create and verify podcast episodes through the Podcraft API service.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/GregM1991/skills --skill podcraft-episode-creation-gregm1991
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: podcraft-episode-creation
Source: https://github.com/GregM1991/skills/tree/main/skills/podcraft-episode-creation
Command: npx skills add https://github.com/GregM1991/skills --skill podcraft-episode-creation-gregm1991

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Producing a podcast episode through the Podcraft service involves multiple risky steps: connecting to a tailnet-restricted API, choosing between generated and bring-your-own-script modes, authorizing a production side effect, and verifying that the episode is actually playable and feed-visible. This Skill orchestrates that entire workflow with dry-run validation, duplicate detection, and explicit delivery gates so no episode is created blindly or left unverified. ## Core Features & Use Cases - Two creation branches: Generated mode (Podcraft researches and writes from a topic and summary file) and BYOS mode (your authoritative script is rendered to audio without rewriting). - Safe production workflow: Dry-run preflight with SHA-256 source hashes, explicit user authorization before creation, no-retry creation policy, and client-side duplicate detection for BYOS submissions. - Mechanical verification gates: Waits for terminal status, then checks production readiness, episode page availability, audio range requests, and RSS feed membership, while keeping human listening-quality review separate. - Use Case: You have a finished script for your tech podcast series. The Skill validates the script length, dry-runs the BYOS create command against your series slug, asks for your confirmation, submits exactly once, waits for rendering, and confirms the episode appears in the series RSS feed with a working audio URL. ## Quick Start Create a Podcraft episode in my series from the script file at /path/to/script.md, then wait for it to finish and verify it is live in the feed.

Frequently Asked Questions about podcraft-episode-creation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a podcast episode with the Podcraft API?▼

Run the bundled podcraft_api.py client with the create command in either generated mode (topic plus summary file) or byos mode (title plus script file). Always run with --dry-run first to validate inputs, then run once without it after authorizing the exact plan.

What is the difference between generated and BYOS episode modes?▼

Generated mode lets Podcraft research and write the script from a topic (up to 1,000 characters) and a summary file (up to 50,000 characters). BYOS mode treats your supplied script (up to 200,000 characters) as authoritative and only performs text-to-speech, production, and delivery.

Does the Podcraft API require authentication?▼

No, Podcraft currently has no application-layer API authentication. Network policy is the only access control: the caller must be on the same Tailscale tailnet and able to reach TCP port 5200 on the server.

Why did my Podcraft episode creation fail or return no episode ID?▼

Creation requires exit code 0 and an episode object with a nonempty id. If the response is lost or ambiguous, do not retry blindly; preserve stdout, stderr, and exit status, then reconcile against recent episodes before attempting another create.

How do I verify a Podcraft episode is live in the RSS feed?▼

Run the wait command until the episode reaches a terminal status, then run the verify command. It checks production readiness, the episode page, a one-byte audio range request, and series RSS membership, exiting 0 only when all gates pass.

Can I submit the same script twice to Podcraft?▼

The client checks existing series episodes for the same trimmed title, script, and voice before BYOS submission and rejects duplicates. The --allow-duplicate flag bypasses this check but requires explicit user authorization, and it is not a cross-host lock.