skill CX Codex

monitoring-observability · akillness — Claude Code skill for monitoring

Q: How do I install monitoring-observability in Claude Code?

Run `npx skills add akillness/jeo-skills --skill monitoring-observability -a claude-code`. The skill file is at `~/.claude/skills/monitoring-observability/SKILL.md`.

Q: Which tasks does the skill route to other skills?

It sends outage-log root-cause work to `log-analysis`, code-level failure isolation to `debugging`, and bottleneck tuning to `performance-optimization`. LLM tracing goes to `langsmith`; game-engine profiler interpretation goes to `game-performance-profiler`.

Turns service, data-pipeline, or live-ops context into a monitoring brief with a primary mode, useful signals, and a small first implementation slice.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓

npx skills add akillness/jeo-skills --skill monitoring-observability -a claude-code

Open on GitHub

What monitoring-observability does

The skill helps decide what a system should measure and which events should reach a person. It starts from the materials at hand, such as alert rules, an architecture note, or an incident summary, then picks one main mode: service reliability, telemetry setup, data-pipeline monitoring, game live-ops visibility, or a review audit.

Next, it frames the core monitoring question and outlines a small signal plan. That plan can cover evidence to collect, what should page now versus become a later task or dashboard item, and who owns each alert or dashboard family. Reference material covers intake packets, mode boundaries, dashboard and alert checks, and rollout choices.

The skill routes log-based outage diagnosis, code failure isolation, performance tuning, and release execution to neighboring skills. That boundary matters: this skill plans observability; it is not the tool for investigating an incident or carrying out a rollout.

What it helps with

choose service-health signals before launch
audit alerts and dashboards that need changes
monitor pipeline freshness and schema changes
plan visibility for game crashes and launch events
separate urgent pages from later tickets

Example prompts for the agent

Review these service notes and choose an observability mode with one small first step.
Audit these alert rules and dashboards; identify what to keep, fix, or remove.
Plan freshness monitoring for this data pipeline and say what should page a person.

How to install monitoring-observability

1Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill monitoring-observability -a claude-code

2Manually: put the files in place

~/.claude/skills/monitoring-observability/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/monitoring-observability/

1Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill monitoring-observability -a codex

2Manually: put the files in place

.agents/skills/monitoring-observability/SKILL.md

For all projects use ~/.agents/skills/

1Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill monitoring-observability -a cursor

2Manually: put the files in place

.cursor/skills/monitoring-observability/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

1GitHub CLI

gh skill install akillness/jeo-skills monitoring-observability

2Manually: put the files in place

.github/skills/monitoring-observability/SKILL.md

1Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill monitoring-observability -a gemini-cli

2Platform CLI

gemini skills install https://github.com/akillness/jeo-skills --path .agent-skills/monitoring-observability

Manually: put the files in place

.devin/skills/monitoring-observability/SKILL.md

The legacy .windsurf/skills/ path still works

Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill monitoring-observability -a opencode

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about monitoring-observability

How do I install monitoring-observability in Claude Code?

Run npx skills add akillness/jeo-skills --skill monitoring-observability -a claude-code. The skill file is at ~/.claude/skills/monitoring-observability/SKILL.md.

What does monitoring-observability do?

It chooses a primary observability mode for the task and drafts a plan for signals, alerts, dashboards, and ownership. It also routes debugging, log analysis, performance tuning, and rollout work elsewhere.

Which tasks does the skill route to other skills?

It sends outage-log root-cause work to log-analysis, code-level failure isolation to debugging, and bottleneck tuning to performance-optimization. LLM tracing goes to langsmith; game-engine profiler interpretation goes to game-performance-profiler.

monitoring-observability by other authors comes first.

monitoring-observability ahmedasmar A skill for building monitoring and observability: metrics strategy, alerts, dashboards, SLOs and incident troubleshooting. CX Codex +1 493installs wizard Matt Pocock This skill creates an interactive bash wizard for manual setup steps, CI secrets, third-party dashboards, and one-off migrations. 553,369installs hyperframes-cli heygen-com Controls HyperFrames video workflows from the CLI: audits layouts and contrast, edits timeline clips, captures snapshots, and renders locally or in cloud runtimes. CX Codex +1 1,300,000installs setup-pre-commit Matt Pocock This skill configures pre-commit checks for a JavaScript repository, running Prettier, type checking, and tests before each commit. 489,289installs using-git-worktrees Jesse Vincent Prepares an isolated workspace before feature work or plan execution. It checks the repository first, then uses native worktree support or Git. CX Codex 217,153installs finishing-a-development-branch Jesse Vincent This skill checks the test suite and guides branch completion: merge locally, open a Pull Request, or leave the work in place. CX Codex 214,439installs orca-cli stablyai The skill lets an agent manage Orca worktrees, terminals, artifacts and the built-in browser through the orca CLI. Useful when your work already runs inside Orca. CX Codex +1 353,600installs

From the same set22

survey This skill runs a bounded landscape scan before planning or implementation and stores reusable results in .survey/{slug}/. Use it to compare workflows and tools. CX Codex +1 385installs log-analysis A skill that reads runtime logs: it picks one evidence packet first, then isolates the earliest failure. Useful when the log is long and you need the one line that matters. CX Codex +1 384installs plannotator The skill opens a browser approval loop: a human reads a plan, diff or spec and leaves notes before any code gets written. CX Codex +1 379installs marketing-automation The skill turns a vague marketing request into one operating mode, one discipline and one operator packet with an owner and proof. CX Codex +1 377installs authentication-setup Walks you through choosing an auth lane for a web app or API and drawing the line between what the provider owns and what stays in your app. CX Codex +1 368installs state-management A skill that classifies React state into packets and picks the narrowest owner, so you stop arguing about libraries before you know what the state is. CX Codex +1 365installs sprint-retrospective Runs a sprint or milestone retrospective and turns it into a few owned actions instead of another template ritual. CX Codex +1 364installs debugging A skill that walks the agent through a reproduce → isolate → verify loop for concrete bugs, regressions and flaky failures. Useful once you already have a failing test or request. CX Codex +1 361installs