onboard SKILL.md skillA
onboard from vivantel/kms is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vivantel/kms/onboard@git:20260905.0921542Pins git:20260905.0921542 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vivantel/kms
- Path
plugins/kms/skills/onboard/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260905.0921542, committed Sep 5, 2026
- First version recorded
- Aug 30, 2026
- Size
- 2,668 bytes
- Repository stars
- 3
- License
- MIT
Creates a role-specific onboarding plan from a project's existing knowledge artifacts, without writing anything. Use when the user wants a ramp-up plan for a specific role, e.g. "onboard me as a frontend developer for this project", "what should a new QA hire read first here".
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
Read `docs/{facts,decisions,guardrails,skills}/` and produce a 5-day, role-tailored onboarding plan — without writing to disk.
## Before producing a plan
1. Ask for the role if not given — it shapes everything else, don't guess it.
2. Read each type's `INDEX.md` first, if present, to identify what's relevant to the role — ignore any `(umbrella)`-marked tag when matching (same exclusion `lint` check 16 applies). Read all four artifact directories directly when no index exists, or when the index-narrowed set looks thin for a role this broad (same staleness caveat `query` applies). If `docs/skills/{product,process}-track-roles.md` exists and lists the given role, weigh its stated scope; otherwise use judgment about what the role would need.
3. **Warn if critical artifacts are missing** before producing the plan — most importantly, no facts at all, but also an empty `decisions/` or `guardrails/` if the project claims to use this system. Say plainly the plan is built on an incomplete base; don't let it read as if the knowledge base were complete when it isn't.
4. No knowledge base at all? Say so and stop — recommend `bootstrap`, don't improvise a plan from nothing.
…Read the whole file at its exact version.
How to install
mdr add vivantel/kms/onboard@sha256:36b7cdd1b620fb8fThe line at the top of this page pins the label git:20260905.0921542, 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_crfx74go5oxw5pmr)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 30, 2026 and Sep 5, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260905.0921542 latest | 2026-09-05 | 0921542 | 2,668 B | A | view · diff |
| git:20260903.35ff927 | 2026-09-03 | 35ff927 | 2,496 B | A | view · diff |
| git:20260830.b13e8e9 | 2026-08-30 | b13e8e9 | 2,351 B | A | view · diff |
| git:20260830.258a310 | 2026-08-30 | 258a310 | 2,351 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 (2668 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
vivantel/kms · 3 stars · license MIT · pushed 2026-10-04 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_crfx74go5oxw5pmr GET https://markdownregistry.com/api/v1/resolve?ref=vivantel/kms/onboard GET https://markdownregistry.com/api/v1/blob/36b7cdd1b620fb8fe1e31631931273903cd74bdf29310e44eedf45c7c17ae219
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.