maxwellokumu/okaudit-claude-skills / hardware-physical/physical-access-review
physical-access-review
VerifiedAnalyze badge or door access logs so Claude can explain after-hours activity, repeated failures, and other physical access anomalies clearly.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 1.5 KB |
| SKILL.md | skill md | 1.7 KB |
| main.py | script | 16.2 KB |
| sample_input/badge_logs.csv | other | 2.7 KB |
| sample_input/roles.json | config | 1.1 KB |
| skill.yaml | config | 1.0 KB |
README.md
View on GitHub# physical-access-review
Analyse badge access logs to detect after-hours access, failed attempt bursts, tailgating and forced entry events, unauthorised door access, and suspicious rapid multi-door traversal patterns.
## Requirements
- Python 3.8+
- No external dependencies
## Usage
```bash
# Basic analysis
python main.py --logs sample_input/badge_logs.csv
# With role mapping and custom business hours
python main.py \
--logs sample_input/badge_logs.csv \
--roles sample_input/roles.json \
--hours 08:00-18:00 \
--failed-threshold 5
```
### Options
| Flag | Required | Default | Description |
|------|----------|---------|-------------|
| `--logs` | ✅ | — | Path to badge access log CSV |
| `--hours` | | `07:00-19:00` | Business hours window (HH:MM-HH:MM) |
| `--roles` | | — | Path to roles JSON for door authorisation checks |
| `--failed-threshold` | | `3` | Max failures per hour per badge before flagging |
### Badge Log CSV Schema
```
badge_id,door,timestamp,result
```
`result` values: `SUCCESS`, `FAILED`, `TAILGATE`, `FORCED`
### Roles JSON Schema
```json
{
"B001": {
"name": "Alice Smith",
"role": "Engineer",
"allowed_doors": ["main-entrance", "office-a", "server-room"]
}
}
```
## Sample Output
```
# Physical Access Audit Report
## Summary
| Category | Count |
|---------------------------|-------|
| After-Hours Access | 4 |
| Failed Attempt Bursts | 1 |
| Tailgate / Forced Events | 1 |
| Unauthorised Door Access | 2 |
| Anomalous Patterns | 1 |
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |