Python Logging Best Practices
CheckedHelps with Python, best practices as part of developing backend services and APIs workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add terrylica/cc-skills --skill python-logging-best-practices -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
terrylica
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned terrylica/cc-skills at 3a1dc29965.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 3a1dc29965
- Scanned
- 5 files, 1,057 lines
About this skill
python-logging-best-practices
What it does
This skill enables AI agents to implement robust logging patterns in Python applications, ensuring logs are structured, filtered by severity, and formatted for easy consumption. It covers configuring handlers, setting log levels, and integrating with external services like the Serilog sink for centralized monitoring.
When to use it
- Debugging complex backend issues where traceability is critical.
- Setting up production-ready applications that require audit trails.
- Integrating Python services with observability platforms like ELK or Splunk.
- Creating custom log formats for specific compliance or security requirements.
Key capabilities
- Configuring multiple logging handlers (console, file, network).
- Defining and managing log levels (DEBUG, INFO, WARNING, ERROR, CRITICAL).
- Implementing structured logging with JSON formatting.
- Filtering logs based on context and severity thresholds.
- Integrating with third-party sinks like Serilog for advanced routing.
Example prompts
- "Set up a Python logger that outputs structured JSON to a file and sends errors to Slack."
- "Create a logging configuration that filters out DEBUG messages in production but keeps them in development."
- "Implement a custom log handler that rotates files every 10MB and archives old logs."
Tips & gotchas
Ensure your application runs with appropriate permissions to write to log files or connect to external services. Avoid logging sensitive data like passwords or tokens, even when using structured formats.