_check-deps

Validate Next.js project environment variables and configuration files against cloud dependency patterns.

34|6|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/flavien-ia/hypervibe-harness --skill check-deps-flavien-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _check-deps
Source: https://github.com/flavien-ia/hypervibe-harness/tree/main/skills/_check-deps
Command: npx skills add https://github.com/flavien-ia/hypervibe-harness --skill check-deps-flavien-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the guesswork of verifying project configurations by programmatically checking if cloud dependencies like databases, authentication, and storage are correctly wired and not just using local placeholders.

Core Features & Use Cases

  • Dependency Validation: Automatically detects if services like Stripe, Resend, or Cloudflare are properly configured with real keys.
  • Environment Analysis: Merges local and Vercel environment variables to provide an accurate view of the project's production readiness.
  • Use Case: Before deploying or adding a new feature, use this skill to ensure your database connection string is pointing to a live cloud instance rather than a local development environment.

Quick Start

Use the check deps skill to verify that the database and email service are correctly configured for the current project.

Frequently Asked Questions about _check-deps

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

FAQPage Schema
How do I verify cloud infrastructure configuration before deploying a Next.js project?

To verify cloud infrastructure configuration before deployment, you can run heuristic-based validation scripts that check environment variables against known cloud dependency patterns and return a structured JSON status report identifying misconfigured services.

How can I check if my environment variables are using local placeholders instead of real cloud service keys?

Checking environment variables for local placeholders involves analyzing configuration files to detect if services like Stripe, Resend, or Cloudflare are properly wired with real keys instead of local development placeholders.

Does the dependency validation process require a specific runtime environment?

The dependency validation process requires a Node.js runtime environment to execute its heuristic-based verification scripts on local Next.js-style projects and generate accurate infrastructure status reports.

What is the best way to validate database connection strings for production readiness?

Validating database connection strings for production readiness is best achieved by merging local and Vercel environment variables to provide an accurate view of whether the database is pointing to a live cloud instance.

Can I analyze Vercel environment variables alongside local configurations for deployment validation?

You can analyze Vercel environment variables alongside local configurations to perform deployment validation, merging both sets of environment variables to ensure accurate production readiness checks for your cloud dependencies.

Why does my project health validation fail to detect misconfigured authentication providers?

Project health validation might fail to detect misconfigured authentication providers if the verification scripts are not run in the required Node.js runtime or if the configuration files do not match known cloud dependency patterns.