styx

Parse and validate Styx configuration language and schemas for correct structure and typing.

66|5|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/bearcove/styx --skill styx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: styx
Source: https://github.com/bearcove/styx/tree/main/crates/styx-cli/contrib
Command: npx skills add https://github.com/bearcove/styx --skill styx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Styx enables teams to author, validate, and reason about configuration documents using a typed, human-friendly syntax and a schema language.

Core Features & Use Cases

  • Styx syntax for scalars, objects, sequences, tags, and heredocs
  • Inline schema language for defining document shapes and validations
  • CLI tooling for formatting, validating, and converting Styx documents
  • Real-world use: ensure configs are correct before deployment

Quick Start

Describe a Styx document and validate it against a schema using the Styx CLI.

Frequently Asked Questions about styx

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

FAQPage Schema
What is schema-driven validation for configuration files?

Schema-driven validation checks configuration documents against a defined typed schema, ensuring correct structure and typing before deployment. It catches syntax and structural errors early by validating scalars, objects, and sequences against predefined rules.

How do I validate a configuration document against a schema using the CLI?

You can validate a configuration document by running the Styx CLI tool against your file. The CLI parses the configuration language and applies the inline schema definitions to report any structural or typing errors found in the document.

How do I format and convert nested configuration schemas?

To format and convert configurations, use the CLI tooling provided for Styx documents. It parses complex nested schemas and sequences, allowing you to safely transform and standardize your configuration files with safe default handling.

Can I define inline schema validations for complex nested structures?

Yes, you can define document shapes and validations using the inline schema language. It supports complex nested schemas, allowing you to specify types for scalars, objects, sequences, tags, and heredocs within a single configuration document.

Does this configuration language support safe defaults and error reporting?

Yes, the configuration parser provides safe default handling and error reporting. When validating documents, it identifies incorrect structure and typing issues, ensuring configurations are safe and correctly formatted before deployment.

What is the best way to ensure configs are correct before deployment?

The best way to ensure configs are correct is to author them using a typed syntax and validate them against an inline schema. This approach verifies structure and typing, catching configuration errors before they reach deployment.