Skip to content
Back to skills

Logging Error Handling

ASecurity

`task-agent`/`review-agent`: use when structured errors, logs, correlation, redaction, propagation, or safe diagnostics change; skip when logging/error handling is unaffected.

  • 7 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 8, 2026
businesssecurity

Works with

  • cli

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add machenjie/rd-skills --skill logging-error-handling --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Logging Error Handling?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Logging Error Handling
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/machenjie-logging-error-handling/badge)](https://www.skillsdirectory.com/skills/machenjie-logging-error-handling)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: logging-error-handling
description: "`task-agent`/`review-agent`: use when structured errors, logs, correlation, redaction, propagation, or safe diagnostics change; skip when logging/error handling is unaffected."
---

# logging-error-handling

## Registry Trigger

**Use when**

- design structured errors logging context propagation and safe diagnostics

**Do not use when**

- no task-local logging error handling decision is required

## Skill Role

Define owned error translation/outcome and diagnostic event/correlation/redaction/volume/reconstruction; consume but do not own protected audit contracts.

## High-Value Rules

- Translate once at the owned boundary while preserving cause, caller action, outcome, and reconstruction correlation.
- Choose no new log until its audience, decision, owner, and outcome are named.
- Load only the Reference selected by the Targeted References table for the current decision or proof gap.

## Anti-Patterns

- Local success substituted for evidence of the logging error handling contract.

## Stop Conditions

- Escalate ambiguous ownership, broken correlation, unclear sensitive-data policy, possible secret/tenant leak, unbounded volume, or unreconstructable outcome.

## Output Contract

- logging and error decision with ownership, external meaning, diagnostic events, correlation, outcome classification, redaction, volume bounds, reconstruction evidence, unverified paths or sinks, proof limits, and residual risk
- accepted audit-contract dependency or named `logging-design-gate`/`security-privacy-gate` handoff for each security-relevant outcome; do not claim protected audit-record closure from diagnostic-log evidence

## Targeted References

| Path | Type | Load when | Do not load when | Required by | Required output |
|---|---|---|---|---|---|
| [benchmarks and patterns](references/benchmarks-and-patterns.md) | benchmark-pattern | log schema correlation redaction or error mapping choices remain unresolved | existing logging policy selects fields levels and client contract | task-agent, review-agent | option-comparison, selected-approach |
| [checklist](references/checklist.md) | decision-checklist | change affects error taxonomy correlation redaction audit or retry context | no logging sink or client-error behavior changes | task-agent, review-agent | checklist-result, residual-risk |
| [evidence patterns](references/evidence-patterns.md) | evidence-pattern | redaction correlation audit or error-mapping claims need fresh proof | current fixtures and captured outputs prove each logging claim | task-agent, review-agent | evidence-record, proof-limit, residual-risk |

Files in this skill

  • SKILL.md4.7 KB
  • examples/example-output.md902 B
  • references/benchmarks-and-patterns.md3.6 KB
  • references/checklist.md963 B
  • references/evidence-patterns.md4.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…