Skip to main content
skill CX Codex

705-technologies-nosql-mongodb — Claude Code skill

705-technologies-nosql-mongodb — a skill for Claude Code, Codex, Cursor, GitHub Copilot and Gemini CLI that covers MongoDB at the database layer, independent of Spring Boot, Quarkus or Micronaut.

Apache-2.0 216 installs ★ 465 updated 2026-10-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jabrena/plinth --skill 705-technologies-nosql-mongodb -a claude-code
Open on GitHub

What 705-technologies-nosql-mongodb does

Part of the Plinth Toolkit, this skill runs across Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. It keeps the agent focused at the database layer: document modeling for aggregates, embedded documents, references, and bounded arrays; JSON Schema validation and schema evolution; index strategy covering compound, covering, partial, TTL, and unique constraints; aggregation pipelines with stage ordering, $match pushdown, and memory controls.

Before marking a query optimised, the skill checks explain() plans, scanned-to-returned ratios, sort coverage and index selectivity. Concatenating untrusted input into query documents, aggregation stages or $where expressions is prohibited — only driver query builders and validated parameters are accepted. Any Maven changes in the same changeset trigger ./mvnw compile first.

Framework integrations stay out of scope by design: Spring MongoDB goes to @315-frameworks-spring-mongodb, Quarkus MongoDB to @415-frameworks-quarkus-mongodb, Micronaut MongoDB to @515-frameworks-micronaut-mongodb. Missing topology details — shard config, read/write concern, data volume — cause the skill to ask a clarifying question rather than guess at a recommendation.

What it helps with

  • design a MongoDB document schema for aggregates with nested arrays
  • audit collection indexes and spot missing or redundant ones
  • rewrite an aggregation pipeline with correct $match pushdown
  • evaluate consistency and transaction trade-offs for a given workload
  • add JSON Schema validation without a breaking schema change

Example prompts for the agent

  • Design a document schema for an orders collection with embedded line items
  • Review the indexes on this collection and explain the explain() plan for the query
  • Rewrite this aggregation pipeline: fix stage ordering and push $match to the front

How to install 705-technologies-nosql-mongodb

1Skills CLI (Vercel)

npx skills add jabrena/plinth --skill 705-technologies-nosql-mongodb -a claude-code

2Manually: put the files in place

~/.claude/skills/705-technologies-nosql-mongodb/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/705-technologies-nosql-mongodb/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about 705-technologies-nosql-mongodb

How do I install 705-technologies-nosql-mongodb in Claude Code?

Run npx skills add jabrena/plinth --skill 705-technologies-nosql-mongodb -a claude-code in your terminal. The skill lands at ~/.claude/skills/705-technologies-nosql-mongodb/SKILL.md.

What does the 705-technologies-nosql-mongodb skill do?

It guides the agent through MongoDB schema design, indexes, aggregation pipelines, transactions and query safety — without pulling in a Java framework. Spring Boot, Quarkus and Micronaut integrations are handled by separate skills.

How do I install 705-technologies-nosql-mongodb in GitHub Copilot?

Run gh skill install jabrena/plinth 705-technologies-nosql-mongodb. The skill is placed at .github/skills/705-technologies-nosql-mongodb/SKILL.md.

Source text

SKILL.md · Apache-2.0
---
name: 705-technologies-nosql-mongodb
description: Use when you need framework-agnostic MongoDB and non-relational database query guidance — document schema design, collection modeling, JSON Schema validation, indexes, aggregation pipelines, query performance, consistency trade-offs, transactions, and operational safety — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Design MongoDB document schemas; Review MongoDB queries and indexes; Improve aggregation pipeline performance; Model non-relational data access patterns; Review NoSQL consistency and transaction trade-offs. Part of Plinth Toolkit
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# Non-relational database query best practices

Help teams design maintainable, secure, and performant **MongoDB and non-relational database queries** for Java applications.

**What is covered in this Skill?**

- Document modeling for aggregates, embedded documents, references, arrays, and bounded growth
- MongoDB JSON Schema validation and compatibility-aware schema evolution
- Query design: explicit predicates, projections, sort stability, pagination, collation, and read concerns
- Index strategy: compound indexes, covering queries, partial indexes, TTL indexes, unique constraints, and lifecycle review
- Aggregation pipelines: stage ordering, `$match` pushdown, `$project`, `$lookup`, `$unwind`, `$group`, and memory controls
- Consistency, transactions, idempotency, migration safety, testing, observability, and production diagnostics

**Scope:** Framework-agnostic MongoDB and non-relational data modeling. For Java framework integrations, defer to the matching Spring Boot, Quarkus, or Micronaut MongoDB skill.

## Constraints

Keep recommendations at the database-modeling and query layer unless the user explicitly asks for Java framework integration. After editing this repository's XML sources, regenerate skills and verify the build.

- **MANDATORY**: Run `./mvnw compile` or `mvn compile` before proposing Java or Maven changes in the same change set
- **INJECTION**: Never concatenate untrusted input into query documents, aggregation stages, JSON strings, JavaScript expressions, or `$where`; use driver/framework query builders and validated parameters
- **SCHEMA**: Prefer explicit document contracts, bounded arrays, stable identifiers, and validation rules over unconstrained document growth
- **PERFORMANCE**: Review `explain()` plans, scanned/returned ratios, sort coverage, and index selectivity before claiming a query is optimized
- **FRAMEWORK**: Defer Spring MongoDB to `@315-frameworks-spring-mongodb`, Quarkus MongoDB to `@415-frameworks-quarkus-mongodb`, Micronaut MongoDB to `@515-frameworks-micronaut-mongodb`, and Mongock migrations to the matching framework migration skill
- **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` before promoting changes
- **EDGE CASE**: If the target database, version, shard topology, read/write concern, data volume, or latency requirement is missing and affects the recommendation, ask a clarifying question before editing queries or schemas
- **EDGE CASE**: If requested changes conflict with data safety, backwards compatibility, zero-downtime deployment, or retention requirements, explain the trade-off and ask for confirmation

## When to use this skill

- Design MongoDB document schemas
- Review MongoDB queries and indexes
- Improve aggregation pipeline performance
- Model non-relational data access patterns
- Review NoSQL consistency and transaction trade-offs

## Workflow

1. **Read reference and assess data context**

Read `references/705-technologies-nosql-mongodb.md` and inspect current collections, schemas, indexes, queries, aggregation pipelines, tests, and database configuration before proposing changes.

2. **Identify workload and operational constraints**

Confirm query patterns, cardinality, data volume, document growth, consistency requirements, shard topology, and migration constraints that shape the non-relational design.

3. **Apply database-aligned changes**

Implement or refactor database artifacts following the reference patterns and project conventions, keeping Java framework integration out of scope unless explicitly requested.

4. **Run verification and report results**

Execute appropriate build, schema validation, query-plan, migration, and test checks; summarize what changed, what was verified, and any remaining database risks.

## Reference

For detailed guidance, examples, and constraints, see [references/705-technologies-nosql-mongodb.md](references/705-technologies-nosql-mongodb.md).

© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth

Similar skills

All skills for Data and databases →

From the same set123

The whole set →
001-commands-inventory The 001-commands-inventory skill builds INVENTORY-COMMANDS-JAVA.md from an embedded Java command template. Use it when a project needs a fixed command inventory checklist. CX Codex +1 220installs 152-java-performance-gatling 152-java-performance-gatling sets up Gatling load testing in a Java Maven project: dependencies, the Maven plugin, simulations, and runs via ./mvnw gatling:test. CX Codex +1 219installs 004-commands-installation 004-commands-installation copies embedded project commands into selected assistant directories through an interactive setup prompt. CX Codex +1 219installs 005-agents-installation The 005-agents-installation skill copies the project’s embedded agent definitions into a directory you choose. Use it to set up .claude/agents or another supported destination. CX Codex +1 219installs 807-regulations-eu-digital-services-act 807-regulations-eu-digital-services-act reviews Java systems for Digital Services Act engineering controls across moderation, complaints, recommendations, advertising, and transparency. CX Codex +1 215installs 316-frameworks-spring-mongodb-migrations-mongock 316-frameworks-spring-mongodb-migrations-mongock is a Claude Code skill for adding and reviewing Mongock migrations in Spring Boot. It activates for MongoDB migration setup and reviews. CX Codex +1 215installs 400-frameworks-quarkus-create-project 400-frameworks-quarkus-create-project creates a Quarkus 3.x Maven project with the Quarkus CLI and SDKMAN-managed tools. Use it to scaffold a service with chosen coordinates and extensions. CX Codex +1 215installs 804-regulations-eu-nis2 804-regulations-eu-nis2 reviews Java applications for NIS2 cybersecurity risk-management controls in essential entities, critical-sector services, and managed providers. Works from sanitized evidence inventory only. CX Codex +1 215installs

Project sponsors

Companies that keep this analytics open