role-activation skillA
role-activation is agent-read markdown (skill) from vmobifystudio/app-dev-team: Use at project start — /app-init, /app-onboard, or /app-run's first step — to decide which of the roles this product actually needs, and to write the durable roster the rest of the flow reads. Triggers whenever a command is about to fan out to a team, or a gate is about to run for a role that may not be on this project..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Role activation The roster is not fixed. A three-screen utility does not need a CEO *and* a CPO, and a backend service does not need an ASO specialist, a store-readiness gate, or a runtime gate hunting for an `.xcodeproj`. Activation has **two axes**, and both are decided once, up front, and written down. - **Tier** — `flagship` | `utility`. How much process the work deserves (House KB §Tiers). - **Product type** — `ios-app` | `android-app` | `mobile-app` | `backend-service` | `web-app` | `cli` | `library`. Which specialists exist at all. **A deactivated role is recorded, never silently absent.** Everything below exists to serve that one rule: an absent role and a skipped role must stay distinguishable six months later. ## Determining the two axes **Greenfield** — from `docs/01-intake.md`, which `requirements-intake` has already written: - *Product type* ← its `## Product type` answer (intake question 3). One answer, verbatim. - *Tier* ← an explicit `--utility` / `--flagship` flag if the user passed one; otherwise derive: **utility** when the intake describes a single-purpose tool with one core action and no …
Read the whole file at its exact version.
How to install
mdr add vmobifystudio/app-dev-team/role-activation@git:20260801.13880fdmdr add vmobifystudio/app-dev-team/role-activation@sha256:fbd29fc2af3fa13aPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_3isomn5um2ug3jge)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260801.13880fd latest | 2026-08-01 | 13880fd | 23,142 B | A | view · diff |
| git:20260729.41f157f | 2026-07-29 | 41f157f | 17,282 B | A | view · diff |
| git:20260729.071181e | 2026-07-29 | 071181e | 16,335 B | A | view · diff |
| git:20260729.c01da4a | 2026-07-29 | c01da4a | 11,683 B | A | view · diff |
| git:20260729.9b895c9 | 2026-07-29 | 9b895c9 | 10,841 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 (23142 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
vmobifystudio/app-dev-team · 4 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3isomn5um2ug3jge GET https://markdownregistry.com/api/v1/resolve?ref=vmobifystudio/app-dev-team/role-activation GET https://markdownregistry.com/api/v1/blob/fbd29fc2af3fa13adfbc41bc1212b7da669abecc180dde54d8ad399ba2017f1c
Your agent 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.