search-first

Search Salesforce tools and libraries across npm, AppExchange, MCP, and GitHub.

13|2|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/jiten-singh-shahi/salesforce-claude-code --skill search-first-jiten-singh-shahi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: search-first
Source: https://github.com/jiten-singh-shahi/salesforce-claude-code/tree/main/.cursor/skills/search-first
Command: npx skills add https://github.com/jiten-singh-shahi/salesforce-claude-code --skill search-first-jiten-singh-shahi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents wasted engineering effort by finding existing Salesforce tools, Apex libraries, MCP servers, AppExchange packages, or GitHub implementations before writing custom code, so teams avoid reinventing well-maintained solutions.

Core Features & Use Cases

  • Parallel discovery: Runs broad searches across npm, AppExchange, MCP servers, GitHub, and local Claude Code skills to gather candidate implementations.
  • Structured evaluation: Scores candidates by functionality fit, maintenance activity, documentation quality, license compatibility, and dependency surface.
  • Decision guidance: Recommends adopt, extend, compose, or build based on search results and provides minimal next steps for installation or prototyping.
  • Agent mode: Launches a general-purpose research agent to produce a structured comparison and recommendation when the problem is non-trivial.

Quick Start

Run the search-first workflow to research existing npm, AppExchange, MCP, and GitHub solutions for the feature you plan to implement and return a scored recommendation with suggested next steps.

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 Salesforce libraries before writing custom Apex code?

To find existing Salesforce libraries before writing custom Apex code, run a parallel discovery workflow that searches npm, AppExchange, GitHub, and MCP servers. The search evaluates functionality fit, maintenance activity, documentation quality, license compatibility, and dependency surface to recommend whether you should adopt, extend, compose, or build a solution.

What is the best way to compare AppExchange apps and npm packages for a new feature?

The best way to compare AppExchange apps and npm packages for a new feature is to use a structured evaluation system that scores candidates by functionality, maintenance, license, documentation, and dependency impact. This comparison provides decision guidance on whether to adopt, extend, compose, or build, along with minimal installation or prototyping next steps.

Can I research existing MCP servers and GitHub implementations for Salesforce architecture design?

Yes, you can research existing MCP servers and GitHub implementations for Salesforce architecture design. The systematized research process gathers candidate implementations across these platforms and local Claude Code skills, producing structured comparisons that inform your design and decision-making workflows before you start coding.

How do I evaluate the maintenance and documentation quality of discovered Salesforce tools?

To evaluate the maintenance and documentation quality of discovered Salesforce tools, apply a structured scoring system during your package discovery process. The evaluation specifically scores candidates by their maintenance activity, documentation quality, license compatibility, and dependency surface area to guide your architecture decisions.

Does this package discovery workflow provide installation steps after recommending a solution?

Yes, the package discovery workflow provides installation steps after recommending a solution. Once the structured evaluation scores candidates and recommends whether to adopt, extend, compose, or build, it delivers minimal next steps for installation or prototyping the chosen Salesforce solution.

When should I avoid using existing AppExchange apps and build custom code instead?

You should avoid using existing AppExchange apps and build custom code instead when the structured evaluation reveals poor maintenance activity, incompatible licenses, inadequate documentation, or excessive dependency surface area. The decision guidance recommends building only when well-maintained existing solutions do not meet your functionality fit requirements.