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

82%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Discovery

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.

This is a strong skill description that clearly defines its scope (Groq deployment to specific platforms), provides explicit trigger guidance with natural user phrases, and distinguishes itself well from both generic deployment skills and other Groq-related skills. The description is concise, uses third-person voice, and covers all key dimensions effectively.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and platforms: deploying to Vercel, Cloud Run, and containerized platforms; configuring platform-specific secrets; setting up deployment pipelines.	3 / 3
Completeness	Clearly answers both 'what' (deploy Groq integrations to specific platforms, configure secrets, set up pipelines) and 'when' (explicit 'Use when' clause plus 'Trigger with phrases like' providing concrete trigger terms).	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say: 'deploy groq', 'groq Vercel', 'groq production deploy', 'groq Cloud Run', 'groq Docker'. These are realistic phrases a user would type.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: Groq-specific deployment across named platforms. The combination of 'Groq' with specific deployment targets (Vercel, Cloud Run, Docker) makes it very unlikely to conflict with generic deployment or generic Groq skills.	3 / 3
	Total	12 / 12 Passed

Implementation

64%

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

The skill provides excellent actionable, executable code for multiple deployment platforms, which is its primary strength. However, it suffers from redundancy (streaming implemented three times), misleading sequential step numbering for what are actually independent deployment options, and lack of validation/verification steps after deployments. The content would benefit from being restructured as an overview with platform-specific details in separate files.

Suggestions

Restructure steps as independent deployment options (not sequential steps 1-6) and add validation checkpoints after each deployment (e.g., 'Verify: curl https://your-app.vercel.app/health')

Extract platform-specific deployment details into separate referenced files (e.g., VERCEL.md, DOCKER.md, CLOUD-RUN.md) and keep SKILL.md as a concise overview with the env var table and error handling

Remove redundant streaming implementations — show streaming once in a shared pattern, then reference it from platform-specific sections

Remove the marketing language ('sub-200ms latency makes it ideal for edge deployments') as it doesn't help Claude deploy anything

Dimension	Reasoning	Score
Conciseness	The skill includes substantial executable code which is valuable, but there's redundancy — streaming logic is implemented three times (Edge function, Express server, AI SDK). The Express server example is quite long and could be trimmed. The overview line about 'sub-200ms latency' is marketing fluff Claude doesn't need.	2 / 3
Actionability	All code examples are fully executable and copy-paste ready — TypeScript route handlers, Dockerfiles, bash deployment commands, and Express servers are all concrete and complete. The environment variable table and error handling table provide specific, actionable guidance.	3 / 3
Workflow Clarity	The steps are numbered but don't form a coherent sequential workflow — they're really independent deployment options (Vercel, Docker, Cloud Run) labeled as steps 1-6. There are no validation checkpoints (e.g., verify deployment succeeded, test the endpoint, validate secrets are set correctly) which is important for deployment operations.	2 / 3
Progressive Disclosure	The content is mostly monolithic with all deployment options inline. The three streaming implementations could be in separate referenced files (e.g., VERCEL.md, DOCKER.md, CLOUD-RUN.md). The reference to 'groq-multi-env-setup' at the end is good but the main body is too long for an overview skill.	2 / 3
	Total	9 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 4dee593

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