What problem does it solve? Developers often reinvent the wheel by writing custom utilities and integrations without checking whether maintained libraries, MCP servers, or existing skills already solve the problem, leading to unnecessary code and dependency bloat. ## Core Features & Use Cases - Structured Research Workflow: Runs a five-stage pipeline covering need analysis, parallel search across npm/PyPI, MCP servers, and GitHub, candidate evaluation, and an adopt/extend/build decision. - Decision Matrix: Scores candidates on functionality, maintenance, community, documentation, license, and dependencies to choose between adopting, extending, composing, or building custom. - Use Case: Before adding dead-link checking to a docs site, the skill finds textlint-rule-no-dead-link on npm and recommends adopting it directly instead of writing a custom checker. ## Quick Start Ask the assistant to research existing tools and libraries for the functionality you are about to implement before writing any code.