Voice AI Development
davila7/claude-code-templates
Expert in building voice AI applications - from real-time voice agents to voice-enabled apps.
Makes this agent generate images, transcribe audio, and synthesize speech on the user's own machine through a local Lemonade Server instead of a paid cloud API.
$ npx skills add amd/skills --skill local-ai-use -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install amd/skills local-ai-use --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/amd/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/local-ai-use .claude/skills/local-ai-use && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "local-ai-use" agent skill from https://github.com/amd/skills/tree/main/skills/local-ai-use into .claude/skills/local-ai-use/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-ai-use", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/amd/skills/tree/main/skills/local-ai-useType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add amd/skills --skill local-ai-use -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install amd/skills local-ai-use --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amd/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/local-ai-use .agents/skills/local-ai-use && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "local-ai-use" agent skill from https://github.com/amd/skills/tree/main/skills/local-ai-use into .agents/skills/local-ai-use/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-ai-use", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add amd/skills --skill local-ai-use -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install amd/skills local-ai-use --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amd/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/local-ai-use .cursor/skills/local-ai-use && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "local-ai-use" agent skill from https://github.com/amd/skills/tree/main/skills/local-ai-use into .cursor/skills/local-ai-use/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-ai-use", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/amd/skills.git --path skills/local-ai-use--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add amd/skills --skill local-ai-use -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install amd/skills local-ai-use --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amd/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/local-ai-use .gemini/skills/local-ai-use && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "local-ai-use" agent skill from https://github.com/amd/skills/tree/main/skills/local-ai-use into .gemini/skills/local-ai-use/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-ai-use", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install amd/skills local-ai-useInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add amd/skills --skill local-ai-use -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/amd/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/local-ai-use .github/skills/local-ai-use && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "local-ai-use" agent skill from https://github.com/amd/skills/tree/main/skills/local-ai-use into .github/skills/local-ai-use/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-ai-use", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add amd/skills --skill local-ai-use -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install amd/skills local-ai-use --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amd/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/local-ai-use .opencode/skills/local-ai-use && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "local-ai-use" agent skill from https://github.com/amd/skills/tree/main/skills/local-ai-use into .opencode/skills/local-ai-use/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-ai-use", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
local-ai-useMakes this agent generate images, transcribe audio, and synthesize speech on the user's own machine through a local Lemonade Server instead of a paid cloud API.
Local AI Use is an agent skill from amd/skills. Makes this agent generate images, transcribe audio, and synthesize speech on the user's own machine through a local Lemonade Server instead of a paid cloud API. Use it above all to change that routing persistently, from now on — keep generating pictures locally while chat stays on the cloud; set this workspace up to make images on my own machine — even when the user asks for no image or file in the same breath. Also use it for a single request the user wants done locally, offline, on-device, or kept private…
Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts (for example `.federated.json`, `evals/evals.json` and `reference.md`).
It sits in Media & Creative, covering Text to speech and voice, Transcription and Speech recognition and synthesis. It works with ElevenLabs and OpenAI. The repository describes itself as: Official AMD catalog of AI agent skills. Empower your AI agents with AMD's optimized SW stack. The licence is MIT.
2 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 6c92b41. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonapt-getwingetaptbrewcurlffmpegFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
lemonade-server.aigithub.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
LEMONADE_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Local AI Use loads about 5k tokens when it runs. Until then it costs about 253 tokens; SKILL.md has 2,651 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
t OS-specific command to start it (e.g. `sudo systemctl start`sudo apt-get install`, pass `--no-install` to the setup script and confirm| Ubuntu/Debian | `sudo apt remove lemonade-server` || Ubuntu | `sudo add-apt-repository -y ppa:lemonade-team/stable && sudo apt-get update && sudo apt-get install -y lemonae-sdk/lemonade/releases/latest) and run `sudo installer -pkg Lemonade-<ver>-Darwin.pkg -target /`. |package; add `sudo apt install lemonade-desktop` only if the user wants then, start it via the OS service manager: `sudo systemctl start lemond` (Linux system install) or `systemctl --user startuninstall -e --id AMD.LemonadeServer` / `sudo apt remove lemonade-server` / `brew uninstall --cask lemonade-server`), th| Start it via the OS service manager — `sudo systemctl start lemond` / `systemctl --user start lemond` (Linux), `launchAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from amd/skills at commit 6c92b41, republished under its MIT licence (© amd). 2,651 words, ~5,001 tokens.
.claude/skills/local-ai-use/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.This is a meta-skill. You run it once. After that, every later request that needs image generation, text-to-speech, or speech-to-text uses the local Lemonade Server instead of a cloud API. The agent's own LLM keeps handling text; only the expensive multimodal calls move on-device.
The skill does three things:
lemonade CLI is found, the setup script installs the latest version of
Lemonade on the user's behalf. Modern Lemonade has no serve command — the
Lemonade service (the lemond daemon) auto-starts on install and is managed
by the OS — so the setup script waits for the service and, if it stays down,
prints the exact OS-specific command to start it (e.g. sudo systemctl start lemond on Linux).lemonade status
reports, so a server already running on a non-default port is used as-is
rather than reported missing (13305 is only the fallback).Local AI Use block into the workspace AGENTS.md so the agent
reads the routing rule on every later turn, in Cursor, Claude Code, Codex,
Gemini CLI, and any other agent that respects AGENTS.md.Requires modern Lemonade (v10.1.0 or newer). Modern Lemonade unified everything under one
lemonadeCLI (lemonade status,lemonade pull, ...) driving an always-onlemondservice.lemonadeis the only valid CLI, and this skill installs Lemonade only from the official install paths listed in Step 1a. If an olderlemonadeis already on thePATHit will shadow the modern CLI; uninstall it first (see the removal commands in Step 1a) before running this skill.
Models are not downloaded during setup. Each default model is pulled lazily, on first use, by the routing rule (e.g. the first image request pulls the image model). This keeps setup fast and avoids gigabytes of downloads the user may never need.
Use this skill when all of the following are true:
http://localhost:13305 if it has never been changed).If the user is instead embedding Lemonade as a private subprocess inside
an app installer, do not use this skill; use local-ai-app-integration
instead.
winget on Windows, the ppa:lemonade-team/stable PPA on Ubuntu/Debian, and
the Homebrew cask on macOS (see Step 1a for the fallbacks). The lemond
service auto-starts after install; the script waits for it rather than
launching it. On Linux the install needs sudo. Pass --no-install if the
user wants to install it themselves instead.SD-Turbo if it is not already cached; on
metered or slow links, consider pulling models eagerly after setup (see
lemonade pull in reference.md).lemonade pull
of each model. After that, every modality runs offline.lemonade CLI this
skill targets). Model IDs and system-info fields can change between
releases; confirm against lemonade status and GET /api/v1/models on the
version actually installed rather than assuming this document is current.Run this checklist top to bottom. Track progress against it; do not move on until each step verifies.
[ ] 1. Ensure Lemonade Server is installed and running (auto-install if missing)
[ ] 2. Install the routing rule into the workspace AGENTS.mdOn a managed or shared machine where the agent must not run
sudo apt-get install, pass --no-install to the setup script and confirm
Lemonade is already installed before continuing.
The single command that does both steps in one shot is:
python scripts/setup_local_ai.pyAlways run this script first — even if Lemonade is already installed and the
server is already running, and even before generating a single image. Writing
the routing rule into AGENTS.md is what makes this skill complete; skipping it
because "Lemonade is already up" leaves the workspace unconfigured for future
turns. The script is safe to run in that case: it detects the running service,
skips the install, and just writes the rule.
It auto-installs the latest version of Lemonade if no modern lemonade CLI
is found, waits for the auto-started lemond service, then writes the rule.
The script is idempotent: re-running it on a fully configured workspace is a
no-op apart from a healthcheck. Read the sections below for what to do when
each step fails.
scripts/setup_local_ai.py handles this end to end, but here is what it does
so you can do it by hand or debug it. Pass --no-install when Lemonade is
already managed elsewhere and the agent must not attempt a package install.
1a. Is a modern lemonade CLI installed? Run lemonade status. The check
is by capability, not by name: modern Lemonade prints Server is running...
or Server is not running. If instead you get an "invalid choice" / usage
error, the lemonade on PATH is an old build that predates the unified CLI
(v10.1.0) — do not use it. Remove it, then re-run this skill:
| OS | Uninstall the old build with |
|---|---|
| Windows | winget uninstall -e --id AMD.LemonadeServer, or Settings > Apps > Installed apps > Lemonade Server > Uninstall |
| Ubuntu/Debian | sudo apt remove lemonade-server |
| macOS | brew uninstall --cask lemonade-server, or delete the installed Lemonade.app and its .pkg receipt |
Never try to drive or auto-remove it for the user.
If no lemonade is found at all, install the latest version on the user's
behalf. Use the package manager first; the download is the fallback when the
package manager is absent. Full matrix, including Arch, Fedora, Debian, Snap,
and Docker, is in the install docs.
| OS | Install | Fallback |
|---|---|---|
| Windows | winget install -e --id AMD.LemonadeServer | Download lemonade.msi and run msiexec /i lemonade.msi /qn (silent, per-user, no elevation). |
| Ubuntu | sudo add-apt-repository -y ppa:lemonade-team/stable && sudo apt-get update && sudo apt-get install -y lemonade-server | sudo snap install lemonade-server |
| macOS | brew install --cask lemonade-server | Download Lemonade-<ver>-Darwin.pkg from the latest release and run sudo installer -pkg Lemonade-<ver>-Darwin.pkg -target /. |
The Ubuntu apt package is named lemonade-server, but the CLI it installs is
lemonade. The browser UI is served at http://localhost:13305 with no extra
package; add sudo apt install lemonade-desktop only if the user wants the
desktop frontend.
After a Windows install the CLI lands in %LOCALAPPDATA%\lemonade_server and
is added to the user PATH (new shells only); the setup script probes that
directory so it works in the same run.
1b. Is the service running, and where? Check lemonade status --json,
which answers both at once by printing the bound port ({"port": 13305}). The
lemond service auto-starts on install — there is no lemonade serve in
modern Lemonade.
lemonade status says | Action |
|---|---|
Server is running on port <N> | Use port <N> for every later request and for the rule, even when it is not 13305. Continue to Step 2. |
Server is not running | Wait a few seconds for the auto-started service (the script polls /api/v1/health, re-asking status in case the service comes up on a different port). If it stays down, start it via the OS service manager: sudo systemctl start lemond (Linux system install) or systemctl --user start lemond (per-user install); launchctl load /Library/LaunchDaemons/com.lemonade.server.plist (macOS); the Lemonade tray app or Start-Service lemond (Windows). |
Never treat 13305 as the definition of "running": the port is a config value
(lemonade config set port) that an existing config, another install channel,
or a port conflict all move, so probing only the default reports a healthy
server as missing. Ask status, which resolves the port from the service's UDP
beacon for you — lemonade scan is for finding servers on other machines
(see reference.md), never
for picking the local endpoint. The setup script prefers --host / --port or
LEMONADE_HOST / LEMONADE_PORT over discovery, and bakes whatever it settles
on into the rule; pass both when pointing at another machine, since the CLI
here cannot report a remote service's port.
Only if the automatic install genuinely fails (no apt-get, no sudo,
download blocked) should you stop and point the user at
https://lemonade-server.ai/docs/guide/install/.
The rest of this skill writes the endpoint as http://localhost:13305/api/v1,
the default; substitute the port status reported if it differs. It also
assumes no API key is required (the system-wide server defaults to no auth on
loopback). If the user has set LEMONADE_API_KEY, the routing rule template
in templates/local-ai-rule.md shows where to add the Authorization header.
1c. Are the backends ready per modality? Backend health is per
modality. A working chat or image request does not prove transcription will
work: auto picks a different backend per modality and can silently fall back
for one while having no alternative for another. Before declaring setup
complete, check the actual per-modality state:
lemonade backends --allAny variant the workspace's routing depends on should read installed. If the
only installed variant for a modality is rocm, install the Vulkan variant as
well so auto has somewhere to fall back to (for example,
lemonade backends install whispercpp:vulkan).
Setup does not download these. The installed rule pulls each one the first time that modality is requested. They are the smallest models Lemonade offers per modality, sized to keep token-and-cost savings real on commodity hardware:
| Modality | Model | Size | Why this default |
|---|---|---|---|
| Image generation | SD-Turbo | ~5 GB | Single-step generation, runs on CPU and AMD iGPU/dGPU |
| Text-to-speech | kokoro-v1 | ~0.3 GB | Only TTS model Lemonade currently supports; CPU-only, low latency |
| Speech-to-text | Whisper-Tiny | ~0.1 GB | Smallest Whisper; fast on CPU. Upgrade to Whisper-Large-v3-Turbo if accuracy matters more than latency. |
To write a different model ID into the rule, pass it to the setup script. For example, to make future image requests use SDXL:
python scripts/setup_local_ai.py --image-model SDXL-TurboThat model ID is written into the installed AGENTS.md rule and pulled on its
first use. The same pattern works for --tts-model and --stt-model. For
larger / higher-quality alternatives (SDXL-Turbo, Flux-2-Klein-4B,
Whisper-Large-v3-Turbo), see the
model picker in reference.md.
The rule is a Markdown block stored in templates/local-ai-rule.md.
Append it to the workspace's AGENTS.md (create the file if missing). Both
Cursor and Claude Code load AGENTS.md automatically on every turn, so the
agent will see the rule on its next message without any further setup.
scripts/setup_local_ai.py does this for you. It bakes the selected endpoint
and model IDs into the rule, surrounded by stable markers so re-running the
script replaces the block in place rather than appending a second copy. The
markers look like:
<!-- BEGIN amd-skills:local-ai-use -->
...rule...
<!-- END amd-skills:local-ai-use -->If you write the file by hand, keep those exact markers. The script relies on them for idempotent updates.
If the user's agent only respects a different convention, mirror the same block to:
CLAUDE.md (Claude Code, project-scoped) or ~/.claude/CLAUDE.md (global).cursor/rules/local-ai-use.mdc (Cursor user/project rules)GEMINI.md (Gemini CLI)The rule's content is identical; only the file location changes.
From the next turn onward, the agent reads the rule in AGENTS.md on every
message. The rule explicitly tells the agent:
POST /api/v1/images/generations on the
local server. Do not call any cloud image API and do not use the
built-in GenerateImage tool (that path bills tokens to the cloud
provider).POST /api/v1/audio/speech. Do not call
cloud TTS providers (OpenAI TTS, ElevenLabs, etc.).POST /api/v1/audio/transcriptions. Do
not call cloud transcription providers.The agent's own text reasoning continues to use whatever LLM Cursor / Claude Code / Codex is configured with. This skill does not redirect chat tokens; it only redirects the multimodal calls that would otherwise leave the machine.
| Symptom | Cause | Recovery |
|---|---|---|
lemonade: command not found | CLI not installed | Re-run python scripts/setup_local_ai.py (auto-installs the latest version). If it just installed on Windows, open a new shell so the user PATH refreshes, or the script will find it under %LOCALAPPDATA%\lemonade_server. |
status gives an "invalid choice" / usage error | An old lemonade (pre-v10.1.0) is shadowing the modern CLI | Uninstall it (see the Step 1a table: winget uninstall -e --id AMD.LemonadeServer / sudo apt remove lemonade-server / brew uninstall --cask lemonade-server), then re-run the setup script. |
Requests to http://localhost:13305 are refused, but lemonade status says the server is running | The service is bound to a non-default port (existing config, another install channel, or a port conflict) | Use the port from lemonade status --json and re-run python scripts/setup_local_ai.py so the rule is rewritten with it. Do not start a second server; the running one is fine. |
Server is not running | lemond service stopped | Start it via the OS service manager — sudo systemctl start lemond / systemctl --user start lemond (Linux), launchctl load /Library/LaunchDaemons/com.lemonade.server.plist (macOS), or the tray app / Start-Service lemond (Windows). There is no lemonade serve. |
POST /v1/images/generations returns 404 model not found | Image model not downloaded | lemonade pull SD-Turbo and retry. |
lemonade pull keeps printing Progress: NN% but never finishes | Download target is a bad path (out of space, no write permission, quota, read-only mount). The write error may surface only in the server log while the console keeps showing progress | Check the target and free space first: GET /api/v1/system-info reports models_dir and model_storage.free_bytes. If a pull stalls, read the recent lines of the server log (typically lemonade-server.log in the OS temp dir) for the real error (e.g. a download/write failure like CURL code 23, or an out-of-space message), then point the download at a writable disk with room. |
| Image generation is slow on CPU (~4–5 min) | sd-cpp on CPU backend | Install the GPU backend on supported AMD hardware: lemonade backends install sd-cpp:rocm. |
| Still slow after installing the GPU backend | The backend is installed but not actually engaged; the runtime fell back to CPU silently | An installed state in system-info and a successful rocminfo both still permit a silent CPU fallback. Check real GPU utilisation (gpu_busy_percent) during a request, and confirm the host's GPU driver stack rather than re-installing the backend. |
POST /v1/audio/transcriptions returns 400 unsupported format | Input is not 16 kHz mono WAV | Re-encode with ffmpeg -i in.* -ar 16000 -ac 1 out.wav. |
POST /v1/audio/speech returns 404 | TTS model not downloaded | lemonade pull kokoro-v1. |
| 401 Unauthorized on every request | User has set LEMONADE_API_KEY | Add Authorization: Bearer $LEMONADE_API_KEY to every request and to the rule block. |
Mark this skill complete only when all of the following are true:
lemonade status --json reports the server running, and the port it
reports is the port in the installed rule (13305 unless the service was
configured otherwise).AGENTS.md contains the
amd-skills:local-ai-use block. This is required even when Lemonade was
already installed and running — generating an image alone does not
complete the skill./api/v1/images/generations on the endpoint in the
rule (pulling the model on first use) rather than calling a cloud tool.lemonade backends --all shows installed for every backend variant
this workspace's routing depends on (see Step 1c). Do not treat a working
image or chat path as proof that transcription will work.If any box is unchecked, the user is still paying cloud cost for at least one modality, or a routed modality may fail silently on first use.
For the full model picker, alternate-quality options, the complete endpoint reference, the API-key flow, and the OmniRouter tool definitions you can hand to an agent's tool-calling loop, see reference.md.
© amd, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 6 other files (scripts) in skills/local-ai-use of amd/skills.
Open the folder on GitHubat commit 6c92b41
Local AI Use next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Local AI Use this skillamd/skills | 395 | — | ~5k | Automated safety check: Notes | MIT | |
| Voice AI Developmentdavila7/claude-code-templates | 32k | 5 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Azure AImicrosoft/GitHub-Copilot-for-Azure | 255 | 2 repos | ~852 | Automated safety check: Pass | MIT | |
| Speech To Texttadaspetra/loop | 296 | 3 repos | ~2k | Automated safety check: Pass | MIT | |
| Video Translatorshang-zhu/violin | 1.1k | — | ~1k | Automated safety check: Notes | MIT | |
| Video Productionspeechlab0210/video-production-skill | 105 | — | ~4.1k | Automated safety check: Notes | MIT |
davila7/claude-code-templates
Expert in building voice AI applications - from real-time voice agents to voice-enabled apps.
microsoft/GitHub-Copilot-for-Azure
A skill your agent uses for Azure AI: Search, Speech, OpenAI, Document Intelligence.
tadaspetra/loop
Transcribe audio to text using ElevenLabs Scribe v2. An agent skill from tadaspetra/loop.
shang-zhu/violin
Dub a video into another language and generate subtitles using the default Together + Cartesia stack.
speechlab0210/video-production-skill
AI educational video production pipeline. An agent skill from speechlab0210/video-production-skill.
tadaspetra/loop
Build voice AI agents with ElevenLabs. An agent skill from tadaspetra/loop.
amd/skills
Inspects and tunes the shared-vs-dedicated memory split on AMD Ryzen APUs with unified memory (UMA) so larger LLMs and image-gen models fit on the iGPU, or so reserved GPU memory is returned to the…
amd/skills
Turns a natural-language description of routing intent into a valid Lemonade collection.router policy JSON.
amd/skills
Serves AI models on AMD Instinct GPU hardware using vLLM. An agent skill from amd/skills.
amd/skills
Serves an LLM on a supported AMD EPYC server CPU using vLLM with zentorch, in Docker, Podman, or conda.
amd/skills
Autonomously optimizes end-to-end LLM inference throughput on AMD Instinct GPUs and reports a validated gain, using the Hyperloom multi-agent optimizer.
amd/skills
Benchmarks LLM inference and drives GPU kernel optimization with Magpie.
Works with
Categories
Makes this agent generate images, transcribe audio, and synthesize speech on the user's own machine through a local Lemonade Server instead of a paid cloud API. Local AI Use is an agent skill from amd/skills. Makes this agent generate images, transcribe audio, and synthesize speech on the user's own machine through a local Lemonade Server instead of a paid cloud API.
Local AI Use fits situations like: asks for no image; file in the same breath; A single request the user wants done locally; kept private: transcribe this recording.
Run `npx skills add amd/skills --skill local-ai-use -a claude-code`. Or copy the skill folder (skills/local-ai-use in amd/skills) into .claude/skills/local-ai-use in your project. Claude Code loads it when a task matches its description.
Run `npx skills add amd/skills --skill local-ai-use -a codex`. Or copy the skill folder (skills/local-ai-use in amd/skills) into .agents/skills/local-ai-use in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add amd/skills --skill local-ai-use -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/local-ai-use, .gemini/skills/local-ai-use, .github/skills/local-ai-use and .opencode/skills/local-ai-use in your project.
Going by SKILL.md and its folder, Local AI Use needs Python for the scripts in its folder, the command-line tools its instructions call (python, apt-get, winget, apt, brew and curl) and credentials named LEMONADE_API_KEY. Our summary lists: Python 3; Docker; A credential in LEMONADE_API_KEY.
SKILL.md names 2 domains. As links in the text: lemonade-server.ai and github.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (runs commands with sudo), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Local AI Use is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Local AI Use: Voice AI Development (davila7/claude-code-templates, 32k stars), Azure AI (microsoft/GitHub-Copilot-for-Azure, 255 stars), Speech To Text (tadaspetra/loop, 296 stars) and Video Translator (shang-zhu/violin, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
amd (a GitHub organization) maintains it in amd/skills, which has 395 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.
Source: amd/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.