Technology Supply Chain Security Auditor

Problem

When assessing a tech company's supply-chain security, the key question is not whether it uses imported parts, but whether critical nodes create fatal dependencies: EDA/IP, advanced process, packaging, equipment/materials, and software ecosystems. This skill turns scattered news, filings, teardown reports, and broker research into comparable risk judgments.

How It Works

The workflow is:
- Dependency mapping: identify technology layers, supplier concentration, and substitutability across design tools, components, manufacturing/packaging, and ecosystems.
- Quantified scoring: assign 1-5 risk scores to each node, and evaluate domestic alternatives by TRL, performance gap, ecosystem compatibility, capacity, and switching cycle.
- Scenario simulation: under basic or comprehensive depth, model partial and full supply cutoffs, estimate buffer time, performance degradation, recovery time, and survival probability.
- Breakout paths: identify rerouting, technology-route switches, ecosystem building, and policy-supported actions across near-, mid-, and long-term horizons.

Boundaries

The skill relies on public, verifiable information and is suited to technical security audits, sanctions screening, and supply-chain resilience reviews. Inferred scenarios should be separated from facts; if supplier relationships, domestic production capacity, or customer ecosystems lack public data, confidence in the conclusion decreases and primary verification is needed.