Skip to content
Skills

Teach agents once. Ship it like software.

Package what an agent should know as a skill: versioned, signed and scanned before use.

A rugged case with the Hexel Studio mark on a table in a sealed concrete room
Skill2.3.1

Invoice matching

  • SignedEd25519
  • ScannedClean
  • Pinned to its hash
Published from CI

Know-how you can trust.

Every version fixed, signed and checked before an agent reads it.

  • Versions that never change.

    Each version is immutable. Tags and ranges pin to an exact hash.

  • Signed at the source.

    Signed with Ed25519, published from CI with OIDC.

  • Scanned before use.

    For secrets, malware and prompt injection. Anything suspect is quarantined.

The details.

  • Plain packagesInstructions and files in the SKILL.md format.
  • Semantic versionsTags and version ranges, each pinned to sha256.
  • Publish from CIYour pipeline signs in with OIDC.
  • QuarantineA suspect skill is held back from every agent.
  • Any bucketStore skills wherever you keep files.

Where Skills sits.

One stack, from the agent to the ground it runs on.

Runs where you run.

From the public cloud to networks sealed from the world.

  • Signed with Ed25519
  • Scanned before use
  • Quarantine
  • Pinned by hash

Questions.

What is a skill?

A package in the SKILL.md format that teaches an agent how to do something.

Can a skill change after it ships?

No. Versions are immutable, and tags and version ranges resolve to a pinned sha256 hash.

How is a skill checked?

It is signed with Ed25519 and scanned for secrets, malware and prompt injection. Anything suspect is quarantined.

Where are skills stored?

In any bucket you choose, published from CI with OIDC.

An engineer replies in a dayTalk to us Docs, SDK and APIStart building