skills.rest
theslashdojo
theslashdojoOFFICIAL
Explore all skills by this author →
GitHub

local

Validate Dojo node read-side registry routes and emit JSON endpoint statuses.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Prevents publishing regressions by verifying that a changed Dojo node is discoverable and that read-side routes are healthy before a live registry publish.

Core Features & Use Cases

  • Checks core read-side endpoints: search, tree, skills, learn, and bundle for a specific node.
  • Emits a machine-readable JSON checklist so CI or release tooling can gate on route health.
  • Use cases include local developer rehearsals, staging smoke tests, and pre-publish validation to catch knowledge or discovery regressions.

Quick Start

Run the rehearsal script with the manifest path, node URI, ecosystem, and optional registry URL to produce a JSON checklist of route health.

Frequently Asked Questions about local

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

FAQPage Schema
How do I smoke-test registry endpoints before publishing a node manifest?▼

Smoke-test registry endpoints by running a rehearsal script that validates search, tree, skills, learn, and bundle routes, returning a JSON checklist of HTTP statuses. This verifies node discoverability and route health before a live registry publish.

What read-side routes should I check to prevent discovery regressions?▼

Check the core read-side routes: search, tree, skills, learn, and bundle endpoints for the specific node. Validating these routes detects discovery and bundle regressions before pushing a live release.

Do I need curl and Node to run pre-publish validation for staging rehearsals?▼

Yes, pre-publish validation requires a Bash-compatible environment with curl and Node available to execute the rehearsal script and exercise the registry endpoints for staging or local node manifests.

Can I gate CI releases on registry health check results?▼

Yes, you can gate CI releases by parsing the machine-readable JSON checklist of endpoint HTTP statuses emitted by the rehearsal script. Release tooling can automatically block publishes when route health validation fails.

What's the best way to validate a Dojo node manifest locally before publishing?▼

Validate a Dojo node manifest locally by running the rehearsal script with the manifest path, node URI, ecosystem, and optional registry URL. It exercises read-side endpoints to produce a JSON checklist confirming route health.

Related Skills

Explore More Software Engineering Skills→
theslashdojotheslashdojo

registry

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

Official
Intermediate
mvillmowmvillmow
18

gh-check-ci-status

Check GitHub pull request CI status and retrieve failure logs.

Community
Basic
zxpmailzxpmail
18

release-builder

Automate build, test, and publish lifecycle for web, desktop, and CLI applications.

Community
Advanced
brainbrewlabsbrainbrewlabs
7

performance-analysis

Analyze application performance metrics and flag regressions against baseline thresholds.

Official
Intermediate