require-api-key

Verifies working LLM and service API credentials before any pipeline stage runs.

1|9|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill require-api-key-agenticgogol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: require-api-key
Source: https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul/tree/main/.claude/skills/require-api-key
Command: npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill require-api-key-agenticgogol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects in this repo call real model providers with no mock mode, so building anything without a verified API key wastes effort and fails late. This Skill hard-stops the pipeline until every required credential is confirmed working with a real API call. ## Core Features & Use Cases - Credential Presence Check: Scans .env for provider keys such as ANTHROPIC_API_KEY, OPENAI_API_KEY, or GROQ_API_KEY before design or code work begins. - Live Verification Call: Makes one small real API call through the project's own client path to confirm a present key actually works, rather than assuming it does. - Extended Credential Gating: Applies the same hard-stop verification to non-LLM credentials like QDRANT_URL/QDRANT_API_KEY or tokens behind MCP servers. - Use Case: After confirming a project brief, run this gate first so a missing or expired OpenAI key stops the pipeline immediately with clear setup instructions instead of failing mid-build. ## Quick Start Run the require-api-key gate to verify my configured provider key works before starting the design phase.

Frequently Asked Questions about require-api-key

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify an API key works before running a pipeline?▼

Make one small, cheap real API call, such as a 1-token completion, using the exact client the project will use. A key present in .env is not proof it works; only a successful live call confirms validity.

Which API keys does the pipeline check for?▼

It checks .env for at least one of ANTHROPIC_API_KEY, OPENAI_API_KEY, or GROQ_API_KEY, or whichever provider the design specifies. It also verifies non-LLM credentials like QDRANT_URL/QDRANT_API_KEY or tokens behind MCP servers.

What happens if no API key is configured?▼

The pipeline stops immediately and tells you exactly which variables to set in .env and where to obtain a key. No design document, code, or placeholder stubs are created, since this repo has no mock mode.

Why does my pipeline fail even though an API key is set?▼

A present key can still be expired, revoked, rate-limited, or lack quota or permissions. The verification call surfaces the exact provider error, and the pipeline stops until a working key replaces it.

Do MCP server credentials need the same verification as LLM keys?▼

Yes. An MCP server whose underlying service needs a token, such as GitHub or Slack, gets the same hard-stop treatment. Each such credential is verified with its own real call before work proceeds.