active-path-complexity-auditor

Audit active deployment, credential, and recovery paths to identify redundant operational complexity.

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/Military-Veteran-Team-LPT-Realty/mvt-manus-public-skills --skill active-path-complexity-auditor-military-veteran-team-lpt-realty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: active-path-complexity-auditor
Source: https://github.com/Military-Veteran-Team-LPT-Realty/mvt-manus-public-skills/tree/main/skills/active-path-complexity-auditor
Command: npx skills add https://github.com/Military-Veteran-Team-LPT-Realty/mvt-manus-public-skills --skill active-path-complexity-auditor-military-veteran-team-lpt-realty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Organizations often accumulate multiple overlapping source, CI, credential, hosting, and domain paths to production, creating hidden risk and unclear ownership. This Skill performs a read-only audit that counts active operational paths, flags ungoverned duplicates, and produces a staged simplification plan without making any changes. ## Core Features & Use Cases - Operational Path Inventory: Uses a structured template to catalog source, CI/release, credential, hosting, domain, and recovery routes with owner and status fields. - Status Classification: Marks each path as ACTIVE, RECOVERY_ONLY, TRANSITIONAL, DISABLED, or UNKNOWN, treating unknowns as risk rather than benign. - Complexity Scoring and Simplification Planning: Counts duplicate active paths to the same production outcome and recommends staged consolidation that preserves a tested recovery path. - Use Case: A team discovers three repositories, two CI pipelines, and multiple DNS aliases all capable of reaching production. Run this audit to classify each path, identify the intended single production route, and produce an approval-gated simplification plan. ## Quick Start Audit my organization's active source, deployment, credential, and recovery paths and report redundant routes to production.

Frequently Asked Questions about active-path-complexity-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit redundant deployment paths in my organization?

Use the audit template to inventory every source, CI, credential, hosting, domain, and recovery route, then mark each as ACTIVE, RECOVERY_ONLY, TRANSITIONAL, DISABLED, or UNKNOWN. Count duplicate active paths to the same production outcome to compute the operational complexity score.

What counts as an active path versus a recovery asset?

An active path can actually change or deploy to production, while a recovery asset like a backup that cannot deploy is classified RECOVERY_ONLY. The audit counts active paths, not just assets, so backups do not inflate the production path count.

Does this audit make changes to repositories, DNS, or credentials?

No, the audit is strictly read-only. It never disables mirrors, deletes repositories, revokes credentials, or alters DNS; any simplification action requires a separate approval packet and verified rollback evidence.

How are unknown owners or deployment targets handled in the audit?

Every unknown source, credential owner, deployment target, domain alias, or rollback path is marked UNKNOWN rather than treated as benign. These unresolved ownership gaps are reported explicitly in the audit output.

What does the audit report include?

The report lists counts of active source, CI, credential, deployment, and domain paths, the intended single production path, independent recovery assets, unresolved ownership gaps, and the smallest approval-required simplification action.