HCS-26 Protocol Live
Publish Once.
Trust Forever.
The universal registry for agent skills.
Guaranteed by cryptographic proofs, not platform promises.
The universal registry for agent skills.
Guaranteed by cryptographic proofs, not platform promises.
Sign in with email or connect a wallet. You need credits to publish—your account ID becomes the on-chain owner.
The 4-step publish wizard walks you through identity, author info, license, documentation, tags, and category. Preview everything before publishing.
Tip: Use Markdown for your skill documentation. It renders directly on the skill detail page.
Get a credit quote based on current network fees, then publish. Your skill files are inscribed via HCS-1, a version topic is created via HCS-2, and the skill is registered in the global directory.
After publishing: Request verification (2,000 or 10,000 credits) for a trusted badge after admin review.
Ready to publish? Start the publish wizard
A tamper-proof pipeline from your terminal to the Hedera consensus layer.
Hashing skill package...
Traditional package registries rely on trust. HCS-26 relies on cryptographic proof.
Maintainers can force-push changes, overwrite versions, or unpublish packages entirely.
Compromised credentials allow attackers to inject malicious code into trusted versions.
Centralized registries can ban users, censor content, or go offline.
Once inscribed on Hedera, a version cannot be changed. History is append-only forever.
Only the original Hedera Account ID can sign new versions. No shared passwords to steal.
SHA-256 checksums allow any agent to independently verify code integrity before execution.
Defines the metadata schema, publishing rules, ownership verification, and discovery protocol.
Provides topic-based message ordering for immutable version histories and global discovery.
Handles content-addressed file inscription and SHA-256 integrity proofs on the consensus ledger.
Every guarantee is enforced by the protocol, not by promises from a platform.
Published skills are inscribed on Hedera consensus. Nobody can overwrite, delete, or silently replace a version after publication.
Every skill ships with a SHA-256 checksum. Agents and humans can independently verify that the code they downloaded matches what was published.
Only the Hedera account that created a skill can publish new versions. No shared credentials. No stolen maintainer accounts.
Publish your first immutable skill or browse verified skills from the community.