Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
Add structured JSON logging, observability commands, and idempotent setup scripts to a project.
Install Wire Observability
$ npx skills add danielvm-git/bigpowers --skill wire-observability -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install danielvm-git/bigpowers wire-observability --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/wire-observability .claude/skills/wire-observability && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "wire-observability" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/wire-observability into .claude/skills/wire-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wire-observability", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/danielvm-git/bigpowers/tree/main/skills/wire-observabilityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add danielvm-git/bigpowers --skill wire-observability -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install danielvm-git/bigpowers wire-observability --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/wire-observability .agents/skills/wire-observability && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wire-observability" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/wire-observability into .agents/skills/wire-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wire-observability", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add danielvm-git/bigpowers --skill wire-observability -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install danielvm-git/bigpowers wire-observability --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/wire-observability .cursor/skills/wire-observability && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wire-observability" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/wire-observability into .cursor/skills/wire-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wire-observability", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/danielvm-git/bigpowers.git --path skills/wire-observability--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add danielvm-git/bigpowers --skill wire-observability -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install danielvm-git/bigpowers wire-observability --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/wire-observability .gemini/skills/wire-observability && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wire-observability" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/wire-observability into .gemini/skills/wire-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wire-observability", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install danielvm-git/bigpowers wire-observabilityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add danielvm-git/bigpowers --skill wire-observability -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/wire-observability .github/skills/wire-observability && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wire-observability" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/wire-observability into .github/skills/wire-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wire-observability", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add danielvm-git/bigpowers --skill wire-observability -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install danielvm-git/bigpowers wire-observability --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/wire-observability .opencode/skills/wire-observability && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wire-observability" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/wire-observability into .opencode/skills/wire-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wire-observability", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
wire-observability- GitHub stars
- 256
- Token cost
- ~969 tokens
- SKILL.md length
- 387 words
- Files
- 1
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- MIT
At a glance
Add structured JSON logging, observability commands, and idempotent setup scripts to a project.
- Works in 5 steps: Assess current state → Add structured JSON logging → Document observability commands in… → …
- A project needs production-readiness instrumentation
- SKILL.md covers What this sets up, Process and BCP Plus Integration
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Wire Observability is an agent skill from danielvm-git/bigpowers. 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.
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Observability. The repository describes itself as: Agent skills synthesizing years of software engineering discipline into a prescriptive methodology for solo developers. The licence is MIT.
When your agent uses it
- A project needs production-readiness instrumentation
- User wants structured logging
- As a production-readiness gate at any phase of development
Example prompts
- “/wire-observability”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 812d57a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json, markdown and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Wire Observability loads about 969 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 387 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from danielvm-git/bigpowers at commit 812d57a, republished under its MIT licence (© danielvm-git). 387 words, ~969 tokens.
Download SKILL.mdSave it as
.claude/skills/wire-observability/SKILL.md (or your agent's skills folder).- name
- wire-observability
- description
- 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.
- model
- sonnet
- effort
- standard
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
- Structured JSON logging — machine-readable logs for debugging and observability
- Observability commands — how to check the system's health documented in CLAUDE.md
- 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:
{
"level": "info",
"timestamp": "2025-01-15T10:23:45.123Z",
"message": "User created",
"userId": "usr_abc123",
"requestId": "req_xyz789"
}Guidelines:
- Include
level,timestamp,messagein every entry - Add context fields relevant to the operation (userId, requestId, traceId)
- Log at boundaries: HTTP requests in/out, DB queries, external API calls, background job start/end
- Log errors with stack traces:
logger.error({ err, context }, "Operation failed") - Never log secrets, passwords, tokens, or PII
3. Document observability commands in CLAUDE.md
Add an "Observability" section to the project's CLAUDE.md:
## Observability
| What | Command |
|------|---------|
| View logs | `<log tail command>` |
| Health check | `<health check command>` |
| Check DB connection | `<db ping command>` |
| View metrics | `<metrics command>` |Show full SKILL.md (161 more words)Show less
4. Write idempotent setup scripts
An idempotent script can be run multiple times and always produces the same result (no errors on re-run).
Pattern: check if the thing already exists before creating it.
#!/usr/bin/env bash
set -euo pipefail
# Idempotent: only create if not exists
if ! psql -c "SELECT 1 FROM pg_database WHERE datname = 'myapp'" | grep -q 1; then
createdb myapp
echo "Database created"
else
echo "Database already exists, skipping"
fiPlace setup scripts in scripts/setup.sh (or language-appropriate equivalent). Document the command in CLAUDE.md under Commands.
5. Verify
- Run the app and confirm JSON logs appear in the correct format
- Run
scripts/setup.shtwice — second run should produce no errors - Health check command returns success
- No sensitive data in log output
BCP Plus Integration
This skill maps to BCP Plus dimension 11 (Quality Attributes) — specifically performance, reliability, and availability instrumentation. Structured logging, health checks, and idempotent setup scripts are observable manifestations of quality-attribute requirements. The NFR Gate rule applies: standard-expectation items (e.g., "the app should log errors") score 0 with a one-line rationale; only above-standard quality requirements (e.g., p99 latency tracking, SLO-based alerting) contribute to the dimension 11 count. See docs/references/bcp-plus.md for the full 13-dimension framework and NFR Gate pattern.
© danielvm-git, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/wire-observability of danielvm-git/bigpowers.
Open the folder on GitHubat commit 812d57a
Compare with similar skills
Wire Observability next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Wire Observability this skilldanielvm-git/bigpowers | 256 | — | ~969 | Automated safety check: Pass | MIT | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 8 repos | ~4.3k | Automated safety check: Pass | None | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| Kubeshark KFL2 Filter Referencekubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Kubernetes Network Root Cause Analysiskubeshark/kubeshark | 12k | — | ~5.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Kubeshark KFL2 Filter Reference
kubeshark/kubeshark
Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
Kubernetes Network Root Cause Analysis
kubeshark/kubeshark
Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.
Caveman Gateway Setup
JuliusBrussee/caveman
Routes every LLM call in a repository through the Caveman Cloud gateway in record mode, so requests and costs are measured without changing behavior.
More from danielvm-git/bigpowers
All 39 skills in this repoExtract Design
danielvm-git/bigpowers
Extract a Google DESIGN.md file from an HTML prototype (claude.ai/design or any styled page) using Puppeteer, producing machine-readable tokens and AI-generated prose.
Align Grid
danielvm-git/bigpowers
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one.
Assess Impact
danielvm-git/bigpowers
Analyze the blast radius of a proposed change before any code is written.
Audit Code
danielvm-git/bigpowers
Self-review checklist for the coding agent to run before dispatching a reviewer.
Audit Plan
danielvm-git/bigpowers
Evaluate an incoming project plan against bigpowers principles and conventions, surface gaps, and produce a READY/NOT READY verdict before engagement begins.
Compose Workflow
danielvm-git/bigpowers
Chain multiple bigpowers skills into a custom workflow recipe saved in specs/.
Related
Categories
Questions about Wire Observability
What does Wire Observability do?
Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Wire Observability is an agent skill from danielvm-git/bigpowers. Add structured JSON logging, observability commands, and idempotent setup scripts to a project.
When should I use Wire Observability?
Wire Observability fits situations like: A project needs production-readiness instrumentation; user wants structured logging; as a production-readiness gate at any phase of development.
How do I install Wire Observability in Claude Code?
Run `npx skills add danielvm-git/bigpowers --skill wire-observability -a claude-code`. Or copy the skill folder (skills/wire-observability in danielvm-git/bigpowers) into .claude/skills/wire-observability in your project. Claude Code loads it when a task matches its description.
How do I install Wire Observability in Codex?
Run `npx skills add danielvm-git/bigpowers --skill wire-observability -a codex`. Or copy the skill folder (skills/wire-observability in danielvm-git/bigpowers) into .agents/skills/wire-observability in your project. Codex loads it when a task matches its description.
Can I use Wire Observability in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add danielvm-git/bigpowers --skill wire-observability -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wire-observability, .gemini/skills/wire-observability, .github/skills/wire-observability and .opencode/skills/wire-observability in your project.
What does Wire Observability need to run?
SKILL.md names no scripts, command-line tools or credentials: Wire Observability is instructions for the agent only.
Does Wire Observability access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Wire Observability safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Wire Observability use?
Wire Observability is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wire Observability use?
About 969 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Wire Observability?
Skills that share tags, products or a category with Wire Observability: Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars), Kubeshark Installer (kubeshark/kubeshark, 12k stars), Kubeshark KFL2 Filter Reference (kubeshark/kubeshark, 12k stars) and KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wire Observability?
danielvm-git (a GitHub user) maintains it in danielvm-git/bigpowers, which has 256 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on September 21, 2026.
Source: danielvm-git/bigpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.