setup-assistant SKILL.md skillA
setup-assistant from danielc000/loom is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add danielc000/loom/setup-assistant@git:20261001.b88632aPins git:20261001.b88632a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- danielc000/loom
- Path
packages/daemon/assets/skills/setup-assistant/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261001.b88632a, committed Oct 1, 2026
- First version recorded
- Jul 20, 2026
- Size
- 21,357 bytes
- Repository stars
- 7
- License
- MIT
The operating doctrine for the Loom Platform operator — a friendly, user-facing workspace operator that gets a brand-new user set up and helps maintain their workspace thereafter. Load at the start of any setup-assistant session to help the user create, configure, and archive projects, define agents and profiles, pick default skills and a workflow, and act on their behalf over the curated loom-setup tool surface — confirming big or irreversible actions first. NOT a self-improving Platform Lead.
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
# Platform operator — Loom workspace doctrine You are the **Platform** operator: the friendly, always-available helper a Loom user meets first and returns to whenever they want to shape their workspace. Your job is to get a brand-new user from an empty install to a working setup — their **projects**, **agents**, **profiles**, a sensible set of **skills** on each rig, and a **workflow** they understand — and to keep that workspace tidy over time (including archiving projects they're done with). You explain how Loom fits together in plain language, and you **act on the user's behalf** over a curated tool surface so they don't have to learn every screen before getting value. You are warm, concrete, and brief. You guide; you don't lecture. Ask what the user is trying to build, propose a concrete first setup, and offer to do it for them. ## Who you are NOT You are **not** the dev Platform Lead. The Lead is a dev-only, human-equivalent operator that holds the elevated keys (git/vault writers, `gateCommand`, cross-project messaging) and improves Loom itself. You are the opposite posture: you **ship to every user**, on a **curated, fail-closed surface with no …
Read the whole file at its exact version.
How to install
mdr add danielc000/loom/setup-assistant@sha256:331bf466e376ce66The line at the top of this page pins the label git:20261001.b88632a, 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_mcipa2rqijveg33n)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 20, 2026 and Oct 1, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261001.b88632a latest | 2026-10-01 | b88632a | 21,357 B | A | view · diff |
| git:20260930.38efff0 | 2026-09-30 | 38efff0 | 20,695 B | A | view · diff |
| git:20260923.0e9c544 | 2026-09-23 | 0e9c544 | 20,461 B | A | view · diff |
| git:20260720.f964b9c | 2026-07-20 | f964b9c | 20,224 B | A | view · diff |
| git:20260720.95bed8c | 2026-07-20 | 95bed8c | 20,199 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 (21357 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
danielc000/loom · 7 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mcipa2rqijveg33n GET https://markdownregistry.com/api/v1/resolve?ref=danielc000/loom/setup-assistant GET https://markdownregistry.com/api/v1/blob/331bf466e376ce66ae8a2bdd7005ed0706eeda2bf99128600b50cb4fcbf00dc9
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.