shipshitdev/mongodb-atlas-checker
bundles/infrastructure/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.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library mongodb-atlas-checkerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 6:38 AM153.5s3 files scanned
SKILL.md
- name:
- mongodb-atlas-checker
- description:
- 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.
- version:
- 1.0.0
- tags:
- mongodb, atlas, database, backend, nestjs, nextjs
MongoDB Atlas Checker
Verify MongoDB Atlas setup and configuration. Identifies configuration issues, missing environment variables, incorrect connection strings, and ensures proper database setup.
When to Use
- Verifying MongoDB Atlas backend setup
- Checking connection string configuration
- Validating environment variable setup
- Troubleshooting database connection issues
- Auditing database setup before deployment
Quick Checklist
1. Environment Variables
- [ ]
MONGODB_URIexists (not hardcoded) - [ ] Uses
mongodb+srv://protocol (required for Atlas) - [ ] Includes database name
- [ ] Includes
retryWrites=true&w=majority - [ ] No credentials in
.env.example
2. Connection String Format
mongodb+srv://<username>:<password>@<cluster-host>/<database>?retryWrites=true&w=majority
3. Driver Installation
- [ ]
mongooseormongodbpackage installed - [ ] In dependencies (not devDependencies)
4. Connection Setup
- [ ] Singleton pattern (Next.js)
- [ ]
MongooseModule.forRoot()(NestJS) - [ ] Error handling implemented
5. Atlas Configuration
- [ ] IP whitelist configured
- [ ] Database user exists with permissions
- [ ] SSL/TLS enabled (default with
mongodb+srv://)
Common Issues
| 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 |
Recommended Connection Options
{
retryWrites: true,
w: 'majority',
maxPoolSize: 10,
serverSelectionTimeoutMS: 5000,
bufferCommands: false,
}
For detailed setup patterns, verification scripts, and complete examples: references/full-guide.md
Related Skills
shipshitdev/worktree
development
VerifiedTrustedCommunity
Create an isolated git worktree from the correct base branch and check it out into a clean, gitignored directory. Use when the user asks to make a worktree, spin up a parallel/isolated workspace, work on something without disturbing the current checkout, branch off the current work, or run multiple agents on the same repo at once. Picks the base branch smartly — the current feature branch when you are on one, otherwise the develop integration branch — so worktrees continue your in-progress work by default instead of forking from the wrong place.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/release-cleanup
development
VerifiedTrustedCommunity
Verify a release was fully promoted through develop, staging, and master/main, then prune merged local and remote branches and stale git worktrees. Squash-merge aware — uses GitHub PR merge state as the merge oracle, not commit ancestry. Use when the user asks to clean up branches after a deploy, prune worktrees, remove merged branches, tidy up after promoting develop to staging to master, or confirm nothing stale was left behind before pruning.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/finishing-a-development-branch
development
VerifiedTrustedCommunity
Structured "done coding, now what?" workflow: verify tests pass, detect the repository environment (normal repo vs worktree, named branch vs detached HEAD), present exactly the right merge / PR / keep / discard options, and execute the chosen path including safe worktree cleanup. Use when implementation is complete and the branch needs to be integrated, published, or abandoned.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/feature-intake
tools
VerifiedTrustedCommunity
Capture a client or stakeholder feature request, turn it into a planner-ready PRD epic with scoped sub-issues, check for duplicate work, and place approved issues on a GitHub Projects kanban. Use when a user invokes feature intake, asks to turn a rough client requirement into GitHub issues, or wants an idea written as a PRD and pushed to a board.
27SKILL.mdUpdated Jun 13, 2026