oss-discoverylisted
Install: claude install-skill shoei03/oss-discovery
# Find OSS and judge whether to adopt it
## First: never send natural language straight to search
GitHub search is an AND search over keywords. A sentence returns nothing.
```bash
gh search repos "a tool that autocompletes SQL when you write in the terminal" # 0 results
gh search repos --topic=sql --topic=cli --stars=">500" --archived=false # hits
```
Always translate the request into topics, languages and numeric qualifiers before searching.
---
## Stage 1. Find
### Check for a domain registry first
If what you are looking for belongs to a specific domain (MCP servers, editor extensions, packages in a
particular ecosystem), that domain's registry beats GitHub search. **When you find a registry, treat it not
as a shortcut within stage 1 but as the output of a full pass through the workflow.**
```
Pass 1: target = "the means of searching this domain"
Stages 1-3 identify the registry.
Stage 4 clarifies its API and constraints.
The output is the search mechanism itself.
Pass 2: target = what you actually wanted
Stage 1 searches using the registry's API, then stages 2-4 as usual.
```
**Do not skip stage 4 and infer capabilities.** If an OpenAPI spec exists, read it. Writing "it should be
able to" is how you get it wrong.
### Package ecosystems are enumerable - never hardcode them
```bash
curl -s "https://packages.ecosyste.ms/api/v1/registries" \
| jq -r '.[] | "\(.name)\t\(.ecosystem)\t\(.packages_count)"' | sort -t$'\t' -k3 -rn
# 100 reg