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
Pending
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 well-structured skill description that clearly identifies its niche (Deepgram SDK authentication setup) and provides explicit trigger terms and use-when guidance. Its main weakness is that the capability description could be more specific about the concrete actions performed (e.g., installing packages, setting environment variables, initializing client objects). However, the trigger coverage and completeness are strong.
Suggestions
Expand the capability description with more concrete actions, e.g., 'Installs Deepgram SDK packages, sets up API key environment variables, and initializes the Deepgram client in Python/Node.js projects.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Deepgram SDK) and some actions (install, configure, authenticate), but doesn't list multiple concrete actions in detail—e.g., it doesn't specify which SDKs, environment variable setup, or specific configuration steps. | 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 of how users would phrase this request. | 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 verbosity — it includes production patterns, scope tables, and resource links that could be split into separate files or trimmed. The verification step and error handling table are strong additions that support workflow clarity.
Suggestions
Move the API Key Scopes table, production singleton pattern, and Resources section to a separate reference file to keep SKILL.md focused on the core install/auth workflow.
Trim the Overview paragraph — Claude doesn't need to be told what Deepgram provides (STT, TTS, audio intelligence) for an install/auth skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary content like the API Key Scopes table, the production singleton pattern, and the Resources section which add bulk beyond what's needed for a setup/auth skill. The 'Current State' shell commands are a nice touch but the overall content could be tightened. | 2 / 3 |
Actionability | Every step includes fully executable, copy-paste ready code for both TypeScript and Python. Installation commands, environment variable setup, client initialization, and verification are all concrete and complete. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from installation through verification to production configuration. Step 5 provides an explicit verification checkpoint to confirm the API key works before proceeding, and the error handling table provides clear recovery paths for common failures. | 3 / 3 |
Progressive Disclosure | The content is well-structured 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 the inline content is heavier than ideal for a SKILL.md overview. | 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
c8a915c
- 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.