AC Groq API Inference
Build and debug Groq API chat and speech workflows with low-latency routing, structured outputs, and production-safe patterns.
Build and debug Groq API chat and speech workflows with low-latency routing, structured outputs, and production-safe patterns.
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureSoftware developmentAI and agentsPersonal productivitytype and topics are labelled automatically from the skill text
How to improve
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-useSKILL.md:46Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host; quoted — discussed, not commanded)Check `GROQ_API_KEY` first and use `Authorization: Bearer $GROQ_API_KEY` for every request. Use `https://api.groq.com/openai/v1` as the base URL and confirm access with `/models`.
vendor-hostquoted
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "changelog"
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (Groq API Inference) differs from the folder (groq-api)
- 100Tools and files. No external tools needed
- 100Steps. 23 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 1187 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 126: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.