api-scan

Scan dependency files across npm, Python, and Rust ecosystems to identify external libraries.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/oozoofrog/codex-skills --skill api-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-scan
Source: https://github.com/oozoofrog/codex-skills/tree/main/api-scan
Command: npx skills add https://github.com/oozoofrog/codex-skills --skill api-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identifies project dependencies and flags libraries that are not internalized, enabling teams to reduce risk and improve maintainability.

Core Features & Use Cases

  • Dependency detection across common ecosystems (npm, Python, Rust, etc.).
  • Internalization auditing by comparing against a central references index (.claude/references/_index.md).
  • Use Case: A codebase can surface uninternalized libraries and generate a remediation plan to standardize dependencies.

Quick Start

Identify all dependencies in your repository and propose actionable steps to internalize or replace them.

Frequently Asked Questions about api-scan

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

FAQPage Schema
How do I audit project dependencies across npm, Python, and Rust ecosystems?

Dependency internalization is the process of identifying external libraries in your codebase and standardizing them as internal references. It reduces risk and improves maintainability by ensuring projects rely on approved, centrally managed libraries.

What is dependency internalization and how does it improve codebase maintainability?

Dependency internalization identifies external libraries in your codebase and standardizes them against a central references index. It improves maintainability by flagging uninternalized dependencies and generating a remediation plan to reduce risk.

How do I identify which libraries in my codebase are not internalized?

You can identify uninternalized libraries by scanning dependency files and comparing the detected packages against a references index like `.claude/references/_index.md`. This cross-language audit flags external dependencies for remediation.

Can I automate a cross-language dependency audit for my repository?

Yes, you can automate a cross-language dependency audit to scan dependency files across common ecosystems. The workflow identifies external dependencies, compares them with your internal index, and proposes actionable steps to internalize or replace them.

Do I need a central references index to scan and plan dependency internalization?

Yes, a central references index such as `.claude/references/_index.md` is required to compare scanned dependencies against internalized libraries. This comparison determines which packages are external and generates the remediation plan.