search-first

Research existing tools, libraries, and integrations before writing custom code.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/sayasaya8039/ZWG_Terminal --skill search-first-sayasaya8039
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: search-first
Source: https://github.com/sayasaya8039/ZWG_Terminal/tree/main/.claude/skills/search-first
Command: npx skills add https://github.com/sayasaya8039/ZWG_Terminal --skill search-first-sayasaya8039

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates wasted development effort by preventing teams from building custom functionality that already exists as maintained, production-ready libraries, tools, or integrations, reducing project timelines and technical debt.

Core Features & Use Cases

  • Multi-source parallel research: Search npm, PyPI, MCP servers, GitHub, and existing Claude Code skills simultaneously for existing solutions to common development problems.
  • Structured decision framework: Score candidates across functionality, maintenance status, community support, documentation, license, and dependencies to choose between adopting, extending, composing, or building custom code.
  • Use Case: When tasked with adding a config file linter to a project, the Skill identifies ajv-cli as a suitable existing tool, avoiding the need to write a custom JSON schema validator from scratch.

Quick Start

Use the search-first skill to research existing tools for adding a resilient HTTP client with retry support to your Node.js project before writing any custom code.

Frequently Asked Questions about search-first

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

FAQPage Schema
How do I find existing open source libraries before writing custom code?

Finding existing open source libraries requires searching npm, PyPI, GitHub, and MCP servers in parallel to prevent redundant development. This approach identifies maintained, production-ready tools that already fulfill your feature requirements before you write custom code.

What is the best way to evaluate dependencies for a software project?

The best way to evaluate dependencies for a software project is through a structured decision framework that scores candidates across functionality, maintenance status, community support, documentation, license compatibility, and transitive dependencies to minimize bloat.

Can I use this research approach to add utility functions to my development workflow?

Yes, you can use this research approach to add utility functions to your development workflow. It applies to feature implementation, dependency addition, and technology stack selection, ensuring you adopt or compose existing solutions instead of building redundant custom utilities.

When should I choose to build custom code over adopting an existing library?

You should choose to build custom code over adopting an existing library only after structured evaluation proves that no maintained open source tool meets your functionality, support, or licensing needs. This decision framework helps decide whether to adopt, extend, compose, or build.

Why does dependency management matter when selecting a technology stack?

Dependency management matters when selecting a technology stack because adding unnecessary custom code increases technical debt and project timelines. Leveraging maintained open-source solutions eliminates redundant development work and minimizes dependency bloat.