search-first

Research existing tools and libraries before implementing custom code.

Updated Jun 24, 2026

Search Tags:#research #integration #implementation #libraries #dependencies #search #mcp

Ready to run

npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill search-first-mostafa-ismail-2004

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: search-first
Source: https://github.com/mostafa-ismail-2004/codex-plugin/tree/main/skills/search-first
Command: npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill search-first-mostafa-ismail-2004

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unnecessary custom coding by forcing a research-first workflow before adding new functionality, dependencies, or abstractions.

Core Features & Use Cases

Need analysis: Clarifies the requirement, constraints, and the exact capability needed before implementation.
Parallel research: Searches libraries, MCP servers, Codex skills, and GitHub for existing solutions that may already solve the problem.
Decision support: Compares options and recommends whether to adopt, extend, compose, or build custom.
Use case: A developer wants to add retryable HTTP handling and uses this Skill to discover whether an existing library already fits instead of writing a new wrapper from scratch.

Quick Start

Ask the assistant to research existing tools and patterns for your feature before writing any 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 libraries before writing custom code for a new feature?▼

To find existing libraries, use a research-first workflow that searches repositories and evaluates maintenance fit before coding. This process clarifies exact capability requirements and compares candidate solutions to recommend whether to adopt, extend, compose, or build custom code.

What is the best way to compare dependencies for JavaScript and Python integrations?▼

The best way to compare dependencies for JavaScript and Python integrations is through structured evaluation of candidate solutions. This involves analyzing feature constraints, searching GitHub for existing tools, and evaluating license fit to determine whether to adopt or build.

Do I need to build a custom MCP server or can I extend an existing one?▼

Whether to build a custom MCP server or extend an existing one depends on a structured comparison of candidate solutions. By researching GitHub-based ecosystems and evaluating maintenance fit, you can decide whether to adopt, extend, compose, or build.

How do I evaluate open source licenses and maintenance fit before adding a dependency?▼

To evaluate open source licenses and maintenance fit before adding a dependency, perform a parallel research sweep of libraries and GitHub repositories. This structured comparison assesses candidate solutions against your constraints and recommends whether to adopt or build.

When should I not use existing libraries and instead build custom utility wrappers?▼

You should not use existing libraries and instead build custom utility wrappers when structured comparison reveals no candidate solution fits your maintenance, license, or capability constraints. This research-first approach ensures you only build custom when adopt or extend options fail.