hex-conventions SKILL.md skillA
hex-conventions 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/hex-conventions@git:20261011.7343419Pins git:20261011.7343419 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-hex/skills/hex-conventions/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261011.7343419, committed Oct 11, 2026
- First version recorded
- Sep 29, 2026
- Size
- 17,877 bytes
- Repository stars
- 3
- License
- MIT
Use when asking where does this file go or what is this class called — the registry deriving a path and class name from a bare identifier, plus the two store profiles with their connection-factory names and `<subdomain>:<Name>` cross-context resolution. Produces no file of its own. What a thing is *called* in general is `naming`; layer boundaries are `hex-architecture`.
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
# Hexagonal Conventions — the derivation registry This is the **derivation layer**: the rules that turn the bare identifiers a change introduces — an entity name, a protocol name, a command base-name, a datastore kind — into concrete file paths, class names and package placement. Other skills own what goes *inside* an artifact; this one owns the mapping between a name and its place in the tree. It produces **no file of its own**. All paths below are relative to the target package root `src/myapp/`. Worked names use a deliberately neutral vocabulary — subdomains `foos` and `bars`, entities `Foo` and `Bar` — so nothing here reads as belonging to one product. Technology tokens (`postgres`, `redis`, `s3`, `jwt`) stay concrete, because the whole point of the infrastructure rule is that the folder is named after the real technology. ## When to use vs. neighbours - Turning a bare identifier into a file path or class name → this skill. - Deciding which repository form a datastore gets, or writing its connection factory → block B. - Resolving a `<subdomain>:<Name>` reference, or deciding what is shared across contexts → block C. …
Read the whole file at its exact version.
How to install
mdr add wntic/pyhouse/hex-conventions@sha256:de50bdf29c8c387bThe line at the top of this page pins the label git:20261011.7343419, 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_ttcj4iwf6vjjixdy)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 29, 2026 and Oct 11, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.7343419 latest | 2026-10-11 | 7343419 | 17,877 B | A | view · diff |
| git:20260929.2b7e78e | 2026-09-29 | 2b7e78e | 19,491 B | A | view · diff |
| git:20260929.3233f4d | 2026-09-29 | 3233f4d | 19,527 B | A | view · diff |
| git:20260929.3868884 | 2026-09-29 | 3868884 | 19,478 B | A | view · diff |
| git:20260929.4240e75 | 2026-09-29 | 4240e75 | 19,482 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 (17877 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_ttcj4iwf6vjjixdy GET https://markdownregistry.com/api/v1/resolve?ref=wntic/pyhouse/hex-conventions GET https://markdownregistry.com/api/v1/blob/de50bdf29c8c387bd98bedf81061649a4d447c7cddf75183ff38614846188182
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.