Skip to content
Skills Library
Security · Review & audit

assemblyai-security-basics

/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".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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".

Triggers from the description

AssemblyAI securityAssemblyAI privacydata retention

Arguments

/assemblyai-security-basics <data-class> <region> <retention-policy>
Original author description

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".

How it works

  1. Overview
  2. Prerequisites
  3. Current Contract
  4. Authentication
  5. Instructions
  6. Tool Discipline
  7. Approval Boundaries
  8. Failure Modes
  9. Output
  10. Example
Original SKILL.md headings · 62 lines, 495 words
SKILL.md preview
---
name: assemblyai-security-basics
description: >-
  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".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<data-class> <region> <retention-policy>"
version: 1.12.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [saas, assemblyai]
model: inherit
effort: high
compatibility: "Designed for Claude Code; live AssemblyAI work requires network access"
---
# 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 `ASSEMBLYAI_API_KEY` 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.

## Approval Boundaries

Require an accountable owner before live audio processing, production credential or endpoint changes, paid model or capacity changes, content retention, callback replay, deployment, or deletion. Read-only repository inspection and synthetic offline validation do not authorize live vendor actions.

## Failure Modes

- Deleting the vendor transcript does not remove downstream copies.
- PII redaction does not replace consent or authorization.
- A client-side project key is compromised even in a private repository.

## Output

Return the operation scope, environment, region, contract surface, authorization class, model and feature decisions, deterministic validation results, content-free identifiers, risks, cleanup or rollback state, and a concise pass/fail receipt. Exclude credentials, signed URLs, audio, transcript text, prompts, and customer-derived content.

## Example

- Start with the named environment, approved regional host, synthetic fixture identity, and bounded operation budget.
- Finish with safe IDs, contract and assertion counts, terminal state, cleanup status, and the decision owner; never reproduce speech content.

## Validation

Rerun the smallest relevant deterministic check, compare actual state with the requested outcome and current first-party contract, verify sensitive fields are absent from evidence, and confirm rollback, termination, or deletion state before reporting success.

## References

Review the dated first-party evidence map before relying on any model, parameter, limit, price, region, or lifecycle claim.

- [Current first-party evidence map](references/official-docs.md)
Files in this package (2)
  • SKILL.md 4 KB
  • references/official-docs.md 1 KB

Versions

The database has no other skills named assemblyai-security-basics.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 4298e32f0058 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100assemblyai-core-workflow-a
    Analyze and operate a production AssemblyAI pre-recorded pipeline with explicit models, Speech Understanding, callbacks, and retention controls. Use when running asynchronous transcription. Trigger with "AssemblyAI async transcription" or "pre-recorded pipeline".
  • 100assemblyai-prod-checklist
    Analyze and gate an AssemblyAI integration across contracts, security, reliability, cost, observability, retention, and rollback. Use when preparing a launch or material change. Trigger with "AssemblyAI production checklist" or "go live".
  • 100assemblyai-webhooks
    Receive and authenticate AssemblyAI transcript webhooks. Use when setting up an AssemblyAI webhook endpoint, checking the webhook_auth_header_name / webhook_auth_header_value header, debugging 401s on deliveries, or handling completed and error transcript statuses.
  • 100assemblyai-transcription
    Use this skill when an agent needs AssemblyAI for speech-to-text or speech-understanding work in media production, including pre-recorded, synchronous short-file, and real-time streaming transcription; speaker diarization or speaker identification; captions and subtitles;…
  • 100granola-security-basics
    Security best practices for Granola meeting data. Use when implementing security controls, reviewing data handling, or ensuring compliance with security policies. Trigger with phrases like "granola security", "granola privacy", "granola data protection", "secure granola", "granola compliance".
  • 90privacy-retention-and-right-to-delete
    Guides agents through privacy, retention, and deletion workflows in data systems. Use when handling personal data, retention limits, deletion requests, legal holds, or data minimization requirements across pipelines and published datasets.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.