registry-presencelisted
Install: claude install-skill agentrel/skills
# Registry presence
Being good is not being found. An agent that cannot resolve a product from a registry will
recommend a competitor that is listed, and no amount of documentation quality changes that.
This skill answers one question with facts rather than judgement: **where is this product
listed, where is it not, and what is the exact step to fix each gap.**
## Applies to
| | |
|---|---|
| **Project types** | Anything an agent could discover and use — MCP servers, SDKs, APIs, CLIs, developer platforms, published packages |
| **Stage** | Any stage with a public artifact. Highest value immediately before a launch, and again a month after, when the listings that were promised have usually not happened |
| **Needs** | A product name, plus whichever of these exist: a repository, a published package name, a docs URL, an MCP server |
| **Skip if** | Nothing is public yet. A private beta has nowhere to be listed, and the run will correctly report a wall of `n/a` |
Run it against a competitor too. The gap between two presence matrices is the most concrete
argument for doing this work that exists.
## How to use
```
/agentrel:registry-presence infer the product from this repository
/agentrel:registry-presence acme check a product by name
/agentrel:registry-presence @acme/sdk check a published package
/agentrel:registry-presence https://acme.com check a product by site
```
Takes about a minute. Produces `registry-presence