device-schema-extraction
Skill9 starsChanged 5 months agoMITView on GitHub
How to extract, complete and validate Ableton Live native device JSON schemas for the ableton-mind knowledge base.
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill when populating src/knowledge/devices, indexing packs or changing scripts/extract-device-schemas.mjs.
- Distinctive: line 13
Default.adv parsing for saved default state.
- Distinctive: line 24
Run recipe and tool checks that depend on the schema.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Device Schema Extraction
Use this skill when populating src/knowledge/devices, indexing packs or changing scripts/extract-device-schemas.mjs.
Sources
- Bridge introspection of device.parameters for name, min, max, default and automation flags.
- Default.adv parsing for saved default state.
- Ableton manuals and LOM docs for behavior notes.
- Manual curation for units, nonlinear curves, macro targets and useful descriptions.
Workflow
- Extract or introspect raw parameters.
- Normalize slug, id, category, vendor and Live version metadata.
- Fill min, max, default, unit, automatable, modulatable and concise description.
- Mark source and completeness.
- Validate uniqueness of ids, names and indexes.
- Run recipe and tool checks that depend on the schema.
Quality Rules
Descriptions must be short, English and useful to an LLM. Do not invent ranges. Use unit=curve for nonlinear 0..1 controls and explain audible behavior. Keep runtime-discoverable facts out of static knowledge unless they are slow-changing and useful.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ableton-mind-buildSkill
- ableton-remote-scriptSkill
- cross-boundary-qaSkill
- device-schema-extractionSkill
- mcp-distributionSkill
- mcp-server-developmentSkill
- recipe-authoringSkill
- ableton-mind-buildSkill
- ableton-mind-quality-auditSkill
- ableton-remote-scriptSkill
- command-surface-auditSkill
- cross-boundary-qaSkill
- local-copilotSkill
- mcp-distributionSkill
- mcp-server-developmentSkill
- recipe-authoringSkill
- refactor-maintainabilitySkill
- runtime-release-auditSkill
- security-auditSkill
- test-coverage-expansionSkill
- usability-flow-auditSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.