maxwellokumu/okaudit-claude-skills / identity-access/sod-analyzer
sod-analyzer
VerifiedDetect segregation of duties conflicts in user role assignments. Use this skill for role conflict analysis, four-eyes control review, and SOD violation detection.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 2.0 KB |
| SKILL.md | skill md | 1.7 KB |
| main.py | script | 15.2 KB |
| sample_input/conflicts.json | config | 677 B |
| sample_input/users.json | config | 707 B |
| skill.yaml | config | 954 B |
SKILL.md
View on GitHub---
name: sod-analyzer
description: Detect segregation of duties conflicts in user role assignments. Use this skill for role conflict analysis, four-eyes control review, and SOD violation detection.
---
# Sod Analyzer
Use this skill when the user asks about segregation of duties, SOD analysis, role conflicts, duties separation, or four-eyes controls.
## Goal
Detect user role combinations that violate segregation-of-duties expectations and report the conflicts with risk context.
## Workflow
1. Confirm the user role dataset and whether built-in or custom conflict rules should be used.
2. Gather the user-role input and any custom conflict definitions.
3. Review README.md if you need examples of supported input shapes or output style.
4. Run main.py with the selected inputs and rule settings.
5. Summarize the conflicts, affected users, and the highest-risk combinations first.
## Inputs
- users (string, required): Path to JSON file mapping usernames to roles.
- conflicts (string, optional): Path to JSON file with custom conflict pairs.
- builtin_conflicts (boolean, optional): Include the built-in conflict library.
## Bundled Files
- main.py: executable logic for the skill.
- README.md: detailed usage, supported inputs, and sample outputs.
- sample_input: bundled example user-role and conflict data.
- skill.yaml: existing repo manifest retained for this project's original packaging.
## Guidance
- Prefer built-in conflicts for standard reviews and add custom rules when the environment has specialized duties.
- Keep the explanation tied to independence of control and risk, not just role names.
- If the role dataset is incomplete, flag that the analysis may underreport conflicts.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |