People write to directory sites with two opposite assumptions. One is that every paragraph was written by an editor who tried the product. The other is that the whole site is an unmarked copy of somebody else's README. Neither is true here. This guide separates the layers so you know what to trust, what to verify, and what to email us about.
Listings
Skill rows point at a public source URL and usually at a canonical name such as a publisher slash a skill name. The short description, the install prompt, the download count, the star count, and the score arrived with that listing or with a later refresh of it. Plugin rows point at a GitHub repository. The star count and the README summary are about that repository. Model rows carry a name, a company, a license, a context window, and the other structured fields we could store. The long text under "About this model" is often a model card or a vendor blurb. We did not run the benchmark chart unless the page says we did, and today it does not.
Those pages exist so you can find the upstream project. They are aggregated. The terms say the copyright stays with the author. If you are the author and you want a listing removed or a link corrected, use the contact form and include the page URL and the source URL you want us to use instead.
What we write
Guides, including this one, are written for AI Agent Hub. Category introductions at the top of a filtered list are written for AI Agent Hub. Editor's notes, labeled as such under the publisher description, are written for AI Agent Hub. They are allowed to say "skip this" or "use this when." They are not allowed to pretend we are the publisher.
A listing with no editor's note has not been individually reviewed. That is most of the directory, on purpose. Reviewing every card with a template that swaps in the name would produce thousands of pages that look original and say nothing. We would rather leave the card as a card. Crawlers are asked to spend their time on guides, category pages, blog posts long enough to be an article, and the listings that have a real note. You can still open every card. The site does not hide it from you.
The blog
The blog is a separate collection of engineering articles: language models, Python, Linux, frameworks, and notes that predate this directory. Posts are ordered by date. A post can be long and still be outdated. Check the date. If a command in a post no longer works, tell us. Short stubs are kept out of the sitemap so a thin page is not presented as an article.
What updates, and what does not
We do not push install prompts into your agent, and we do not update a plugin you already cloned. When a listing's upstream date changes, the card can change on the next refresh. Your local copy will not. Re-read the prompt before you replace a skill you depend on. The install guide is the procedure.
Prices, context windows, and "latest" model aliases go stale first. The comparison tool reads whatever is in the database today. If you are putting a price in a document that other people will rely on, click through to the vendor. Deciding after a comparison tells you to do that anyway.
How to ask for a correction
Send one message per issue. Include:
- The page URL on this site.
- The sentence that is wrong.
- The URL that shows the right fact, if you have one.
- Whether you want a correction or a removal.
Do not send your API key, a password, or a private chat export as evidence. A sentence and a link are enough. We store the message so we can reply, which the privacy policy describes. A human reads the contact table. There is no chatbot on that form.
Takedown requests from a copyright holder should say you are the holder or their agent and should identify the work. We will remove a listing that we cannot justify keeping. We will not remove a guide because it says a category of tools is easy to misuse.
What we will not pretend
We will not add a badge that says every top-sorted skill was tested. We will not generate a unique-looking review for every row in order to look larger to a crawler. The about page is the short version of that policy, and how ranking works is the version about numbers. If a page on this site ever reads like a mad-lib with the product name filled in, that page is a bug. Send it to us.
What a correction changes, and what it does not
Fixing a star count, a broken source link, or a license field updates the card. It does not install or uninstall anything on your machine. If you already pasted a prompt, you still have the old prompt. Re-read the card after we change it, and follow the install guide if you intend to replace the text you saved.
Removing a listing removes our page. It does not remove the upstream repository. People who cloned the plugin still have the clone. People who saved the skill prompt still have the prompt. Say so if you are the publisher asking for a takedown, so your users are not surprised that their editor still contains the text.
A correction to a guide is different. Guides are our text. If a step is wrong, we should change the guide, not add a footnote that blames the directory data. Tell us which heading and what you did. "The uninstall section assumes a settings screen my agent does not have" is a useful report. "Your site is biased" without a sentence we can fix is not something we can edit.
We also will not turn a correction into a backlink arrangement or a paid placement. Pay Skill is a category of listings about payments, not a way to buy a higher score. Ranking stays mechanical, as how ranking works describes. If someone tells you they can sell you the top slot on this site, they are not us. The contact form is the only intake we read. If you are unsure whether a sentence is ours or the publisher's, look for the editor's note heading or the guide layout. Everything above that heading on a listing is the aggregated layer. Quoting it as "AI Agent Hub says" misstates the page. Quote the guide or the note if you are quoting us, and quote the upstream URL if you are quoting the product. That distinction is the whole reason this guide exists, and it is the distinction a correction should preserve rather than blur. When you quote us, link the guide. When you quote a product, link the publisher. Mixing the two is how a directory sentence becomes someone else's warranty, which our terms refuse to be. If a sentence has no editor's note heading above it and it sits on a listing, attribute it to the publisher. That one habit prevents most of the corrections we should not have to make.