Skills structured-logging
📦

structured-logging

Content revision r1 Medium Risk ⚙️ External commands

Improve Structured Logging

Scattered logs make production incidents slow to diagnose. This skill guides Claude, Codex, and Claude Code to design wide events with actionable request context.

Supports: Claude Codex Code(CC)
📊 66 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "structured-logging" from https://skillstore.io/skills/chemiseblanc-structured-logging.md and its manifest at https://skillstore.io/api/skills/chemiseblanc-structured-logging/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/chemiseblanc-structured-logging.md Signed manifest GET /api/skills/chemiseblanc-structured-logging/manifest Signed lockfile GET /api/skills/chemiseblanc-structured-logging/lockfile

Test it

Using "structured-logging". A checkout service logs payment retry messages across several statements.

Expected outcome:

  • Replace the scattered messages with one request completion event.
  • Keep payment provider, attempt count, latency, final error type, and retry result.
  • Redact payment details and avoid storing full card or token values.

Using "structured-logging". A database timeout log only says that the query failed.

Expected outcome:

  • Add request identifier, operation name, table, timeout value, elapsed time, and rows scanned.
  • Include the user segment only when allowed by policy.
  • Add a suggested remediation that helps the responder act quickly.

Using "structured-logging". An API team wants to query slow enterprise requests.

Expected outcome:

  • Capture duration, status code, endpoint, subscription tier, trace identifier, and relevant feature flags.
  • Use consistent field names so incidents can be filtered across services.

Security Audit

Medium Risk
v8 • 7/5/2026 Open versioned report

The static external command, sensitive file, and reconnaissance alerts are false positives caused by Markdown formatting, observability field names, and defensive guidance. No prompt injection or executable behavior was found. One medium semantic issue remains because the logging guidance can encourage broad collection of user, payment, business, and infrastructure data.

2
Files scanned
509
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
SKILL.md:65-76references/wide-event-fields.md:47-58references/wide-event-fields.md:78-80references/wide-event-fields.md:152-162references/wide-event-fields.md:199-202
Overbroad Sensitive Data Logging Guidance
The skill recommends logging broad user, business, payment, and infrastructure fields. It warns against unnecessary PII, but it should add stronger redaction and minimization rules.
The cited examples and field reference include user identifiers, email, permissions, payment last four, and infrastructure identifiers. The PII warning helps, but it does not fully constrain collection or retention.

Risk Factors

⚙️ External commands (21)
SKILL.md:22-40 SKILL.md:40-46 SKILL.md:46-106 SKILL.md:106-121 SKILL.md:121-122 SKILL.md:122-123 SKILL.md:123-124 SKILL.md:124-130 SKILL.md:130-139 SKILL.md:139-143 SKILL.md:143-163 SKILL.md:163-167 SKILL.md:167-169 SKILL.md:169-173 SKILL.md:173-193 SKILL.md:193-199 SKILL.md:199-238 SKILL.md:238-242 SKILL.md:242-273 SKILL.md:273-279 SKILL.md:279-303
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/chemiseblanc-structured-logging/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/chemiseblanc-structured-logging/security.svg)](https://skillstore.io/skills/chemiseblanc-structured-logging?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/chemiseblanc-structured-logging?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/chemiseblanc-structured-logging/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/chemiseblanc-structured-logging.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

Chemiseblanc. (2026). structured-logging security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/chemiseblanc-structured-logging/audits/8

BibTeX citation

@techreport{chemiseblanc-chemiseblanc-structured-logging-2026, author = {Chemiseblanc}, title = {structured-logging security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/chemiseblanc-structured-logging/audits/8}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "structured-logging security audit report (audit version 8)" version: "unspecified" type: report authors: - name: "Chemiseblanc" date-released: "2026-07-05" url: "https://skillstore.io/skills/chemiseblanc-structured-logging/audits/8" identifiers: - type: other value: "skillstore:chemiseblanc-structured-logging:audit:8" description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score
Doyajin174 Recommended

doyajin174-structured-logging

Skillstore Score 78
Evidence Confidence High
Skillstore usage 11
Updated

2026-08-21

Chemiseblanc Current

chemiseblanc-structured-logging

Skillstore Score 66
Evidence Confidence High
Skillstore usage 6
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
41
Architecture
85
Maintainability
87
Content
72
Community
83
Spec Compliance

What You Can Build

Add Canonical Request Logs

Create a single request completion event with timing, status, user, and business context.

Improve Incident Investigation

Identify fields that help compare failures by customer tier, feature flag, error type, and latency.

Review Logging Standards

Evaluate existing log statements against wide event practices and remove scattered low-context messages.

Try These Prompts

Plan a Wide Event 
Help me design one wide event for this request flow. Include request, user, business, error, timing, and feature flag fields. Flag sensitive fields that need redaction.
Improve Existing Logs 
Review these current log statements and propose a single canonical log line. Preserve useful context, remove duplication, and explain any privacy concerns.
Add Middleware Logging 
Design a middleware logging pattern for this service. Show where to initialize context, enrich it, handle errors, and emit the final event.
Audit Observability Coverage 
Audit this service for structured logging gaps. Compare the current fields with wide event guidance, identify missing dimensions, and prioritize changes by incident value.

Best Practices

  • Define redaction rules before adding high-cardinality user fields.
  • Emit one complete event at request completion instead of many partial messages.
  • Use consistent field names and types across services.

Avoid

  • Do not log raw tokens, passwords, full card numbers, or unnecessary PII.
  • Do not split one request story across many unconnected log lines.
  • Do not rely only on low-cardinality messages like failed or timeout.

Frequently Asked Questions

What is a wide event?
A wide event is one structured log entry with many useful fields about a request or operation.
Does this skill run commands?
No. It is documentation and guidance for designing structured logs.
Can I use it with any logging library?
Yes, but you must adapt the examples to your language, framework, and logging backend.
How does it help debugging?
It keeps request, user, timing, error, and business context together so incidents are easier to query.
Should I log user data?
Only log user data that is necessary, approved, and protected by redaction and retention controls.
Does it replace tracing or metrics?
No. It complements traces and metrics by adding rich event context for investigation.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/Chemiseblanc/ai/tree/main/skill/structured-logging

Ref

02f077c174c5335e2f5d02ca15e77b70d9543e58

Maintenance freshness

7/18/2026

Usage

4 downloads · 349 views

File structure

📁 references/

📄 wide-event-fields.md

📄 SKILL.md

More from Chemiseblanc

View all

Related Skills

View all