groq-ci-integration

Configure Groq CI/CD integration with GitHub Actions, testing, and model validation. Use when setting up automated testing, configuring CI pipelines, or integrating Groq tests into your build process. Trigger with phrases like "groq CI", "groq GitHub Actions", "groq automated tests", "CI groq".

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

78%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.

Well-structured, actionable content that uses progressive disclosure effectively and includes real validation checkpoints for the CI/release workflow. Main gaps are minor verbosity in transitional prose and an inline workflow skeleton that is not fully copy-paste-ready.

Suggestions

Tighten meta-narration in the Instructions intro (e.g., remove "Read this section for the high-level flow, then drill into...") to improve conciseness.

Add an explicit validate→fix→retry loop for the publish step (e.g., "if the live Groq round-trip fails, fix the key/model and re-run before retrying publish") to push workflow clarity to the top anchor.

Inline at least one complete, copy-paste-ready minimal workflow or link more directly to the exact section in references/implementation.md so the body's job skeleton is executable without hunting.

Dimension	Reasoning	Score
Conciseness	Largely efficient and assumes Claude's competence (no boilerplate explaining GitHub Actions or Groq), but contains light meta-narration like "The integration has four moving parts. Read this section for the high-level flow, then drill into the reference files" that could be trimmed.	4 / 5
Actionability	Provides concrete executable commands ("gh secret set GROQ_API_KEY --body ...", "GROQ_INTEGRATION=1 npx vitest ...") and a workflow skeleton, but the inline YAML job block is a stub with comments rather than copy-paste-ready, with full files deferred to references.	4 / 5
Workflow Clarity	A clear four-step sequence with validation checkpoints present (release gated on a live Groq round-trip, model-check exits non-zero on deprecated IDs, integration tests env-gated), but lacks an explicit validate→fix→retry feedback loop in the step prose despite the batch/destructive-adjacent publish step.	4 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-signaled, one-level-deep references to references/implementation.md and references/examples.md (both real files), with content appropriately split and easy navigation across labeled sections.	5 / 5
	Total	17 / 20 Passed

Description

87%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 strong description that clearly states what the skill does, when to use it, and supplies concrete trigger phrases. Minor weaknesses are slight over-genericity in a couple of named actions and the mildly unnatural "CI groq" trigger.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — "Configure Groq CI/CD integration with GitHub Actions, testing, and model validation" plus "configuring CI pipelines" and "integrating Groq tests" — but the actions are slightly high-level ("testing") rather than fully enumerated, leaving minor coverage gaps.	4 / 5
Completeness	Clearly answers both what ("Configure Groq CI/CD integration with GitHub Actions, testing, and model validation") and when ("Use when setting up automated testing, configuring CI pipelines...") and adds concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Good keyword coverage with explicit trigger phrases ("groq CI", "groq GitHub Actions", "groq automated tests", "CI groq") plus a Use-when clause, though "CI groq" is somewhat unnatural and a few natural synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The "Groq CI/CD integration" niche with Groq-specific triggers ("groq CI", "groq GitHub Actions") is clearly distinct from other skills with minimal overlap risk.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/tons-of-skills-marketplace
Path: plugins/saas-packs/groq-pack/skills/groq-ci-integration/SKILL.md
Commit: 88dcf65

Reviewed: 3 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.