search-first

Identify and evaluate existing tools, libraries, and patterns before writing code.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and evaluate existing tools, libraries, and patterns before writing code.

Core Features & Use Cases

  • NEED ANALYSIS: Define functionality needed and constraints.
  • PARALLEL SEARCH: Explore npm/PyPI, MCP servers, GitHub for candidates.
  • DECIDE: Determine adopt/extend/build decisions and plan integration.

Quick Start

Run the researcher workflow to identify and evaluate existing tools before coding.

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 and tools before writing code for a new feature?

To find existing libraries before writing code, you define functionality constraints, execute parallel searches across package registries and GitHub, and evaluate candidates to decide whether to adopt, extend, or build.

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

Evaluating external dependencies involves applying structured criteria to candidates discovered through parallel searches, ultimately producing a decision to adopt, extend, or build the functionality yourself.

When should I search for existing patterns instead of building a solution from scratch?

Search for existing patterns when starting a new feature, adding dependencies, or integrating with unfamiliar tech to guide decision-making, reduce code duplication, and avoid rebuilding existing solutions.

How do I analyze project needs to find matching tools on package registries?

Analyze project needs by defining the exact functionality required and your constraints, then use these structured criteria to filter and evaluate matching tools found across npm, PyPI, and GitHub.

Does this pattern-discovery workflow support searching MCP servers for integration candidates?

Yes, the pattern-discovery workflow supports parallel searches across MCP servers, GitHub, and package registries to identify and evaluate integration candidates before making an adopt or build decision.