pitroom-crew SKILL.md skillA
pitroom-crew from atastech/pitroom is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add atastech/pitroom/pitroom-crew@git:20261002.c00d862Pins git:20261002.c00d862 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- atastech/pitroom
- Path
skills/pitroom-crew/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261002.c00d862, committed Oct 2, 2026
- First version recorded
- Sep 30, 2026
- Size
- 5,328 bytes
- Repository stars
- 28
- License
- MIT
Use when facing two or more independent tasks - questions about different areas, unrelated bugs or failing test files, the same mechanical change in separate modules - to run Pitroom workers in parallel, watch them live and merge their results.
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
# Running a Pitroom crew Several workers at once, each with its own session (and, for changes, its own isolated copy of the project): one worker per independent problem domain. You split the work, watch, and merge. ## When to use - Several questions about different areas of the code. - Three or more test files failing with different root causes; subsystems broken independently. - The same mechanical change in separate modules. Don't use it when the failures are related (fixing one might fix the others: investigate them together first), when understanding needs the whole system, when you don't yet know what is broken (exploratory debugging: `pitroom-debugging`), or when workers would edit the same files. The tasks of a written plan run through `pitroom-driven-development`, which has its own rules for parallel tasks. ## 1. Split Parts must be **independent**: no part needs another's result, and no two parts edit the same file. Start as many workers as there are independent parts: up to 20 run at a time by default (`maxParallel`, 30 at most), the rest queue. Keep dependent or judgment-heavy parts for yourself. ## 2. Write focused briefs …
Read the whole file at its exact version.
How to install
mdr add atastech/pitroom/pitroom-crew@sha256:1034a0d52a9c65b2The line at the top of this page pins the label git:20261002.c00d862, 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_lwnebeqihoit4hgo)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 30, 2026 and Oct 2, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261002.c00d862 latest | 2026-10-02 | c00d862 | 5,328 B | A | view · diff |
| git:20261001.0d4ddc3 | 2026-10-01 | 0d4ddc3 | 5,204 B | A | view · diff |
| git:20260930.b257fbb | 2026-09-30 | b257fbb | 4,871 B | A | view · diff |
| git:20260930.edf1281 | 2026-09-30 | edf1281 | 4,794 B | A | view · diff |
| git:20260930.b3d668b | 2026-09-30 | b3d668b | 4,695 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 (5328 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
atastech/pitroom · 28 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lwnebeqihoit4hgo GET https://markdownregistry.com/api/v1/resolve?ref=atastech/pitroom/pitroom-crew GET https://markdownregistry.com/api/v1/blob/1034a0d52a9c65b2fad40622519267b2cd0924efc8a080cd9b4272d7a9f44679
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.