groq-install-auth
Install and configure Groq SDK authentication for TypeScript or Python. Use when setting up a new Groq integration, configuring API keys, or initializing the groq-sdk in your project. Trigger with phrases like "install groq", "setup groq", "groq auth", "configure groq API key".
71
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
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 a well-crafted skill description that clearly defines its scope (Groq SDK installation and authentication), specifies the target languages, provides explicit 'Use when' guidance, and includes natural trigger phrases. It follows third-person voice and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: install, configure authentication, set up SDK for specific languages (TypeScript/Python). These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (install and configure Groq SDK authentication for TypeScript or Python) and 'when' (setting up a new Groq integration, configuring API keys, initializing groq-sdk), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'install groq', 'setup groq', 'groq auth', 'configure groq API key', plus mentions of 'Groq SDK', 'API keys', 'groq-sdk', and language names. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific SDK (Groq), specific task (installation and auth configuration), and specific languages. Unlikely to conflict with other skills unless there are multiple Groq-related skills. | 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 solid, actionable skill with clear step-by-step workflow and executable code for both TypeScript and Python. Its main weakness is moderate verbosity — several sections (API Key Formats table with one row, detailed Prerequisites, Resources list) add tokens without proportional value for Claude. The workflow is well-sequenced with verification steps and error recovery guidance.
Suggestions
Remove or condense the API Key Formats table — a single sentence ('All keys use the `gsk_` prefix with full API access') replaces the entire table.
Trim Prerequisites to just the non-obvious items; Claude knows what npm and pip are and doesn't need version requirements for basic SDK installation.
Consider consolidating the Resources section into inline links where they're first relevant rather than a separate section at the end.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary elements: the API Key Formats table adds little value (single row, single key type), the Prerequisites section explains things Claude would know, and the SDK Defaults section partially repeats what's shown in the verify step. The .gitignore template and Resources sections add marginal value. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code for both TypeScript and Python, concrete bash commands for installation and environment setup, and specific URLs for obtaining API keys. The verification scripts are complete and runnable. | 3 / 3 |
Workflow Clarity | Clear sequential steps from installation through verification, with explicit validation via the verify connection steps (Steps 4/5) that confirm the setup works. The error handling table provides a feedback loop for common failure modes with specific solutions. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's somewhat long for a single-file skill with no bundle. The SDK Defaults, API Key Formats, Error Handling, and Resources sections could potentially be separated or trimmed. The reference to 'groq-hello-world' as a next step is a good navigation signal. | 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
8a9cd04
- 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.