Groq Local Dev Loop

What it does

When your agent uses it

• Setting up a Groq development environment
• Configuring mocked vs live test workflows
• Establishing a fast iteration cycle with Groq
• With phrases like groq dev setup

Example prompts

• “groq dev setup”
• “groq local development”
• “groq dev environment”
• “/groq-local-dev-loop”

Requirements

• Node.js
• A credential in GROQ_API_KEY
• Compatibility (from SKILL.md): Designed for Claude Code
• Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(npm:*), Bash(pnpm:*)

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

1. 1Project structure — create src/groq/{client,models,completions}.ts, tests/, and .env.local / .env.example.
2. 2Package setup — wire dev (tsx watch), test / test:watch (vitest), and test:integration scripts.
3. 3Singleton client — a lazily-memoized getGroqClient() that fails fast when GROQ_API_KEY is missing and a resetClient() for tests.
4. 4Model constants — a MODELS map with DEV_MODEL defaulting to llama-3.1-8b-instant to conserve dev quota.
5. 5Unit tests with mocking — vi.mock("groq-sdk") so unit tests run sub-second with zero API calls.
6. 6Integration tests — guard live-API tests behind GROQ_INTEGRATION=1 with describe.skipIf so the default run stays offline.
7. 7Environment template — commit .env.example, git-ignore .env.local.

What it can do on your machine

Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Write
  • Edit
  • Bash(npm:*)
  • Bash(pnpm:*)

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • npm

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • console.groq.com
  • npmjs.com
  • vitest.dev
  • github.com

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • GROQ_API_KEY

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  Designed for Claude Code

  From compatibility in the SKILL.md frontmatter.

Context cost

Groq Local Dev Loop loads about 1.5k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 88 tokens; SKILL.md has 541 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~88

When it runs · the whole SKILL.md, loaded when a task matches

~1.5k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:42

  git-ignored `.env.local`, and commit only `.env.example` as a template. Never

• NoteMentions a .env fileSKILL.md:43

  hardcode the key or commit `.env.local`.

• NoteMentions a .env fileSKILL.md:51

  ,models,completions}.ts`, `tests/`, and `.env.local` / `.env.example`.

• NoteMentions a .env fileSKILL.md:57

  e** — commit `.env.example`, git-ignore `.env.local`.

• NoteMentions a .env fileSKILL.md:68

  OQ_API_KEY not set. Copy .env.example to .env.local");

• NoteMentions a .env fileSKILL.md:90

  eam, with real secrets in a git-ignored `.env.local`.

• NoteMentions a .env fileSKILL.md:96

  | `GROQ_API_KEY not set` | Missing .env.local | Copy from .env.example |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 541 words, ~1,466 tokens.

name

groq-local-dev-loop

description

Configure Groq local development with hot reload, mocking, and testing. Use when setting up a Groq development environment, configuring mocked vs live test workflows, or establishing a fast iteration cycle with Groq. Trigger with phrases like "groq dev setup", "groq local development", "groq dev environment", "develop with groq".

allowed-tools

Read, Write, Edit, Bash(npm:*), Bash(pnpm:*)

compatibility

Designed for Claude Code

version

1.11.0

license

MIT

author

Jeremy Longshore <jeremy@intentsolutions.io>

tags

saas, groq, testing, workflow

// src/groq/client.ts -- lazily-memoized singleton
import Groq from "groq-sdk";

let _client: Groq | null = null;

export function getGroqClient(): Groq {
  if (!_client) {
    if (!process.env.GROQ_API_KEY) {
      throw new Error("GROQ_API_KEY not set. Copy .env.example to .env.local");
    }
    _client = new Groq({ apiKey: process.env.GROQ_API_KEY, maxRetries: 2, timeout: 30_000 });
  }
  return _client;
}
export function resetClient(): void { _client = null; }

npm run dev                # tsx watch src/index.ts (hot reload)
npm run test:watch         # vitest --watch (mocked, no API calls)
npm run test:integration   # GROQ_INTEGRATION=1 vitest (live API)

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/.curated/groq-local-dev-loop of jeremylongshore/tons-of-skills-marketplace.

• SKILL.md
• references/examples.md
• references/implementation.md

Open the folder on GitHubat commit 80f86df