Install
openclaw skills install @saitowu/podwiseopenclaw skills install @saitowu/podwisePodwise skills help you get more out of every podcast you listen to. All capabilities are reached through the Podwise MCP server.
Load these files when needed — do not load all of them upfront:
taste.md in the current working directory — the user's listener profile, generated by the refine-taste workflow. Load at the start of any workflow that benefits from personalisation. Not present until the user has run refine-taste.Before running any workflow, verify the Podwise MCP server is connected by calling:
get_me — returns the account email, plan, and remaining AI processing credits.If the Podwise tools are not available or get_me fails with an authentication error, load references/installation.md and stop until the connection is set up.
Tool names may be prefixed by the host with the server name (for example
podwise_get_me). Use whatever prefix the host exposes.
Before calling a Podwise tool, load references/mcp.md as the source of truth for exact tool names, parameters, return shapes, and quota rules. Do not guess tool signatures from memory.
Every tool identifies content by numeric IDs, not URLs:
episodeSeq from https://app.podwise.ai/dashboard/episodes/<seq>podcastSeq from https://app.podwise.ai/dashboard/podcasts/<seq>When the user pastes a Podwise URL, extract the trailing integer and pass it as the seq. Link episodes back as https://app.podwise.ai/dashboard/episodes/<seq>.
If the taste profile does not exist yet, suggest running the refine-taste workflow before any other workflow. Other workflows will still run without it, but their outputs will not be personalised.
workflows/refine-taste.md
workflows/catch-up.md
workflows/weekly-recap.md
workflows/episode-notes.md
workflows/topic-research.md
workflows/episode-debate.md
workflows/language-learning.md
workflows/discover.md
Once you identify the right workflow, load that file and follow its instructions exactly.
If the user's intent matches more than one workflow, ask one clarifying question before routing. If it matches none, ask what they are trying to accomplish. Do not guess.
Some requests can be handled directly with a single MCP tool call without loading a workflow. Load references/mcp.md and execute directly when the user's intent is a single, self-contained operation:
set_podcast_followsearch_episodes / search_podcastsget_popular_episodeslist_followed_episodeslist_my_episodesget_episode_summary / get_episode_transcriptexport_episode_markdown / export_episode_srt / send_episodeask_podwise