Skip to content
Agentmart
Submit a tool

observability-logging

Use when diagnosing bugs, performance issues, production behavior, flaky systems, or any task where logs, metrics, traces, profiles, or structured runtime…

Skill by fabiocantone

IndexedMIT
Write a review

Chalk Labs

Need help deploying observability-logging?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/fabiocantone-observability-logging

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when diagnosing bugs, performance issues, production behavior, flaky systems, or any task where logs, metrics, traces, profiles, or structured runtime evidence are needed before choosing a fix

Use cases: productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/observability-logging

What's inside

Skill name
observability-logging
Description
Use when diagnosing bugs, performance issues, production behavior, flaky systems, or any task where logs, metrics, traces, profiles, or structured runtime evidence are needed before choosing a fix
License
MIT
Instructions
57 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Observability Logging

## Overview

No serious diagnosis should rely only on static code reading when runtime behavior matters. Before selecting a fix, check what the system logs, measures, traces, and profiles. If the data is missing, propose the smallest useful instrumentation before committing to a root cause.

## Required Gate

For non-trivial runtime, performance, integration, or production issues:

1. Identify existing logs, metrics, traces, profiles, reports, and debug flags.
2. State what each signal proves and what it cannot prove.
3. Identify missing signals needed to distinguish hypotheses.
4. Add or propose minimal instrumentation when the missing signal blocks diagnosis.
5. Define privacy and noise limits.
6. Prefer structured logs and metrics over raw transcript dumps or broad console spam.

## Observability Plan Shape

```markdown
## Observability And Logging Plan

| Signal | Source | Proves | Gap | Action |
| --- | --- | --- | --- | --- |
|  |  |  |  |  |

Privacy/noise limits:

Minimum instrumentation before fix:
```

## Good Signals

- Structured logs with request/task/message IDs.
- Timing spans around suspected slow paths.
- Counters for retries, errors, queue depth, dropped events, cache hits, and render counts.
- Performance profiles for UI/rendering issues.
- Persistent benchmark reports for performance claims.
- Correlated frontend/backend/native IDs for cross-layer flows.

## Bad Signals

- Raw secrets, API keys, personal data, prompts, or full chat transcripts.
- Console spam without IDs or timestamps.
- Logs that prove only that a function ran, not how long it took or what state mattered.
- Metrics that cannot be tied back to a hypothesis.

## Completion Criteria

Before claiming a diagnosis is strong:

- Say which runtime signals were checked.
- Say which signals were missing.
- Say whether missing instrumentation blocks the conclusion.
- Add the instrumentation task to the plan when needed.

From fabiocantone/codersteroids, MIT.

More from fabiocantone/codersteroids

Signals

Stars
0
Forks
0
Open issues
1
Last commit (this folder)
May 26, 2026 (5 months ago)
Last release
May 27, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from fabiocantone

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get observability-logging running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying observability-logging?

CallGet help
Cite this page

observability-logging skill. Agent Mart. https://agentmart.dev/skills/fabiocantone-observability-logging (last updated 2026-10-24)