instrument-maker

Automates cloud-native app delivery with GitOps and progressive deployment strategies.

1|Updated May 9, 2026

Search Tags:#workflow #versioning #documentation #validation #migration #instrument-design

Ready to run

npx skills add https://github.com/tonykoop/claude-skills --skill instrument-maker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: instrument-maker
Source: https://github.com/tonykoop/claude-skills/tree/main/plugins/maker/skills/instrument-maker
Command: npx skills add https://github.com/tonykoop/claude-skills --skill instrument-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Instrument development workflows are often scattered across separate documents and scripts, making migration and governance challenging. This partial-skill entry provides a coherent path to design, document, validate, and ship musical instruments within a staged migration to the canonical instrument-maker.

Core Features & Use Cases

Incremental migration: additive references, tests, and templates designed to merge smoothly into the full skill.
Validator tooling: included scripts for acoustic-law and visual-authority checks that guard quality.
Developer guidance: references and examples to accelerate repo-first packets and readiness templates.

Quick Start

Copy the references and scripts from this partial-skill into your instrument-maker installation to begin validating acoustic rules and visual-authority checks.

Frequently Asked Questions about instrument-maker

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

FAQPage Schema

How do I automate end-to-end instrument development workflows including design and validation?▼

Automating end-to-end instrument development workflows is achieved by consolidating design, documentation, validation, and deployment steps into a single process. This approach handles references, validators, tests, and example packets across migration scenarios.

What is the best way to manage versioning and governance constraints during instrument migration?▼

Managing versioning and governance constraints during instrument migration requires aligning development with versioning metadata, manifest requirements, and repository structure. This ensures that migration scenarios from v4 stubs to canonical installs satisfy necessary governance checks.

How do I validate acoustic rules and visual-authority checks for instrument design?▼

Validating acoustic rules and visual-authority checks for instrument design utilizes included validator scripts. These tools guard quality by applying specific acoustic-law and visual-authority validations directly within your instrument-maker installation.

Can I use this instrument design workflow for incremental migration from v4 stubs to canonical installs?▼

Using this workflow for incremental migration from v4 stubs to canonical installs is fully supported. It provides additive references, tests, and templates designed to merge smoothly into the full skill without disrupting existing repository structures.

What documentation and manifest requirements are needed to ship musical instruments?▼

Documentation and manifest requirements needed to ship musical instruments involve aligning with versioning metadata and repository structure constraints. The workflow consolidates necessary documentation, validators, and example packets to ensure readiness templates are complete.

Why does instrument development become challenging when scattered across separate documents and scripts?▼

Instrument development becomes challenging when scattered across separate documents and scripts because migration and governance alignment is lost. Consolidating design, documentation, validation, and deployment steps into a coherent path resolves this fragmentation.