Wire Observability
Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.
Install
npx skills add danielvm-git/bigpowers --skill wire-observabilitygit clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p ~/.claude/skills
cp -r /tmp/bigpowers/.cline/skills/wire-observability ~/.claude/skills/wire-observabilityPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Wire Observability
> **HARD GATE** — **HARD GATE** — Observability is not optional. Before shipping, verify: structured logging is in place, key metrics are instrumented, error cases emit signals. 'We'll add metrics later' becomes 'never.'
Add structured logging, observability commands, and idempotent setup scripts. Can be invoked at any phase — recommended at the end of the first working slice, before the first deploy.
## What this sets up
1. **Structured JSON logging** — machine-readable logs for debugging and observability
2. **Observability commands** — how to check the system's health documented in CLAUDE.md
3. **Idempotent setup scripts** — scripts that can be run repeatedly without side effects
## Process
### 1. Assess current state
Check what's already in place:
- Is there a logging library? (pino, winston, structlog, zap, slog, etc.)
- Is logging JSON or plain text?
- Is there a health check endpoint or command?
- Are there setup scripts? Are they idempotent?
### 2. Add structured JSON logging
**For user-facing CLI output:** plain text is fine.
**For everything else:** structured JSON.
Structured log entry format:
```json
{
"level": "info",
"timestamp": "2025-01-15T10:23:45.123Z",
"message": "User created",
"userId": "usr_abc123",
"requestId": "req_xyz789"
}
```
Guidelines:
- Include `level`, `timestamp`, `message` in every entry
- Add context fields relevant to the operation (userId, requestId, traceId)Details
- Skill name
wire-observability- Repository
- danielvm-git/bigpowers
- Path
.cline/skills/wire-observability/SKILL.md- License
- MIT
- Repo updated
- 9 November 2026
FAQ
What does the Wire Observability skill do?
Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.
How do I install the Wire Observability skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add danielvm-git/bigpowers --skill wire-observability. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Wire Observability popular?
It lives in danielvm-git/bigpowers, which has 292 GitHub stars and 23 forks.
Related skills
Align Grid
292danielvm-git/bigpowers
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay that lives in the SAME content box as the content, subgrid "bands" so every element snaps to a column line, an 8px baseline lock, and runtime OPTICAL ALIGNMENT that puts display type's i
Assess Impact
292danielvm-git/bigpowers
Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT_LATEST.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks "what does this break?".
Audit Code
292danielvm-git/bigpowers
Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.
Grad Strat Agency
248asgard-ai-platform/skills
Apply Agency Theory (Jensen and Meckling, 1976) to diagnose principal-agent problems — moral hazard, adverse selection — and design governance mechanisms to align interests. Use this skill when the user needs to analyze conflicts of interest between owners and managers, design incentive or monitoring structures, evaluate corporate governance effectiveness, or when they ask 'how do we ensure managers act in shareholders interest', 'why is this incentive plan failing', or 'what governance mechanisms reduce agency costs'.
Wire CI
292danielvm-git/bigpowers
CI pipeline setup with bundled, forge-neutral templates and local validation. Detects the forge from the git remote, generates workflows for supported forges, and skips honestly for the rest. The CI equivalent of wire-observability.
Msp Website Setup
121RTFM-IT-Services-LLC/msp-claude-skills
Your MSP's standard process for setting up a new static client website hosted on your static hosting platform with a git-based dev/prod CI/CD pipeline, plus the client-practice rules around it. Use this skill whenever starting a new website project for a client, setting up a static site, initializing a website repo, connecting a site to your static hosting platform, or wiring up dev and prod deployments for a small business site, even if the user just says "let's build a site for this client" or "set up the repo for the new website". Also trigger for questions about who owns a client's site, d
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.