Octo Logs Setup

One-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_USERNAME / LOKI_PASSWORD) — Loki no longer exists; old LOKI_* variables can be deleted from the private profile. Run this when the mcp__dash0__* tools are missing or return auth errors. Trigger on: set up log access, configure log access, octo-logs setup, Dash0 MCP, dash0 tools missing, mcp__dash0

10 starsAI, LLMs & Agents Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add meshmakers/octo-claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add meshmakers/octo-claude-skills --skill octo-logs-setup
Manual install
git clone --depth 1 https://github.com/meshmakers/octo-claude-skills.git /tmp/octo-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/octo-claude-skills/skills/octo-logs-setup ~/.claude/skills/octo-logs-setup

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# OctoMesh Log Access — Dash0 MCP Setup

## Overview

`/octo-logs` reads logs exclusively through the **Dash0 MCP server**
(`mcp__dash0__*` tools). There are no log credentials to store: the MCP
connection authenticates with Dash0 via OAuth in the browser, and Claude Code
keeps the token. Loki/logcli and the `LOKI_USERNAME` / `LOKI_PASSWORD` variables
are obsolete.

**Internal details** — the MCP endpoint URL of the organization, the Dash0
organization to log in to, the datasets: if the plugin `octo-claude-pm` is
installed, its internal reference `agent-operating-rules/references/dash0.md`
holds them. This public plugin deliberately contains none. Without that plugin,
ask a colleague or your Dash0 administrator for the MCP endpoint.

## Step 1 — check whether the tools are already there

Call `mcp__dash0__listDatasets`.

- Works and returns datasets → setup is done, go back to `/octo-logs`.
- Tool unknown / not listed → Step 2.
- Auth error → Step 3.

## Step 2 — register the Dash0 MCP server (user runs this)

Register the MCP server for the workspace (or with `--scope user` for all
projects). `<mcp-endpoint>` is the HTTP MCP URL of your organization's Dash0
region (see the internal reference):

```bash
claude mcp add --transport http --scope local dash0 <mcp-endpoint>
```

Then restart the Claude Code session so the tools load.

## Step 3 — log in

In Claude Code run `/mcp`, select **dash0** and choose *Authenticate*. The browser
Read the full skill on GitHub

Details

Skill name
octo-logs-setup
Path
skills/octo-logs-setup/SKILL.md
Repo updated
17 November 2026

FAQ

What does the Octo Logs Setup skill do?

One-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_USERNAME / LOKI_PASSWORD) — Loki no longer exists; old LOKI_* variables can be deleted from the private profile. Run this when the mcp__dash0__* tools are missing or return auth errors. Trigger on: set up log access, configure log access, octo-logs setup, Dash0 MCP, dash0 tools missing, mcp__dash0

How do I install the Octo Logs Setup skill?

Claude Code plugin: /plugin marketplace add meshmakers/octo-claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Octo Logs Setup popular?

It lives in meshmakers/octo-claude-skills, which has 10 GitHub stars and 0 forks.

Related skills

Octo

10

meshmakers/octo-claude-skills

Primary 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 model and runtime instances via GraphQL. Routes specialized work to sibling skills. When unsure which OctoMesh skill to use, start here. Trigger on: OctoMesh, octo-cli, CLI command, environment switch, auth/login, AuthStatus, tenant, temporary tenant, test tenant, user, role, group, client credentials

Software Development

Octo Agent

10

meshmakers/octo-claude-skills

Debugging 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 to isolate a regression; and manages Docker volume backups for safe rollback. Use it when something broke after a build, version bump, merge, or upgrade and you need to find the root cause safely. Trigger on: help me fix, investigate this bug, what broke, isolate the issue, why is the model broken, R

AI, LLMs & Agents

Octo App Builder

10

meshmakers/octo-claude-skills

Build 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 packages all of it so a single InstallBlueprint provisions any tenant. Encodes the verified build sequence (model → pipelines → app image → blueprint → install → deploy → verify) and the pitfalls that silently break it (blueprint catalog cache, pipeline registration rotation, HTTP response shaping,

DevOps & Cloud

Octo MCP

10

meshmakers/octo-claude-skills

Develop 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 modifying MCP tools, classifying tool risk, wiring *ClientContext helpers, building file-transfer flows, or following the mandatory test conventions. Trigger on: MCP tool development, octo-mcp-service, adding MCP tools, McpRisk, MCP server, model context protocol server work in OctoMesh.

AI, LLMs & Agents

Octo Logs

10

meshmakers/octo-claude-skills

Query 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 line to its trace. Loki/Promtail/LogQL are not used any more. Run /octo-logs-setup if the dash0 MCP tools are missing. Trigger on: logs, cluster logs, view logs, service logs, error logs, grep logs, tail logs, Dash0 logs, getLogRecords, D0QL, trace error, error over deployments, log retention, namesp

AI, LLMs & Agents

Build MCP App

9

Vincent-the-gamer/skills

This skill should be used when the user wants to build an "MCP app", add "interactive UI" or "widgets" to an MCP server, "render components in chat", build "MCP UI resources", make a tool that shows a "form", "picker", "dashboard" or "confirmation dialog" inline in the conversation, or mentions "apps SDK" in the context of MCP. Use AFTER the build-mcp-server skill has settled the deployment model, or when the user already knows they want UI widgets.

AI, LLMs & Agents

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.