CtrlK
BlogDocsLog inGet started
Tessl Logo

groq-hello-world

Create a minimal working Groq chat completion example. Use when starting a new Groq integration, testing your setup after installing the SDK, or learning the basic Groq API request/response pattern before building something larger. Trigger with phrases like "groq hello world", "groq example", "groq quick start", "simple groq code".

68

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

A well-organized skill body with fully executable code, clear sequencing, an explicit verification step, and properly structured one-level-deep references. Minor conciseness trims and a more explicit retry checkpoint would lift it further.

Suggestions

Tighten the Output section by replacing the multi-line illustrative response prose with a one-line expected format.

Make the validation/retry loop explicit in the Instructions (e.g., 'If Step 1 errors, match the message to the Error Handling table, fix, and re-run before proceeding to Step 2').

DimensionReasoningScore

Conciseness

Mostly lean with executable code and a compact error table, but a few tokens could be trimmed (the illustrative output prose and the '10-50x faster' speed claim add little actionable value).

4 / 5

Actionability

Fully copy-paste-ready TypeScript code with a concrete model ID, specific install command, env var requirement, and a solution-oriented error table covering common cases.

5 / 5

Workflow Clarity

Clear sequenced flow (prerequisites -> create file -> run to confirm -> extend via references) with an explicit validation step ('run it to confirm your key and SDK work') and an error-recovery table, though the retry loop is implied rather than spelled out as a numbered checkpoint.

4 / 5

Progressive Disclosure

A concise overview with well-signaled one-level-deep references to real files (examples.md, models-and-response.md), each labeled with the specific content it holds; deeper variants are appropriately moved out.

5 / 5

Total

18

/

20

Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed description that clearly states what it does and when to use it, with concrete natural-language trigger phrases and a distinct Groq niche. The only weakness is specificity, which names a single action rather than enumerating multiple concrete capabilities.

Suggestions

Broaden specificity by naming the concrete outcomes produced (e.g., 'create and run a minimal chat completion, verify your API key, and confirm token usage') so the capability list is more comprehensive.

DimensionReasoningScore

Specificity

Names the domain ('Groq chat completion') and one concrete action ('Create a minimal working...example'), but coverage is limited to a single action rather than multiple specific capabilities.

3 / 5

Completeness

Explicitly answers both 'what' (create a minimal Groq chat completion example) and 'when' (starting integration, testing setup, learning the pattern) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Lists four natural trigger phrases ('groq hello world', 'groq example', 'groq quick start', 'simple groq code') users would actually say; good coverage though a few synonyms could be added.

4 / 5

Distinctiveness Conflict Risk

A clear Groq-specific niche with distinct Groq-branded trigger phrases; minimal conflict risk with other skills.

5 / 5

Total

17

/

20

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.