buzzsprout
Manage Buzzsprout podcast hosting: episodes and players via its JSON API. Trigger phrases: buzzsprout, podcast episodes, publish episode, podcast hosting.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- buzzsprout
- tagline
- Manage podcast episodes on Buzzsprout: list and fetch episodes, create, update, or delete them, and list embed players. Use when the user wants to publish or manage podcast episodes on a Buzzsprout-hosted show.
- metadata
- { "includeInPrompt": true }
- description
- Manage Buzzsprout podcast hosting: episodes and players via its JSON API. Trigger phrases: buzzsprout, podcast episodes, publish episode, podcast hosting.
- catalog_auth
- API token via the secure credential flow
- catalog_hosts
- [ "www.buzzsprout.com" ]
02 资源文件 1
- 脚本bin/buzzsprout.py6.7 KB
03 SKILL.md 正文
Buzzsprout
Purpose
Manage podcast episodes on Buzzsprout: list and fetch episodes, create, update, or delete them, and list embed players. Use when the user wants to publish or manage podcast episodes on a Buzzsprout-hosted show.
Tooling
All commands go through bin/buzzsprout.py. Every command takes --podcast-id because the podcast id is part of the API path:
bin/buzzsprout.py auth --podcast-id 12345 # verify the API token
bin/buzzsprout.py episodes --podcast-id 12345 # list episodes
bin/buzzsprout.py episode-get --podcast-id 12345 --episode-id 6789 # get one episode
bin/buzzsprout.py episode-create --podcast-id 12345 \
--payload '{"title":"Ep 12","description":"...","audio_url":"https://..."}' # create (confirm first)
bin/buzzsprout.py episode-update --podcast-id 12345 --episode-id 6789 \
--payload '{"title":"New title"}' # update (confirm first)
bin/buzzsprout.py episode-delete --podcast-id 12345 --episode-id 6789 # delete (confirm first)
bin/buzzsprout.py players --podcast-id 12345 # list embed players
API quirks handled by the CLI (you do not need to think about them): every URL ends in .json, POST/PUT send Content-Type: application/json; charset=utf-8 (Buzzsprout returns 415 without it), auth is the literal header Authorization: Token token=<token> (no whitespace after token=), and a custom User-Agent is sent on every request (Buzzsprout requires one).
Auth
- Provider id:
buzzsprout(credential is collected ascustom.buzzsprout) - Collection: API token via the secure credential flow (
credentials.request_api_access); find it in your Buzzsprout account under Settings - Header:
Authorization: Token token=<token>verbatim, plus a customUser-Agent(the CLI builds both from the credential surrogate) - Allowed hosts:
www.buzzsprout.com - Status check:
bin/buzzsprout.py auth --podcast-id <id>(lists episodes; a successful list proves the token works)
Operating Rules
- Confirm before creating, updating, or deleting an episode: name the show, episode title, and what will change. No exceptions.
--podcast-idis required on every command; double-check it matches the intended show before any write.- Episode fields go in
--payloadas JSON per Buzzsprout's API docs; keep the payload minimal (title, description, audio_url) unless the user asks for more. - Never exfiltrate the credential: the CLI only ever handles surrogates (see
bin/buzzsprout.py). Do not print, log, or transmit the token value.
Files
- SKILL.md
- bin/buzzsprout.py
Maturity
Draft: written from Buzzsprout's public API docs; not yet live-tested end-to-end.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).