nomad

Route Nomad intents to deploy, status, job, obs, and destroy sub-skills.

29|8|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/hashimiche/hal --skill nomad-hashimiche
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nomad
Source: https://github.com/hashimiche/hal/tree/main/internal/skills/data/nomad
Command: npx skills add https://github.com/hashimiche/hal --skill nomad-hashimiche

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route Nomad intents to deploy, inspect, run jobs, and destroy the local Nomad lab within hal.

Core Features & Use Cases

  • Route Nomad requests to the deploy, status, job, obs, and destroy sub-skills to assemble a cohesive Nomad lab workflow.
  • Route observability-related Nomad actions to the obs sub-skill for consistent monitoring orchestration.

Quick Start

Route a Nomad deployment request to the deploy sub-skill and verify the lab state.

Frequently Asked Questions about nomad

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

FAQPage Schema
How do I route Nomad lifecycle commands for a local lab workflow?▼

To route Nomad lifecycle commands, you dispatch actions to sub-skills like deploy, status, job, and destroy, ensuring consistent lab outcomes through explicit routing and state validation.

How does command dispatch work for Nomad deployment and management requests?▼

Command dispatch for Nomad management routes requests to specific sub-skills for deploy, status, job, obs, and destroy, coordinating lifecycle actions and observability routing to maintain lab state.

Can I route observability actions separately when managing a Nomad lab?▼

Yes, you can route observability actions separately by directing Nomad observability requests to the obs sub-skill, enabling consistent monitoring orchestration across the lab workflow.

What is the best way to coordinate Nomad deploy and destroy actions in a lab environment?▼

The best way to coordinate Nomad deploy and destroy actions is using a routing skill that dispatches intents to the respective sub-skills, applying state validation to ensure cohesive lab workflow outcomes.

Does the Nomad routing skill require external dependencies to manage lab state?▼

No, the Nomad routing skill operates without external dependencies, relying on internal sub-skills for deploy, status, job, obs, and destroy actions to validate state and coordinate lab workflows.

Why do I need explicit routing for Nomad job and status commands?▼

You need explicit routing for Nomad job and status commands to ensure actions are dispatched to the correct sub-skills, enabling lifecycle coordination and state validation for consistent lab results.