search-first

Searches existing tools and libraries before coding to avoid duplication.

3|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/nassimbf/ftitos-claude-code --skill search-first-nassimbf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: search-first
Source: https://github.com/nassimbf/ftitos-claude-code/tree/main/skills/search-first
Command: npx skills add https://github.com/nassimbf/ftitos-claude-code --skill search-first-nassimbf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Research-before-coding workflow that helps teams search for existing tools, libraries, and patterns before writing new code to reduce duplication and rework.

Core Features & Use Cases

  • Structured pre-implementation research: guides discovery across npm/PyPI, MCP servers, GitHub, and internal catalogs.
  • Evaluation framework: scores candidates by functionality, maintenance, docs, license, and dependencies.
  • Decision guidance: helps decide to adopt as-is, extend, compose, or build custom solutions.

Quick Start

Run the search-first workflow to identify existing solutions before implementing new functionality.

Frequently Asked Questions about search-first

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

FAQPage Schema
How do I research existing libraries before coding to prevent duplication?

To research existing libraries before coding, use a structured pre-implementation workflow to search npm, PyPI, GitHub, and internal catalogs. This evaluates candidates by functionality, maintenance, and license to reduce rework and prevent writing duplicate code.

What is the best way to evaluate existing tools for software feature development?

The best way to evaluate existing tools for feature development is using a structured evaluation framework. This framework scores candidates by functionality, maintenance, documentation, license, and dependencies to ensure you select the most reliable solution for your project.

Can I use this research workflow for dependency upgrades and tool selection?

Yes, you can use this research workflow for dependency upgrades and tool selection. It is applicable across software projects to identify existing solutions, supporting structured research, parallel searching, and evaluation before making adoption decisions.

How do I decide whether to adopt, extend, or build a custom software solution?

To decide whether to adopt, extend, compose, or build a custom software solution, follow structured decision guidance after evaluating existing candidates. This guidance helps determine if an existing tool meets your needs or if custom development is required.

When should I not use existing libraries and instead build custom solutions?

You should build custom solutions instead of reusing existing libraries when candidates fail the evaluation framework for functionality, maintenance, or licensing. If no existing tool fits your project requirements, the workflow guides you to build custom code.