access-review

Solid

Review an Acme Corp service access-grant request against the least-privilege access policy. Use ONLY when the user explicitly asks to review, risk-analyze, or policy-check a SPECIFIC access request, identified by a request ID such as AR-2043 accompanied by review intent, or pasted access-request JSON (fields like request_id, requestor, service, role, environment, duration_days). Applies the least-privilege policy (role catalog, production time-boxing, privileged-PII manager approval) and renders a structured Markdown review comment. Do NOT use this skill for - access status lookups (e.g. "what's the status of AR-2043" - answer directly), requests to grant, approve, or revoke access (decline - this DE never makes access decisions), listing or searching access requests, or general questions about what the policy says (answer those from the knowledge base without reviewing any request). Comment-only output; the grant decision stays with a human approver.

Code & Development 0 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
0
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Access Review (Least-Privilege Policy) Review service access-grant requests against the Acme Corp least-privilege access policy. Apply the policy rules to the request and post a structured pass/warn/fail review comment. **This skill never grants, approves, or revokes access.** It produces a comment for a human access approver to act on. ## When to trigger Trigger on: - A bare access-request ID with review intent, e.g. "review access request AR-2043 against the policy" - Pasted access-request JSON/content with a request to review it - "least-privilege check" / "access policy risk analysis" phrasing on a specific request Do **not** trigger (or trigger as review) on: - Pure status queries ("what's the status of AR-2043") — that's a lookup, not a review; a review re-runs the policy checks and produces a fresh comment - Any request to grant, approve, or revoke access ("grant me admin on checkout") — this skill has no grant/approve/revoke capability by design; redirect the user to the access-management system's own approval action - Questions about what the policy says in general — answer those from the knowledge base without reviewing a specific request ## Inputs - **Access request** (required): pasted JSON, or a request ID the user supplies the JSON for. Expected fields: `request_id`, `requestor`, `service`, `role`, `environment`, and (for production) `justification_ticket`, `duration_days`, `manager_approved`. - **Policy** (optional): defaults to the bu...

Details

Author
arthaszyb
Repository
arthaszyb/bright-talent
Created
1 weeks ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

authz-review

Use when reviewing authorization end-to-end — route → gate → policy → query scope → response filter — before changes to permissions, tenants, ownership, or admin flows.

7 Updated today
event4u-app
Code & Development Listed

review-a11y

Use to REVIEW code changes for accessibility — '/review-a11y', 'review my changes/PR/branch for a11y', 'accessibility review of this diff'. Scopes to exactly the code under change (staged files, working diff, or branch vs merge-base), runs the bundled install-free ultra11y engine (node scripts/ultra11y.mjs, no keys; static WCAG 2.2 AA checks tied to success criteria, cross-file JSX/TSX via --graph), then adds YOUR judgment: refute false positives (SFC/library-source findings are preliminary), decide alt relevance and link purpose, name the rendering criteria (contrast, focus, zoom) as residual risks — never invent a non-conformity. Output: a severity-ranked review (blocking → major → minor) with file:line, concrete fixes, residual risks and a one-line verdict, in the conversation's language (technical tokens stay in English). Companion of the ultra11y skill (full audits, reports, PRD, RGAA packs). Triggers: 'review a11y', 'a11y review', 'accessibility review'.

1 Updated today
maxgfr
Code & Development Listed

accessibility-review

Audits a digital product against recognized accessibility standards — WCAG (the W3C Web Content Accessibility Guidelines) and IBM's accessibility requirements — and produces a prioritized findings report mapping each issue to the specific success criterion it fails, with severity and a concrete fix. Use this whenever the user wants an accessibility review, a11y audit, WCAG check, Section 508 / EN 301 549 conformance pass, or wants to know whether a screen, component, flow, PDF, or document is accessible; wants to fix contrast, keyboard, screen-reader, focus, alt-text, form-label, or ARIA problems; or asks which WCAG criterion something violates. Reach for it even when "accessibility" isn't named — any request to make a UI usable for people with disabilities, or to meet a legal accessibility requirement, qualifies.

0 Updated today
JoaoMonteiro100