Skip to content

ericrisco/rsc-harness / skills/mongodb

mongodb

Verified

Use when modeling MongoDB documents (embed versus reference, the 16MB cap, bucket and subset patterns), choosing or fixing indexes (compound order by the ESR rule, partial, TTL, multikey, reading explain), writing aggregation pipelines that stay index-eligible, running multi-document transactions with retry, or operating and securing a deployment (replica set, read/write concern, Atlas tiers, Vector Search, Queryable Encryption). MongoDB 8.2, driver-agnostic. NOT relational schema, SQL or EXPLAIN ANALYZE (that is `postgresdb`).

FileKindSize
SKILL.mdskill md18.9 KB
evals/README.mdmarkdown1.6 KB
evals/cases.yamlconfig3.7 KB
references/aggregation.mdmarkdown4.8 KB
references/data-modeling.mdmarkdown5.4 KB
references/transactions-and-ops.mdmarkdown5.9 KB
scripts/verify.shexecutablescript6.5 KB

evals/cases.yaml

View on GitHub
skill: mongodb

should_trigger:
  - prompt: "This find() takes forever and the logs say it's scanning the whole collection — 4 million docs. How do I make it fast?"
    why: "A full collection scan (COLLSCAN) on a large collection is core scope; the skill owns reading explain and choosing the index, even though the user never says 'index' or 'COLLSCAN'."
  - prompt: "Should I put the comments inside the post document or keep them in their own collection?"
    why: "Embed vs reference is a named modeling decision with an explicit rule and the 16 MB rationale."
  - prompt: "My aggregation with a $lookup and a $group is slow and sometimes errors out on memory. What's wrong?"
    why: "Pipeline stage order, $lookup cost, and the 100 MB blocking-stage limit / allowDiskUse are all in scope."
  - prompt: "My multi-document transaction keeps throwing TransientTransactionError and I don't know how to handle it."
    why: "Non-obvious: the fix is the mandatory retry-on-the-transient-label (withTransaction), a core transactions topic the user wouldn't phrase as 'retry'."
  - prompt: "Necesito modelar una colección de pedidos con muchísimos items que crece sin límite, cómo lo hago?"
    why: "Spanish; unbounded array growth → reference or bucket pattern, a named modeling case."
  - prompt: "Which Atlas tier do I actually need to run Vector Search — is the free M0 enough?"
    why: "Non-obvious tier boundary: M0 won't run Vector Search for real workloads; Atlas tier choice + Vector Search are explicitly in scope."

should_not_trigger:
  - prompt: "Design a normalized Postgres schema with foreign keys and help me read this EXPLAIN ANALYZE output."
    route_to: "postgresdb"
    why: "Relational engine, SQL, and EXPLAIN ANALYZE — a different planner and concurrency model; the named boundary sibling."
  - prompt: "My Mongoose pre-save hook isn't firing and I don't understand what updateMany returns."
    route_to: "nodejs"
    why: "ODM/driver API ergonomics, not engine behavior; nearest catalog skill is the JS runtime, the ODM's own docs own this."
  - prompt: "Audit my repo for hardcoded credentials and unsafe authentication patterns."
    route_to: "security-audit"
    why: "A security audit of the codebase, not MongoDB modeling/indexing; security-audit owns app-layer security review."
  - prompt: "Set up a Redis cache in front of my read queries to cut database load."
    route_to: "redis"
    why: "App-layer caching with a different store; explicitly out of scope for this engine skill."
  - prompt: "Help me choose between Pinecone and Weaviate for our vector store."
    route_to: "vector-db"
    why: "Cross-engine vector-DB selection is out of scope; Atlas Vector Search inside Mongo would be in scope, but choosing between external products is not."

capability:
  - scenario: "A posts/comments app where the number of comments per post is unbounded, and a feed query filters by author and sorts by date. The user asks how to model the collections and which index to add."
    must_include:
      - "Chooses to reference comments in a separate collection (not an unbounded embedded array), citing the 16 MB document cap — or proposes a bucket pattern for the comment stream"
      - "Designs a compound index ordered by ESR: author equality first, then createdAt as the sort key (e.g. { 'author._id': 1, createdAt: -1 })"
      - "Shows explain('executionStats') and reads it: confirms IXSCAN (not COLLSCAN) and totalKeysExamined close to nReturned, with no in-memory SORT stage"
      - "States that inserting a single comment or post is already atomic, so no multi-document transaction is needed for it"
      - "Uses mongosh syntax (createIndex/find/explain), money as Decimal128 if money appears, not relational/SQL framing"
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall