tmt-layout SKILL.md skillA
tmt-layout from wkh237/tmux-team is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wkh237/tmux-team/tmt-layout@git:20261002.e53804cPins git:20261002.e53804c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wkh237/tmux-team
- Path
.agents/skills/tmt-layout/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261002.e53804c, committed Oct 2, 2026
- First version recorded
- Oct 2, 2026
- Size
- 1,840 bytes
- Repository stars
- 14
- License
- MIT
Review repository file additions and moves against the owned layout map.
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
# Repository layout review Use this procedure when adding or moving repository files. Read the single [Repository layout map](../../../ARCHITECTURE.md#repository-layout) first; it owns homes, responsibilities, pending moves and the linked top-level allowlist. 1. Compare the proposed paths with the map and existing neighboring owners. Check component ownership through the existing component map, and identify affected imports, links, build inputs, fixtures and release consumers before editing. 2. If a new home or exception is needed, send the infra lead a bounded proposal: responsibility, component owner, why an existing home does not fit, and a removal issue for a temporary exception. Obtain review before adding it; update the owning map and its linked JSON together rather than copying them here. 3. Keep moves separate from behavior changes. Use `git mv` for retained files and separate pure rename commits from link/import/config rewrites so reviewers can verify preservation. Respect the pending-move gates in the map and coordinate shared paths with their owners; never move dirty or unowned work. …
Read the whole file at its exact version.
How to install
mdr add wkh237/tmux-team/tmt-layout@sha256:94ab3129f50e79baThe line at the top of this page pins the label git:20261002.e53804c, 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_rcig32jazaktfa3f)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Oct 2, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261002.e53804c latest | 2026-10-02 | e53804c | 1,840 B | A | view · diff |
| git:20261002.38ec2df | 2026-10-02 | 38ec2df | 1,813 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 (1840 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
wkh237/tmux-team · 14 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rcig32jazaktfa3f GET https://markdownregistry.com/api/v1/resolve?ref=wkh237/tmux-team/tmt-layout GET https://markdownregistry.com/api/v1/blob/94ab3129f50e79ba57d9788fbda54ee4ecca2cce6bd5fcb2d027e8ea313ae92c
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.