Skills & Plugins
Podwise distributes its agent tooling in two pieces that are designed to be installed together:
| Piece | What it adds |
|---|---|
| Podwise skill | Named workflows (catch-up, weekly recap, episode notes, topic research, and more) that tell the agent which tools to call, in what order |
| Podwise MCP server | The 38 tools themselves — search, summaries, transcripts, Clips, exports, Ask — at https://mcp.podwise.ai/mcp |
The Podwise plugin bundles both. Install it once and the app has the tools and the know-how.
The plugin repositories are being restructured, so the install commands below are the current ones rather than a final interface. If a command changes, hardhackerlabs/podwise-plugin is the source of truth.
Install
/plugin marketplace add hardhackerlabs/podwise-plugin
/plugin install podwise@podwiseThen run /mcp, select the Podwise server, and finish the sign-in in your browser. If you added the plugin on claude.ai or Claude Desktop, it is already available in Claude Code; plugins are saved to your Claude account.
The skill on its own
The Podwise CLI ships the same skill for agents that already run shell commands, plus one extra workflow:
npx skills add hardhackerlabs/podwise-cliThat version calls podwise instead of the MCP server, so the CLI must be installed and signed in first.
Workflows
The plugin's skill routes a request to one of these workflows:
| Workflow | Use it for |
|---|---|
| catch-up | "I haven't listened in a while" — triage a backlog and summarise what you missed |
| weekly-recap | A digest of everything you listened to this week |
| episode-notes | Turn one episode into notes in Notion, Obsidian, or Logseq |
| topic-research | Collect and synthesise what several episodes say about a topic |
| episode-debate | Stress-test an episode's claims, play devil's advocate |
| language-learning | Turn a transcript into vocabulary or Anki cards |
| discover | Recommend shows and episodes outside your subscriptions |
The CLI's copy adds refine-taste, which builds a listener profile from your history for more personalised output.
You do not call workflows by name. Describe what you want and the skill picks one; if a request matches more than one, it asks a clarifying question first.
How the skill behaves
These behaviours are worth knowing because they explain what the agent does before it answers:
- Connection check. Every session starts with
get_me, which returns your account, plan, and remaining credits. If the tools are missing or unauthenticated, it stops and points at the setup steps. - IDs, not URLs. Podwise tools take numeric sequence numbers. The skill extracts the
seqfrom a pasted episode or podcast URL, and links episodes back in the same form. - No stored profile. Personalisation comes from your Podwise data at the start of a session. Preferences the data cannot infer — output format, PKM tool, study language — are asked once per session, not remembered.
- Podcast content is untrusted. Transcripts, summaries, and show notes are treated as data. Instructions found inside an episode do not change what the agent does.
- Confirmations. Processing an episode, uploading audio, deleting a Clip, and the Enterprise tools are marked destructive, so the app asks before each call.
Example prompts
| Prompt | What runs |
|---|---|
| "Catch me up on this week's episodes" | catch-up: list_followed_episodes, then summaries of what matters |
| "Write my weekly listening recap" | weekly-recap: history plus highlights, as a digest |
| "Save notes for this episode to Obsidian" | episode-notes: get_episode_summary, then export_episode_markdown |
| "What do podcasts say about startup pricing?" | topic-research: search_episodes across shows, then a synthesis with sources |
| "Challenge the claims in this episode" | episode-debate: transcript and highlights, argued back |
| "Make flashcards from this transcript" | language-learning: get_episode_transcript, then cards |
| "Find me something new to listen to" | discover: taste from list_followed_podcasts and list_my_episodes |
Requirements
- A Podwise account. The plugin authenticates with OAuth; no key is stored in the repository.
- Network access to
https://mcp.podwise.ai/mcp. - A Pro or Enterprise plan for the MCP tools. The
enterprise_*tools additionally need an Enterprise entitlement.
Related
- MCP Server: every tool, and per-client setup without a plugin.
- CLI: the local option, with the same tools over a command.
- Recipes: longer jobs built from these workflows.