Identify what is actually missing
A skill supplies reusable procedural knowledge. A plugin extends Hermes through code, including tools or hooks. An MCP connection makes a server's capabilities available through a standard interface. A workflow can use all three, but they are not interchangeable: instructions describing a mailbox do not grant mailbox access.
Start with the desired operation. If Hermes already has the necessary tools but repeats a complicated procedure badly, a skill may be the useful addition. If a service exposes an appropriate MCP server, evaluate that connection. A custom plugin becomes relevant when you need behavior or an integration that existing capabilities cannot supply.
Evaluate the complete dependency chain
For each candidate, write down its source, installation scope, required executable or service, credentials, permitted actions and update owner. Then choose a small read-only operation that demonstrates the connection. For a document service, listing a known folder and opening one accessible document is more informative than a successful installation notice.
Keep the procedure portable by explaining inputs and expected outputs separately from account-specific settings. Do not put tokens in a shared skill. When documenting a workflow, name the underlying capability as well as the extension: readers need to know whether a different supported connection can accomplish the same task.
Scope and limits
These distinctions follow the current official extension guides. Availability still depends on the installed Hermes version, active profile and extension configuration. A catalog listing is a discovery lead rather than proof of compatibility, access or quality. This page does not endorse a third-party server or imply that any extension has been executed by this library.
Primary sources
Spotted something wrong or out of date? Tell us on X at @HermesWatcher (opens in a new tab) and we will fix it.
New Hermes Agent updates every day on X. Follow @HermesWatcher