roost-config SKILL.md skillA
roost-config from beakpoint-insights/roost is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add beakpoint-insights/roost/roost-config@git:20261026.505a1daPins git:20261026.505a1da in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- beakpoint-insights/roost
- Path
skills/roost-config/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261026.505a1da, committed Oct 26, 2026
- First version recorded
- Oct 26, 2026
- Size
- 15,906 bytes
- Repository stars
- 30
- License
- MIT
Load the team's roost config (which tracker, which repos and sessions, the local stack's commands, branching rules, deploy and design details) and the adapter notes for its tracker and test tool. Every other roost skill uses this first, before it reads or changes anything. Use it directly when the user asks "what does roost know about our setup?" or "which config is roost using?".
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
# Roost Config roost's skills describe a way of working. Everything specific to one team (its tracker and project, its repos, its local stack, its branching and deploy rules, its design system) lives in one config file. Load it before doing anything else, and use its values wherever a skill names a config key. **Read the config before any other call.** Don't send a tracker, GitHub or other tool call in the same batch as reading the config, and never guess a value it holds (a site, a cloud ID, a project key, a repo name). Wait for the config, then use its values. ## 1. Find the config Use the first one that exists: 1. A path the user gave in this conversation. 2. The `ROOST_CONFIG` environment variable (`echo "$ROOST_CONFIG"`). 3. `.roost/config.yml` in the current directory or the nearest parent that has one (stop at the repo root). 4. `~/.claude/roost/config.yml` (often a link to the team's shared config in its private repo). …
Read the whole file at its exact version.
How to install
mdr add beakpoint-insights/roost/roost-config@sha256:dcc5638ca97278a9The line at the top of this page pins the label git:20261026.505a1da, 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_cwzixxyn3qkoisms)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, all committed on Oct 26, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.505a1da latest | 2026-10-26 | 505a1da | 15,906 B | A | view · diff |
| git:20261026.dec76bc | 2026-10-26 | dec76bc | 13,259 B | A | view · diff |
| git:20261026.c517de3 | 2026-10-26 | c517de3 | 10,864 B | A | view · diff |
| git:20261026.8cbba28 | 2026-10-26 | 8cbba28 | 10,031 B | A | view · diff |
| git:20261026.66cdcd9 | 2026-10-26 | 66cdcd9 | 8,925 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 (15906 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
beakpoint-insights/roost · 30 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cwzixxyn3qkoisms GET https://markdownregistry.com/api/v1/resolve?ref=beakpoint-insights/roost/roost-config GET https://markdownregistry.com/api/v1/blob/dcc5638ca97278a9087b9560814734ffaa37bd2e6836c143f718463422742b9d
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.