CtrlK
BlogDocsLog inGet started
Tessl Logo

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

73

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and clearly sequenced with a built-in verification step, and it is well-organized for a self-contained install/auth skill. Its main weakness is mild verbosity — a marketing line and a redundant single-row key-format table that could be trimmed.

Suggestions

Remove the marketing clause "ultra-fast LLM inference on custom LPU hardware" from the Overview; keep only the API endpoint fact needed for the task.

Collapse the single-row "API Key Formats" table and its follow-up paragraph into one sentence (e.g. "Groq uses a single `gsk_` key with full API access; restrict via console org controls."), since a one-row table adds no structuring value.

Trim the "SDK Defaults" section's repeated apiKey note, since auto-reading GROQ_API_KEY is already implied by Step 3's environment setup.

DimensionReasoningScore

Conciseness

The body is mostly efficient but includes padding such as the marketing line "Groq provides ultra-fast LLM inference on custom LPU hardware" and a one-row "API Key Formats" table followed by prose restating that there is a single key type — fitting the 'mostly efficient but could be tightened' anchor rather than the every-token-earns-its-place level 3.

2 / 3

Actionability

It provides copy-paste-ready, fully executable guidance — `npm install groq-sdk`, `pip install groq`, `export GROQ_API_KEY=...`, and complete TypeScript and Python verify scripts — matching the executable-code anchor rather than the pseudocode level 2.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced with an explicit verification checkpoint (Steps 4–5 verify the connection), and the operation is non-destructive so the destructive-ops cap does not apply; this matches the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

No bundle files exist, so the skill is self-contained with well-organized single-level sections (Overview, Prerequisites, Instructions, Error Handling, Resources); for this scoped single-purpose skill that warrants a 3 rather than the monolithic or poorly-signaled level 2.

3 / 3

Total

11

/

12

Passed

Description

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.

The description is well-crafted: concrete actions, explicit Use-when triggers, natural trigger phrases, and a distinct Groq-specific niche. It closely matches the rubric's good examples with no notable fluff or over-claims.

DimensionReasoningScore

Specificity

"Install and configure Groq SDK authentication for TypeScript or Python" names multiple concrete actions (install SDK, configure API key auth, initialize groq-sdk) and pins the languages, matching the 'lists multiple specific concrete actions' anchor rather than the partial domain-only level 2.

3 / 3

Completeness

It answers both what ("Install and configure Groq SDK authentication...") and when ("Use when setting up a new Groq integration, configuring API keys, or initializing the groq-sdk"), satisfying the explicit what-AND-when anchor; the missing-Use-when cap of 2 does not apply.

3 / 3

Trigger Term Quality

Explicit natural triggers "install groq", "setup groq", "groq auth", "configure groq API key" are phrases a user would realistically say, giving good coverage rather than the missing-variations level 2.

3 / 3

Distinctiveness Conflict Risk

The Groq-specific niche and Groq-branded triggers make conflict with other skills unlikely, fitting the clear-niche anchor rather than the overlapping level 2.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.