[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MMYYYC0BDP629EGN1Z8KF4":3,"skill-same:01M6MMYYYC0BDP629EGN1Z8KF4":91},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6MMYYYC0BDP629EGN1Z8KF4","simulink-interactions",null,"Interact with a Simulink model currently open in MATLAB via the MATLAB MCP server. Use this skill whenever the user asks to inspect, modify, query, or navigate a Simulink model that is open in MATLAB — for example changing block properties, finding blocks, adding blocks, connecting signals, or navigating model hierarchy. Trigger whenever the user refers to \"this model\", \"this block\", \"this subsystem\", \"selected blocks\", or asks to do anything to a Simulink model without specifying a file path to open. Also trigger for requests like \"change the gain\", \"color all sum blocks\", \"find all integrators\", or any other operation on an already-open model.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsummer521521\u002FMATLAB_Simulink_plugin\u002Fskills\u002Fsimulink-interactions\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"simulink interactions","matlab","navigate","hierarchy","for","path","inspect","sum","model hierarchy","color","MCP","signals","query","do","example","model","open","server","change","mcp server","2026-11-10 10:12:30",false,"---\nname: simulink-interactions\ndescription: Interact with a Simulink model currently open in MATLAB via the MATLAB MCP server. Use this skill whenever the user asks to inspect, modify, query, or navigate a Simulink model that is open in MATLAB — for example changing block properties, finding blocks, adding blocks, connecting signals, or navigating model hierarchy. Trigger whenever the user refers to \"this model\", \"this block\", \"this subsystem\", \"selected blocks\", or asks to do anything to a Simulink model without specifying a file path to open. Also trigger for requests like \"change the gain\", \"color all sum blocks\", \"find all integrators\", or any other operation on an already-open model.\n---\n\n# Simulink Open Model Interaction\n\nThis skill defines conventions for interacting with the Simulink model currently open in MATLAB, using `mcp__matlab__evaluate_matlab_code` as the primary tool.\n\n## Tooling Fallback\n\nIf the MATLAB MCP tool is unavailable in the current session but the user explicitly asks for real model creation or modification, fall back to local MATLAB execution such as `matlab -batch`. State the fallback briefly and keep the workflow identical: inspect, modify, verify, save.\n\n## Step 1: Resolve References\n\nBefore doing anything, determine what model\u002Fsystem\u002Fblock(s) the user is referring to.\n\n| User says | Resolution |\n|---|---|\n| \"this model\" | `bdroot(gcs)` |\n| \"this system\" \u002F \"this subsystem\" | `gcs` |\n| \"this block\" | `gcb` |\n| \"selected blocks\" (plural) | see snippet below |\n| \"all [Type] blocks in this subsystem\" | see snippet below |\n| \"all [Type] blocks in the model\" | see snippet below |\n\n### Selected blocks (plural)\n\n```matlab\nopts = Simulink.FindOptions;\nopts.SearchDepth = 1;\nblks = getfullname(Simulink.findBlocks(gcs, 'Selected', 'on', opts));\n```\n\n### All blocks of a specific type in the current subsystem\n\n```matlab\nopts = Simulink.FindOptions;\nopts.SearchDepth = 1;\nBlockType = 'Gain'; % replace with actual type\nblks = getfullname(Simulink.findBlocksOfType(gcs, BlockType, opts));\n```\n\n### All blocks of a specific type in the entire model\n\n```matlab\nBlockType = 'Gain'; % replace with actual type\nblks = getfullname(Simulink.findBlocksOfType(bdroot, BlockType));\n```\n\n## Step 2: Inspect Before Modifying\n\nUse `get_param` to read current state before making changes. This helps you confirm you have the right block and understand its current configuration.\n\n```matlab\nget_param(gcb, 'Gain')           % read a specific parameter\nget_param(gcb,'DialogParameters')  % list all dialog parameters\nget_param(gcb, 'ObjectParameters') % list all available parameters\n```\n\n## Step 3: Apply Changes\n\nUse `set_param` for most property changes:\n\n```matlab\nset_param(gcb, 'Gain', '2')\nset_param(gcb, 'BackgroundColor', 'red')\n```\n\nFor bulk operations on multiple blocks, iterate over the `blks` cell array:\n\n```matlab\nfor i = 1:numel(blks)\n    set_param(blks{i}, 'BackgroundColor', 'yellow');\nend\n```\n\n## Adding Blocks\n\nWhen adding blocks, follow these rules:\n\n- **Never** pass a `'Position'` argument to `add_block`\n- **Never** use `set_param(blk, 'Position', ...)` or `set_param(blk, 'Location', ...)`\n- **Never** use `Simulink.BlockDiagram.arrangeSystem`\n- Use `getBlockPosition` and `setBlockDimensions` (bundled in `utils\u002F`) for all positioning\n- To read block size, use `getBlockDimensions`; to resize, use `setBlockDimensions`\n- Add blocks **one at a time**: add a block, connect it, then position it relative to existing blocks before proceeding to the next\n\nUtility signatures (see `utils\u002F` for full source):\n```matlab\n[x, y]          = getBlockPosition(block)          % top-left corner\n[width, height] = getBlockDimensions(block)         % block size\nsetBlockPosition(block, x, y)                      % move, preserving size\nsetBlockDimensions(block, width, height)            % resize, preserving top-left\n```\n\n**Never use `set_param(block, 'Position', ...)`** — always use `setBlockPosition` and\u002For `setBlockDimensions` instead.\n\n```matlab\n% Example: add a Gain block to the right of the current block\nmodelName = bdroot(gcs);\nrefBlk = gcb;\n\n% 1. Get reference block geometry\n[refX, refY] = getBlockPosition(refBlk);\n[refW, ~]    = getBlockDimensions(refBlk);\n\n% 2. Add block (no position argument)\nnewBlk = [modelName '\u002FMyGain'];\nadd_block('built-in\u002FGain', newBlk);\n\n% 3. Position it to the right of the reference block\ngap = 50;\nsetBlockPosition(newBlk, refX + refW + gap, refY);\n\n% 4. Connect it\nSimulink.connectBlocks(Source,Destination);\n```\n\n## Programmatic MATLAB Function Blocks\n\nWhen editing a MATLAB Function block programmatically, do **not** assume `set_param(block,'Script',...)` exists. For MATLAB Function blocks, update the script through `MATLABFunctionConfiguration`:\n\n```matlab\nblk = 'model\u002FMyMATLABFunction';\ncfg = get_param(blk, 'MATLABFunctionConfiguration');\ncfg.FunctionScript = sprintf([ ...\n    'function y = fcn(u)\\n' ...\n    '%%#codegen\\n' ...\n    'y = 2*u;\\n' ...\n    'end\\n']);\n```\n\nIf the function body references workspace parameters such as `Kp`, `tau_sys`, or `Q_max`, explicitly create `Stateflow.Data` entries with `Scope = 'Parameter'` or Simulink may fail size\u002Ftype inference during compile:\n\n```matlab\nrt = sfroot;\nmachine = rt.find('-isa', 'Stateflow.Machine', 'Name', bdroot(blk));\nchart = machine.find('-isa', 'Stateflow.EMChart', 'Path', blk);\n\nparam = Stateflow.Data(chart);\nparam.Name = 'Q_max';\nparam.Scope = 'Parameter';\n```\n\nWithout this explicit parameter declaration, a programmatically generated MATLAB Function block can fail with errors like \"cannot determine output size\u002Ftype\" even when the same code works interactively.\n\nCommon built-in library paths:\n- `built-in\u002FGain`\n- `built-in\u002FProduct`\n- `built-in\u002FConstant`\n- `built-in\u002FScope`\n- `built-in\u002FSubsystem`\n\nException for Inport and Outport use:\n- `sprintf('simulink\u002FPorts &\\nSubsystems\u002FIn1')`\n- `sprintf('simulink\u002FPorts &\\nSubsystems\u002FOut1')`\n\nException for Sum. Never use the Sum block, always use Add or Subtract instead:\n- `sprintf(['simulink\u002FMath\\nOperations\u002FAdd'])`\n- `sprintf(['simulink\u002FMath\\nOperations\u002FSubtract'])`\n\n## Connecting Blocks\n\nAlways use `Simulink.connectBlocks` to connect blocks — never `add_line`. This API is more robust and handles port resolution automatically.\n\n```matlab\n% Connect two blocks (Simulink picks the appropriate ports)\nSimulink.connectBlocks(srcBlock, dstBlock);\n\n% Connect specific ports when needed\nSimulink.connectBlocks([srcBlock '\u002F1'], [dstBlock '\u002F1']);\n```\n\n## Signal Logging\n\nWhen the user asks to log a signal, use Simulink's built-in signal logging on the port directly. **Never use a To Workspace block or a To File block.**\n\n```matlab\n% Log the first output port of a block\nph = get_param(gcb, 'PortHandles');\nset(ph.Outport(1), 'DataLogging', 'on');\n\n% Set the name lf the logged signal\nset(ph.Outport(1), 'DataLoggingNameMode', 'SignalName');\nset(ph.Outport(1), 'Name', 'mySignalName');\n```\n\nTo log a specific block by path instead of `gcb`:\n```matlab\nph = get_param('modelName\u002FBlockName', 'PortHandles');\nset(ph.Outport(1), 'DataLogging', 'on');\n```\n\nAfter simulation, logged signals are accessible via `logsout` in the `SimulationOutput` object (when using `sim()`) or via `Simulink.SimulationData.Dataset`.\n\nIf the user explicitly asks for `To Workspace` blocks or named workspace artifacts as deliverables, follow the user's request. The \"never use To Workspace\" rule is only the default when the user asks to log signals and does not constrain the export mechanism.\n\n## Creating Subsystems\n\nWhen adding a group of related blocks that should live inside a subsystem, add and connect all the blocks first (following the iterative one-at-a-time workflow above), then group them into a subsystem at the end:\n\n```matlab\n% Collect handles of all blocks to group\nblocks = [get_param('model\u002FBlock1', 'Handle'), ...\n          get_param('model\u002FBlock2', 'Handle'), ...\n          get_param('model\u002FBlock3', 'Handle')];\n\n% Group into a subsystem — Simulink handles port creation automatically\nSimulink.BlockDiagram.createSubsystem(blocks);\n```\n\n`createSubsystem` automatically adds the necessary Inport\u002FOutport blocks inside the subsystem and rewires external connections. Do **not** manually create a Subsystem block and move blocks into it.\n\n## Clearing a Subsystem\n\n`Simulink.BlockDiagram.deleteContents` only accepts a block diagram, not an arbitrary subsystem path. If you need to rebuild a subsystem in place, delete its lines and child blocks manually:\n\n```matlab\nsubsys = 'model\u002FMySubsystem';\nlines = find_system(subsys, 'FindAll', 'on', 'SearchDepth', 1, 'Type', 'line');\nif ~isempty(lines)\n    delete_line(lines);\nend\n\nblocks = find_system(subsys, 'SearchDepth', 1, 'Type', 'Block');\nblocks = setdiff(blocks, {subsys}, 'stable');\nfor i = 1:numel(blocks)\n    delete_block(blocks{i});\nend\n```\n\nThis is the safe pattern when regenerating subsystem internals from a script.\n\n## Step 4: Verify\n\nAfter making changes, confirm success by reading back the modified parameter or reporting what was changed.\n","# Simulink Open Model Interaction\n\nThis skill defines conventions for interacting with the Simulink model currently open in MATLAB, using `mcp__matlab__evaluate_matlab_code` as the primary tool.\n\n## Tooling Fallback\n\nIf the MATLAB MCP tool is unavailable in the current session but the user explicitly asks for real model creation or modification, fall back to local MATLAB execution such as `matlab -batch`. State the fallback briefly and keep the workflow identical: inspect, modify, verify, save.\n\n## Step 1: Resolve References\n\nBefore doing anything, determine what model\u002Fsystem\u002Fblock(s) the user is referring to.\n\n| User says | Resolution |\n|---|---|\n| \"this model\" | `bdroot(gcs)` |\n| \"this system\" \u002F \"this subsystem\" | `gcs` |\n| \"this block\" | `gcb` |\n| \"selected blocks\" (plural) | see snippet below |\n| \"all [Type] blocks in this subsystem\" | see snippet below |\n| \"all [Type] blocks in the model\" | see snippet below |\n\n### Selected blocks (plural)\n\n```matlab\nopts = Simulink.FindOptions;\nopts.SearchDepth = 1;\nblks = getfullname(Simulink.findBlocks(gcs, 'Selected', 'on', opts));\n```\n\n### All blocks of a specific type in the current subsystem\n\n```matlab\nopts = Simulink.FindOptions;\nopts.SearchDepth = 1;\nBlockType = 'Gain'; % replace with actual type\nblks = getfullname(Simulink.findBlocksOfType(gcs, BlockType, opts));\n```\n\n### All blocks of a specific type in the entire model\n\n```matlab\nBlockType = 'Gain'; % replace with actual type\nblks = getfullname(Simulink.findBlocksOfType(bdroot, BlockType));\n```\n\n## Step 2: Inspect Before Modifying\n\nUse `get_param` to read current state before making changes. This helps you confirm you have the right block and understand its current configuration.\n\n```matlab\nget_param(gcb, 'Gain')           % read a specific parameter\nget_param(gcb,'DialogParameters')  % list all dialog parameters\nget_param(gcb, 'ObjectParameters') % list all available parameters\n```\n\n## Step 3: Apply Changes\n\nUse `set_param` for most property changes:\n\n```matlab\nset_param(gcb, 'Gain', '2')\nset_param(gcb, 'BackgroundColor', 'red')\n```\n\nFor bulk operations on multiple blocks, iterate over the `blks` cell array:\n\n```matlab\nfor i = 1:numel(blks)\n    set_param(blks{i}, 'BackgroundColor', 'yellow');\nend\n```\n\n## Adding Blocks\n\nWhen adding blocks, follow these rules:\n\n- **Never** pass a `'Position'` argument to `add_block`\n- **Never** use `set_param(blk, 'Position', ...)` or `set_param(blk, 'Location', ...)`\n- **Never** use `Simulink.BlockDiagram.arrangeSystem`\n- Use `getBlockPosition` and `setBlockDimensions` (bundled in `utils\u002F`) for all positioning\n- To read block size, use `getBlockDimensions`; to resize, use `setBlockDimensions`\n- Add blocks **one at a time**: add a block, connect it, then position it relative to existing blocks before proceeding to the next\n\nUtility signatures (see `utils\u002F` for full source):\n```matlab\n[x, y]          = getBlockPosition(block)          % top-left corner\n[width, height] = getBlockDimensions(block)         % block size\nsetBlockPosition(block, x, y)                      % move, preserving size\nsetBlockDimensions(block, width, height)            % resize, preserving top-left\n```\n\n**Never use `set_param(block, 'Position', ...)`** — always use `setBlockPosition` and\u002For `setBlockDimensions` instead.\n\n```matlab\n% Example: add a Gain block to the right of the current block\nmodelName = bdroot(gcs);\nrefBlk = gcb;\n\n% 1. Get reference block geometry\n[refX, refY] = getBlockPosition(refBlk);\n[refW, ~]    = getBlockDimensions(refBlk);\n\n% 2. Add block (no position argument)\nnewBlk = [modelName '\u002FMyGain'];\nadd_block('built-in\u002FGain', newBlk);\n\n% 3. Position it to the right of the reference block\ngap = 50;\nsetBlockPosition(newBlk, refX + refW + gap, refY);\n\n% 4. Connect it\nSimulink.connectBlocks(Source,Destination);\n```\n\n## Programmatic MATLAB Function Blocks\n\nWhen editing a MATLAB Function block programmatically, do **not** assume `set_param(block,'Script',...)` exists. For MATLAB Function blocks, update the script through `MATLABFunctionConfiguration`:\n\n```matlab\nblk = 'model\u002FMyMATLABFunction';\ncfg = get_param(blk, 'MATLABFunctionConfiguration');\ncfg.FunctionScript = sprintf([ ...\n    'function y = fcn(u)\\n' ...\n    '%%#codegen\\n' ...\n    'y = 2*u;\\n' ...\n    'end\\n']);\n```\n\nIf the function body references workspace parameters such as `Kp`, `tau_sys`, or `Q_max`, explicitly create `Stateflow.Data` entries with `Scope = 'Parameter'` or Simulink may fail size\u002Ftype inference during compile:\n\n```matlab\nrt = sfroot;\nmachine = rt.find('-isa', 'Stateflow.Machine', 'Name', bdroot(blk));\nchart = machine.find('-isa', 'Stateflow.EMChart', 'Path', blk);\n\nparam = Stateflow.Data(chart);\nparam.Name = 'Q_max';\nparam.Scope = 'Parameter';\n```\n\nWithout this explicit parameter declaration, a programmatically generated MATLAB Function block can fail with errors like \"cannot determine output size\u002Ftype\" even when the same code works interactively.\n\nCommon built-in library paths:\n- `built-in\u002FGain`\n- `built-in\u002FProduct`\n- `built-in\u002FConstant`\n- `built-in\u002FScope`\n- `built-in\u002FSubsystem`\n\nException for Inport and Outport use:\n- `sprintf('simulink\u002FPorts &\\nSubsystems\u002FIn1')`\n- `sprintf('simulink\u002FPorts &\\nSubsystems\u002FOut1')`\n\nException for Sum. Never use the Sum block, always use Add or Subtract instead:\n- `sprintf(['simulink\u002FMath\\nOperations\u002FAdd'])`\n- `sprintf(['simulink\u002FMath\\nOperations\u002FSubtract'])`\n\n## Connecting Blocks\n\nAlways use `Simulink.connectBlocks` to connect blocks — never `add_line`. This API is more robust and handles port resolution automatically.\n\n```matlab\n% Connect two blocks (Simulink picks the appropriate ports)\nSimulink.connectBlocks(srcBlock, dstBlock);\n\n% Connect specific ports when needed\nSimulink.connectBlocks([srcBlock '\u002F1'], [dstBlock '\u002F1']);\n```\n\n## Signal Logging\n\nWhen the user asks to log a signal, use Simulink's built-in signal logging on the port directly. **Never use a To Workspace block or a To File block.**\n\n```matlab\n% Log the first output port of a block\nph = get_param(gcb, 'PortHandles');\nset(ph.Outport(1), 'DataLogging', 'on');\n\n% Set the name lf the logged signal\nset(ph.Outport(1), 'DataLoggingNameMode', 'SignalName');\nset(ph.Outport(1), 'Name', 'mySignalName');\n```\n\nTo log a specific block by path instead of `gcb`:\n```matlab\nph = get_param('modelName\u002FBlockName', 'PortHandles');\nset(ph.Outport(1), 'DataLogging', 'on');\n```\n\nAfter simulation, logged signals are accessible via `logsout` in the `SimulationOutput` object (when using `sim()`) or via `Simulink.SimulationData.Dataset`.\n\nIf the user explicitly asks for `To Workspace` blocks or named workspace artifacts as deliverables, follow the user's request. The \"never use To Workspace\" rule is only the default when the user asks to log signals and does not constrain the export mechanism.\n\n## Creating Subsystems\n\nWhen adding a group of related blocks that should live inside a subsystem, add and connect all the blocks first (following the iterative one-at-a-time workflow above), then group them into a subsystem at the end:\n\n```matlab\n% Collect handles of all blocks to group\nblocks = [get_param('model\u002FBlock1', 'Handle'), ...\n          get_param('model\u002FBlock2', 'Handle'), ...\n          get_param('model\u002FBlock3', 'Handle')];\n\n% Group into a subsystem — Simulink handles port creation automatically\nSimulink.BlockDiagram.createSubsystem(blocks);\n```\n\n`createSubsystem` automatically adds the necessary Inport\u002FOutport blocks inside the subsystem and rewires external connections. Do **not** manually create a Subsystem block and move blocks into it.\n\n## Clearing a Subsystem\n\n`Simulink.BlockDiagram.deleteContents` only accepts a block diagram, not an arbitrary subsystem path. If you need to rebuild a subsystem in place, delete its lines and child blocks manually:\n\n```matlab\nsubsys = 'model\u002FMySubsystem';\nlines = find_system(subsys, 'FindAll', 'on', 'SearchDepth', 1, 'Type', 'line');\nif ~isempty(lines)\n    delete_line(lines);\nend\n\nblocks = find_system(subsys, 'SearchDepth', 1, 'Type', 'Block');\nblocks = setdiff(blocks, {subsys}, 'stable');\nfor i = 1:numel(blocks)\n    delete_block(blocks{i});\nend\n```\n\nThis is the safe pattern when regenerating subsystem internals from a script.\n\n## Step 4: Verify\n\nAfter making changes, confirm success by reading back the modified parameter or reporting what was changed.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fsummer521521\u002FMATLAB_Simulink_plugin\u002Fskills\u002Fsimulink-interactions",490,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 02:12:02",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill simulink-interactions",{"tool":65,"command":66},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill simulink-interactions",{"tool":68,"command":69},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill simulink-interactions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsummer521521\u002FMATLAB_Simulink_plugin\u002Fskills\u002Fsimulink-interactions\u002FSKILL.md",true,[73,79,83,87],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"utils\u002FgetBlockDimensions.m","OTHER","其他",651,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsummer521521\u002FMATLAB_Simulink_plugin\u002Fskills\u002Fsimulink-interactions\u002Futils\u002FgetBlockDimensions.m",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"utils\u002FgetBlockPosition.m",271,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsummer521521\u002FMATLAB_Simulink_plugin\u002Fskills\u002Fsimulink-interactions\u002Futils\u002FgetBlockPosition.m",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"utils\u002FsetBlockDimensions.m",762,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsummer521521\u002FMATLAB_Simulink_plugin\u002Fskills\u002Fsimulink-interactions\u002Futils\u002FsetBlockDimensions.m",{"path":88,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":89,"sourceHtmlUrl":90},"utils\u002FsetBlockPosition.m",333,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsummer521521\u002FMATLAB_Simulink_plugin\u002Fskills\u002Fsimulink-interactions\u002Futils\u002FsetBlockPosition.m",[92,100,107,114,140,165],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":99},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":99},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":99},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":44},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,42,137,138,139],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","cli","merge","past",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":44},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[147,148,149,136,150,151,152,153,154,155,156,157,158,159,126,160,161,162,163,164],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":178,"publishedAt":44},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[171,174,175],{"categoryNo":172,"categoryName":173,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":176,"categoryName":177,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[167,179,180,181,182,183,184,161,185,127,186,187,34,188,132,189,43,190,191,192],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","song","image","schedule","api","publish"]