admin-access-control-specification SKILL.md skillA
admin-access-control-specification from fattain-naime/engineering-docs is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add fattain-naime/engineering-docs/admin-access-control-specification@git:20260717.2f82174Pins git:20260717.2f82174 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- fattain-naime/engineering-docs
- Path
skills/admin-access-control-specification/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260717.2f82174, committed Jul 17, 2026
- First version recorded
- Jul 12, 2026
- Size
- 16,892 bytes
- Repository stars
- 6
- License
- MIT
Specify admin roles, permissions, and every admin-facing control in a system - a full role-permission matrix (RBAC), the principle of least privilege applied concretely, admin action audit logging, and emergency/break-glass access procedures. Use whenever a system has more than one privilege level, before building the admin panel or access-control logic.
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
## Purpose Produce an access control specification that defines every privilege level in a system, exactly what each one can and cannot do, how admin actions are logged, and what happens when access is needed outside the normal process. **"If user.is_admin" is not an access control design - it's the absence of one.** This document forces every permission to be a deliberate decision, written down once, instead of discovered by testing what an admin account happens to be able to click. ## Input **Works best with:** The name of the system and the roles that already exist or are anticipated (even informally - "there's regular users and then there's us"). **Also valuable:** Any compliance requirements (SOC 2, PCI-DSS, GDPR), known sensitive actions (refunds, data export, user impersonation), and whether multiple organizations/tenants share the system. **Example invocation:** `Define the access control specification for our project-management SaaS. Roles so far: workspace owner, admin, regular member, and a guest role with view-only access. We also have an internal support team that needs to see customer data to help with tickets.` ## Key Concepts …
Read the whole file at its exact version.
How to install
mdr add fattain-naime/engineering-docs/admin-access-control-specification@sha256:0ae7a20f62e6406bThe line at the top of this page pins the label git:20260717.2f82174, 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_evxbetv4e5b57lpi)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 12, 2026 and Jul 17, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260717.2f82174 latest | 2026-07-17 | 2f82174 | 16,892 B | A | view · diff |
| git:20260712.59c5852 | 2026-07-12 | 59c5852 | 7,064 B | A | view · diff |
| git:20260712.7e3d1bb | 2026-07-12 | 7e3d1bb | 7,147 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 (16892 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
fattain-naime/engineering-docs · 6 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_evxbetv4e5b57lpi GET https://markdownregistry.com/api/v1/resolve?ref=fattain-naime/engineering-docs/admin-access-control-specification GET https://markdownregistry.com/api/v1/blob/0ae7a20f62e6406b3fe6dfa6fee04d655fe46a683b94351462ee91559dcf5b02
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.