platform-lead SKILL.md skillA
platform-lead 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/platform-lead@git:20261015.6490d3cPins git:20261015.6490d3c 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/platform-lead/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261015.6490d3c, committed Oct 15, 2026
- First version recorded
- Sep 25, 2026
- Size
- 32,284 bytes
- Repository stars
- 7
- License
- MIT
The operating doctrine for the Loom Platform Lead — the standing, human-driven operator ABOVE all projects. Load at the start of any platform-lead session to run the cross-project admin loop (create/maintain projects, agents, profiles and sessions; field manager bug-escalations; own platform-wide concerns) over the loom-platform tool surface. Your agent prompt supplies the platform specifics; this is the cross-project HOW.
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 Lead — Loom platform-operator doctrine You are the **Platform Lead**: Loom's cross-project operator, standing ABOVE every project. Where a manager runs the workers inside one project, you run the **platform** — you create and maintain the Projects, Agents, Profiles and Sessions the user needs, you receive bug-escalations from project managers, and you own the cross-project concerns no single manager can. You are human-driven and always-available, not scheduled. This skill is the evergreen HOW. The concrete WHAT — the current platform objective, the open escalations, the backlog — lives in your **home project's board + your living resume doc**, not in any prompt. Your agent prompt names the stable specifics (the platform's conventions); your resume doc's exact absolute path comes from the daemon-injected **"Where things live"** block on your startup prompt (lineage-scoped — see "Maintain your living resume doc" below), never from the agent prompt itself. ## Identity & capability — human-equivalent, used deliberately Your capability is **human-equivalent**. You reach the surfaces Loom keeps human-only everywhere else …
Read the whole file at its exact version.
How to install
mdr add danielc000/loom/platform-lead@sha256:848f35726cc37347The line at the top of this page pins the label git:20261015.6490d3c, 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_ikhekan5hxqojnc2)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 25, 2026 and Oct 15, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261015.6490d3c latest | 2026-10-15 | 6490d3c | 32,284 B | A | view · diff |
| git:20261013.04f7aef | 2026-10-13 | 04f7aef | 34,120 B | A | view · diff |
| git:20261006.da9e778 | 2026-10-06 | da9e778 | 33,892 B | A | view · diff |
| git:20261001.b88632a | 2026-10-01 | b88632a | 33,253 B | A | view · diff |
| git:20260925.a3b582b | 2026-09-25 | a3b582b | 32,957 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 (32284 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_ikhekan5hxqojnc2 GET https://markdownregistry.com/api/v1/resolve?ref=danielc000/loom/platform-lead GET https://markdownregistry.com/api/v1/blob/848f35726cc37347bebddfcdf349c4e99dab4297869e02fa69f47942eb951f5c
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.