MongoDB
DatabaseCommonly used with
Skills using MongoDB (114)
moai-domain-backend
Backend development specialist covering API design, database integration, microservices architecture, and modern backend patterns. Use when designing APIs, implementing server logic, authentication, or authorization.
moai-domain-database
Database specialist covering PostgreSQL, MongoDB, Redis, Oracle, and cloud database platforms (Neon, Supabase, Firestore). Use for schema design, query optimization, indexing strategies, data modeling, or cloud database selection. Cloud vendor guide absorbed from moai-platform-database-cloud.
mongodb-natural-language-querying
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.
mongodb-query-optimizer
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query writing unless user asks for performance or index help. Prefer indexing as optimization strategy. Use MongoDB MCP when available.
atlas-stream-processing
Manages MongoDB Atlas Stream Processing (ASP) workflows. Handles workspace provisioning, data source/sink connections, processor lifecycle operations, debugging diagnostics, and tier sizing. Supports Kafka, Atlas clusters, S3, HTTPS, and Lambda integrations for streaming data workloads and event processing. NOT for general MongoDB queries or Atlas cluster management. Requires MongoDB MCP Server with Atlas API credentials.
mongodb-atlas-stream-processing
Manages MongoDB Atlas Stream Processing (ASP) workflows. Handles workspace provisioning, data source/sink connections, processor lifecycle operations, debugging diagnostics, and tier sizing. Supports Kafka, Atlas clusters, S3, HTTPS, and Lambda integrations for streaming data workloads and event processing. NOT for general MongoDB queries or Atlas cluster management. Requires MongoDB MCP Server with Atlas API credentials.
mongodb-connection
Optimize MongoDB client connection configuration (pools, timeouts, patterns) for any supported driver language. Use this skill when working/updating/reviewing on functions that instantiate or configure a MongoDB client (eg, when calling `connect()`), configuring connection pools, troubleshooting connection errors (ECONNREFUSED, timeouts, pool exhaustion), optimizing performance issues related to connections. This includes scenarios like building serverless functions with MongoDB, creating API endpoints that use MongoDB, optimizing high-traffic MongoDB applications, creating long-running tasks and concurrency, or debugging connection-related failures.
mongodb-mcp-setup
Guide users through configuring key MongoDB MCP server options. Use this skill when a user has the MongoDB MCP server installed but hasn't configured the required environment variables, or when they ask about connecting to MongoDB/Atlas and don't have the credentials set up.
mongodb-schema-design
MongoDB schema design patterns and anti-patterns. Use when designing data models, reviewing schemas, migrating from SQL, or troubleshooting performance issues caused by schema problems. Triggers on "design schema", "embed vs reference", "MongoDB data model", "schema review", "unbounded arrays", "one-to-many", "tree structure", "16MB limit", "schema validation", "JSON Schema", "time series", "schema migration", "polymorphic", "TTL", "data lifecycle", "archive", "index explosion", "unnecessary indexes", "approximation pattern", "document versioning".
mongodb-search-and-ai
Guides MongoDB users through implementing and optimizing Atlas Search (full-text), Vector Search (semantic), and Hybrid Search solutions. Use this skill when users need to build search functionality for text-based queries (autocomplete, fuzzy matching, faceted search), semantic similarity (embeddings, RAG applications), or combined approaches. Also use when users need text containment, substring matching ('contains', 'includes', 'appears in'), case-insensitive or multi-field text search, or filtering across many fields with variable combinations. Provides workflows for selecting the right search type, creating indexes, constructing queries, and optimizing performance using the MongoDB MCP server.
app-builder
App scaffolding: Next.js, Vite, Nuxt, Astro, FastAPI, Django, Laravel, RN, Flutter. Triggers: scaffold, bootstrap, new project, starter, dashboard, mobile app.
health
Service/infra health via liveness/readiness checks, resource usage, quick diagnostics. Triggers: health check, services up, system status, infra health, degraded service.
python-guidelines
This skill should be used when writing, reviewing, or refactoring Python code. Covers code integration, idiomatic patterns, docstring formatting, anti-abstraction rules, and software engineering basics.
database-patterns
Database design and migration patterns for Alembic migrations, schema design (SQL/NoSQL), and database versioning. Use when creating migrations, designing schemas, normalizing data, managing database versions, or handling schema drift.
emulate-seed
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS (S3/SQS/IAM), Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs. Not mocks — full state machines where create-a-PR-and-it-appears-in-the-list, send-an-email-and-retrieve-from-local-inbox. Use when setting up test environments, CI pipelines, integration tests, or offline development.
hunt-nosqli
Hunt NoSQL Injection — MongoDB operator injection ($where, $regex, $gt, $ne), CouchDB, Redis command injection, auth bypass via NoSQLi, data dump. Use when target uses MongoDB/Mongoose, CouchDB, Redis, or shows NoSQL error messages.
pm-tech
Use when: 需要与技术团队对接技术方案、评估技术可行性、制定技术架构、评估第三方服务 Do NOT use when: 技术方案已由技术团队确定、仅需功能描述无需技术评估
database-documentation
Generate grounded-and-verified, engine-agnostic database documentation that reaches 100% parity with the real schema. Introspects the LIVE database as ground truth and cross-validates it against ORM models, migrations, generated types, seeds, and application queries, then proves completeness by diffing the docs back against the database. Produces ER diagrams (mermaid), per-table data dictionaries, and a machine-readable schema.json. Works with PostgreSQL, MySQL, SQL Server, and SQLite across any ORM (Prisma, TypeORM, Drizzle, Sequelize, Knex, Django, Rails) or raw SQL. Use when asked to document a database, produce an ERD or data dictionary, write db/schema docs, audit schema drift, or refresh existing DB docs.
fastapi-senior-dev
Senior Python Backend Engineer skill for FastAPI. Use when scaffolding production-ready APIs, enforcing clean architecture, optimizing async patterns, or auditing FastAPI codebases.
mongo-migration
MongoDB schema migration safety reviewer and migration script generator. ALWAYS use when writing, reviewing, or planning MongoDB schema changes — field additions/removals, index builds, schema validator changes, document type migrations, shard key modifications, or any bulk update touching production collections. Covers index build lock behavior (foreground vs rolling builds), additive schema evolution, _id-range batched updates, write concern tuning during migration, reshardCollection (5.0+), collMod validator changes, and rollback planning. Use even for "just add a field" — MongoDB's schema-less nature makes silent type inconsistencies and missing-field bugs harder to detect than RDBMS constraint violations.
alibaba-migration-architect
Plan Alibaba Cloud migrations using SMC (Server Migration Center), DTS (Data Transmission Service) for data sync, OSSImport for object storage migration, and design cutover sequencing with rollback paths.
better-auth
Better Auth integration guide for TypeScript/JavaScript authentication. Covers server/client configuration, database adapters, session management, plugins, OAuth, and scaffolding auth from scratch. Use when setting up authentication with Better Auth, configuring auth.ts, adding OAuth providers, or creating sign-in/sign-up flows.
create-auth-skill
Scaffold and implement authentication in TypeScript/JavaScript apps using Better Auth. Detect frameworks, configure database adapters, set up route handlers, add OAuth providers, and create auth UI pages. Use when users want to add login, sign-up, or authentication to a new or existing project with Better Auth.
be-testing
Backend testing patterns — API request construction, response verification, database state checks, error handling testing, and adaptive tool detection.
mongodb
MongoDB 数据库管理
go-bootstrap
Bootstraps a new Go project from scratch with hexagonal architecture, testcontainers, CI pipeline, and the full skill/agent suite installed. Use when starting a new project or microservice.
api-cms-payload
Payload CMS v3 — TypeScript-native headless CMS with code-first collections, hooks, access control, Local/REST/GraphQL APIs, admin panel, and database adapter pattern
api-database-mongodb
MongoDB with Mongoose ODM - schemas, models, queries, aggregation, indexes, TypeScript typing, connection management
api-database-mongoose
MongoDB ODM with schemas, validation, middleware, and TypeScript support
dbdesign
Design and review production database schemas, data models, ERDs, migration plans, and storage patterns. Use for OLTP schema design, OLAP/star-schema modeling, fact/dimension tables, indexes, constraints, partitioning, multi-tenant data models, CSV/JSON-to-table design, schema review, migration risk review, and database design documents across PostgreSQL, MySQL, SQLite/D1, BigQuery, and MongoDB. Does not execute DDL by default.
fastapi-senior-dev
Senior Python Backend Engineer skill for FastAPI. Use when scaffolding production-ready APIs, enforcing clean architecture, optimizing async patterns, or auditing FastAPI codebases.
database
Database design, SQL, NoSQL, and data management
databases
SQL, databases, ORMs, and data modeling. Activated when Claude works with database code, .sql files, Prisma schemas, or database-related npm packages.
skills-reviewer
Reviews Agent Skills / SKILL.md packages for quality, spec compliance, trigger clarity, examples, references, eval coverage, bloat, conflicts, and risky instructions. Use when asked to audit, review, improve, score, or validate an agent skill.
vault-repo-docs
Use when indexing, scanning, or documenting a repository into the Otto Vault as a durable OKF bundle, including full, focused, and incremental scans or feature dependency maps; not for code review or one-off repository questions.
pdlc-adopt
旧项目接入 PDLC
epic-identification
This skill should be used when the user asks to "identify epics", "break down vision into epics", "find major features", "discover capability areas", "decompose vision", "group requirements into themes", "define high-level features", "what epics do I need", "turn vision into work items", or "split project into epics". Provides methodology for deriving epics from a vision statement using user journey mapping, capability decomposition, and stakeholder analysis.
prioritization
This skill should be used when the user asks to "prioritize requirements", "prioritize epics", "prioritize stories", "prioritize tasks", "prioritize backlog", "use MoSCoW", "apply MoSCoW priorities", "assign priorities", "set priority labels", "rank features", "what should I build first", "what's most important", "order by importance", "must have vs should have", or when they need to determine the priority order of epics, user stories, or tasks using the MoSCoW framework.
requirements-feedback
This skill should be used when the user asks about "feedback loops", "iterate on requirements", "continuous documentation", "refine requirements", "update requirements", "requirements changed", "stakeholder review", "validate requirements", "incorporate feedback", "gather feedback", "requirements review meeting", "backlog refinement feedback", "user research findings", "sprint retrospective feedback", "help me gather feedback", "run a feedback session", "get input on my vision", "get input on my epics", "get input on my stories", "collect user feedback", "document feedback from meeting", "review requirements with stakeholders", or when they need guidance on collecting and incorporating feedback throughout the requirements lifecycle.
shared-patterns
This skill should be used when the user asks to "implement recovery flow", "add error handling to command", "handle gh operation failures", "implement idempotency check", "prevent duplicate issues", "check before creating", "implement batch tracking", "track created and failed items", "implement two-layer metadata", "update custom fields and labels", "standardize command patterns", or when developing or modifying /re:* commands that need consistent error handling, duplicate detection, batch operation tracking, or GitHub Projects metadata updates.
task-breakdown
This skill should be used when the user asks to "create tasks", "break down story into tasks", "define tasks", "what tasks are needed", "write acceptance criteria", "implementation tasks", "task list", "create work items", "technical tasks", "work breakdown", "decompose story", "story to tasks", or when decomposing user stories into specific, executable tasks with clear acceptance criteria for GitHub Projects.
user-story-creation
This skill should be used when the user asks to "create user stories", "write user stories", "break down epic into stories", "define user stories", "what stories do I need", "apply INVEST criteria", "write acceptance criteria", "split a large story", "story is too big", "story splitting", or when decomposing epics into specific, valuable user stories.
validation
This skill should be used when the user asks to "validate requirements", "review requirements quality", "check requirements completeness", "verify traceability", "check INVEST compliance", "validate user stories", "requirements health check", "quality gate check", or when running /re:review validation.
vision-discovery
This skill should be used when the user asks to "discover vision", "create a vision", "define product vision", "document vision", "what should my vision be", "help me with vision", "start requirements from scratch", "begin new product planning", "define product direction", "establish product vision", or when starting a new requirements project and needs to establish the foundational product vision before identifying epics or stories.
super-claudiosoftware-development
Software development skill. Use when the user wants to build, code, automate, or deploy anything technical. Covers backend APIs, databases, workflow automation, scripts, free public APIs, and hosting/deployment. Trigger on backend: "build an API", "REST API", "database schema", "Supabase", "Firebase", "PostgreSQL", "MongoDB", "FastAPI", "Express", "Fastify", "GraphQL", "Node.js server", "Python API", "Prisma", "ORM", "authentication backend", "serverless functions". Trigger on automation: "automate this", "connect these apps", "n8n", "Make.com", "Zapier", "when X happens do Y", "no-code automation", "schedule a script", "webhook", "automate posting", "IFTTT", "auto-post to Instagram", "batch processing", "automate email". Trigger on free APIs: "free API for X", "public API", "build a weather app", "NASA API", "real-time data", "open data", "free data source", "API without credit card", "government API". Trigger on deployment: "deploy my app", "Docker", "Railway", "GitHub Actions", "CI/CD", "hosting", "go live
qa-engineering-architect
QA Engineer Senior, QA Lead, Test Architect, SDET, Automation Engineer, consultor ISTQB y mentor de testing. Úsala SIEMPRE que el usuario quiera asegurar, revisar o construir la CALIDAD de un software: analizar la calidad de un proyecto/repo, revisar requisitos o criterios de aceptación, hacer análisis de riesgos, diseñar una estrategia o plan de pruebas, crear casos de prueba, hacer QA manual o exploratorio, reportar defectos, automatizar (Selenium, Playwright, Cypress, Pytest, Robot Framework), construir un framework Cucumber BDD con Java/Selenium/Maven, escribir o revisar Gherkin, probar APIs (REST Assured, Postman), probar bases de datos (PostgreSQL/MySQL/MongoDB), pruebas de performance (K6/JMeter), seguridad autorizada (OWASP ZAP/Top 10), integrar pruebas en CI/CD (Jenkins/GitHub Actions), auditar una suite, depurar flakiness, documentar QA para una tesis/TSP, o aprender/prepararse para ISTQB. Frases como "prueba esto", "haz QA", "crea casos de prueba", "automatiza con Cucumber", "revisa mi suite", "rep
verdict
Architect-grade technology decision briefs — "which option should we pick, and why?" Takes a decision question (X vs Y vs Z for a stated context: library, database, framework, platform, buy-vs-build) plus your constraints, fans out parallel sub-agents to research each option's project health, community sentiment, technical claims, and operational story, then scores options across weighted criteria and emits an ADR-style recommendation with a full scorecard and cited evidence. Keyless; the recommendation is advisory — you decide. Use when the user must choose between technologies or approaches — e.g. "/verdict postgres vs mongodb for <use case>", "should we use Kafka or NATS", "compare X and Y", "buy vs build", "which framework for this". Also supports "/verdict revisit <brief>" to cheaply re-check a past verdict's revisit-when triggers. For community buzz on a single topic use pulse; for exhaustive fact-checked research use deep-research.
brewtoolssecrets-scan
Scans git-tracked files for leaked secrets. Triggers - secrets scan, find credentials, leaked keys, security audit.
database
Database setup wizard — PostgreSQL, ScyllaDB/Cassandra, Redis — schema design, migrations, query patterns, and connection setup
db
Full database skill — MySQL, PostgreSQL, MongoDB, Redis, ScyllaDB, Meilisearch — setup, queries, optimization, backups, debugging
digitalocean
DigitalOcean infrastructure — Droplets, managed databases, Spaces, load balancers, firewalls, DNS management
graphql
Sets up a GraphQL API — schema-first design, resolvers, subscriptions, with PostgreSQL or MongoDB, and optional codegen
webapp
Full-stack web app wizard — Angular/Node, React/Node, Vue/Node — with optional deployment to AWS or DigitalOcean
pydantic-model
Pydantic v2 model patterns for req/res validation, MongoDB conversion, validation rules. Travel Panel conventions.
vault-api-review
Review Otto Vault repository documentation specifically for complete HTTP/RPC/WebSocket contracts, real request and response bodies, errors, auth, examples, OpenAPI parity, and runtime side effects. Use as a focused post-scan reviewer; do not author or repair docs.
vault-data-review
Review Otto Vault repository documentation specifically for complete relational, document, analytical, and Redis schemas; real reads/writes; indexes/TTL; consistency; relationships; and field-level impact. Use as a focused post-scan reviewer; do not author or repair docs.
vault-docs-review
Review an Otto Vault repository-documentation run for missed surfaces, shallow concepts, unsupported claims, broken coverage, and incomplete API/data/runtime detail. Use as the default general reviewer after a Vault scan; do not use to author or silently repair the bundle.
vault-runtime-review
Review Otto Vault repository documentation specifically for runtime flows, messages, schedules, reconciliation, startup/shutdown, failure handling, retries, idempotency, observability, and external side effects. Use as a focused post-scan reviewer; do not author or repair docs.
database-designer
Schema analysis, ERD generation, index optimization, and migration safety. TRIGGER when: user asks about database schema design, normalization, index strategy, query optimization, migration planning, or choosing between database engines. DO NOT TRIGGER when: application-level ORM usage without schema concerns, or general API design (use relevant language skill).
db-clickhouse
Specialized assistant for exploring and querying a ClickHouse database read-only in Otto's DB Explorer — columnar/OLAP idioms, FINAL and merge semantics, system.* introspection, approximate aggregates, join pitfalls, and producing a single final query.
db-mongodb
Specialized assistant for exploring and querying a MongoDB database read-only in Otto's DB Explorer — find vs aggregation pipelines, $lookup joins, explain plans, schema-less discovery, and producing a single final query.
db-mysql
Specialized assistant for exploring and querying a MySQL/MariaDB database read-only in Otto's DB Explorer — dialect idioms, safe schema discovery, EXPLAIN-driven performance, and producing a single final query.
db-redis
Specialized assistant for exploring and querying a Redis keyspace read-only in Otto's DB Explorer — type-aware reads, SCAN instead of KEYS, key-pattern/namespacing conventions, big-key care, and producing a final command.
okf-authoring
Use when creating, maintaining, consuming, converting, or validating Open Knowledge Format bundles, especially Otto Vault documentation for repositories, services, APIs, data assets, decisions, runbooks, metrics, and references.
database-connect
Database MCP server integration for PostgreSQL, MySQL, MongoDB
backend-master-agent
Backend implementation playbook — API endpoints, database models/migrations, auth, query optimization, and the framework-specific traps that break servers in production. Use when implementing or reviewing server-side code: FastAPI / Django / Flask / Express / NestJS / Go / Axum handlers, SQLAlchemy / Prisma / Mongoose / Tortoise models, JWT / OAuth / session auth, bcrypt / argon2 password hashing, rate limiting, N+1 query fixes, async/event-loop bugs, or when a handoff spec asks for "the backend" of a feature.
integration-specialist-agent
Resilient third-party integration patterns — API clients, webhooks, MCP server wiring, retries/circuit-breakers, and idempotency. Use when connecting to an external service (Stripe/GitHub/Slack/S3/etc.), building or verifying a webhook receiver, adding retry/backoff or circuit-breaker resilience, registering an MCP server, or reviewing an integration for signature-verification and rate-limit gaps.
farm-stack
Use when building or scaffolding FastAPI + React + MongoDB (FARM stack) applications. Covers project structure, async MongoDB with Motor, Pydantic v2 models, config patterns, Docker setup, and testing conventions.
excellent-skill
Use this skill when reviewing small API migration pull requests for the Acme Payments service, especially changes touching idempotency keys, retry behavior, webhook signatures, or migration SQL.
good-focused
Reviews D2 diagram skill drafts for syntax workflow, diagram examples, references, and eval coverage. Use when asked to audit a D2-specific Agent Skill; do not use for generic code review.
vault-evidence-review
Review Otto Vault repository documentation specifically for citation precision, claim-to-source support, source hierarchy, invented examples, stale contradictions, coverage-status evidence, and honest uncertainty. Use as a focused post-scan reviewer; do not author or repair docs.
sealos-database
Provision, connect, and operate Sealos Cloud databases through sealos-cli for local development, Devbox development, and app setup. Use when the user needs a cloud database for a project, asks to create or connect PostgreSQL/MySQL/MongoDB/Redis or another Sealos database, wants DATABASE_URL or similar env vars wired into a dev environment, needs database connection details, backups, logs, public access, or wants to replace local Docker Compose databases with a managed Sealos database.
speckit.migrate
Legacy Code Migrator - Reverse-engineer existing codebase to SDD standard.
bad-bloated
Helps with everything and all tasks across coding, writing, research, diagrams, deployment, finance, product work, emails, analysis, and anything else.
cm-database-engineer
数据库工程师 Skill，执行数据模型设计、migration、查询优化，自动适配 ORM 和数据库类型
executor-and-planner
Edit the PostgreSQL executor or planner — covers src/backend/executor/ (nodeXxx.c, ExecInitNode/ExecProcNode/ExecEndNode/ExecReScan dispatch, PlanState lifecycle, EXPLAIN wiring) and src/backend/optimizer/ (Path → Plan via createplan.c, RelOptInfo lifecycle, add_path cost-dominance pruning, cost_* units in cost.h). Use whenever a PG patch adds or modifies a plan-node executor, introduces a new Path or Plan type, changes cost-model fields in cost.h, adds EXPLAIN output for a node, plumbs a node into execParallel.c, or tweaks join-path enumeration. Skip for end-user query tuning, EXPLAIN ANALYZE of a production query, work_mem / shared_buffers tuning, MySQL / MongoDB / BigQuery / Snowflake / DuckDB / Spark / Trino query engines, ORM query-builder optimization, and pandas / polars dataframe operations.
replication-overview
Hack or review PostgreSQL replication internals — covers physical streaming, archive shipping, logical decoding, logical replication PUB/SUB, and synchronous-commit machinery. Names walsender / walreceiver / replication slot / output plugin callbacks plus the relevant GUCs (wal_level, max_wal_senders, max_replication_slots, max_logical_replication_workers, primary_conninfo, primary_slot_name, synchronous_standby_names) and the source files behind each flavor. Use whenever a PG patch touches walsender, walreceiver, replication slots, logical decoding, output plugins, publications/subscriptions, conflict detection, sync replication, failover slots, pg_basebackup, or pg_receivewal — or when picking which mechanism fits a feature design. Skip for MySQL row-based / GTID replication, MongoDB replica sets, Cassandra hinted handoff, Kafka MirrorMaker / Confluent Replicator, Debezium / Flink CDC pipelines, AWS DMS, and Galera / Group Replication.
database-optimizer
Use when you need to analyze slow queries, optimize database performance across multiple systems, or implement indexing strategies to improve query execution.
bad-conflicts
Reviews release notes skill drafts for clarity, examples, references, and evals. Use when asked to audit release-note skills before publishing.
bad-no-examples
Audits SQL query optimization skills for trigger clarity, workflow structure, references, evals, and safe script usage. Use when reviewing a SQL-optimization Agent Skill package.
bad-script-risk
Checks deployment helper skills for script safety, examples, references, evals, and conflict risks. Use when reviewing a deployment Agent Skill that bundles shell or Python scripts.
bloated-conflicting-skill
Helps with everything related to documents, coding, research, travel, and productivity.
mongo-conventions
MongoDB conventions for this repo — async access via Motor, append-only data-lake discipline, and provenance on every datum. Use when reading/writing Mongo collections, adding ingest or transform pipelines, designing indexes, building an embedding/vector store on Mongo, or reasoning about which data is the system of record.
architecture-review
A focused, single-lens review of a change's design and structure — not its defects. Judges separation of concerns and SOLID, coupling and cohesion, module/layer boundaries and dependency direction, whether the right abstraction is present (and the wrong/early one is absent), files and functions that have grown too large or do too much, leaky abstractions, intent-hiding names, duplication that wants to be a shared unit, and whether the change fits how this codebase is already built. Every finding cites file/module:line, a severity, the future cost it imposes, and a concrete refactor direction. Constructive and pragmatic — flags structure that will cost future change, never taste.
commit-message
Use BEFORE writing or finalizing ANY git commit message — when staging changes, running git commit, or asked to "commit", "write a commit message", or "draft a commit". Covers Conventional Commits, the repo's emoji/scope convention, the Jira key, splitting mixed changes, and the rule that a commit carries NO AI attribution.
correctness-review
A focused single-lens code review that hunts correctness bugs only — logic errors, off-by-one, inverted conditions, broken invariants, wrong state transitions, null/None/nil mishandling, and the unhandled branch the author never ran. For each suspected bug it hand-traces (and reproduces where it can) before asserting, then reports it with file:line, severity, why-it-matters, and a concrete fix. Run it alone for a sharp pass, or compose it with security/performance/etc. — it deliberately does not duplicate grill's exhaustive all-lens sweep.
d2-diagram
Use whenever asked to work on a diagram — create, update, improve, review, validate, or render one — including architecture / C4 maps, sequence & API flows, ERDs / SQL schemas, data flows & ETL pipelines, infrastructure / Kubernetes / deployment topology, dependency & module graphs, state machines, incident/debug timelines, and repo-derived diagrams. Produces durable D2 (`.d2`) sources plus rendered SVG in `docs/diagrams/`, with quality linting (d2_doctor) and layout/style rules. For Otto Canvas scenes (a per-scene `canvas.d2`/`canvas.mermaid`/`canvas.json` edited over HTTP), use the `otto-canvas` skill instead.
grill
Adversarially grill a product story or PRD — hunt scope holes, ambiguities, non-testable acceptance criteria, unhandled edge cases, hidden dependencies, and conflicting requirements. Evidence-based and specific; never invent requirements.
insights
Generate an action-first coding-agent usage report across ALL providers Otto uses (Claude, Codex, agy/Gemini) for a chosen period (day/week/month or explicit range), compare it to the previous comparable period for trends, and emit a self-contained HTML report where every finding — even the good ones — carries Evidence/threshold → Action → Expected effect. Use when the user wants a usage/productivity insights report, a weekly/daily/monthly review, or trend tracking of how they work with AI agents.
otto-canvas
Use when drawing/generating a diagram for the Otto Canvas, creating or editing canvas scenes, or driving Discovery Chat on a Product story, from an agent session over HTTP. Covers the FILE-BACKED canvas model with THREE modes — Mermaid (edit a per-scene `canvas.mermaid`; any diagram type), Excalidraw (edit a per-scene `canvas.json`; fully editable shapes), and D2 (edit a per-scene `canvas.d2`; modern declarative diagrams — architecture, sequence, SQL tables) — top-notch pretty-Mermaid styling, the D2 shape/class syntax, the Excalidraw simplified element format, the OTTO_API_TOKEN auth model, the Canvas + Discovery-Chat endpoints, and the canvas.mjs helper.
otto-mockup
Use when generating or refining a product MOCKUP for an Otto Product story from an agent session — the in-place "Create with AI" / "Refine" mockup agent. Covers the FILE-BACKED mockup model with TWO formats — HTML (edit a per-mockup `mockup.html`; a self-contained, sandbox-safe UI screen) and Mermaid (edit a per-mockup `mockup.mmd`; any diagram type) — the quality rules for each, and how the file is committed as a `kind:mockup` attachment that renders in the Mockups tab.
pull-request
Use BEFORE opening or drafting ANY pull request — when asked to "open a PR", "create a pull request", "draft a PR", or to write a PR title/description. Covers summarizing the whole branch, the Jira key as title prefix (never in the body), GitHub vs Bitbucket creation, and the rule that a PR carries NO AI attribution.
security-review
A focused, single-lens security review of a change. The one specialist a user runs alone when they care about exploitability — not a general sweep. Core method is taint tracing - follow untrusted input from its source, across the trust boundary, to a dangerous sink - and prove the path is reachable before calling it a finding. Covers injection (SQL/NoSQL/command/LDAP), XSS, SSRF, path traversal, insecure deserialization, authn/authz gaps (missing permission checks, IDOR), secret handling, sensitive-data exposure in logs/errors/URLs, crypto misuse, and unsafe defaults. Every finding cites file:line, a severity (a real exploit path is a blocker), the concrete attack, and a fix.
test-review
A focused, single-lens review of test quality and coverage for a change — does the test actually exercise the new behavior AND its failure modes, or does it merely pass? Hunts happy-path-only coverage, weak assertions, tests that pass even when the code is wrong, over-mocking that tests the mock, missing negative/edge/error cases, flakiness, and tests coupled to implementation detail. Every finding asks "would this test fail if I broke the code?", cites file:line, a severity, why it matters, and the concrete missing case or stronger assertion.
go-architect
Designs implementation architecture following hexagonal patterns, produces TASKS.md and individual task-N.md files for the orchestrator to execute using red-green TDD.
create-auth
Scaffold and implement authentication in TypeScript/JavaScript apps using Better Auth. Detect frameworks, configure database adapters, set up route handlers, add OAuth providers, and create auth UI pages. Use when users want to add login, sign-up, or authentication to a new or existing project with Better Auth.
missing-evals-skill
Use this skill when converting legacy CSV exports from the Northstar billing system into normalized JSON invoices.
azure-cosmosdb
Azure Cosmos DB partition keys, consistency levels, change feed, SDK patterns
data
Set up database / persistent-state discipline for a project with a DB. Authors a data-auditor agent (5 categories of integrity check), a migration-create skill, query-discipline rule (CLI > MCP DB tool for reads), and edit-time regen hook — all derived from the project's actual schema, migration framework, and access-control model. Optionally an RLS-security-reviewer if Postgres + row-level security is in use. Invoke /dotclaude:data in any project with persistent state.
mongodb
Work with MongoDB databases using best practices. Use when designing schemas, writing queries, building aggregation pipelines, or optimizing performance. Triggers on MongoDB, Mongoose, NoSQL, aggregation pipeline, document database, MongoDB Atlas.
Showing top 100 of 114 skills using MongoDB by quality score.
See all 114 skills via search →Integration detected automatically from skill content. Some results may be false positives.