groq-deploy-integration

Deploy Groq integrations to Vercel, Cloud Run, and containerized platforms. Use when deploying Groq-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy groq", "groq Vercel", "groq production deploy", "groq Cloud Run", "groq Docker".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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 with executable code for multiple platforms, but it is verbose with redundant streaming implementations, lacks validation checkpoints around risky production deployments, and is a monolithic single file with no progressive disclosure into bundle references.

Suggestions

Add explicit validation/verification checkpoints after each deployment step (e.g. 'vercel inspect <url>' or 'gcloud run services describe' to confirm the deploy succeeded before proceeding).

Consolidate the three near-duplicate streaming chat examples (Vercel Edge, Express, AI SDK) into one canonical implementation plus brief variants, or move the extra variants into a references/ file to reduce redundancy.

Split the per-platform deployment recipes (Vercel, Docker, Cloud Run) into separate reference files under references/ and keep SKILL.md as a concise overview with clearly signaled links.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable code and tables that earn their place, but it carries mild marketing prose ('Groq's sub-200ms latency makes it ideal for edge deployments and real-time applications') and three near-duplicate streaming chat implementations (Vercel Edge, Express, AI SDK) that could be tightened. Not score 3 because of this redundancy and fluff; not score 1 because it avoids explaining concepts Claude already knows.	2 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript, Dockerfile, and shell commands (e.g. 'vercel env add GROQ_API_KEY production', 'gcloud run deploy groq-api --source .') with specific flags and model names. Not score 2 because guidance is complete and concrete rather than pseudocode.	3 / 3
Workflow Clarity	Steps are numbered and sequenced (Step 1–6), but production deploys and secret management are risky operations with no validation or verification checkpoints (no 'confirm deploy succeeded' or 'verify secret' step). Per the rubric, missing validation in destructive/risky workflows caps this at 2; not score 1 because the sequence is present and clear.	2 / 3
Progressive Disclosure	No bundle files exist and the entire ~240-line skill is inline in SKILL.md, with full per-platform code examples that could be split into references. There is section structure and external resource links, but content that should be separate remains inline. Not score 3 because it is a monolithic single file well over the simple-skill threshold; not score 1 because sections are organized and references are not deeply nested.	2 / 3
	Total	9 / 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 strong across all dimensions: it states concrete actions, provides explicit 'Use when' trigger guidance with natural keyword phrases, and occupies a clearly distinct niche. Third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Deploy Groq integrations to Vercel, Cloud Run, and containerized platforms', 'configuring platform-specific secrets', 'setting up deployment pipelines' — matching the anchor for listing multiple specific concrete actions.	3 / 3
Completeness	Clearly answers both what ('Deploy Groq integrations to Vercel, Cloud Run, and containerized platforms') and when ('Use when deploying Groq-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines') with explicit triggers present.	3 / 3
Trigger Term Quality	Explicit natural trigger phrases ('deploy groq', 'groq Vercel', 'groq production deploy', 'groq Cloud Run', 'groq Docker') give good coverage of terms a user would actually say; not score 2 because common variations are well covered rather than missing.	3 / 3
Distinctiveness Conflict Risk	The Groq-plus-specific-deployment-platforms niche with distinct 'groq' trigger phrases is unlikely to conflict with unrelated skills; not score 2 because the scope is narrowly scoped rather than overlapping.	3 / 3
	Total	12 / 12 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/claude-code-plugins-plus-skills
Commit: 6e3a65f

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.