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".

Quality

82%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

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 correctly 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

64%

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 setup skill with executable code examples for both TypeScript and Python. Its main weaknesses are moderate verbosity (some sections like the single-row API Key Formats table and basic .gitignore template add little value) and the lack of integrated validation feedback loops in the workflow. The error handling table is useful but would be more effective if tied into the verification steps.

Suggestions

Remove or condense the API Key Formats table (single key type doesn't warrant a table) and the .gitignore template to reduce token usage.

Integrate error handling guidance directly into the verification steps (e.g., 'If you see 401, check your key at console.groq.com/keys; if MODULE_NOT_FOUND, re-run install') rather than as a separate section.

Dimension	Reasoning	Score
Conciseness	Generally efficient but includes some unnecessary content: the API Key Formats table adds little value (single row, single key type), the Prerequisites section explains things Claude would know, and the .gitignore template is basic knowledge. The SDK Defaults section noting that GROQ_API_KEY is auto-read is useful, but the comment 'Optional if env var set' is redundant given the preceding sentence.	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. The error handling table maps specific errors to specific solutions.	3 / 3
Workflow Clarity	Steps are clearly sequenced (install → get key → configure env → verify), but there's no explicit validation checkpoint or feedback loop after the environment configuration step. If the verify step fails, there's no 'fix and retry' guidance beyond the error table — the error handling is separated from the workflow rather than integrated into it.	2 / 3
Progressive Disclosure	The content is reasonably structured with clear sections and links to external resources, but it's somewhat long for a setup skill. The TypeScript and Python verification examples could potentially be split or the SDK Defaults/Error Handling could reference separate docs. The 'Next Steps' reference to groq-hello-world is good progressive disclosure.	2 / 3
	Total	9 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 70e9fa4

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.