Podcast Transcript Mining Authority Positioning

What to check before installing or using this skill: - Confirm exactly how the skill will authenticate to WordPress, Notion, Google Docs, Spotify/Apple, or other services it mentions — the SKILL.md does not declare credentials for those. Ask the author whether you'll be prompted for per-action credentials or whether additional env vars are required. - Treat the Slack webhook as sensitive: a webhook can post any data to the given Slack channel. If you must provide one, use a channel and webhook with limited visibility and permissions. - Use a limited-scope OpenAI key (or an account that can be revoked) and a dedicated Google Search API key to avoid tying production credentials to this skill. - Test with non-sensitive transcripts first and verify where (if anywhere) the skill stores processed data. Ask whether the skill logs or caches transcripts and for how long. - If the skill claims to pull private Notion/Google Docs content, require the author to document the exact auth flow and scope; refuse to provide full-account credentials. - If you need the WordPress push feature, request clear documentation for required WP credentials and recommend creating a limited author account or using site-specific API keys. I have medium confidence because this is an instruction-only skill (no code to inspect); clarifying the missing integration/auth details from the maintainer would likely change the assessment.