bp-skill-validate

Validates workflow.yaml definitions for schema, graph, and type conformance.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/hiivmind/hiivmind-blueprint --skill bp-skill-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bp-skill-validate
Source: https://github.com/hiivmind/hiivmind-blueprint/tree/main/skills/_archived/bp-skill-validate
Command: npx skills add https://github.com/hiivmind/hiivmind-blueprint --skill bp-skill-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates workflow.yaml definitions to ensure they meet schema, graph, and type requirements, preventing runtime errors.

Core Features & Use Cases

  • Schema validation: checks required fields and value formats.
  • Graph validation: verifies reachability, cycles, and dead ends to ensure a path to an ending.
  • Type validation: validates preconditions and consequences against current catalogs and flags deprecated patterns.
  • Use case: auditing workflows during CI/CD or skill authoring to ensure safety before deployment.

Quick Start

Provide the path to a workflow.yaml to validate, or ask me to locate a suitable workflow and validate it.

Frequently Asked Questions about bp-skill-validate

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

FAQPage Schema
How do I validate a workflow.yaml file for errors and dead ends?

To validate a workflow.yaml file, provide its path to the validator, which checks schema, graph, and type conformance to report errors, warnings, and informational notes. This ensures path reachability and prevents runtime errors.

What is workflow graph validation and why do I need it for my YAML definitions?

Workflow graph validation verifies reachability, cycles, and dead ends in YAML definitions to ensure a path to an ending. You need it to audit Claude-powered skill workflows and prevent runtime errors during skill authoring or CI/CD deployment.

How do I debug node references and cycles in a workflow.yaml file?

Debug node references and cycles in a workflow.yaml file by running validation checks that verify path reachability, detect cycles, and identify dead ends. The validator reports errors and warnings for invalid transitions and deprecated patterns.

Can I use workflow validation to check preconditions and consequences against current catalogs?

Yes, you can use workflow validation to check preconditions and consequences against current catalogs. Type validation validates these elements and flags deprecated patterns to ensure your workflow definitions meet schema and type requirements.

Does workflow.yaml validation check for deprecated patterns and state references?

Workflow.yaml validation checks for deprecated patterns and state references as part of its schema, graph, and type conformance checks. It reports errors, warnings, and informational notes to ensure safety before deployment.

What is the best way to audit workflow.yaml safety before CI/CD deployment?

The best way to audit workflow.yaml safety before CI/CD deployment is to run validation checks for required fields, node references, path reachability, cycles, dead ends, and type conformance. This prevents runtime errors and ensures safe transitions.