skills/mongodb-atlas-checker/SKILL.md
Verify MongoDB Atlas setup and configuration for backend applications. Checks connection strings, environment variables, connection pooling, and ensures proper setup for Next.js and NestJS applications. Use when verifying MongoDB Atlas setup, checking connection strings or environment variables, or troubleshooting database connection issues before deployment.
npx skillsauth add shipshitdev/library mongodb-atlas-checkerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
MONGODB_URI exists (not hardcoded)mongodb+srv:// protocol (required for Atlas)retryWrites=true&w=majority.env.examplemongodb+srv://USERNAME:PASSWORD@CLUSTER-HOST/DATABASE?retryWrites=true&w=majority
mongoose or mongodb package installedMongooseModule.forRoot() (NestJS)mongodb+srv://)| Issue | Solution |
|-------|----------|
| Missing MONGODB_URI | Add to .env.local or .env |
| Wrong protocol | Use mongodb+srv:// not mongodb:// |
| Multiple connections (Next.js) | Use singleton pattern |
| Connection timeout | Check IP whitelist in Atlas |
| Auth failed | Verify credentials, URL-encode special chars |
{
retryWrites: true,
w: 'majority',
maxPoolSize: 10,
serverSelectionTimeoutMS: 5000,
bufferCommands: false,
}
For detailed setup patterns, verification scripts, and complete examples: references/full-guide.md
development
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.