package-scout

Search internal, Deere, and public npm packages to generate a REUSE_CATALOG.md.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/aiguy611/cc-tools --skill package-scout-aiguy611
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: package-scout
Source: https://github.com/aiguy611/cc-tools/tree/main/.github/skills/package-scout
Command: npx skills add https://github.com/aiguy611/cc-tools --skill package-scout-aiguy611

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Package Scout helps teams avoid reinventing the wheel by discovering reusable code and packages across internal codebases, Deere registries, and public npm ecosystems, and by generating a consolidated REUSE_CATALOG.md.

Core Features & Use Cases

  • Tiered discovery across internal codebase utilities, Deere npm packages, and public npm packages.
  • Generates a REUSE_CATALOG.md with sections: Internal Reuse, Deere Packages, External Packages, Build-From-Scratch.
  • Used before story decomposition, before implementation, or when asked to find existing solutions.

Quick Start

Provide planning documents to package-scout to generate a comprehensive reuse catalog before feature decomposition.

Frequently Asked Questions about package-scout

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

FAQPage Schema
How do I discover reusable code packages before starting feature implementation?▼

Reuse cataloging helps avoid reinventing the wheel by locating existing packages across internal codebases, Deere registries, and public npm ecosystems, reducing risk and dependency planning effort before story decomposition.

What is the best way to catalog internal and public npm packages for dependency planning?▼

The best way to catalog packages is executing multi-tier searches across internal, Deere, and public npm sources, which outputs a REUSE_CATALOG.md detailing Internal Reuse, Deere Packages, External Packages, and Build-From-Scratch sections.

Do I need planning documents to search for reusable code across multiple registries?▼

Yes, planning documents are required as input to effectively search across multiple tiers and generate a comprehensive reuse catalog that accurately matches your feature discovery and dependency planning needs.

Can I find Deere npm packages and internal codebase utilities using the same search?▼

Yes, you can find Deere npm packages and internal codebase utilities simultaneously through a multi-tier search that scans internal code, Deere registries, and public npm packages in one consolidated operation.

When should I generate a reuse catalog instead of building a package from scratch?▼

You should generate a reuse catalog before story decomposition or implementation to identify existing internal, Deere, or public packages, moving to Build-From-Scratch only when no suitable reusable code is found.