Run any Skill in Manus with one click

authority-map

Stars1

Forks0

UpdatedJune 3, 2026 at 18:28

Map decision rights and action permissions across humans, agents, skills, plugin families, hooks, scripts, MCP servers, CI jobs, and external systems. Use when the user asks who can approve, edit, merge, deploy, access secrets, run commands, or make final decisions in an agent workflow.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

kas1987

kas1987/Chromatic_Governance

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name	authority-map
description	Map decision rights and action permissions across humans, agents, skills, plugin families, hooks, scripts, MCP servers, CI jobs, and external systems. Use when the user asks who can approve, edit, merge, deploy, access secrets, run commands, or make final decisions in an agent workflow.

Authority Map

Make authority explicit so agents know what they may decide, what they may recommend, and what requires approval.

Core procedure

List actors and components: user, coordinator, specialist agents, hooks, skills, scripts, MCP servers, CI, release process.
List action categories: read, write, execute, network, secrets, dependency changes, merge, deploy, delete, external communication.
Assign authority level for each actor/action: observe, recommend, draft, modify, approve, execute, or forbidden.
Define escalation triggers for ambiguous, destructive, credentialed, production, legal, financial, or security-sensitive actions.
Align the map with security-family permissions-plan when available.
Produce a matrix and highlight over-broad or missing authority.

Output format

Produce a concise, auditable markdown artifact. Include:

## Authority Map

**Scope:** ...
**Decision / recommendation:** ...
**Risk level:** low / medium / high / critical

### Findings
- ...

### Plan / matrix / record
| Item | Owner | Scope | Evidence | Gate / next action |
|---|---|---|---|---|

### Escalations
- ...

### Next actions
1. ...

Expected output focus: authority matrix plus overreach findings, missing owner findings, escalation gates, recommended corrections.

Guardrails

Prefer the narrowest capable agent and least authority required.
Do not let an agent approve its own high-risk work.
Mark assumptions separately from confirmed facts.
Require human approval for destructive, credentialed, production, external, legal, financial, or security-sensitive actions.
Do not invent agent capabilities; use the roster, plugin manifests, source files, and explicit user instructions.

Related references

references/authority-model.md
references/delegation-matrix.md
references/escalation-policy.md

More from this repository

same repository

visual-design

kas1987/Chromatic_Governance

Interactive front-end design companion — iterate on layouts, live component previews, and design tokens in a real browser, then hand the validated design to the frontend-family implement skills. Use when the user wants to design or refine UI look-and-feel, compare layout/wireframe options, preview real components, or tune color/spacing/typography before building.

2026-06-051

repo-pdr-swarm-router

kas1987/Chromatic_Governance

Ingest, decompose, govern, and route large repository PDR packages into agent-routable work queues with manifests, decision registers, risk registers, governance gates, and swarm-ready handoff packets. Use when the user provides repo PDR packages, audit bundles, project design records, implementation plans, backlog packs, or governance artifacts and wants them parsed, scored, split into agent assignments, and dispatched through the Chromatic router.

2026-06-041

cognitive-stack-architect

kas1987/Chromatic_Governance

Triage scattered, nonlinear, or overloaded thinking into a structured stack of decisions, priorities, and handoffs. Use when the project feels ambiguous, when too many threads are running in parallel, when you cannot determine what to work on next, or when a session has accumulated more open questions than resolved ones.

2026-06-041

repo-tree-architect

kas1987/Chromatic_Governance

Audit and redesign a repository's folder structure, root hygiene, scattered files, and naming conventions. Use when the repo root is cluttered, directories have grown organically without governance, files are misplaced across boundaries, or you need a clean canonical tree before onboarding agents or contributors.

2026-06-041

tree-repo-auditor

kas1987/Chromatic_Governance

Enforce numbered folder and subfolder naming standards across a repository. Audit whether directories follow an established numeric prefix convention (e.g. .01_, .02_, 01-, 1.) and produce a compliance report with remediation steps. Use when repo directories have grown without consistent naming, when onboarding contributors, or before a structural refactor.

2026-06-041

github-org-governance-manager

kas1987/Chromatic_Governance

Plan, audit, and standardize GitHub organization and repository governance — including personal-to-org repo transfers, branch protection, rulesets, team permissions, labels, repository settings, secrets review, and post-transfer validation. Use when moving repos into an organization, auditing existing permissions, generating settings checklists, or producing migration runbooks.

2026-06-041

name	authority-map
description	Map decision rights and action permissions across humans, agents, skills, plugin families, hooks, scripts, MCP servers, CI jobs, and external systems. Use when the user asks who can approve, edit, merge, deploy, access secrets, run commands, or make final decisions in an agent workflow.

Authority Map

Make authority explicit so agents know what they may decide, what they may recommend, and what requires approval.

Core procedure

List actors and components: user, coordinator, specialist agents, hooks, skills, scripts, MCP servers, CI, release process.
List action categories: read, write, execute, network, secrets, dependency changes, merge, deploy, delete, external communication.
Assign authority level for each actor/action: observe, recommend, draft, modify, approve, execute, or forbidden.
Define escalation triggers for ambiguous, destructive, credentialed, production, legal, financial, or security-sensitive actions.
Align the map with security-family permissions-plan when available.
Produce a matrix and highlight over-broad or missing authority.

Output format

Produce a concise, auditable markdown artifact. Include:

## Authority Map

**Scope:** ...
**Decision / recommendation:** ...
**Risk level:** low / medium / high / critical

### Findings
- ...

### Plan / matrix / record
| Item | Owner | Scope | Evidence | Gate / next action |
|---|---|---|---|---|

### Escalations
- ...

### Next actions
1. ...

Expected output focus: authority matrix plus overreach findings, missing owner findings, escalation gates, recommended corrections.

Guardrails

Prefer the narrowest capable agent and least authority required.
Do not let an agent approve its own high-risk work.
Mark assumptions separately from confirmed facts.
Require human approval for destructive, credentialed, production, external, legal, financial, or security-sensitive actions.
Do not invent agent capabilities; use the roster, plugin manifests, source files, and explicit user instructions.

Related references

references/authority-model.md
references/delegation-matrix.md
references/escalation-policy.md