search-first

Research existing tools, libraries, and patterns before implementing custom code.

2|Updated May 11, 2026

Search Tags:#development workflow #code reuse #tool discovery #solution selection #dependency evaluation #research before coding #open source search

Ready to run

npx skills add https://github.com/himanshu231204/AI_Research_agent --skill search-first-himanshu231204

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: search-first
Source: https://github.com/himanshu231204/AI_Research_agent/tree/main/.opencode/skills/search-first
Command: npx skills add https://github.com/himanshu231204/AI_Research_agent --skill search-first-himanshu231204

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates wasted development effort from building custom functionality that already exists as maintained, production-ready tools, libraries, or integrations, reducing technical debt and speeding up feature delivery.

Core Features & Use Cases

Systematic Research Workflow: Guides you to check package registries, MCP servers, existing skills, and open source GitHub projects before writing any new code.
Structured Decision Matrix: Helps you choose between adopting, extending, composing, or building custom solutions based on candidate quality, maintenance status, and license compatibility.
Use Case Example: When asked to add retry logic to an HTTP client, this Skill finds pre-built, battle-tested libraries like httpx or got instead of requiring you to write custom retry code from scratch.

Quick Start

Use the search-first skill to research existing maintained tools for adding dead link checking to your markdown documentation before writing any custom validation code.

Frequently Asked Questions about search-first

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

FAQPage Schema

How do I avoid building redundant custom code for new software features?▼

To avoid redundant custom code, research existing maintained libraries and open source tools before implementation. A search-first workflow checks package registries and GitHub projects to find production-ready solutions, reducing development time and technical debt.

What is the best way to evaluate existing libraries before adding a dependency?▼

Evaluating existing libraries requires a structured decision matrix comparing candidate quality, maintenance status, and license compatibility. This solution selection process helps you decide whether to adopt, extend, compose, or build custom solutions for your dependency.

How do I find pre-built tools for adding retry logic to an HTTP client?▼

Finding pre-built tools for HTTP client retry logic involves checking package registries for battle-tested libraries like httpx or got. Researching these maintained open source tools prevents writing custom validation code from scratch and speeds up feature delivery.

When should I research existing open source tools instead of writing custom code?▼

You should research existing open source tools whenever adding new features, dependencies, utilities, or integrations across programming languages. Checking MCP servers and GitHub projects before coding ensures you adopt maintained solutions and avoid wasting development effort.

Does the search-first approach work for utility creation across different programming frameworks?▼

The search-first approach applies to utility creation across all programming languages and frameworks. It systematically guides you to check existing skills and open source projects to ensure you are not rebuilding functionality that already exists as maintained code.

How do I choose between extending an existing tool and building a custom solution?▼

Choosing between extending or building requires a structured decision matrix evaluating candidate quality and maintenance status. This dependency evaluation ensures you select the most viable solution, minimizing technical debt while meeting your feature requirements.