the archive.

Search, filter and compare every signed capability. Open one to see what it contains, what it asks for and who published it.

Registry

Every listing is a real, signed package. What the labels mean.

Loading the live registry…

1 of 1 capability

Example .adcapsarja/example-adcap

A small, complete example of an .adcap capability: a skill, two tools and documentation. Install it to see how packages work.

skillstoolsexamplestartertutorialtemplate

v1.0.0 · Apache-2.0updated 2026-10-24freeVerifiedTrusted publisher

Reading the labels

Verified: The listed version is signed by an active key of its publisher, and the signature, the file hashes and the catalogue all check out. A version the registry published openly, without a signature, does not carry this label; its file and archive hashes are still checked on every install.
Trusted publisher: The registry maintainers have reviewed the publisher's identity. It is not an audit of the capability's code.
Experimental: The publisher marks the behaviour or interface as likely to change.
Incompatible: Shown for the platform you selected: the capability does not support it, so an install would be refused.
Deprecated: The registry has marked this capability as superseded or no longer maintained.

“Installed” is not shown here: only the CLI and the apps that embed Arcotheon know what is on your machine. They show it next to these labels.

§ 02The format

One manifest, its files, and a signature.

This is the real sarja/example-adcap@1.0.0, read from the registry when this page was built. The full specification.

capability.json / who it is
```
{
  "adcap": "1.0",
  "id": "sarja/example-adcap",
  "version": "1.0.0",
  "license": "Apache-2.0",
  "publisher": {
    "id": "sarja"
  },
  "compat": {
    "runtimes": {
      "node": ">=22"
    }
  }
}
```
01 — identity and compatibility
Publisher-namespaced id, a semantic version, licence, product tier and the platforms, hosts and runtimes it needs. A host refuses an install it cannot satisfy and says why.
capability.json / what it asks for
```
{}
```
02 — permissions
Nothing.

capability.json / skills, tools, workflows

{
  "skills": [
    {
      "path": "skills/example-adcap"
    }
  ],
  "tools": [
    {
      "name": "shout",
      "runtime": "node",
      "entry": "tools/shout.mjs",
      "permissions": []
    },
    {
      "name": "word_count",
      "runtime": "node",
      "entry": "tools/word-count.mjs",
      "permissions": []
    }
  ]
}

03 — what runs

Skills are standard Agent Skills folders. Tools are real programs; they run only when called, inside a sandbox. Workflows chain tool steps and hand judgement back to the agent.

capability.json / knowledge and resources
```
{
  "resources": []
}
```
04 — what stays remote
Large indexes are not in the package. They are fetched when a tool needs them, from an HTTPS source, and rejected unless the bytes match this SHA-256.
capability.json / files
```
{
  "files": [
    "… 7 entries …",
    {
      "path": "CHANGELOG.md",
      "sha256": "e4b640138dc3…39aec7",
      "size": 121
    }
  ]
}
```
05 — what pins everything
The build lists every file with its SHA-256 and size. The SHA-256 of this whole document, d38d16a52bce…004f43, is the package’s identity.

The archive · sarja-example-adcap-1.0.0.adcap · 61 KiB

A gzip-compressed tar: regular files only, sorted, timestamps zeroed, so the same source always builds the same bytes.

capability.json2.9 KiB

CHANGELOG.md121 B · e4b64013

README.md1.3 KiB · 532c9036

assets/

preview.png59 KiB · 0369b78e

docs/

structure.md1.3 KiB · fc52a1db

skills/example-adcap/

SKILL.md971 B · 35834e5f

tools/

shout.mjs564 B · 766013e3

word-count.mjs533 B · 15e95de1

SIGNATURE.json435 B

The chain of trust, with this package’s real values

1 Files → manifest
Every file is hashed and checked against files; the manifest’s SHA-256 is recomputed.
d38d16a52bce4b25c45c186e8a25313aaa8f09c03c85ba5db202fc6501004f43
2 Manifest → publisher signature
SIGNATURE.json is an Ed25519 signature over id, version and that digest, by key bc52 5ed0 a4a6 7e0f e276 e089 8049 7240 (active).
d38d16a52bce4b25c45c186e8a25313aaa8f09c03c85ba5db202fc6501004f43
3 Publisher key → signed catalogue
The key comes from the catalogue (sequence 12, signed 2026-10-24), which pins this package document:
a27216960e5e77044f8590e61ed929020d62d41dba950388bb4fb1c2157c78b7
4 Catalogue → pinned root key
The catalogue’s Ed25519 signature must verify under a root key the client already trusts:
a777b16554396ce49bd2485f68ccfee8da5323419c5ab9facdf60edb312bd49f

§ 03Install

Review, then allow.

Installing resolves dependencies, verifies the signature and every file hash, shows the permissions each package asks for, and only then unpacks. There are no install scripts. A tool runs when it is called, with the permissions you approved, in an operating-system sandbox.

The CLI is built from the Arcotheon repository for now; the getting-started guide walks through it.

What is and isn’t enforced

terminal · the CLI’s own prompt format

$ arcotheon install sarja/example-adcap + sarja/example-adcap@1.0.0     asks for no permissions New permissions requested: Approve? [y/N] y✓ installed sarja/example-adcap@1.0.0

§ 04Read on

Documentation

All documents