Agent skill · security · jeremylongshore

assemblyai-security-basics

Analyze and apply AssemblyAI secret, region, consent, retention, deletion, and model-training controls. Use when reviewing security or regulated speech workflows. Trigger with "AssemblyAI security", "AssemblyAI privacy", or "data retention".

Why this skill is useful

Provides specific security practices for managing API keys and PII redaction in AssemblyAI that the AI wouldn't reliably generate on its own.

What it needs

Requires assemblyai installed locally. Requires assemblyai account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.

What this skill does

AssemblyAI Security and Data Governance Overview Govern speech and derived data across every AssemblyAI surface. Keep consent, credentials, region, training posture, retention, and deletion as explicit decisions. Prerequisites The target repository or integration path and the requested operator outcome. The AssemblyAI project, environment, region, data classification, and accountable owner. Current first-party documentation plus credentials only for a narrowly approved live check. Current Contract Speech, transcripts, prompts, and derived intelligence are governed data. Long-lived keys stay server-side; US and EU hosts are explicit decisions. Retention, training posture, transcript deletion, and downstream copies require policy evidence. Infrastructure TTL processing means physical deletion should not be described as instantaneous without confirmation. Authentication For live work, inject ASSEMBLYAIAPIKEY from an approved secret manager and send the raw value only in the AssemblyAI Authorization header to the configured first-party host. Never print, commit, place in a URL, or expose it to an untrusted client. Callback secrets and temporary streaming tokens are separate credentials. Instructions 1. Classify every source and derived data field. 2. Confirm consent, purpose, region, training posture, and subprocessors. 3. Separate, store, rotate, and monitor environment keys. 4. Use temporary browser tokens and a separate callback secret. 5. Minimize requested features, persisted fields, and broad access. 6. Delete and reconcile AssemblyAI plus every downstream copy. Tool Discipline Use Read, Glob, and Grep to inspect repository code, configuration, fixtures, and evidence. Use Write and Edit only for approved implementation or documentation changes. Do not call AssemblyAI, upload audio, open a streaming session, mint a token, replay a callback, deploy, rotate a key, or delete a transcript merely because this skill was invoked. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills jeremylongshore/assemblyai-security-basics--413167

View the source on GitHub

Browse the @skills marketplace