skills.rest
iceflower
iceflowerCOMMUNITY
Explore all skills by this author →
GitHub

logging

Establishes logging standards with SLAs, severity levels, and payload masking for HIPAA/GDPR compliance.

1|Updated Mar 16, 2026
Search Tags:#security#logging#observability#standards#data masking#structured logging
One-click install
npx skills add https://github.com/iceflower/opencode-agents-and-skills --skill logging-iceflower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: logging
Source: https://github.com/iceflower/opencode-agents-and-skills/tree/main/skills/logging
Command: npx skills add https://github.com/iceflower/opencode-agents-and-skills --skill logging-iceflower

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill establishes clear guidelines for logging practices, ensuring consistency, readability, and the secure handling of sensitive information within application logs.

Core Features & Use Cases

  • Log Level Standardization: Defines appropriate usage for ERROR, WARN, INFO, DEBUG, and TRACE levels.
  • Structured Logging: Enforces a consistent format for log messages, including timestamps, trace IDs, and context.
  • Sensitive Data Masking: Provides rules and examples for masking PII and secrets to prevent data leakage.
  • Use Case: Ensure all application logs adhere to company standards for debugging, monitoring, and security compliance.

Quick Start

Apply the logging skill to ensure all sensitive data is masked before writing to the log file.

Frequently Asked Questions about logging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I mask sensitive data and PII in application logs?▼

To mask sensitive data in application logs, apply specific masking techniques to PII and secrets before writing entries. This prevents data leakage by ensuring all sensitive information is obfuscated according to security compliance rules.

What is structured logging and why do I need it for observability?▼

Structured logging enforces a consistent JSON format for log messages, including timestamps, trace IDs, and context. It is needed for observability because standardized formats enable reliable debugging, monitoring, and security compliance across applications.

When should I use ERROR, WARN, INFO, DEBUG, and TRACE log levels?▼

Log level standardization defines appropriate usage for ERROR, WARN, INFO, DEBUG, and TRACE levels. Use ERROR for failures, WARN for anomalies, INFO for general operations, DEBUG for diagnostics, and TRACE for detailed execution flow.

How do I standardize application logs for debugging and monitoring?▼

Standardize application logs by enforcing structured JSON logging with consistent message formats, timestamps, and trace IDs. This ensures clarity and consistency across applications, enabling reliable debugging and monitoring operations.

Does structured logging require specific formats for security compliance?▼

Structured logging for security compliance requires adherence to specific JSON formats and masking techniques for PII and secrets. This ensures sensitive data handling meets company standards for application observability and security.

What are the limitations of not standardizing log levels and formats?▼

Without standardizing log levels and formats, application logs lack consistency and readability, making debugging and monitoring difficult. Failing to mask sensitive data also risks security non-compliance and potential PII or secret leakage.

Related Skills

Explore More Software Engineering Skills→
andregusman-raizandregusman-raiz
19

ag-referencia-seguranca-rules

Enforce RLS, audit trails, LGPD compliance, and PII masking across data systems.

Community
Advanced
joelhooksjoelhooks
22

zap-cli

Query and trace agent events with JSON output via CLI.

Community
Intermediate
ajianazajianaz
4

observability-monitor

Orchestrate end-to-end observability and monitoring for complex applications.

Community
Advanced
ancolemanancoleman
503

siem-logging

Configure SIEM systems for threat detection, log aggregation, and compliance.

Community
Advanced