Use when a curated list or directory covers your area and you have one genuine reason to be on it.
resource-page-inclusion-request.md
You are asking a maintainer to add an entry to a curated list. They gain nothing by saying yes, so the case has to be about their page.
Page URL and what it lists: {{RESOURCE_PAGE}}
What is listed there now, with the descriptions: {{EXISTING_ENTRIES}}
What I want added, with its URL: {{MY_ENTRY}}
What it does that nothing on the list does: {{GAP_IT_FILLS}}
Maintainer name and role: {{MAINTAINER}}
Output:
1. A gap check: does {{GAP_IT_FILLS}} survive contact with {{EXISTING_ENTRIES}}, or is it already covered. Name the closest existing entry either way. If it is covered, say do not send.
2. The email to {{MAINTAINER}} under 90 words: the page named, the gap in one sentence, the entry and its URL, and a description matching the length and format of the entries in {{EXISTING_ENTRIES}}.
3. Up to two other things on {{RESOURCE_PAGE}} worth telling them about: a dead entry, a tool that has shut down, a thin category. Include these only where they are visible in what I supplied, and say so if none are.
Rules:
- Never mention links, SEO, authority or rankings.
- Do not suggest removing anyone.
- If {{MY_ENTRY}} is a product or pricing page rather than a resource, say so. Most lists reject those, and one rejection usually closes the page for good.
- No em dashes, no flattery about their excellent list.
Replace each placeholder with your own detail. The more specific you are, the less the model invents.
When should I ask for a listing rather than send broken link outreach?
When the list is working but incomplete and you can name something it does not cover. Where the page is full of dead links, the broken link prompt is the better approach. Ask once, because rejection on these pages tends to be permanent, so do not spend the ask on a weak entry.
What do I need from the list itself?
The page and every existing entry with its description, your entry and URL, the gap it fills, and the maintainer name. The descriptions matter because your email has to match their format and length. If what you want listed is a product or pricing page, the prompt tells you plainly.
What comes back, and which part decides it?
A gap check naming the closest existing entry either way, an email under 90 words with a description written in their format, and up to two other issues on the page. The description does the work, because a maintainer who has to rewrite it will move on to something else.
What spends the ask for nothing?
Flagging dead entries you have not loaded yourself. A false positive undoes exactly the goodwill the email was meant to create, and the prompt only raises issues visible in what you supplied. Suggesting a removal is worse, since it turns a small favour into an argument about somebody else.