v0.2.0

Podwise

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 8:03 AM.

Analysis

Podwise is a coherent podcast-workflow skill, but it relies on an external CLI/account and can process local media, read listening-profile data, export notes, and change podcast subscriptions when used.

GuidanceInstall this only if you want Podwise CLI-based podcast workflows. Review the CLI installer before running it, protect your Podwise API key, confirm before processing private local recordings, and be aware that follow/unfollow and export commands can change your Podwise or connected note-taking accounts.

Findings (5)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Agentic Supply Chain Vulnerabilities

SeverityLowConfidenceHighStatusNote

references/installation.md

curl -sL https://raw.githubusercontent.com/hardhackerlabs/podwise-cli/main/install.sh | sh

The setup guide includes an optional remote shell installer from the repository's main branch. This is a common CLI installation pattern and is user-directed, but it is not pinned to a specific release or checksum.

User impactInstalling through this command runs remote code on the user's machine.

RecommendationPrefer Homebrew or a reviewed release binary, or inspect the install script before running it.

Tool Misuse and Exploitation

SeverityLowConfidenceHighStatusNote

references/cli.md

podwise follow https://podwise.ai/dashboard/podcasts/{id}
podwise unfollow https://podwise.ai/dashboard/podcasts/{id}
...
podwise export notion <episode-url>
podwise export readwise <episode-url>
podwise export obsidian <episode-url>

The documented CLI can change podcast subscriptions and export content to external tools. These actions align with the skill's stated purpose, but they are account- or workspace-mutating operations.

User impactA user request could result in changed Podwise subscriptions or notes being exported into connected services.

RecommendationConfirm the intended podcast or destination before asking the agent to follow, unfollow, or export content.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityLowConfidenceHighStatusNote

references/installation.md

podwise auth ... podwise config set api_key your-sk-xxxx ... The configuration is stored at `~/.config/podwise/config.toml`.

The skill requires the Podwise CLI to authenticate and store an API key locally. This is expected for a Podwise account integration, but it gives the CLI delegated account access.

User impactThe CLI can act through the user's Podwise account for searches, history, processing, subscriptions, and exports.

RecommendationUse a Podwise account/API key you trust, keep the config file private, and revoke or rotate the key if it is exposed.

Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Insecure Inter-Agent Communication

SeverityLowConfidenceHighStatusNote

references/cli.md

Submit an episode, video, or local file for AI processing. ... podwise process ./meeting.wav --title "Product Review Meeting" ... `process` consumes quota/credits. Always confirm with the user before running it

The CLI can process local audio or video files through Podwise. The instructions require user confirmation, which is good, but users should still consider privacy before submitting local recordings.

User impactPrivate recordings may be processed by the Podwise service if the user confirms the action.

RecommendationDo not process confidential local audio or video unless you are comfortable with Podwise handling that content.

Memory and Context Poisoning

SeverityLowConfidenceHighStatusNote

workflows/catch-up.md

Look for `taste.md` in the current working directory. ... If found, read it silently. Use the **Core Interest Areas**, **Shows to Prioritize**, and **Shows to Deprioritize** sections

The workflows use a persistent local listener profile to personalize results. This is purpose-aligned, but the file can influence later recommendations and triage behavior.

User impactPreferences stored in taste.md may affect future workflow outputs without being shown each time.

RecommendationReview or edit the taste profile if recommendations seem wrong, and avoid placing unrelated instructions or sensitive secrets in that file.