ableton-test-generator
Generate Ableton Live project files (.als) for testing. Use this skill when the user wants to create test .als files with specific configurations (tempo, tracks, clips, devices, etc.). The skill parses user prompts, applies changes via Ableton MCP tools, saves the project using ableton-save skill, and returns the saved file path.
What this skill does
# Ableton Test Generator ## Overview Generate Ableton Live project files (.als) for testing by parsing user prompts, applying changes via Ableton MCP tools, and saving the project. ## Workflow ### 1. Parse User Request Extract from the user's prompt: **File path (required)** - Look for patterns like: - "save to <path>" - "save as <path>" - "output to <path>" - Relative or absolute paths ending in `.als` **Changes to apply (optional)** - Identify: - Tempo changes (e.g., "145 BPM", "tempo 120") - Track creation (e.g., "create 3 MIDI tracks", "add audio track") - Clip creation (e.g., "add clip", "create 4-bar clip") - Device parameters (e.g., "set filter to 500 Hz") - Automation (e.g., "automate volume from -inf to 0 dB") - Other Live set modifications ### 2. Apply Changes Using Ableton MCP Tools Map the parsed changes to the appropriate MCP tools: | Change Type | MCP Tool | |------------|----------| | Tempo | `mcp__AbletonMCP__set_tempo` | | Time signature | `mcp__AbletonMCP__set_signature_numerator`, `mcp__AbletonMCP__set_signature_denominator` | | Create MIDI track | `mcp__AbletonMCP__create_midi_track` | | Create audio track | `mcp__AbletonMCP__create_audio_track` | | Set track name | `mcp__AbletonMCP__set_track_name` | | Create clip | `mcp__AbletonMCP__create_clip` | | Add MIDI notes | `mcp__AbletonMCP__add_notes_to_clip` | | Set device parameter | `mcp__AbletonMCP__set_device_parameter` | | Write automation | `mcp__AbletonMCP__write_automation` | For comprehensive list of all 76 available MCP tools, see `references/ableton-mcp-tools.md`. ### 3. Save the Live Set Use the Skill tool to invoke `ableton-save:save-live-set` with the extracted file path: ``` skill: "ableton-save", args: "<file_path>" ``` ### 4. Return Result Display the saved file path returned by the `ableton-save` skill: ``` Saved test .als file to: <returned_path> ``` ## Error Handling - **Missing file path**: Ask the user to provide the output file path - **Ableton Live not running**: Inform the user that Ableton Live must be running - **Change application failed**: Describe what went wrong and suggest alternatives - **Save failed**: Check the ableton-save skill output for specific error messages ## Examples **Example 1: Simple tempo change** ``` User: "Create a test file with tempo 145 BPM, save to test_als/test.als" Actions: 1. Parse: tempo=145, path="test_als/test.als" 2. Call: mcp__AbletonMCP__set_tempo(tempo=145.0) 3. Call: skill: "ableton-save", args: "test_als/test.als" 4. Return: "Saved test .als file to: /path/to/test.als" ``` **Example 2: Multiple tracks with clips** ``` User: "Create 2 MIDI tracks with clips, tempo 120, save to /tmp/test_set.als" Actions: 1. Parse: tracks=2, clips=yes, tempo=120, path="/tmp/test_set.als" 2. Call: mcp__AbletonMCP__set_tempo(tempo=120.0) 3. Call: mcp__AbletonMCP__create_midi_track(index=-1) 4. Call: mcp__AbletonMCP__create_clip(track_index=0, clip_index=0, length=4.0) 5. Call: mcp__AbletonMCP__create_midi_track(index=-1) 6. Call: mcp__AbletonMCP__create_clip(track_index=1, clip_index=0, length=4.0) 7. Call: skill: "ableton-save", args: "/tmp/test_set.als" 8. Return: "Saved test .als file to: /tmp/test_set.als" ``` ## Resources ### references/ableton-mcp-tools.md Complete reference of all 76 Ableton MCP tools organized by category. Read this file when you need to find specific tools for advanced Live set manipulation. ### scripts/ No scripts required for this skill - all operations are performed through MCP tools. ### assets/ No assets required for this skill.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.