CtrlK
BlogDocsLog inGet started
Tessl Logo

mongodb

MongoDB operations expert for queries, aggregation pipelines, indexes, and schema design

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, well-organized MongoDB reference with concrete operators and commands, but it reads as topical guidance rather than a sequenced workflow with validation checkpoints, capping workflow clarity at 2.

Suggestions

Add a short ordered workflow for risky operations (e.g., index creation on production: build background/explain -> monitor -> cutover) with explicit validation checkpoints.

Include one or two fully assembled, copy-paste-ready examples (a complete aggregation pipeline, a compound-index creation command) to strengthen actionability further.

Optionally break the larger reference sections (Aggregation, Index Optimization) into a referenced file once the body grows well beyond 50 lines.

DimensionReasoningScore

Conciseness

Lean bullet-point guidance with no padding or explanation of basic MongoDB concepts; brief justification clauses like "— reduces network transfer" earn their place; not level 2 because there is no unnecessary explanation to tighten.

3 / 3

Actionability

Names concrete, directly applicable operators and commands ($elemMatch, $lookup, $facet, db.collection.getIndexes(), explain("executionStats"), the ESR rule); not level 2 because guidance is specific and partly copy-paste ready rather than vague pseudocode.

3 / 3

Workflow Clarity

Content is organized by topic with a verification hint ("explain before deploying") but offers no multi-step sequenced workflow with validation checkpoints; not level 1 because organization and a verification cue exist, not level 3 because there is no checkpointed sequence or single unambiguous action.

2 / 3

Progressive Disclosure

At roughly 49 lines with well-organized section headers and no need for external references, this meets the rubric's under-50-lines allowance for scoring 3 on well-organized sections; not level 2 because structure is clear and content is appropriately inline.

3 / 3

Total

11

/

12

Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description that lists concrete MongoDB capabilities and distinct trigger terms, but it omits an explicit when-to-use clause, capping completeness at 2.

Suggestions

Add an explicit trigger clause, e.g. "Use when working with MongoDB, designing schemas, writing aggregation pipelines, or optimizing indexes and query performance."

Include common natural variations users say, such as "collections", "documents", or "database", to broaden trigger coverage.

Keep the concise third-person voice; only append the when-to-use guidance without padding existing capability wording.

DimensionReasoningScore

Specificity

Names four concrete actions — "queries, aggregation pipelines, indexes, and schema design" — matching the anchor for listing multiple specific concrete actions; not level 2 because the action list is comprehensive rather than partial.

3 / 3

Completeness

It clearly states what the skill does but lacks any "Use when..." clause or explicit trigger guidance, which the rubric caps at 2; not level 3 because when-to-use is missing, not level 1 because what is stated clearly.

2 / 3

Trigger Term Quality

"MongoDB, queries, aggregation pipelines, indexes, schema design" are natural terms a user would say when needing this skill, giving good coverage; not level 2 because several relevant variations are present rather than just one.

3 / 3

Distinctiveness Conflict Risk

"MongoDB operations expert" is a clear, narrow niche unlikely to trigger for unrelated skills; not level 2 because the trigger is specific rather than broadly overlapping.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
RightNow-AI/openfang
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.