Individual skill
access-lifecycle
Use when preparing or running a user access review, checking that leavers lost their access, finding orphaned or ownerless service accounts, answering an auditor's access-control request for SOC 2, ISO 27001, PCI DSS, HIPAA or NIST 800-53, or checking whether a finished review campaign will hold up. Diffs the HR roster against account exports, tests the campaign for coverage, self-review, unremoved revokes and rubber-stamping, and maps every exception to the controls it breaks.
ra-qm-team/access-lifecycle/skills/access-lifecycle/SKILL.md
Source commit 9ef0c3c213932e645cc5cbeeb3c35c3a762a2437
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 29,505
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentic-ai Repository topic
- anthropic-claude Repository topic
- claude-ai Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- claude-code-skills Repository topic
- ai-coding-agent Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- openai-codex Repository topic
- marketing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,835 bytesSKILL.mdcore · 5,835 bytesassets/access_review_signoff.mddoc · 1,522 bytesassets/accounts.example.csvasset · 742 bytesassets/campaign.example.csvasset · 591 bytesassets/hr_roster.example.csvasset · 428 bytesreferences/access_review_campaigns.mddoc · 4,546 bytesreferences/control_crosswalk.mddoc · 3,515 bytesreferences/joiner_mover_leaver_standards.mddoc · 5,468 bytesscripts/access_diff.pyruns · 17,329 bytesscripts/access_review_campaign.pyruns · 16,073 bytesscripts/control_evidence_mapper.pyruns · 13,029 bytes
Read excerpt
# Access Lifecycle
> **Portability:** 3 stdlib scripts, no network, no IdP or HR connection. Export CSV, run, keep the output as evidence.
> **Not audit advice.** Periods and thresholds are your policy; the scripts make you state them.
Access reviews fail audits in four ordinary ways: the review ran on an incomplete
export, someone approved their own access, a revoke was decided and never
carried out, and leavers kept working accounts nobody looked at. Each script
catches one class of these before the auditor does.
## Workflow
```bash
# 1 - Diff: who has access that the HR roster says they should not?