project-brief SKILL.md skillA
project-brief from drayline/rootnode-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add drayline/rootnode-skills/project-brief@v6.0.0Pins v6.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- drayline/rootnode-skills
- Path
plugins/rootnode-projects/skills/project-brief/SKILL.md- Versions recorded
- 2
- Latest version
- v6.0.0, committed Nov 3, 2026
- First version recorded
- Nov 1, 2026
- Size
- 13,302 bytes
- Repository stars
- 40
- License
- a license file GitHub does not identify
Generates a structured Project Brief — a comprehensive markdown document that extracts goals, architecture, knowledge file inventory, Custom Instructions summary, Memory contents, current state, ecosystem position, and key decisions from a Claude Project. Briefs serve as uploadable context documents: add one to any other Project for immediate deep awareness of the source Project's purpose, architecture, and progress. Use when user says "create a brief," "brief this project…
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
# Project Brief Builder > **Calibration:** Tier 1 (Model-compatible) — runs cleanly on the current dual-primary tier (Opus 5.5, Sonnet 5.5) and on Haiku 5.5. Structured retrieval, rule evaluation, or template lookup — output shape does not depend on the model. Fallback-graceful on Opus 5 / Sonnet 5; legacy-graceful on Sonnet 4.6. See repository README for model compatibility. You generate Project Briefs — structured markdown documents that capture everything another Project needs to understand about a source Project. A brief is not a session summary or a project audit. It is a portable context artifact: upload it to any other Project and that Project immediately has deep awareness of the source Project's purpose, architecture, current state, and ecosystem position. Briefs are consumed as knowledge files in receiving Projects. Every token matters — a 5,000-token brief in a project with 60,000 tokens of knowledge files is fine, but the same brief in a small project would dominate the context budget. Target 2,000–6,000 tokens. Be dense and structured, not verbose. ## Critical: Extraction, Not Fabrication …
Read the whole file at its exact version.
How to install
mdr add drayline/rootnode-skills/project-brief@sha256:6633a062ee0ca271The line at the top of this page pins the label v6.0.0, 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_yyi3mdw4rfrfp5kl)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Nov 1, 2026 and Nov 3, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v6.0.0 latest | 2026-11-03 | 7bd17b8 | 13,302 B | A | view · diff |
| v5.0.0 | 2026-11-01 | f34b7ac | 13,255 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 (13302 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
drayline/rootnode-skills · 40 stars · license a license file GitHub does not identify · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yyi3mdw4rfrfp5kl GET https://markdownregistry.com/api/v1/resolve?ref=drayline/rootnode-skills/project-brief GET https://markdownregistry.com/api/v1/blob/6633a062ee0ca271821aab224a7f22c827ba1d893a296d62cd5cacaf85203ba9
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 drayline/rootnode-skills
Every file in drayline/rootnode-skills