beatlab-contract

Validate or generate 16-step BeatLab JSON for pianoSequence and drumSequence.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/ryok/claude-beatlab --skill beatlab-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beatlab-contract
Source: https://github.com/ryok/claude-beatlab/tree/main/.claude/skills/beatlab-contract
Command: npx skills add https://github.com/ryok/claude-beatlab --skill beatlab-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BeatLab JSON contract standardizes 16-step beat data, ensuring consistent pianoSequence and drumSequence definitions for reliable generation and editing.

Core Features & Use Cases

  • Fixed schema: pianoSequence and drumSequence mappings with steps 0-15.
  • Output validation: Ensures JSON data conforms to the 16-step contract for reliable downstream processing.
  • Use Case: Create a beat payload with a simple repeating motif that aligns piano notes with drum hits across 16 steps.

Quick Start

Provide a JSON payload that adheres to this contract to create or validate BeatLab beat data.

Frequently Asked Questions about beatlab-contract

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

FAQPage Schema
How do I validate a JSON payload for a 16-step beat sequence?

To validate a 16-step beat sequence, the JSON payload must contain fixed keys for pianoSequence and drumSequence, mapping allowed note and drum hits across steps 0-15 to ensure reliable downstream processing.

What is the required JSON schema for a 16-step BeatLab pattern?

The required JSON schema for a 16-step BeatLab pattern uses fixed pianoSequence and drumSequence keys, mapping allowed notes and drum hits to specific steps from 0 to 15 for reliable beat generation.

How do I generate a JSON beat payload with aligned piano and drum steps?

Generate a JSON beat payload by defining pianoSequence and drumSequence mappings with allowed keys, aligning piano notes with drum hits across 16 steps to create a repeating motif.

Can I use this contract to validate 16-step musical patterns outside of BeatLab?

This contract applies to any workflow involving 16-step musical patterns where JSON payloads must be validated or generated, ensuring fixed keys and allowed notes conform to the standard schema.

Does the beat JSON contract enforce a strict output format?

Yes, the beat JSON contract enforces a JSON-only output when a beat payload is requested, strictly validating fixed pianoSequence and drumSequence keys to prevent schema violations.