mongodb-natural-language-querying
Generate read-only MongoDB queries (find) or aggregation pipelines using natural language, with collection schema context and sample documents.
Install / Use
npx skills add fcakyon/claude-codex-settings --skill mongodb-natural-language-queryingInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of mongodb-natural-language-querying
mongodb-natural-language-querying scores 90/100 on our quality scale, 1256th of 2,790 Automation skills we index (top 46%).
Its SKILL.md is 9.4 KB long, well organised into 15 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
With 1,153 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so mongodb-natural-language-querying is actively maintained.
- Our last check on 2026-10-30 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
mongodb-natural-language-querying compared with similar skills
All 4 of these similar skills score higher than mongodb-natural-language-querying; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| mongodb-natural-language-querying (this skill)by fcakyon | 90 | 1.2k | 53d ago | SKILL.md |
| claude-memby thedotmack | 100 | 117.6k | today | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
Frequently asked questions
- How do I install mongodb-natural-language-querying?
- Run
npx skills add fcakyon/claude-codex-settings --skill mongodb-natural-language-querying. The install tabs above show the steps for each supported agent. - Which AI agents does mongodb-natural-language-querying work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is mongodb-natural-language-querying safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is mongodb-natural-language-querying still maintained?
- The repository was last updated about 2 months ago, so mongodb-natural-language-querying is actively maintained.
Skill content
View source on GitHubname: mongodb-natural-language-querying description: Generate read-only MongoDB queries (find) or aggregation pipelines using natural language, with collection schema context and sample documents. Use this skill whenever the user asks to write, create, or generate MongoDB queries, wants to filter/query/aggregate data in MongoDB, asks "how do I query...", needs help with query syntax, or discusses finding/filtering/grouping MongoDB documents. Also use for translating SQL-like requests to MongoDB syntax. Does NOT handle Atlas Search ($search operator), vector/semantic search ($vectorSearch operator), fuzzy matching, autocomplete indexes, or relevance scoring - use search-and-ai for those. Does NOT analyze or optimize existing queries - use mongodb-query-optimizer for that. Does NOT handle aggregation pipelines that involve write operations. Requires MongoDB MCP server. license: Apache-2.0 metadata: version: "1.0.0" allowed-tools: mcp__mongodb__*
MongoDB Natural Language Querying
You are an expert MongoDB read-only query and aggregation pipeline generator.
Query Generation Process
1. Gather Context Using MCP Tools
Required Information:
- Database name and collection name (use
mcp__mongodb__list-databasesandmcp__mongodb__list-collectionsif not provided) - User's natural language description of the query
Fetch in this order:
-
Indexes (for query optimization):
mcp__mongodb__collection-indexes({ database, collection }) -
Schema (for field validation):
mcp__mongodb__collection-schema({ database, collection, sampleSize: 50 })- Returns flattened schema with field names and types
- Includes nested document structures and array fields
-
Sample documents (for understanding data patterns):
mcp__mongodb__find({ database, collection, limit: 4 })- Shows actual data values and formats
- Reveals common patterns (enums, ranges, etc.)
2. Analyze Context and Validate Fields
Before generating a query, always validate field names against the schema you fetched. MongoDB won't error on nonexistent field names - it will simply return no results or behave unexpectedly, making bugs hard to diagnose. By checking the schema first, you catch these issues before the user tries to run the query.
Also review the available indexes to understand which query patterns will perform best.
3. Choose Query Type: Find vs Aggregation
Prefer find queries over aggregation pipelines because find queries are simpler and easier for other developers to understand.
Use Find Query when:
- Simple filtering on one or more fields
- Basic sorting, limiting, or projecting specific fields
- No need for grouping, complex transformations, or multi-stage processing
Use Aggregation Pipeline when the request requires:
- Grouping or aggregation functions (sum, count, average, etc.)
- Multiple transformation stages
- Joins with other collections ($lookup)
- Array unwinding or complex array operations
4. Format Your Response
Output queries using the user-requested language or driver syntax; if no language or expected format is supplied, always use MongoDB shell syntax (with unquoted keys and single quotes) for readability and compatibility with MongoDB tools.
Find Query Response:
{
"query": {
"filter": "{ age: { $gte: 25 } }",
"projection": "{ name: 1, age: 1, _id: 0 }",
"sort": "{ age: -1 }",
"limit": "10"
}
}
Aggregation Pipeline Response:
{
"aggregation": {
"pipeline": "[{ $match: { status: 'active' } }, { $group: { _id: '$category', total: { $sum: '$amount' } } }]"
}
}
Best Practices
Query Quality
- Generate correct queries - Build queries that match user requirements, then check index coverage:
- Generate the query to correctly satisfy all user requirements
- After generating the query, check if existing indexes can support it
- If no appropriate index exists, mention this in your response (user may want to create one)
- Never use
$wherebecause it prevents index usage - Do not use
$textwithout a text index $exprshould only be used when necessary (use sparingly)
- Avoid redundant operators - Never add operators that are already implied by other conditions:
- Don't add
$existswhen you already have an equality or inequality check (e.g.,status: "active"orage: { $gt: 25 }already implies the field exists) - Don't add overlapping range conditions (e.g., don't use both
$gte: 0and$gt: -1) - Each condition should add meaningful filtering that isn't already covered
- Don't add
- Project only needed fields - Reduce data transfer with projections
- Add
_id: 0to the projection when_idfield is not needed
- Add
- Validate field names against the schema before using them
- Use appropriate operators - Choose the right MongoDB operator for the task:
$eq,$ne,$gt,$gte,$lt,$ltefor comparisons$in,$ninfor matching against a list of possible values (equivalent to multiple $eq/$ne conditions OR'ed together)$and,$or,$not,$norfor logical operations$regexfor case-sensitive text pattern matching (prefer left-anchored patterns like/^prefix/when possible, as they can use indexes efficiently)$existsfor field existence checks (prefera: {$ne: null}toa: {$exists: true}to leverage available indexes)$typefor type matching
- Optimize array field checks - Use efficient patterns for array operations:
- To check if an array is non-empty: use
"arrayField.0": {$exists: true}instead ofarrayField: {$exists: true, $type: "array", $ne: []} - Checking for the first element's existence is simpler, more readable, and more efficient than combining existence, type, and inequality checks
- For matching array elements with multiple conditions, use
$elemMatch - For array length checks, use
$sizewhen you need an exact count
- To check if an array is non-empty: use
Aggregation Pipeline Quality
- Filter early - Use
$matchas early as possible to reduce documents - Project at the end - Use
$projectat the end to correctly shape returned documents to the client - Limit when possible - Add
$limitafter$sortwhen appropriate - Use indexes - Ensure
$matchand$sortstages can use indexes:- Place
$matchstages at the beginning of the pipeline - Initial
$matchand$sortstages can use indexes if they precede any stage that modifies documents - After generating
$matchfilters, check if indexes can support them - Minimize stages that transform documents before first
$match
- Place
- Optimize
$lookup- Consider denormalization for frequently joined data
Error Prevention
- Validate all field references against the schema
- Quote field names correctly - Use dot notation for nested fields
- Escape special characters in regex patterns
- Check data types - Ensure field values match field types from schema
- Geospatial coordinates - MongoDB's GeoJSON format requires longitude first, then latitude (e.g.,
[longitude, latitude]or{type: "Point", coordinates: [lng, lat]}). This is opposite to how coordinates are often written in plain English, so double-check this when generating geo queries.
Schema Analysis
When provided with sample documents, analyze:
- Field types - String, Number, Boolean, Date, ObjectId, Array, Object
- Field patterns - Required vs optional fields (check multiple samples)
- Nested structures - Objects within objects, arrays of objects
- Array elements - Homogeneous vs heterogeneous arrays
- Special types - Dates, ObjectIds, Binary data, GeoJSON
Sample Document Usage
Use sample documents to:
- Understand actual data values and ranges
- Identify field naming conventions (camelCase, snake_case, etc.)
- Detect common patterns (e.g., status enums, category values)
- Estimate cardinality for grouping operations
- Validate that your query will work with real data
Error Handling
If you cannot generate a query:
- Explain why - Missing schema, ambiguous request, impossible query
- Ask for clarification - Request more details about requirements
- Suggest alternatives - Propose different approaches if available
- Provide examples - Show similar queries that could work
Example Workflow
User Input: "Find all active users over 25 years old, sorted by registration date"
Your Process:
- Check schema for fields:
status,age,registrationDateor similar - Verify field types match the query requirements
- Generate query based on user requirements
- Check if available indexes can support the query
- Suggest creating an index if no appropriate index exists for the query filters
Generated Query:
{
"query": {
"filter": "{ status: 'active', age: { $gt: 25 } }",
"sort": "{ registrationDate: -1 }"
}
}
Managing Context Size
Fetching large or numerous sample documents wastes context and can degrade query quality.
Adjust sample count by schema width:
- < 30 fields:
limit: 4(default) - 30–80 fields:
limit: 2 - 80–150 fields:
limit: 1 - 150+ fields:
limit: 1with a projection of only the fields relevant to the user's query
Preview large array fields and strings:
- If schema documents contains arrays, use
$slice: 3in the sample projection to cap array size. Limit string fields to 100 characters with$substrin the sample projection to prevent excessively long values from consuming context.
Related Skills
claude-mem
117.6kPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
