Podwise logo

Podwise

Organization
hardhackerlabs
podwise

Podcast knowledge workflows powered by Podwise CLI: search podcasts and episodes by keyword, monitor followed shows for new releases, find popular episodes, ask questions and extract insights from transcript content, process Podwise episode URLs, YouTube videos, Xiaoyuzhou links, and local audio or video files to retrieve transcripts, summaries, chapters, Q&A, mind maps, highlights, and keywords — plus catch up on your backlog, refine your listening taste, generate weekly recaps, export episode notes to PKM tools, research topics across podcasts, debate episode ideas, and generate language learning cards. Use when the user wants to find, summarize, transcribe, or extract insights from any podcast or audio content, or manage their listening library.

Overview

Publisherhardhackerlabs
Repositorypodwise-cli
Skill namepodwise
Stars
418
Forks
17
Bundled files
10
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 10 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by hardhackerlabs on GitHub. Read the source before you install it.

Installation

Install the Podwise AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/hardhackerlabs/podwise-cli/tree/main/skills
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/hardhackerlabs/podwise-cli.git /tmp/podwise-cli
mkdir -p .claude/skills
cp -r /tmp/podwise-cli/skills .claude/skills/podwise
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Podwise in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Podwise on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Podwise is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Podwise

Podwise skills help you get more out of every podcast you listen to.

References

Load these files when needed — do not load all of them upfront:

  • references/cli.md — full CLI command reference. Load before running any podwise command or looking up flags and syntax.
  • references/installation.md — installation and API key setup. Load if podwise is not installed or not configured.
  • references/taste.md — the user's listener profile. Load at the start of any workflow that benefits from personalisation.

Environment Check

Before running any workflow, verify the CLI is available:

bash
podwise --help
podwise config show

If podwise is not installed or the API key is missing, load references/installation.md and stop until setup is complete.

CLI Reference

Before running any podwise command, load references/cli.md as the source of truth for exact flags, subcommands, and examples. Do not guess command syntax from memory.

First-Time Setup

If references/taste.md does not exist, suggest running the refine-taste workflow before any other workflow. Other workflows will still run without it, but their outputs will not be personalised.

Workflow Routing


workflows/refine-taste.md

  • "Set up my Podwise profile"
  • "Tell me about my listening habits"
  • "I want to personalise my recommendations"
  • "Refine my taste profile"
  • Running any other workflow for the first time and references/taste.md does not exist

workflows/catch-up.md

  • "I haven't listened in a while, catch me up"
  • "What did I miss this week?" / "What's new from my podcasts?"
  • "Help me clear my backlog" / "Too many unheard episodes"
  • "Show me what's new from the shows I follow"
  • "Triage my podcast queue"

workflows/weekly-recap.md

  • "Give me a recap of this week's listening"
  • "What did I listen to this week?" / "Summarise my week in podcasts"
  • "Send me a weekly digest" / "What were the highlights from this week?"
  • "I want a summary of what I've been listening to lately"

workflows/episode-notes.md

  • "Save notes for this episode" / "Export this episode to Notion / Obsidian / Logseq"
  • "Turn this episode into a note" / "I want to keep notes on this episode"
  • "Export the summary and highlights from this episode to my PKM"
  • "Create a note from this podcast" — followed by a URL or episode title

workflows/topic-research.md

  • "What do podcasts say about [topic]?"
  • "Research [topic] across my podcasts" / "Synthesise what I've heard about [topic]"
  • "Find everything related to [topic] across episodes"
  • "I want a deep dive into [topic] from podcast content"
  • "Compile insights on [topic] from multiple episodes"

workflows/episode-debate.md

  • "Challenge the ideas in this episode" / "Debate this episode with me"
  • "I want to stress-test what [speaker] said"
  • "Push back on the claims in this episode"
  • "Play devil's advocate on this podcast"
  • "Help me think critically about this episode"

workflows/language-learning.md

  • "Make flashcards from this episode" / "Generate Anki cards from this transcript"
  • "I want to learn vocabulary from this podcast"
  • "Extract phrases for language learning from this episode"
  • "Help me study English / Japanese / [language] using this podcast"
  • "Turn this transcript into study cards"

workflows/discover.md

  • "Recommend new podcasts for me" / "Find me something new to listen to"
  • "What shows should I subscribe to?" / "Discover podcasts based on my taste"
  • "I want to find podcasts similar to [show]"
  • "What else would I like based on what I already follow?"
  • "Suggest new episodes outside my subscriptions"

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 the CLI without loading a workflow. Load references/cli.md and execute directly when the user's intent is a single, self-contained CLI operation:

  • Follow or unfollow a podcast — podwise follow / unfollow
  • Search for an episode or podcast by name — podwise search
  • Check what's trending — podwise popular
  • Browse listening or reading history — podwise history
  • Fetch a specific artifact from an episode — podwise get
  • Ask a one-off question from transcripts — podwise ask

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Podwise AI skill do?

Podcast knowledge workflows powered by Podwise CLI: search podcasts and episodes by keyword, monitor followed shows for new releases, find popular episodes, ask questions and extract insights from transcript content, process Podwise episode URLs, YouTube videos, Xiaoyuzhou links, and local audio or video files to retrieve transcripts, summaries, chapters, Q&A, mind maps, highlights, and keywords — plus catch up on your backlog, refine your listening taste, generate weekly recaps, export episode notes to PKM tools, research topics across podcasts, debate episode ideas, and generate language...

Why use Podwise on TypingMind?

Because you install it once and use it with any model. Podwise is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Podwise in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hardhackerlabs/podwise-cli/tree/main/skills. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Podwise?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Podwise?

As many as you like. As long as a model supports skills, you can use Podwise with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Podwise AI skill free?

Yes. It is published on GitHub by hardhackerlabs under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇