agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/access-control-audit/SKILL.md

access-control-audit

Skill1 starsChanged 23 days agoMITView on GitHub

Audits identity and access controls when excessive privileges, stale accounts or weak approvals create exposure.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use after team changes, before assurance work, or when privileged and sensitive access lacks clear governance.

    line 9
  2. Distinctive:

    Test provisioning, periodic recertification, removal and emergency access controls.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Access Control Audit

When to use it

Use after team changes, before assurance work, or when privileged and sensitive access lacks clear governance.

What Claude needs

  • client-context.md for business background
  • User, role, group and privilege extracts
  • Joiner, mover and leaver procedures
  • System owners, approval records and access policies

Method

  1. Define sensitive resources, privileged actions and incompatible duty combinations.
  2. Reconcile active identities with current workers, partners and service accounts.
  3. Compare assigned access with role need, approval and least-privilege rules.
  4. Identify dormant accounts, privilege accumulation, shared credentials and segregation conflicts.
  5. Test provisioning, periodic recertification, removal and emergency access controls.
  6. Build a remediation queue and sustainable role-based access model.

Output format

Provide an exceptions table with identity, resource, access, issue, evidence, risk and action. Add control findings and a recertification schedule.

Quality checks

  • Privileged, service and external accounts are included.
  • Exceptions are validated with system and business owners.
  • Removal actions consider operational dependencies and recovery access.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.