mcpbeat

Configuring Block Policy

matlab/configuring-block-policy

Guide users through creating and managing .satk/block-policy.json for controlling which blocks the agent can use, which are excluded, and which block parameters the agent should not modify. Use when setting up block usage policy for a project.

1k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
900
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/matlab/simulink-agentic-toolkit --skill configuring-block-policy

The instruction itself

10 sections, as written by the author

Configuring Block Policy

Create or update .satk/block-policy.json — the file that controls which blocks (library or built-in) the agent can use, which are excluded, and which block parameters the agent should not modify.

When to Use

  • User asks to set up, create, or configure block policy
  • User asks to restrict or exclude blocks
  • User wants to prevent the agent from modifying certain block parameters
  • building-simulink-models routes here via the policy gate

When NOT to Use

  • Actively building a model → building-simulink-models
  • Improving block descriptions or categories → curating-library-kg
  • Declaring which libraries exist → Library Setup gate in building-simulink-models

Prerequisites

  • .satk/reuse-libraries.json must exist.

Workflow

  • Check state — Does .satk/block-policy.json exist? If yes, load and summarize. If no, start fresh.
  • Policy mode — (skip if no libraries specified) Ask: prefer libraries with built-in fallback, or custom libraries blocks only (no fallback)?
  • Excluded blocks (optional) — Are there any blocks (library or built-in) that should never be placed in your models? Collect referenceBlock + reason.
  • Off-limits parameters (optional) — Are there any block parameters you don't want the agent to modify? Collect referenceBlock + protectedParams[].
  • Save — Validate and write with library.BlockPolicy.save().

API

policyData = struct();
policyData.policyMode = 'approved_blocks_only';
policyData.fallbackToBuiltins = false;
% Excluded — agent will never place these blocks
policyData.blockedBlocks = struct('referenceBlock', 'LegacyLib/OldCtrl', 'reason', 'Superseded');
% Protected params — agent won't modify these values
policyData.blockRules = struct('referenceBlock', 'Lib/SpeedCtrl', ...
    'protectedParams', {{'Kp', 'Ki', 'Kd'}});

library.BlockPolicy.save(projectRoot, policyData);

For defaults (no restrictions):

policyData = library.BlockPolicy.defaults();
library.BlockPolicy.save(projectRoot, policyData);

Schema

{
  "schemaVersion": 1,
  "policyMode": "approved_blocks_only | prefer_customer_libraries",
  "fallbackToBuiltins": false,
  "blockedBlocks": [
    { "referenceBlock": "LegacyLib/OldController", "reason": "Superseded" }
  ],
  "blockRules": [
    { "referenceBlock": "Lib/SpeedController", "protectedParams": ["Kp", "Ki", "Kd", "SampleTime"] }
  ]
}

Validation Rules

  • policyMode: must be prefer_customer_libraries or approved_blocks_only
  • approved_blocks_only + fallbackToBuiltins: true → rejected (contradictory)
  • protectedParams must be a non-empty array of strings
  • Malformed policy → error (never silently ignored)

Updating an Existing Policy

When .satk/block-policy.json already exists:

  • Load with library.BlockPolicy.loadRaw(projectRoot, libConfig)
  • Summarize current state — do NOT re-run the full wizard
  • Ask what to change, apply to existing struct, save

Common updates: exclude a block, mark params as off-limits, change mode, remove an entry.

Guardrails

  • Never write block-policy.json without user confirmation
  • Always validate before saving (library.BlockPolicy.validate(policyData))
  • If user provides a block name without the full library path, look it up in the KG to resolve the referenceBlock

----

Copyright 2026 The MathWorks, Inc.

----

How to use it

Copy the folder

Take matlab/configuring-block-policy from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.