python-logging SKILL.md skillA
python-logging from wntic/pyhouse is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wntic/pyhouse/python-logging@git:20261011.363b85ePins git:20261011.363b85e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wntic/pyhouse
- Path
plugins/pyhouse-universal/skills/python-logging/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261011.363b85e, committed Oct 11, 2026
- First version recorded
- Sep 27, 2026
- Size
- 13,100 bytes
- Repository stars
- 3
- License
- MIT
Use when writing code that reports what it did or what went wrong — a log call, a `print` for progress or errors, an `except` that records a failure, or logging setup in an entry point, a CLI or a library. Owns one structured event per occurrence with a stable `<subject>_<past_tense_verb>` name and identifiers as fields, the rule that an error is logged once by the scope that stops it and never by a scope that re-raises, the warning a failed undo under compensation earns, logging configured…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Python Logging A log line exists to be **queried** — filtered, grouped, counted, alerted on. Prose cannot be queried, so every occurrence worth recording produces **exactly one structured event**: a name plus fields, never a sentence with values spliced into it. These rules hold whatever the architecture is. Only one thing here varies from project to project, and it varies as a *consequence*, not as a separate rule: an error is logged once, by the scope that can add context and will not re-raise it — and where a project's errors propagate to decides which scope that is. Everything else is unconditional. ## When to use vs. neighbours - Writing or changing any log call, naming an event, configuring logging → this skill. - Annotation forms, record types, comments → `python-style`. - The exception classes, what goes into their `context`, translation with `from exc`, best-effort compensation itself → `exception-catalog`. - Which layer of a hexagonal service may log at all → `hex-architecture`, in the `pyhouse-hex` plugin; in a flat service, where the scope that stops a run's failure sits → `flat-layered` and `flat-entrypoint`, in `pyhouse-flat`. …
Read the whole file at its exact version.
How to install
mdr add wntic/pyhouse/python-logging@sha256:7544e4fcbd0af18aThe line at the top of this page pins the label git:20261011.363b85e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_y7jxbbsj3gw5g3zx)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 27, 2026 and Oct 11, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.363b85e latest | 2026-10-11 | 363b85e | 13,100 B | A | view · diff |
| git:20260929.d4e3593 | 2026-09-29 | d4e3593 | 13,047 B | A | view · diff |
| git:20260928.709c593 | 2026-09-28 | 709c593 | 13,042 B | A | view · diff |
| git:20260928.e8e67b0 | 2026-09-28 | e8e67b0 | 12,804 B | A | view · diff |
| git:20260927.f40de46 | 2026-09-27 | f40de46 | 12,789 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13100 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wntic/pyhouse · 3 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_y7jxbbsj3gw5g3zx GET https://markdownregistry.com/api/v1/resolve?ref=wntic/pyhouse/python-logging GET https://markdownregistry.com/api/v1/blob/7544e4fcbd0af18aee39d6020e15ee012df5339fac3a02b481c8659e8c66f50d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.