Monitoring Observability

Q: Why use Monitoring Observability on TypingMind?

Because you install it once and use it with any model. Monitoring Observability is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

Q: How do I install Monitoring Observability in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cosmicstack-labs/mercury-agent-skills/tree/main/categories/devops/monitoring-observability. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Q: Which AI models can use Monitoring Observability?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

Q: How many AI models can I use with Monitoring Observability?

As many as you like. As long as a model supports skills, you can use Monitoring Observability with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Q: Is the Monitoring Observability AI skill free?

Yes. It is published on GitHub by cosmicstack-labs under the MIT license. You only pay your own AI provider for the tokens you use.

Q: What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

Q: How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Organization

cosmicstack-labs

monitoring-observability

Prometheus, Grafana, ELK/Loki, Jaeger, metrics, logging, tracing, and alerting

Overview

Publisher	cosmicstack-labs
Repository	`mercury-agent-skills`
Skill name	`monitoring-observability`
Stars	485
Forks	63
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by cosmicstack-labs on GitHub. Read the source before you install it.

Installation

Install the Monitoring Observability AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/cosmicstack-labs/mercury-agent-skills/tree/main/categories/devops/monitoring-observability
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/cosmicstack-labs/mercury-agent-skills/tree/main/categories/devops/monitoring-observability

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/cosmicstack-labs/mercury-agent-skills.git /tmp/mercury-agent-skills
mkdir -p .claude/skills
cp -r /tmp/mercury-agent-skills/categories/devops/monitoring-observability .claude/skills/monitoring-observability

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Monitoring Observability in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Monitoring Observability on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Monitoring Observability is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Monitoring & Observability

Build comprehensive observability for your systems.

The Three Pillars

1. Metrics (Prometheus)

yaml
# Instrument your app
http_requests_total{method="GET", endpoint="/api/users", status="200"} 1024
http_request_duration_seconds{quantile="0.95"} 0.235

2. Logging (Loki / ELK)

Structured JSON logging
Include: timestamp, level, service, trace_id, message
Centralized log aggregation
Log levels: DEBUG < INFO < WARN < ERROR < FATAL

3. Tracing (Jaeger / Tempo)

Trace every request across services
Span: individual operation with timing
Distributed context propagation via trace ID headers
Sample 1-10% of production traffic

Alerting (Alertmanager)

Alert Severity

Severity	Response Time	Channel
Critical	Immediately	PagerDuty + SMS
Warning	1 hour	Slack + Email
Info	Next day	Dashboard

Golden Signals (Google SRE)

Latency: Time to respond
Traffic: Requests per second
Errors: Error rate (5xx, exceptions)
Saturation: Resource utilization

Dashboard Design (Grafana)

Rules

3-5 panels per row
Time series with trend lines, not raw numbers
RED metrics: Rate, Errors, Duration per service
USE metrics: Utilization, Saturation, Errors per resource
Include annotations for deployments, incidents

Best Practices

Monitor from outside (synthetic checks)
Monitor everything, alert on what matters
Use SLOs to define what's "good enough"
Test alerts (fire drills, tabletop exercises)
Review dashboards monthly with the team

Frequently asked questions

What does the Monitoring Observability AI skill do?

Prometheus, Grafana, ELK/Loki, Jaeger, metrics, logging, tracing, and alerting

Why use Monitoring Observability on TypingMind?

Because you install it once and use it with any model. Monitoring Observability is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Monitoring Observability in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cosmicstack-labs/mercury-agent-skills/tree/main/categories/devops/monitoring-observability. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Monitoring Observability?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Monitoring Observability?

As many as you like. As long as a model supports skills, you can use Monitoring Observability with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Monitoring Observability AI skill free?

Yes. It is published on GitHub by cosmicstack-labs under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Land And Deploy

garrytan

CommunityPopular

Land and deploy workflow. (gstack)

Clawsweeper

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions…

Openclaw Ci Limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Openclaw Testing

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Monitoring & Observability

The Three Pillars

1. Metrics (Prometheus)

2. Logging (Loki / ELK)

3. Tracing (Jaeger / Tempo)

Alerting (Alertmanager)

Alert Severity

Golden Signals (Google SRE)

Dashboard Design (Grafana)

Rules

Best Practices

Frequently asked questions

Related AI Skills

Set up your own AI workspace now