npx skills add smithery/VilnaCRM-Org --skill observability-instrumentation
rockclaver/systemcraft
observability-instrumentation
Adds structured logging, metrics, tracing, and actionable alerts so financial systems are explainable in production. Use for hard-to-diagnose incidents, new money-moving paths, or drift/queue-depth/latency/failure-rate observability.
Installation
$
npx skills add rockclaver/systemcraft --skill observability-instrumentation
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
appinsights-instrumentation
Similar name
microsoft/azure-skills
Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns…
566.6K installs
appinsights-instrumentation
Similar name
github/awesome-copilot
Instrument a webapp to send useful telemetry data to Azure App Insights
9.6K installs
posthog-instrumentation
Similar name
posthog/posthog-for-claude
Automatically add PostHog analytics instrumentation to code. Triggers when user asks to add tra…
1.8K installs
arize-instrumentation
Similar name
github/awesome-copilot
Adds Arize AX tracing to an LLM application for the first time.
1.1K installs
planetscale-codebase-sqlcommenter-instrumentation
Similar name
planetscale/skills
Inspect an application repository connected to PlanetScale and recommend SQLCommenter-compatibl…
13 installs
sentry-instrumentation-guide
Similar name
getsentry/sentry-for-ai
Decide which Sentry signal to reach for when instrumenting code — error, span, span attribute, …
952 installsAlso in this package
Other skills from rockclaver/systemcraft · top by installs.
npx skills add rockclaver/systemcraft
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude Code
Not declared
Cursor
Not declared
Codex
Not declared
GitHub Copilot
Not declared
Windsurf
Not declared
Gemini CLI
Not declared
Cline
Not declared
OpenCode
Not declared
Also listed on
Alternate registries and mirrors of this skill.
Repository health
Default branch
main
Open issues
0
Status
Active
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,945 B -
docs
SUMMARY.md270 B
History
- First seen on skills.sh
- First recorded snapshot · 5 installs
SKILL.md
Observability Instrumentation
Use when scale-readiness-review/resilience-patterns says "add a metric"; use debug-runtime to diagnose live failures.
Workflow
- Pick the path (payment, payout, settlement, reconciliation, hot endpoint); list the questions ops will ask (did X succeed, failure rate/p95, queue depth, reconciliation drift).
- Log: structured key-value/JSON, correlation id, stable business keys (transaction, account, idempotency key, provider ref, tenant) — never secrets/PANs/credentials; log decisions/transitions and call boundaries.
- Metrics via the repo's client:
- RED: Rate, Errors, Duration (histogram) for request-driven paths. - USE: Utilization, Saturation, Errors for resources (pools, workers, connections). - Domain signals: queue depth/age, settlement lag, retry counts, breaker state, reconciliation drift, idempotency-conflict rate. - Label by operation/outcome; bound cardinality.
- Trace: propagate context through jobs/queues/calls; span each external call with duration/status.
- Alert on symptoms users feel (error rate, latency, backlog, drift); SLO thresholds/burn rates; name cause and next step; delete unused alerts.
- Verify: trigger the path, confirm logs/metrics/traces appear and alerts fire on failure.
Guardrails
- Do not log secrets, full card numbers, credentials, or unmasked PII.
- Do not use unbounded label cardinality (raw ids, emails).
- Do not rely on average latency; use histograms/percentiles.
- Do not add alerts without an owner and a response action.
- Do not over-instrument the hot path; sample where appropriate.