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 an excellent skill description that clearly defines its scope (Groq SDK installation and authentication), specifies supported languages, provides explicit 'Use when' guidance, and includes natural trigger phrases. It follows third-person voice and is concise without being vague. It serves as a strong example of a well-crafted skill description.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: install, configure, authenticate, 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 contextual terms like 'groq-sdk', 'API keys', 'TypeScript', 'Python'. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific SDK (Groq), specific task (installation and auth configuration), and specific languages. Very unlikely to conflict with other skills unless there's another Groq-specific skill. | 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 single-row table, Prerequisites, Resources) add limited value for Claude and could be trimmed or externalized. The verification steps serve as effective validation checkpoints for the auth setup process.
Suggestions
Remove or condense the API Key Formats table (single-row table with minimal information) and fold the key insight ('all keys have full access') into the Step 2 note.
Trim the Prerequisites section — Claude knows what Node.js and pip are; just note the minimum versions inline if critical.
Consider moving Resources and .gitignore template to a bundle reference file to keep the main skill leaner.
| 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 section add marginal value for a skill targeting Claude. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code for both TypeScript and Python, specific bash commands for installation and environment setup, and concrete verification scripts that confirm the connection works. The error handling table maps specific errors to specific solutions. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced (install → get key → configure env → verify), and the verification step serves as an explicit validation checkpoint. For a setup/auth skill, this is a complete workflow with a clear success signal (listing available models confirms auth works). | 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 error handling table, SDK defaults, API key formats, resources, and .gitignore template could be split into referenced files or trimmed. The 'Next Steps' reference to groq-hello-world is good but there's no bundle to support deeper navigation. | 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
a04d1a2
- 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.