octo-agentDebugging and investigation agent for OctoMesh — diagnoses CK model failures (ResolveFailed, modelState 2, broken dependencies, version-bump cascades), blueprint install failures, and CK migration problems; inspects MongoDB tenant databases directly; runs selective DebugL builds and targeted tests t
octo-app-builderBuild a complete OctoMesh-powered application end to end — a custom Construction Kit data model published to the CK catalog, an HTTP API made of dataflow pipelines on the tenant's Mesh Adapter, an optional containerized web app the Communication Operator rolls out to Kubernetes, and a blueprint that
octo-ck-miroVisualizes OctoMesh Construction Kits as UML class diagrams on a Miro board. Reads CK YAML definitions from a specified git branch in the local octo-construction-kit checkout (non-destructive via git show) and creates one detailed UML diagram per CK — types with attributes and datatypes, records, en
octo-commitStructured workflow for committing finished work across OctoMesh repositories: scans repos for changes, resolves or creates the Azure DevOps work item, builds the AB# commit message and PR title (AB#<id> <Fix|New|Chore|Refactor|Test|Docs>: …), verifies the build/tests, and optionally opens a PR and
octo-deployGuide the promotion of an OctoMesh-powered app from local dev to the shared test-2 environment — publish the CK model and blueprint to the shared GitHub catalogs (octo-ckc / octo-bpm), push the app image to <registry>, register a test-2 octo-cli context, install + deploy on the target tenant, and ve
octo-devtoolsDrives OctoMesh local development through the octo-tools PowerShell cmdlets — building repos in dependency order, starting and stopping services (always non-interactively for agents via Start-Octo -nonInteractive $true / Stop-Octo), managing Docker or local kind Kubernetes infrastructure, syncing an
octo-logs-setupOne-time setup and health check of the Dash0 MCP connection that /octo-logs relies on to read OctoMesh cluster logs. Walks through registering the Dash0 MCP server in Claude Code, the browser OAuth login via /mcp, and verifies access with listDatasets. Replaces the former Loki credential setup (LOKI
octo-logsQuery and trace OctoMesh logs, traces and metrics through the Dash0 MCP server — no credentials, port-forwards or logcli needed. Filter by namespace/container/pod/service/severity, search message bodies, count error rates with D0QL (SQL), trace an error across pod redeployments and jump from a log l
octo-mcpDevelop and extend the OctoMesh MCP server (octo-mcp-service) — the Model Context Protocol server exposing ~181 tools that mirror octo-cli plus generic CK CRUD and aggregation/stream-data queries, used by AI assistants to administer OctoMesh tenants without the CLI or GraphQL. Use when adding or mod
octo-operatorUse this skill for developing and operating the OctoMesh Communication Operator — the .NET 10 KubeOps Kubernetes operator that watches CommunicationPool CRDs, connects to the Communication Controller over SignalR (/operatorHub), and runs helm upgrade/uninstall for Adapter and Application workloads.
octoPrimary entry point and router for ALL OctoMesh tasks. Drives the octo-cli for platform administration (users, roles, groups, tenants, clients, identity providers, blueprints, CK catalog/library management, stream-data archives, communication adapters/pipelines, AI services) and explores the data mo
pipeline-expertAuthoring, reading, editing, debugging, and validating OctoMesh ETL pipeline YAML — the node-by-node config, DataContext/JSONPath data flow, triggers, transformations, entity CRUD via CreateUpdateInfo/ApplyChanges, archive (CrateDB) writes, inter-pipeline chaining within a DataFlow, and deployment/d
refinery-studioGuides Angular development on the OctoMesh Data Refinery Studio (octo-frontend-refinery-studio) — the main web app for CK model design, dashboards, queries, pipelines, and visualizations (distinct from the older admin panel). Covers the tech stack, multi-tenant /:tenantId/ routing, the OctoGraphQlDa