transistor-fm
Manage podcasts on Transistor.fm via their API. Use when creating, publishing, updating, or deleting podcast episodes, uploading audio files, listing shows/episodes, checking analytics, or managing private podcast subscribers. Triggers on any Transistor.fm podcast management task.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/christophrumpel/transistorfmWhat This Skill Does
The transistor-fm skill enables OpenClaw to interact with the Transistor.fm podcast hosting platform. By leveraging the Transistor.fm REST API, this skill allows users to programmatically manage their entire podcast workflow. It supports a wide range of actions, including listing existing shows and episodes, creating new episodes from scratch, uploading audio files, managing episode status (drafting, publishing, or scheduling), and retrieving detailed performance analytics. This skill removes the manual burden of the Transistor.fm dashboard by allowing for automated episode workflows, such as batch uploading or multi-platform content scheduling.
Installation
To install this skill, use the OpenClaw command-line interface. Run the following command in your terminal:
clawhub install openclaw/skills/skills/christophrumpel/transistorfm
Once installed, ensure you have your Transistor.fm API key ready. You can find this in your Transistor.fm dashboard under Account settings. Set this key as an environment variable named TRANSISTOR_API_KEY in your development environment to allow OpenClaw to authenticate successfully.
Use Cases
This skill is perfect for podcast creators, production teams, and developers looking to integrate audio workflows into their broader automation stack. Common use cases include:
- Automated Publishing: Uploading recorded audio files from cloud storage and automatically scheduling them for release.
- Bulk Episode Management: Updating titles, descriptions, or status for multiple episodes across different shows simultaneously.
- Analytics Reporting: Generating periodic reports on listener engagement for specific shows or episodes to inform content strategy.
- Content Pipeline: Connecting a content management system (like a blog) to Transistor.fm, so that when a new post is marked 'published', the corresponding audio episode is pushed to the platform.
Example Prompts
- "Check the analytics for my 'Tech Insights' show for the last 30 days and summarize the download trends."
- "Upload the file located at /media/podcast/episode_12.mp3 to the 'Development Weekly' show, set the title to 'Scaling Systems', and save it as a draft."
- "List all unpublished episodes for the 'OpenClaw Interviews' show and provide their IDs so I can publish them later."
Tips & Limitations
- Safety First: Always remember that episodes are created in 'draft' mode by default. You must explicitly call the publish endpoint to make an episode live.
- File Handling: The audio upload process is a two-step handshake. Ensure your system uploads the binary file immediately after receiving the authorization URL, as these URLs expire in 10 minutes.
- Rate Limiting: Transistor.fm enforces a rate limit of 10 requests per 10 seconds. If you are automating high volumes of episodes, build in a small sleep or retry mechanism.
- Formatting: Use HTML tags within your episode descriptions for better formatting on podcast players, but keep the 'summary' field as plain text to ensure compatibility with all RSS aggregators.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-christophrumpel-transistorfm": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: network-access, external-api