elevenlabs-agents
Build conversational AI voice agents with ElevenLabs Platform. Configure agents, tools, RAG knowledge bases, agent versioning with A/B testing, and MCP security. React, React Native, or Swift SDKs. Prevents 34 documented errors. Use when: building voice agents, AI phone systems, agent versioning/branching, MCP security, or troubleshooting @11labs deprecated, webhook errors, CSP violations, localhost allowlist, tool parsing errors.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill elevenlabs-agentsOverall
score
87%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific capabilities, includes a comprehensive 'Use when' clause with natural trigger terms, and is highly distinctive to the ElevenLabs voice agent domain. The inclusion of specific error types and SDK names makes it particularly effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Configure agents, tools, RAG knowledge bases, agent versioning with A/B testing, and MCP security' plus specific SDKs (React, React Native, Swift) and mentions '34 documented errors'. | 3 / 3 |
Completeness | Clearly answers both what ('Build conversational AI voice agents with ElevenLabs Platform' plus specific capabilities) AND when (explicit 'Use when:' clause with multiple trigger scenarios including building, troubleshooting, and specific error types). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'voice agents', 'AI phone systems', 'agent versioning', 'MCP security', '@11labs deprecated', 'webhook errors', 'CSP violations', 'localhost allowlist', 'tool parsing errors' - these are specific, searchable terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: ElevenLabs-specific, voice agents, specific error types like '@11labs deprecated' and 'CSP violations'. Very unlikely to conflict with other skills due to platform-specific terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and comprehensive skill for building ElevenLabs voice agents, with excellent executable code examples and thorough error documentation. The main weakness is its length - at ~1500 lines, it would benefit from splitting detailed reference material (errors, webhook schemas, API endpoints) into separate files while keeping the SKILL.md as a focused overview with navigation.
Suggestions
Move the 34 documented errors to a separate ERRORS.md file, keeping only the 5-10 most critical errors inline with links to the full reference
Extract webhook payload schemas and examples to a WEBHOOKS.md reference file
Consider splitting API/SDK reference details into SDK-REFERENCE.md to reduce main file length by ~40%
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | While the skill is comprehensive and avoids explaining basic concepts Claude knows, it's quite verbose at ~1500 lines. Some sections like the overview could be tighter, and the extensive error documentation (34 errors) could be moved to a separate reference file. | 2 / 3 |
Actionability | Excellent actionability with copy-paste ready code examples throughout, specific package versions, concrete CLI commands, and executable TypeScript/JSON snippets. Error solutions include exact code fixes and workarounds. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints. The CLI workflow, testing framework, and agent versioning sections show clear step-by-step flows. Error recovery paths are documented with specific solutions. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but the document is monolithic. The 34 documented errors, detailed webhook payload examples, and extensive API reference could be split into separate files with clear navigation links. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1378 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.