setup SKILL.md skillA
setup 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/setup@git:20261028.fe7bbe6Pins git:20261028.fe7bbe6 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/setup/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261028.fe7bbe6, committed Oct 28, 2026
- First version recorded
- Oct 26, 2026
- Size
- 8,527 bytes
- Repository stars
- 30
- License
- MIT
Set up roost for a team. Links an existing team config, or makes a new one by asking about the team's tracker (Jira or GitHub Issues), tests, repos and how each reaches production, local stack, branching and deploy rules, and release notes (where they're published, and the team's voice), leaving out what the team doesn't have, then checks it. Use when a roost skill says there's no config, or the user says "set up roost", "configure roost", "roost for our team" or "change our roost config".
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
# Set Up roost Every roost skill reads one team config (see `roost-config`). This skill puts one in place. ## 1. Is there one already? Look where `roost-config` looks: a path the user named, `$ROOST_CONFIG`, `.roost/config.yml` from here up to the repo root, then `~/.claude/roost/config.yml`. If one exists, say which, and ask whether they want to change it or start again. To change one part (getting ready for release notes, say), ask only the questions for that part (step 3), show the lines that would change, save nothing until the user agrees, then run step 4's checks on what changed. ## 2. Link the team's config, if there is one Most teams keep one config in a private repo so everyone uses the same. Ask whether the team has one. If so: ```bash mkdir -p ~/.claude/roost ln -s <path to the team's config.yml> ~/.claude/roost/config.yml ``` A link follows the clone, so `git pull` there updates everyone's config. If this machine differs from the others (its own database, other ports), put only those values in `~/.claude/roost/local/<team.name>.yml` rather than editing the shared file (`config-schema.md`, "Machine overrides"). Go to step 4. ## 3. Make a new one …
Read the whole file at its exact version.
How to install
mdr add beakpoint-insights/roost/setup@sha256:25e5c871c28ce1a7The line at the top of this page pins the label git:20261028.fe7bbe6, 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_zoxdahsuoovrmyrv)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 26, 2026 and Oct 28, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.fe7bbe6 latest | 2026-10-28 | fe7bbe6 | 8,527 B | A | view · diff |
| git:20261027.026f562 | 2026-10-27 | 026f562 | 8,283 B | A | view · diff |
| git:20261026.505a1da | 2026-10-26 | 505a1da | 6,035 B | A | view · diff |
| git:20261026.dec76bc | 2026-10-26 | dec76bc | 4,538 B | A | view · diff |
| git:20261026.66cdcd9 | 2026-10-26 | 66cdcd9 | 4,526 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 (8527 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_zoxdahsuoovrmyrv GET https://markdownregistry.com/api/v1/resolve?ref=beakpoint-insights/roost/setup GET https://markdownregistry.com/api/v1/blob/25e5c871c28ce1a79a392a07aa9219f17747573741fd571ead1669beff4b0033
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.
More from beakpoint-insights/roost
Every file in beakpoint-insights/roost