tools-marketplace-inventory

To generate a complete inventory of marketplace components, you can scan local marketplace structures and plugin caches. This process enumerates all bundles, agents, commands, skills, and scripts, outputting a structured TOON or JSON report for downstream auditing and automation pipelines.

The best way to detect dependencies and script notations is using a scanner that applies frontmatter parsing and dependency detection. It identifies script notations, skill references, imports, relative paths, and implements, providing a structured inventory for analysis.

Yes, you can filter marketplace inventory reports by specific scopes, bundles, and resource types. This allows you to generate targeted reports focusing on particular components like commands, skills, or scripts rather than the entire repository.

Yes, the inventory scanner supports JSON output format for automation pipelines. It generates structured JSON or TOON inventory files detailing all marketplace components, enabling seamless integration with downstream automation and dependency analysis tools.

You need to scan plugin caches when auditing installed components or analyzing dependencies across local marketplace structures. This identifies relationships between bundles, agents, commands, skills, and scripts to support reporting and dependency analysis.

TOON format provides a structured inventory representation optimized for marketplace components. Both TOON and JSON outputs are supported, allowing you to choose the format that best integrates with your specific automation pipelines and downstream tooling requirements.