Individual skill
assemblyai-sdk-patterns
Analyze and design a typed AssemblyAI adapter that isolates SDK drift, regional routing, polling, and streaming lifecycles. Use when integrating an official SDK. Trigger with "AssemblyAI SDK pattern", "AssemblyAI adapter", or "wrap AssemblyAI".
plugins/saas-packs/assemblyai-pack/skills/assemblyai-sdk-patterns/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,916
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- assemblyai Declared skill tag
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,180 bytesreferences/official-docs.mddoc · 1,386 bytes
Read excerpt
# AssemblyAI Typed Adapter Boundary
## Overview
Design a narrow application-owned boundary around the current SDK. Keep data, credentials, region, retries, spend, and destructive state separately governed.
## 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
Pre-recorded jobs, Streaming v3 sessions, temporary-token issuance, webhooks, and LLM Gateway requests have different lifecycles. Keep vendor objects behind a narrow application-owned port. New code must not expose legacy LeMUR methods or Streaming v2 service names.