deepgram-install-auth
Install and configure Deepgram SDK authentication. Use when setting up a new Deepgram integration, configuring API keys, or initializing Deepgram in your project. Trigger: "install deepgram", "setup deepgram", "deepgram auth", "configure deepgram API key", "deepgram credentials".
85
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 a solid skill description with excellent trigger terms and clear 'when' guidance. Its main weakness is that the 'what' could be more specific about the concrete actions performed (e.g., installing packages, setting env vars, initializing the client). Overall it performs well for skill selection purposes.
Suggestions
Expand the capability description with more concrete actions, e.g., 'Installs the Deepgram SDK package, sets environment variables for API keys, and initializes the Deepgram client in your project.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Deepgram SDK) and some actions (install, configure, authentication), but doesn't list multiple concrete actions in detail—e.g., it doesn't specify steps like 'set environment variables, validate API key, initialize client'. | 2 / 3 |
Completeness | Clearly answers both 'what' (install and configure Deepgram SDK authentication) and 'when' (setting up a new integration, configuring API keys, initializing Deepgram) with explicit trigger terms listed. | 3 / 3 |
Trigger Term Quality | Includes a well-curated list of natural trigger terms users would actually say: 'install deepgram', 'setup deepgram', 'deepgram auth', 'configure deepgram API key', 'deepgram credentials'. These cover common variations effectively. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive—focuses specifically on Deepgram SDK setup and authentication, which is a clear niche unlikely to conflict with other skills. The trigger terms are all Deepgram-specific. | 3 / 3 |
Total | 11 / 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 solid, actionable skill with clear step-by-step instructions and executable code for both TypeScript and Python. Its main weakness is moderate verbosity — the API scopes table, production singleton pattern, and resources section inflate the token count beyond what's strictly needed for install and auth. The workflow is well-sequenced with a verification step and comprehensive error handling.
Suggestions
Trim the overview to remove the description of Deepgram's capabilities (STT, TTS, audio intelligence) — Claude doesn't need this context for installation.
Move the API Key Scopes table and production singleton pattern to a separate reference file to keep the core skill lean and focused on basic install/auth.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary content like the API Key Scopes table, the production singleton pattern, and the Resources section with external links that add bulk without being essential for the core install/auth task. The overview sentence explaining what Deepgram provides (STT, TTS, audio intelligence) is unnecessary context for Claude. | 2 / 3 |
Actionability | Every step includes fully executable, copy-paste ready code for both TypeScript and Python. Installation commands, environment variable configuration, client initialization, and verification are all concrete and complete with real import paths and method calls. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from installation through configuration, initialization, verification, and production setup. Step 5 provides an explicit verification checkpoint that validates the API key works before proceeding, and the error handling table provides a clear feedback loop for common failure modes. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but it's somewhat monolithic — the production singleton pattern, API key scopes table, and error handling could be in separate reference files. The 'Next Steps' reference to deepgram-hello-world is good, but there are no bundle files to offload the detailed content to. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.