AgentSkills.site

About

A practical reference for agent skills, built from primary sources rather than paraphrased search results.

Published

AgentSkills.site editorial

What this is

AgentSkills.site is an independent reference site about agent skills — the SKILL.md-based system, standardized at agentskills.io, that lets AI agents load specialized capabilities on demand. We publish focused, verified guides organized around specific agent ecosystems, starting with a full cluster on Hermes Agent, the open-source agent built by Nous Research.

We are not affiliated with Nous Research, Anthropic, or any agent vendor we write about. We don't sell a product related to any of these tools.

Why this exists

Search results for emerging technical topics like this fill quickly with content that either lightly rewrites the official documentation, or ranks things ("best skills," "top tools") without saying what the ranking is actually based on. Neither is that useful if you're trying to get something working. We wrote each page in this cluster only after checking what already ranks and identifying a clear reason for the page to exist beyond paraphrasing that. Sometimes that reason is missing information — a mechanic nobody explained, a fact scattered across multiple docs pages that nobody had assembled in one place. Just as often it's substantially better synthesis, organization, verification against primary sources, or a more usable structure than what's already out there — the individual facts don't have to be novel for the page to be worth publishing, as long as putting them together this way is. The research notes behind this cluster are the basis for what got published; pages that didn't clear that bar didn't get written.

Editorial methodology

Primary sources first. For factual and technical claims — commands, file paths, configuration keys, system behavior — we go to the official documentation and the official GitHub repository directly, not to secondary writeups. Where we cite a command or path, we cross-checked it against the documented source and, where practical, against the actual source code in the repository (not just the marketing docs site).

Community sources are cited as what they are. When we reference a community repository, a third-party tool, or a claim made by an unofficial source, we attribute it as such — we don't launder a repo's own marketing claim ("70+ verified skills") into a fact we assert independently.

No fabricated testing. We do not claim to have run software, installed skills, or benchmarked anything unless we actually did. Where a page discusses expected behavior based on documentation rather than direct testing, it says so.

Official facts vs. our interpretation. Where we're explaining documented behavior, we say what's documented. Where we're offering a recommendation, a category judgment, or a "here's what we'd check" — that's clearly framed as editorial judgment, not as a vendor's stated fact.

No fake precision. If public evidence doesn't support a ranking or a specific number, we say that directly instead of presenting a guess as data. This is why our "best skills" coverage uses stated criteria and categories rather than a numbered list.

Corrections and updates

Software documentation changes, and so does the skills ecosystem this site covers. When we're made aware of something that's gone stale or turns out to be wrong, we update the affected page and its "Updated" date. We don't quietly rewrite history — if a page's core claims change materially, that's a new "Updated" date, not a silent edit.

This site does not use invented author personas or fabricated credentials. Pages are published under editorial ownership of AgentSkills.site as a whole, not an individual byline, because that's an accurate description of how they're produced.

What's next

The architecture here is built to extend to other agent ecosystems — Claude Code, Codex, OpenClaw, Cursor, and others — as separate, equally researched clusters, without restructuring what already exists. We'd rather ship one excellent cluster than five thin ones, so new clusters go up when they clear the same bar this one did, not on a schedule.