registry

Publish a versioned Dojo manifest to a registry via HTTP POST.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/theslashdojo/dojo --skill registry-theslashdojo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: registry
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/dojo/publish/registry
Command: npx skills add https://github.com/theslashdojo/dojo --skill registry-theslashdojo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, curl, bash, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the final, authenticated publish step by sending a versioned Dojo manifest to a registry so maintainers can reliably perform the release POST without manually crafting requests or parsing raw responses.

Core Features & Use Cases

  • Authenticated publish: POST a manifest to the registry's /v1/skills endpoint using a bearer token for secure release.
  • Dry-run support: Preview the resulting normalized JSON without performing the live write to verify the payload and metadata.
  • Automation-friendly output: Emits stable JSON containing published status, uri, and version so CI/CD and callers can programmatically confirm success.

Quick Start

Run the publish-registry script with the manifest path and optional registry URL to preview or perform an authenticated publish.

Frequently Asked Questions about registry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a Dojo manifest to an authenticated registry endpoint?

Publish a Dojo manifest by sending an HTTP POST to the /v1/skills registry endpoint using a bearer token. This automates the final release write step without manually crafting curl requests or parsing raw responses.

Can I preview the JSON payload before performing an authenticated registry publish?

Yes, you can preview the normalized JSON payload using the dry-run support feature. This allows you to verify the manifest payload and metadata without performing a live write to the registry endpoint.

Do I need curl and node installed to post a versioned manifest to a registry?

Yes, you need curl and node installed to perform the registry publish. Curl handles the HTTP POST request while node processes the JSON normalization for the versioned manifest payload.

What's the best way to automate a Dojo release workflow in CI/CD?

Automate Dojo release workflows by running the publish script with a manifest path and bearer token. It emits stable JSON containing published status, uri, and version so CI/CD pipelines can programmatically confirm success.

How does bearer token authentication work for Dojo manifest publishing?

Bearer token authentication requires providing your credential in the DOJO_TOKEN environment variable. The publish script includes this token in the HTTP POST request header to securely authorize the manifest write to the registry.

What should I do if my manifest publish to the Dojo registry is not working?

If the manifest publish is not working, verify the DOJO_TOKEN environment variable is set correctly and the manifest file path is valid. Use the dry-run option to inspect the normalized JSON payload and confirm metadata before attempting the live POST.