Skip to content
Back to skills

Ad Inventory And Paths

ASecurity

Analyze approved local Active Directory inventory exports for provenance-linked candidate relationship paths and coverage gaps.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 15, 2026
securitypythonrust

Security analysis

A100/100

Scanned October 15, 2026

npx -y skills add sodejm/copilot-operation-plugin-for-security --skill ad-inventory-and-paths --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ad Inventory And Paths?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ad Inventory And Paths
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sodejm-ad-inventory-and-paths/badge)](https://www.skillsdirectory.com/skills/sodejm-ad-inventory-and-paths)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ad-inventory-and-paths
description: Analyze approved local Active Directory inventory exports for provenance-linked candidate relationship paths and coverage gaps.
---

# AD inventory and paths

Use this skill only for an explicitly scoped, approved local export. Verify the
forest, domain, and host scope with the requester before handling real data. Do
not request credentials or query AD, LDAP, Kerberos, or hosts. The input contract
is in `specs/ad-inventory-and-paths.md` at the repository root.

1. From the installed package root, run `python3 scripts/analyze.py <local-export.json>`.
2. Review `coverage` first. `unknown` or `partial` means collection cannot support
   a claim of absence. A missing path means only that a completed search of the
   collected graph lacks it; `search_incomplete` means the search hit a bound.
3. Trace each candidate path's directed edges to collector ID, UTC time,
   completeness, and observed/inferred support. Treat trust, protected identities,
   partial collection, and inferred edges as validation questions.
4. Report candidate structural relationships, uncertainty, and the additional
   evidence needed. Never describe an observed edge or graph path as proof of
   usable access, exploitation, or live validation.

The fixture and demo are synthetic. Keep imported data local and follow the
engagement's evidence handling rules. The analyzer rejects raw display names and
attributes; prepare opaque IDs before import.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.