agentsclimarketplace

Schema analyzer

Skill hoqo/claude-plugins/plugins/mongodb/skills/schema-analyzer

Claude Code plugins & skills

Install
npx -y skills add hoqo/claude-plugins --skill schema-analyzer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Analyze MongoDB collection schemas, infer data types, detect inconsistencies, and recommend schema design improvements. Use when the user asks about database structure, data modeling, schema validation, or wants to understand their MongoDB collections.

SKILL.md

3.0 KB, 685 tokens by cl100k_base, as published. Nobody here has run it

MongoDB Schema Analyzer

You analyze MongoDB schemas to understand data structure, detect problems, and recommend improvements.

Analysis Process

  1. Sample documents: Fetch 100 random documents from the collection
  2. Infer types: Detect field types, nesting depth, array contents
  3. Check consistency: Find fields that vary in type or presence
  4. Assess design: Evaluate embedding vs referencing choices
  5. Recommend: Suggest schema validation rules, indexes, and restructuring

Schema Discovery Script

Run this to analyze a collection's schema:

mongosh "$MONGODB_URI" --quiet --eval "
  const coll = '<COLLECTION>';
  const sample = db.getCollection(coll).aggregate([{ \$sample: { size: 100 } }]).toArray();

  const schema = {};
  sample.forEach(doc => {
    function analyze(obj, prefix) {
      Object.entries(obj).forEach(([key, val]) => {
        const path = prefix ? prefix + '.' + key : key;
        const type = Array.isArray(val) ? 'array' : typeof val;
        if (!schema[path]) schema[path] = { types: {}, count: 0 };
        schema[path].types[type] = (schema[path].types[type] || 0) + 1;
        schema[path].count++;
        if (type === 'object' && val !== null) analyze(val, path);
      });
    }
    analyze(doc, '');
  });

  Object.entries(schema)
    .sort(([a], [b]) => a.localeCompare(b))
    .forEach(([path, info]) => {
      const types = Object.entries(info.types).map(([t, c]) => t + '(' + c + ')').join(', ');
      print(path + '  |  ' + types + '  |  present in ' + info.count + '/100 docs');
    });
"

Schema Validation

Recommend JSON Schema validation rules when appropriate:

db.runCommand({
  collMod: "collection",
  validator: {
    $jsonSchema: {
      bsonType: "object",
      required: ["name", "email", "createdAt"],
      properties: {
        name: { bsonType: "string", description: "must be a string" },
        email: { bsonType: "string", pattern: "^.+@.+$" },
        age: { bsonType: "int", minimum: 0, maximum: 150 },
        createdAt: { bsonType: "date" }
      }
    }
  },
  validationLevel: "moderate",
  validationAction: "warn"
})

Schema Design Guidelines

When to Embed (denormalize)

  • Data is read together frequently
  • Child documents are bounded in number
  • One-to-few relationships
  • Data doesn't change independently

When to Reference (normalize)

  • Data is large or unbounded
  • Many-to-many relationships
  • Data is read independently
  • Documents would exceed 16MB limit

Anti-patterns to Flag

  • Arrays that grow without bound (unbounded arrays)
  • Deeply nested documents (>3 levels)
  • Storing large blobs in documents
  • Inconsistent field types across documents
  • Missing indexes on frequently queried fields
  • Using $where or JavaScript expressions in queries

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.