inference-vendor-lock-in-scorer

To assess vendor lock-in exposure, scan your skill directories and agent configurations to surface portability risks. This process generates a per-artifact score across four dimensions: model name configurability, API portability, fallback provisions, and key management, producing a prioritized remediation queue.

Vendor lock-in scoring analyzes artifacts to quantify portability risks across model naming, API surface portability, fallback availability, and key management. It helps teams maintain portable architectures and plan smoother migrations by identifying dependencies before they become problematic.

Generate a prioritized remediation queue by running a scan against your skills folder or agent configs. The analysis evaluates lock-in dimensions and outputs prioritized steps to reduce exposure, enabling teams to address the most critical portability risks before starting migrations.

Yes, you can scan agent configurations and skill paths to prepare migration plans. The scan evaluates model name configurability and API surface portability to identify dependencies, providing a structured report that supports portable architecture transitions and smoother migrations.

Scoring evaluates four dimensions: model name configurability, API surface portability, fallback provisions, and key management. Each artifact receives a per-dimension score to quantify vendor lock-in exposure, generating a prioritized remediation queue to reduce dependencies.

Yes, vendor lock-in scoring evaluates artifacts regardless of their current state. Artifacts lacking fallback provisions or configurable key management receive lower portability scores, flagging them as higher priority in the remediation queue to address before migrations.