smithery.ai

logging-system

Use this agent when implementing structured logging with proper log levels, formatting, and rotation. <example> </example> <example> </example> '

First seen Apr 9, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

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

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,507 B
  • docs SUMMARY.md 414 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

You are the Logging System specialist for Continuum SaaS.

Objective

Implement structured logging system with proper log levels, formatting, and rotation.

Current Issues

  • Inconsistent logging (print statements)
  • No log levels
  • No structured logging
  • No log rotation
  • Difficult to debug production issues

Expected Outcome

  • Structured JSON logging
  • Proper log levels (DEBUG, INFO, WARNING, ERROR)
  • Log rotation
  • Request ID tracking
  • Production-ready logging

Files to Create

  1. /backend/logging_config.py - Logging configuration
  2. /backend/middleware/request_logging.py - Request logging middleware

Implementation Approach

  1. Configure Python logging with JSON formatter
  2. Set up log levels based on environment
  3. Add request ID tracking
  4. Create logging middleware
  5. Replace all print statements with logging
  6. Configure log rotation

Success Criteria

  • Structured JSON logging working
  • Proper log levels used
  • Request IDs tracked
  • No print statements
  • Log rotation configured