Podwise

What this means and what to check before installing/use: - This is an instruction-only skill that drives the Podwise CLI. It does not bundle or execute code itself; instead it runs podwise commands and reads/writes files in the current working directory. That behavior aligns with the described podcast workflows. - Installation: the included installation doc suggests several install options. The automatic curl | sh installer (raw.githubusercontent.com/hardhackerlabs/...) and an untrusted Homebrew tap are the riskiest suggestions — do NOT run curl | sh without reviewing the script first. Prefer installing from a GitHub release archive you inspect, building from source, or using a package manager you trust. - Local file access: the skill will read a local taste.md for personalization and will write note/export files to your current working directory (e.g., debate summaries, episode notes, Anki/CSV exports). If taste.md may contain sensitive data, review or remove sensitive fields before using the skill. - Config and API keys: Podwise CLI stores config in ~/.config/podwise/config.toml and requires an API key or browser auth. Confirm any API keys are from podwise.ai and that you trust that service. Exports to third-party services (Notion, Readwise) will use whatever credentials the Podwise CLI or its auth flow provides — verify and control those integrations in the CLI before exporting. - Quota/processing: running podwise process consumes Podwise credits. The workflows explicitly require confirming before processing; the agent should ask you before using quota. Always confirm before allowing processing of remote content or local files. - Transparency: some workflow steps say to 'read' taste.md silently and to 'silently record' internal notes used for a later saved summary. This is not exfiltration, but it means the agent will access and temporarily store some internal state. If you want full transparency, ask the agent to show any notes it recorded before saving them to disk or exporting. If you decide to proceed: (1) review the install script before running it, (2) inspect ~/.config/podwise/config.toml and any connected integrations, (3) ensure taste.md contains only the non-sensitive preferences you want the agent to use, and (4) be prepared to confirm any processing that consumes credits or exports data externally.