What problem does it solve? Developers often write custom utilities and integrations without checking whether maintained libraries, MCP servers, or existing skills already solve the problem, leading to duplicated effort and unnecessary maintenance burden. ## Core Features & Use Cases - Structured Research Workflow: Runs a five-phase process covering need analysis, parallel search across npm/PyPI, MCP servers, and GitHub, candidate evaluation, and an adopt/extend/build decision. - Tool Availability Preflight: Verifies which search channels (ripgrep, package managers, GitHub CLI, MCP tools) are actually available and honestly reports skipped channels. - Decision Matrix: Maps search outcomes to concrete actions such as adopting a well-maintained package, extending a partial match, or building custom code only when nothing fits. - Use Case: When asked to add dead-link checking to a documentation site, the skill searches npm, finds textlint-rule-no-dead-link, and recommends installing it instead of writing a custom checker. ## Quick Start Before writing any new utility or integration, ask the assistant to run the search-first workflow to find existing packages, MCP servers, or skills that already solve the problem.