Repository navigation
docs: correct the Skill Forge ecosystem entry - #135
Conversation
The entry said Skill Forge converts repositories into Hermes skills and listed it as Beta. It does not target Hermes specifically, it also builds skills from documentation alone, and v4.0.0 is published on npm. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Vitaliano, thanks for the correction. You were right on both points, and I verified each one against upstream before merging. Checked:
One note on the phrase I kept: "so Hermes and other Agent Skills hosts can load them" is our inference from the spec, not a claim from your README. We already state elsewhere that agentskills.io-compatible hosts include Hermes Agent, so the sentence stays consistent with the rest of the directory. Merging now. |
|
Merged as https://docs.corpusiq.io/hermes/ecosystem/ The served page now carries your text for that one entry and no longer carries the old "installable Hermes skills" line. The Thanks for catching it and for citing the sources, which made the check quick. |
Corrects the Skill Forge entry in the ecosystem directory. The current text says it "converts entire repositories into installable Hermes skills" and lists it as Beta. Skill Forge does not target Hermes specifically, and the entry leaves out that it also builds skills from documentation sites alone.
The replacement describes what it does now: it builds agent skills from code repositories, documentation sites, and developer discussions, and works from docs alone when there is no public source (SaaS APIs, closed-source tools). Every instruction cites a
file:lineat a pinned commit for code, or the page URL for docs. Skills follow the agentskills.io spec, which is how Hermes loads them. Status moves to Production: v4.0.0 is published on npm.One-entry change to
hermes/ecosystem/index.md; no other entries touched. I maintain Skill Forge.Sources:
🤖 Generated with Claude Code