One consolidated Kiro power for ElevenLabs developer workflows.
This repository is a documentation-only power: a single root POWER.md plus capability-specific files in steering/. There is no mcp.json in this repo.
POWER.md into the initial context window.steering/.The installation and setup guidance now lives in one place: the root POWER.md. Capability-specific behavior stays in separate steering files so Kiro can retrieve a smaller, more targeted context set.
Install this repository from:
When installing from disk, select the repository root as the local power path.
Most workflows require:
export ELEVENLABS_API_KEY="your-api-key"
Get the key from ElevenLabs API Keys.
For JavaScript, use @elevenlabs/elevenlabs-js, not the legacy elevenlabs package.
Use TESTING.md for the manual validation matrix covering setup and every routed capability in this power.
MIT
4 commits
One consolidated Kiro power for ElevenLabs developer workflows.
This repository is a documentation-only power: a single root POWER.md plus capability-specific files in steering/. There is no mcp.json in this repo.
POWER.md into the initial context window.steering/.The installation and setup guidance now lives in one place: the root POWER.md. Capability-specific behavior stays in separate steering files so Kiro can retrieve a smaller, more targeted context set.
Install this repository from:
When installing from disk, select the repository root as the local power path.
Most workflows require:
export ELEVENLABS_API_KEY="your-api-key"
Get the key from ElevenLabs API Keys.
For JavaScript, use @elevenlabs/elevenlabs-js, not the legacy elevenlabs package.
Use TESTING.md for the manual validation matrix covering setup and every routed capability in this power.
MIT
4 commits