atlas-stream-processing
atlas-stream-processing manages MongoDB Atlas Stream Processing workflows including workspace provisioning, data source and sink connections, processor lifecycle operations, debugging diagnostics, and tier sizing. Use this skill to build, operate, and debug streaming data pipelines that integrate with Kafka, Atlas clusters, S3, HTTPS, and Lambda when you have the MongoDB MCP Server connected with Atlas API credentials and a valid project ID.
git clone --depth 1 https://github.com/fcakyon/claude-codex-settings /tmp/atlas-stream-processing && cp -r /tmp/atlas-stream-processing/plugins/mongodb-skills/skills/atlas-stream-processing ~/.claude/skills/atlas-stream-processingSKILL.md
# MongoDB Atlas Streams Build, operate, and debug Atlas Stream Processing (ASP) pipelines using four MCP tools from the MongoDB MCP Server. ## Prerequisites This skill requires the **MongoDB MCP Server** connected with: - Atlas API credentials (`apiClientId` and `apiClientSecret`) The 4 tools: `atlas-streams-discover`, `atlas-streams-build`, `atlas-streams-manage`, `atlas-streams-teardown`. **All operations require an Atlas project ID.** If unknown, call `atlas-list-projects` first to find your project ID. ## If MCP tools are unavailable If the MongoDB MCP Server is not connected or the streams tools are missing, see [references/mcp-troubleshooting.md](references/mcp-troubleshooting.md) for diagnostic steps and fallback options. ## Tool Selection Matrix ### atlas-streams-discover — ALL read operations | Action | Use when | |--------|----------| | `list-workspaces` | See all workspaces in a project | | `inspect-workspace` | Review workspace config, state, region | | `list-connections` | See all connections in a workspace | | `inspect-connection` | Check connection state, config, health | | `list-processors` | See all processors in a workspace | | `inspect-processor` | Check processor state, pipeline, config | | `diagnose-processor` | Full health report: state, stats, errors | | `get-networking` | PrivateLink and VPC peering details. Optional: `cloudProvider` + `region` to get Atlas account details for PrivateLink setup | **Pagination** (all list actions): `limit` (1-100, default 20), `pageNum` (default 1). **Response format**: `responseFormat` — `"concise"` (default for list actions) or `"detailed"` (default for inspect/diagnose). ### atlas-streams-build — ALL create operations | Resource | Key parameters | |----------|---------------| | `workspace` | `cloudProvider`, `region`, `tier` (default SP10), `includeSampleData` | | `connection` | `connectionName`, `connectionType` (Kafka/Cluster/S3/Https/Kinesis/Lambda/SchemaRegistry/Sample), `connectionConfig` | | `processor` | `processorName`, `pipeline` (must start with `$source`, end with `$merge`/`$emit`), `dlq`, `autoStart` | | `privatelink` | `privateLinkConfig` (project-level, not tied to a specific workspace) | **Field mapping — only fill fields for the selected resource type:** - **resource = "workspace":** Fill: `projectId`, `workspaceName`, `cloudProvider`, `region`, `tier`, `includeSampleData`. Leave empty: all connection and processor fields. - **resource = "connection":** Fill: `projectId`, `workspaceName`, `connectionName`, `connectionType`, `connectionConfig`. Leave empty: all workspace and processor fields. (See [references/connection-configs.md](references/connection-configs.md) for type-specific schemas.) - **resource = "processor":** Fill: `projectId`, `workspaceName`, `processorName`, `pipeline`, `dlq` (recommended), `autoStart` (optional). Leave empty: all workspace and connection fields. (See [references/pipeline-patterns.md](references/pipeline-patterns.md) for pipeline examples.) - **resource = "privatelink":** Fill: `projectId`, `privateLinkConfig`. Note: PrivateLink is **project-level**, not workspace-level. `workspaceName` is not required — omit it. Leave empty: all connection and processor fields. ### atlas-streams-manage — ALL update/state operations | Action | Notes | |--------|-------| | `start-processor` | Begins billing. Optional `tier` override, `resumeFromCheckpoint` | | `stop-processor` | Stops billing. Retains state 45 days | | `modify-processor` | Processor must be stopped first. Change pipeline, DLQ, or name | | `update-workspace` | Change tier or region | | `update-connection` | Update config (networking is immutable — must delete and recreate) | | `accept-peering` / `reject-peering` | VPC peering management | **Field mapping** — always fill `projectId`, `workspaceName`, then by action: - `"start-processor"` → `resourceName`. Optional: `tier`, `resumeFromCheckpoint`, `startAtOperationTime` (ISO 8601 timestamp to resume from a specific point) - `"stop-processor"` → `resourceName` - `"modify-processor"` → `resourceName`. At least one of: `pipeline`, `dlq`, `newName` - `"update-workspace"` → `newRegion` or `newTier` - `"update-connection"` → `resourceName`, `connectionConfig`. **Exception: networking config (e.g., PrivateLink) cannot be modified after creation** — delete and recreate. - `"accept-peering"` → `peeringId`, `requesterAccountId`, `requesterVpcId` - `"reject-peering"` → `peeringId` **State pre-checks:** - `start-processor` → errors if processor is already STARTED - `stop-processor` → no-ops if already STOPPED or CREATED (not an error) - `modify-processor` → errors if processor is STARTED (must stop first) **Processor states:** `CREATED` → `STARTED` (via start) → `STOPPED` (via stop). Can also enter `FAILED` on runtime errors. Modify requires STOPPED or CREATED state. **Teardown safety checks:** - **Processor deletion** → auto-stops before deleting (no need to stop manually first) - **Connection deletion** → blocks if any running processor references it. Stop/delete referencing processors first. - **Workspace deletion** → See detailed workflow below (lines 108-111). ### atlas-streams-teardown — ALL delete operations | Resource | Safety behavior | |----------|----------------| | `processor` | Auto-stops before deleting | | `connection` | Blocks if referenced by running processor | | `workspace` | Cascading delete of all connections and processors | | `privatelink` / `peering` | Remove networking resources | **Field mapping** — always fill `projectId`, `resource`, then: - `resource: "workspace"` → `workspaceName` - `resource: "connection"` or `"processor"` → `workspaceName`, `resourceName` - `resource: "privatelink"` or `"peering"` → `resourceName` (the ID). These are project-level resources, not tied to a specific workspace. **Before deleting a workspace**, inspect it first: 1. `atlas-streams-discover` → `inspect-workspace` — get connection/processor counts 2. Present to user
Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Use 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, .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.
This skill should be used when user asks to "query Azure resources", "list storage accounts", "manage Key Vault secrets", "work with Cosmos DB", "check AKS clusters", "use Azure MCP", or interact with any Azure service.
This skill should be used when user encounters "Tavily MCP error", "Tavily API key invalid", "web search not working", "Tavily failed", or needs help configuring Tavily integration.