Setup Custom Libraries

Register or update custom Simulink block libraries so the agent prefers them over built-in blocks during model building.

When to Use

• User asks to set up, register, add, or configure custom libraries
• User wants to add new .slx files to an existing library configuration
• User says "setup custom libraries", "add my library", "configure libraries", "add a new library file"
• building-simulink-models routes here via the policy gate (gatePass: false)
• Never invoke when found: false, that means no custom libraries are configured and the user hasn't asked for them

When NOT to Use

• User wants to create a custom library from scratch (author new blocks, build a new .slx library file) → use building-simulink-models skill with model_edit directly. This skill only registers existing libraries; it cannot create library content.
• Only configuring block exclusions or parameter protection (libraries already declared) → configuring-block-policy
• Only curating block descriptions/categories (libraries already declared) → simulink-curating-library-kg

Workflow

Do this FIRST and ALONE, no other tool calls in the same message.

Call library.settingsLookup(), returns a struct with resolved absolute paths:

• found, whether a libraries file was located (satk-libraries.json or legacy reuse-libraries.json)
• enabled, whether custom libraries are configured
• gatePass, whether the gate is satisfied
• dataRoot, absolute path to the directory containing .satk/
• kgIndexPath, librariesPath, policyPath, absolute paths to data files

Interpret the result: