Olas registry

Skill Jinn-Network/shared-skills/skills/olas-registry

Register and manage OLAS protocol units (components, agents, services) with correct metadata hashing, IPFS publishing, and on-chain verification. Sanitized for public use.From its SKILL.md

Install

npx -y skills add Jinn-Network/shared-skills --skill olas-registry

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, 458 tokens by cl100k_base, as published. Nobody here has run it

OLAS Registry Management

Public workflow for registering components, agents, and services on OLAS-compatible registries.

Critical Hashing Rule

On-chain metadata hashes typically expect the raw digest from the IPFS multihash payload, not an arbitrary alternate hash.

Correct pattern

Upload metadata JSON to IPFS
Decode CID/multihash payload
Extract expected digest bytes
Submit digest as bytes32 where required

Incorrect pattern

Do not hash the ipfs://... string itself and submit that as metadata hash.

Metadata Schema Baseline

Use stable fields that clients/indexers can rely on:

name
description
code_uri
image
attributes (including version)

Keep custom fields optional and additive.

Registration Flow

Components / Agents

Build metadata
Upload to IPFS
Convert metadata CID to on-chain hash format
Call registry manager create function
Parse minted ID from transfer logs/events

Services

Build service config metadata
Upload to IPFS
Submit service creation using correct manager/token utility contracts
Verify resulting tokenURI resolves metadata

Verification

For each minted unit:

retrieve tokenURI(unitId)
fetch JSON payload
verify required fields and version value
confirm marketplace/indexer visibility

Common Failure Modes

Create-event parser mismatch: parse transfer log fallback
Zero-value bonds: create call reverts
Threshold mismatch: multisig threshold outside accepted range
Wrong token sentinel: create call rejects configuration
Ownership mismatch on updates: hash updates must be called by unit owner context

Public Documentation Rules

Do not include personal machine paths
Do not include private key handling details
Do not publish internal wallet ownership mapping unless explicitly intended
Prefer placeholders for chain-specific addresses in generic templates

Minimal Command Pattern

# compile
yarn compile

# register units
yarn <register-command> --dry-run

# verify
yarn <verify-command>

Keep command names aligned with local project scripts while preserving this sequence.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.