10gen Repo Intelligence
researched 2026-05-25· 0 sources · 10 concepts · skill 10gen
- Identify which 10gen repo or script is most relevant to a case-tracker or troubleshooting scenario
When to use this skill
- Identify which 10gen repo or script is most relevant to a case-tracker or troubleshooting scenario [source]
- Get install/run guidance for any repo in the high-signal set [source]
- Find integration ideas for connecting external repos into the Chrome extension or local backend [source]
- Map a scenario (FTDC diagnostics, explain plans, Jira enrichment, escalation UI) to the right tool [source]
- Understand which repos require internal credentials or special prerequisites [source]
When NOT to use this skill
Skill guidance
- Use the scenario-to-repo mapping section as the first lookup for any incoming question. [source]
- Cross-reference docs/init_index.md for broad repo discovery and docs/high_signal_file_index.json for per-file detail. [source]
- Prefer backend-mediated integrations over direct browser-side secrets. [source]
mdb-tam
- Direct Chrome extension architecture, local backend, native messaging hosts, Monday sync, Glean/Slack/calendar integrations, operator dashboards. [source]
- Best scenario: Build or extend the extension, mirror customer context locally, or automate operator workflows. [source]
- Install: npm install; npm run prepare:extension-root; cd native-host && ./install.sh <extension-id> [source]
- Run: Load repo root as unpacked Chrome extension; optional Node CLIs via node scripts/*.mjs [source]
- Notes: Strongest reference implementation. Many integrations should be backend-mediated rather than direct browser calls. [source]
ts-tools-customer-hub
- Customer context UX, Salesforce/Coveo/S3 integrations, monitoring, and runbook patterns. [source]
- Best scenario: Account context views, search, escalation workflows, and complex operator navigation patterns. [source]
- Install: npm ci --ignore-scripts after private npm auth and env setup [source]
- Run: npm run dev [source]
- Notes: Large, high-value repo; reuse concepts selectively. [source]
ts-tools-support-api
- Case creation, uploads, auth flows, swagger/openapi-backed automation surface. [source]
- Best scenario: Secure backend for programmatic case operations. [source]
- Install: npm install [source]
- Run: npm run dev after configuring Salesforce/JWT-related env vars [source]
- Notes: Security-sensitive. Prefer a thin backend wrapper instead of exposing it directly to the extension. [source]
ts-tools-scrapers-tickets
- Jira, Salesforce, and support-alert ingestion; support DB synchronization patterns. [source]
- Best scenario: Background enrichment, queue hydration, and joining ticket streams into one support model. [source]
- Install: poetry install [source]
- Notes: Good ingestion logic; fits better behind a backend worker due to scheduling and service credentials. [source]
ts-tools-escalation-manager
- Escalation-oriented UI, list/detail flows, active escalated case handling. [source]
- Best scenario: Extension side-panel UX around escalations or "cases needing attention now." [source]
- Install: npm install --legacy-peer-deps [source]
- Run: npm run dev [source]
- Notes: UI-focused; easier to mine for patterns than ts-tools-customer-hub. [source]
ts-search-explain-helper (SearchPlanIQ)
- Atlas Search explain diagnostics, visual exports, markdown writeups, MCP server mode. [source]
- Best scenario: Cases involving Atlas Search or vector search that need explain-plan analysis. [source]
- Install: uv sync or uv pip install -e . [source]
- Run: uv run python -m searchplaniq.app or searchplaniq-mcp [source]
- Notes: High-value troubleshooting tool; great fit for attachment-based workflows and AI summarization. [source]
alexandria
- FTDC diagnostics, rule-based issue detection, metric explorer, remote web analysis. [source]
- Best scenario: FTDC-driven troubleshooting and automated "what stands out in this diagnostic bundle?" flows. [source]
- Install: go build ./... or use a release binary [source]
- Run: ./alexandria <diagnostic.data path> [source]
- Notes: Best FTDC-specific diagnostic engine in the set. [source]
devprod-mcp-router
- Unified access to Jira, Confluence, Evergreen, Git, Backstage, and other debugging tools through one MCP gateway. [source]
- Best scenario: Extension/backend needing broad tool access without bespoke integrations. [source]
- Install: go build ./... or go install the devprod-mcp-proxy command [source]
- Run: devprod-mcp-proxy --gateway <gateway-url> [source]
- Notes: Ideal as a force multiplier for agentic flows. [source]
ts-support-demand-tracking
mongolyser
- Local desktop analysis of logs, profiling, indexes, cache, sharding, and cluster health. [source]
- Best scenario: Companion deep-dive tool when extension triage decides a human needs full diagnostics. [source]
- Install: npm install [source]
- Run: npm run electron:start [source]
- Notes: Better as a companion tool than something embedded in-browser. [source]
hmm-aha-search
ts-ftdc-requestor
- Requesting FTDC from Atlas and storing/retrieving shared FTDC bundles. [source]
- Best scenario: "Request diagnostics now" or collaboration on FTDC bundles. [source]
- Install: pip install -r requirements.txt or Docker-based local setup [source]
- Notes: Strong backend action surface for extension-triggered diagnostics collection. [source]
Implementation guidance
- Prefer backend-mediated integrations for Salesforce, Jira, Slack, Atlas, Gmail, Discord, and other privileged systems. Avoid direct browser-side secrets. [source]
- Treat mdb-tam as the primary architectural reference for extension composition, local/backend mediation, prompt workflows, and operator UX. [source]
- For diagnostics, keep the extension lightweight: trigger actions through ts-ftdc-requestor, alexandria, ts-search-explain-helper, or mongolyser instead of rebuilding those engines in-browser. [source]
- Use devprod-mcp-router when broad engineering-tool access is needed. [source]
- Mine ts-tools-customer-hub, ts-tools-escalation-manager, and support-dashboard for workflow ideas and UI patterns; avoid large-scale code copying unless dependencies are already aligned. [source]
Caveats and risk notes
- Many repos require internal credentials, Kanopy/CorpSecure access, private npm auth, Atlas API keys, Salesforce integration users, or Google service accounts. [source]
- Some tools are legacy, Stitch/App Services-era, or partially documented. Validate fit before adopting them as core dependencies. [source]
- Diagnostic artifacts (FTDC, explain plans, logs, support tickets) may contain sensitive customer or operational information. Keep storage, transmission, and sharing paths explicit. [source]
- Not every useful repo should be embedded directly. Some are better as external companion tools or backend services invoked by the extension. [source]
Installation and setup
- The generated script install_10gen_case_tracker_dependencies.sh is clone-first and safe by default: [source]
- Clones high-signal repos into ~/Documents/GitHub/10gen and installs prerequisite toolchains only when missing and when Homebrew is available. [source]
- Dependency installation is gated behind --install-deps or INSTALL_DEPS=1. [source]
- Node repos use npm ci --ignore-scripts where possible. [source]
- Python repos prefer uv sync, poetry install, or pip install -r requirements.txt depending on the manifest. [source]
- Go repos build locally with go build ./.... [source]
- Manual steps still required: Chrome unpacked extension load, native host install with extension ID, private npm auth for TS repos, internal secrets and service credentials. [source]
Common prerequisites
Manual credentials likely needed
- Salesforce integration user credentials / JWT materials [source]
- Atlas API keys or Atlas project-level credentials [source]
- Jira / Confluence tokens [source]
- Glean, Slack, Monday.com, Google Calendar, Gmail, Discord, S3, or Trino credentials depending on scenario [source]
- Private npm auth for @ts-tools packages [source]
Children
- Repo Prioritization and Mapping (frontier)
- Diagnostic Tool Catalog (frontier)
- Dashboard Integration Patterns (frontier)
- Install and Run Guidance (frontier)
Frontier under this node: Dashboard Integration Patterns, Diagnostic Tool Catalog, Install and Run Guidance, Repo Prioritization and Mapping