OperationsPROPRO REQUIREDFC-OPS-009
Logging Claw
logging-claw
v0.2.0May 22, 2026Structured logging — correlation IDs, log levels, and retention policies that make debugging possible at 3am
Logs you can't query under pressure might as well not exist—and unstructured logs you can grep are only slightly better. I enforce structured JSON logging with correlation IDs that propagate across every service boundary, define retention policies that balance compliance with cost, and make sure PII never leaks into your log stream because regulators don't care that it was an accident.
OpenClaw
Hermes
Claude Code
Codex
Cursor
Windsurf
Aider
OllamaPRIMARY ACTION
Unlock with ProCOMPATIBLE WITH
OpenClawHermesClaude CodeCodex+4
8 compatible tools5 output formats
When to Use
- Harden deployment and release workflows
- Improve observability and alert readiness
- Define environment standards
- Prepare operational runbooks
Compatible Frameworks
OpenClawHermesClaude CodeCodexCursorWindsurfAiderOllama8 TOOLS
Quality Gates
- Structured format with standard fields
- Correlation IDs configured
- Log levels with clear guidelines
- Retention policies defined
- Sensitive data excluded from logs
5 GATES DEFINED
Expected Outputs
Logging Standards and Schema DocumentLog Pipeline Architecture DiagramRetention Policy Specification by Data ClassPII Redaction Rule Set and Validation TestCorrelation ID Propagation Guide
Native exports per tool
OpenClaw10 files
openclaw/AGENTS.mdopenclaw/SOUL.mdopenclaw/TOOLS.md+7 moreHermes5 files
hermes/skills/flickclaw/logging-claw/SKILL.mdhermes/skills/flickclaw/logging-claw/references/workflow.mdhermes/skills/flickclaw/logging-claw/references/quality-gates.md+2 moreClaude Code6 files
claude-code/CLAUDE.mdclaude-code/.claude/skills/logging-claw/SKILL.mdclaude-code/.claude/skills/logging-claw/references/workflow.md+3 moreCodex5 files
codex/AGENTS.mdcodex/.flickclaw/agents/logging-claw/codex.mdcodex/.flickclaw/agents/logging-claw/workflow.md+2 moreCursor3 files
cursor/.cursor/rules/flickclaw-logging-claw.mdccursor/.cursor/rules/flickclaw-logging-claw-workflow.mdccursor/.cursor/rules/flickclaw-logging-claw-quality-gates.mdcWindsurf3 files
windsurf/.windsurf/rules/flickclaw-logging-claw.mdwindsurf/.windsurf/rules/flickclaw-logging-claw-workflow.mdwindsurf/.windsurf/rules/flickclaw-logging-claw-quality-gates.mdAider3 files
aider/CONVENTIONS.mdaider/aider.mdaider/.aider.conf.ymlOllama4 files
ollama/Modelfileollama/system-prompt.mdollama/template.md+1 moreInstall Commands
Install the FlickClaw CLI, then select your AI agent framework below to get the correct install command.
Step 1: Install CLI (one-time)
npm install -g @flickclaw/cli@latestStep 2: Select Framework
OpenClaw
npm exec --yes @flickclaw/cli@latest -- install logging-claw --target openclawDownload as ZIP
Example Prompt
Try this prompt with Logging Claw to see what it can do:
Review the deployment pipeline and monitoring. Identify bottlenecks and single points of failure. Produce Logging Standards and Schema Document, Log Pipeline Architecture Diagram, Retention Policy Specification by Data Class.Example Output
IllustrativeWhat a typical Logging Claw report looks like:
# Logging Claw — Assessment Report **Project**: microservices-cluster **Context**: a Kubernetes cluster running 12 microservices with Istio and Prometheus **Generated**: 2026-07-10 ## Executive Summary The Logging Claw completed its review of microservices-cluster (a Kubernetes cluster running 12 microservices with Istio and Prometheus). 3 findings were identified with concrete remediation steps. All quality gates were verified before delivery. ## Findings | # | Severity | Area | Finding | Recommended Action | |---|----------|------|---------|-------------------| | 1 | **P0** | Deployment | No rollback strategy defined for 4 services | Add Helm rollback hooks and deployment pause windows | | 2 | **P1** | Monitoring | Alert fatigue from 200+ low-priority alerts/day | Consolidate alerts, add severity routing, mute during maintenance | | 3 | **P2** | Cost | 3 dev clusters running 24/7 without downscaling | Add cron-based scaling to zero during off-hours | ## Quality Gates - [✓] Structured JSON logging on all services - [✓] Correlation IDs propagate across all service boundaries - [✓] Log retention meets compliance minimums per data class ## Outputs Generated - **Logging Standards and Schema Document**: Included in the report above. - **Log Pipeline Architecture Diagram**: Included in the report above. - **Retention Policy Specification by Data Class**: Included in the report above. - **PII Redaction Rule Set and Validation Test**: Included in the report above. - **Correlation ID Propagation Guide**: Included in the report above. ## Validation - [x] All quality gates passed (3/3) - [x] 3 findings documented with severity and remediation - [x] 5 output sections generated - [x] Evidence collected and referenced --- *This is an illustrative example output from FlickClaw. Results vary based on project context.*
RELATED AGENTS