[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MMZGA4SJ8WN43H9N2YA4ZW":3,"skill-same:01M6MMZGA4SJ8WN43H9N2YA4ZW":68},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6MMZGA4SJ8WN43H9N2YA4ZW","simulink-simulation",null,"Use this skill whenever simulating a Simulink model, running the sim command, setting up SimulationInput objects, passing input signals via timeseries or datasets, configuring model or block parameters programmatically, or accessing logged output data from SimulationOutput. Trigger for any request involving sim(), Simulink.SimulationInput, Simulink.SimulationOutput, logsout, setExternalInput, or setModelParameter.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsummer521521\u002FMATLAB_Simulink_plugin\u002Fskills\u002Fsimulink-simulation\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"simulation","simulink simulation","trigger","running","request","for","sim","block","output","via","input","timeseries","signals","objects","datasets","up","use","command","model","data","2026-11-10 10:12:30",false,"---\nname: simulink-simulation\ndescription: Use this skill whenever simulating a Simulink model, running the sim command, setting up SimulationInput objects, passing input signals via timeseries or datasets, configuring model or block parameters programmatically, or accessing logged output data from SimulationOutput. Trigger for any request involving sim(), Simulink.SimulationInput, Simulink.SimulationOutput, logsout, setExternalInput, or setModelParameter.\n---\n\n# Simulating Simulink Models with the sim Command\n\n## Minimal working pattern\n\nAlways simulate using `Simulink.SimulationInput` and `Simulink.SimulationOutput`:\n\n```matlab\nin = Simulink.SimulationInput('MyModel');\nin = in.setModelParameter('StopTime', '10');\nout = sim(in);\n```\n\nNever use `set_param`, `load_system`, or `open_system` to drive simulation — the `SimulationInput` API replaces all of these.\n\nIf the MATLAB MCP tool is unavailable but the user explicitly asks for real artifacts such as `.slx`, exported figures, or `.mat` results, use local MATLAB execution such as `matlab -batch` as a fallback. Give MATLAB generous timeouts because startup alone can take minutes.\n\nFor MATLAB MCP core server v0.9.0 and newer, this personal plugin launcher can pass through optional session\u002Flogging settings via environment variables:\n- `MATLAB_SESSION_MODE` -> `--matlab-session-mode`\n- `MATLAB_EXTENSION_FILE` -> `--extension-file`\n- `MATLAB_EXTENSION_FILES` -> repeated `--extension-file` values, separated by the OS path separator (`;` on Windows)\n- `MATLAB_LOG_FOLDER` -> `--log-folder`\n- `MATLAB_LOG_LEVEL` -> `--log-level`\n\nMATLAB MCP core server v0.9.2 improves `--initialize-matlab-on-startup=true` so the MCP server is not blocked while MATLAB starts, and fixes `shareMATLABSession()` failures on Windows. Keep the launcher default lazy startup unless the user explicitly wants startup-time initialization.\n\nMATLAB MCP core server v0.10.0 makes `auto` the default session mode. Leave `MATLAB_SESSION_MODE` unset for normal use, set it to `existing` only when the user has run `shareMATLABSession()` in the target MATLAB session, and use multiple extension files only when the current MCP server exposes those custom tools.\n\nKeep `MATLAB_SETUP_MATLAB` unset for normal MCP sessions; set it only for a one-time upstream setup run.\n\n## Setting parameters\n\nUse `SimulationInput` methods to configure the simulation:\n\n```matlab\n% Model-level parameters (StopTime, SolverType, SimulationMode, etc.)\nin = in.setModelParameter('StopTime', '10', 'SolverType', 'Fixed-step');\n\n% Block parameters\nin = in.setBlockParameter('MyModel\u002FGain', 'Gain', '5');\n\n% MATLAB workspace variables used by the model\nin = in.setVariable('Kp', 1.2);\n```\n\n## Input signals\n\nPass input signals through Inport blocks using a `Simulink.SimulationData.Dataset`. Each timeseries `Name` must match the corresponding Inport block's signal name, otherwise the signal won't be routed correctly.\n\n```matlab\ndt = 0.01; % sample time\nN = 1000; % Number of points\nt = dt*(0:N)';\nu = sin(2*pi*t);\n\nts = timeseries(u, t);\nts.Name = 'mySignal';   % must match the Inport signal name in the model\n\nds = Simulink.SimulationData.Dataset;\nds{1} = ts;\n\nin = in.setExternalInput(ds);\nout = sim(in);\n```\n\n## Discovering logged signals\n\nBefore accessing logged data by name, discover what signals the model actually logs by running a simulation and inspecting `logsout`:\n\n```matlab\nin = Simulink.SimulationInput('MyModel');\nout = sim(in);\ndisp('List of logged signals:');\ndisp(out.logsout.getElementNames);\n```\n\nThis is especially useful when working with an unfamiliar model — the names returned here are exactly the names to use when calling `out.logsout.get(...)`.\n\n## Accessing logged data\n\nLogged signals are available through `out.logsout`. Access them directly by name — no intermediate variables needed:\n\n```matlab\n% Plot a logged signal\nplot(out.logsout.get('signalName').Values)\n\n% Get time and data separately\nsig = out.logsout.get('signalName').Values;\nplot(sig.Time, sig.Data)\n```\n\nDo not validate `out` with try-catch or `isfield` — `sim` either returns a valid `SimulationOutput` or throws an error. `Simulink.SimulationOutput` has no `isfield` method.\n\n## Accessing To Workspace Outputs\n\nIf the model uses `To Workspace` blocks and `ReturnWorkspaceOutputs` is on, retrieve those outputs directly from the `SimulationOutput` object:\n\n```matlab\nin = Simulink.SimulationInput('MyModel');\nin = in.setModelParameter('ReturnWorkspaceOutputs', 'on');\nout = sim(in);\n\nT = out.simout_T;\nQ = out.simout_Qbase;\n```\n\nNormalize the exported value before post-processing because `To Workspace` may return a `timeseries`, a `Simulink.SimulationData.Signal`, or a numeric matrix depending on block settings:\n\n```matlab\nif isa(T, 'timeseries')\n    t = T.Time(:);\n    y = T.Data(:);\nelseif isa(T, 'Simulink.SimulationData.Signal')\n    t = T.Values.Time(:);\n    y = T.Values.Data(:);\nelse\n    t = T(:,1);\n    y = T(:,2);\nend\n```\n\n## Multiple simulations\n\nWhen running many simulations, create an array of `Simulink.SimulationInput` objects using the `repmat` function instead of looping over `sim`:\n\n```matlab\nin = repmat(Simulink.SimulationInput('MyModel'),N,1);\nfor k = 1:N\n    in(k) = Simulink.SimulationInput('MyModel');\n    in(k) = in(k).setVariable('gain', gains(k));\nend\nout = sim(in);\n```\n\nWhen collecting results from multiple cases into a struct array, preallocate a homogeneous struct shape before the loop. MATLAB will throw \"subscripted assignment between dissimilar structures\" if later cases add fields or nested layouts that the first element did not have.\n\n## Parallel simulation (parsim)\n\nTo run multiple simulations, use `parsim` instead of looping over `sim`:\n\n```matlab\nfor k = 1:N\n    in(k) = Simulink.SimulationInput('MyModel');\n    in(k) = in(k).setVariable('gain', gains(k));\nend\nout = parsim(in);\n```\n\n## Rebuild-and-Simulate Pitfalls\n\nIf a script repeatedly rebuilds and reruns a model:\n\n- Save or clear the dirty flag before `close_system`, otherwise MATLAB can warn that the changed model cannot be closed.\n- Avoid model names that shadow scripts or functions on the MATLAB path; model\u002Fscript name collisions can produce confusing warnings during `sim` and `run`.\n- When a generated model relies on MATLAB Function blocks with workspace parameters, make sure those symbols are declared as block parameters during model construction; otherwise simulation can fail before `sim` starts with output-size\u002Ftype inference errors.\n","# Simulating Simulink Models with the sim Command\n\n## Minimal working pattern\n\nAlways simulate using `Simulink.SimulationInput` and `Simulink.SimulationOutput`:\n\n```matlab\nin = Simulink.SimulationInput('MyModel');\nin = in.setModelParameter('StopTime', '10');\nout = sim(in);\n```\n\nNever use `set_param`, `load_system`, or `open_system` to drive simulation — the `SimulationInput` API replaces all of these.\n\nIf the MATLAB MCP tool is unavailable but the user explicitly asks for real artifacts such as `.slx`, exported figures, or `.mat` results, use local MATLAB execution such as `matlab -batch` as a fallback. Give MATLAB generous timeouts because startup alone can take minutes.\n\nFor MATLAB MCP core server v0.9.0 and newer, this personal plugin launcher can pass through optional session\u002Flogging settings via environment variables:\n- `MATLAB_SESSION_MODE` -> `--matlab-session-mode`\n- `MATLAB_EXTENSION_FILE` -> `--extension-file`\n- `MATLAB_EXTENSION_FILES` -> repeated `--extension-file` values, separated by the OS path separator (`;` on Windows)\n- `MATLAB_LOG_FOLDER` -> `--log-folder`\n- `MATLAB_LOG_LEVEL` -> `--log-level`\n\nMATLAB MCP core server v0.9.2 improves `--initialize-matlab-on-startup=true` so the MCP server is not blocked while MATLAB starts, and fixes `shareMATLABSession()` failures on Windows. Keep the launcher default lazy startup unless the user explicitly wants startup-time initialization.\n\nMATLAB MCP core server v0.10.0 makes `auto` the default session mode. Leave `MATLAB_SESSION_MODE` unset for normal use, set it to `existing` only when the user has run `shareMATLABSession()` in the target MATLAB session, and use multiple extension files only when the current MCP server exposes those custom tools.\n\nKeep `MATLAB_SETUP_MATLAB` unset for normal MCP sessions; set it only for a one-time upstream setup run.\n\n## Setting parameters\n\nUse `SimulationInput` methods to configure the simulation:\n\n```matlab\n% Model-level parameters (StopTime, SolverType, SimulationMode, etc.)\nin = in.setModelParameter('StopTime', '10', 'SolverType', 'Fixed-step');\n\n% Block parameters\nin = in.setBlockParameter('MyModel\u002FGain', 'Gain', '5');\n\n% MATLAB workspace variables used by the model\nin = in.setVariable('Kp', 1.2);\n```\n\n## Input signals\n\nPass input signals through Inport blocks using a `Simulink.SimulationData.Dataset`. Each timeseries `Name` must match the corresponding Inport block's signal name, otherwise the signal won't be routed correctly.\n\n```matlab\ndt = 0.01; % sample time\nN = 1000; % Number of points\nt = dt*(0:N)';\nu = sin(2*pi*t);\n\nts = timeseries(u, t);\nts.Name = 'mySignal';   % must match the Inport signal name in the model\n\nds = Simulink.SimulationData.Dataset;\nds{1} = ts;\n\nin = in.setExternalInput(ds);\nout = sim(in);\n```\n\n## Discovering logged signals\n\nBefore accessing logged data by name, discover what signals the model actually logs by running a simulation and inspecting `logsout`:\n\n```matlab\nin = Simulink.SimulationInput('MyModel');\nout = sim(in);\ndisp('List of logged signals:');\ndisp(out.logsout.getElementNames);\n```\n\nThis is especially useful when working with an unfamiliar model — the names returned here are exactly the names to use when calling `out.logsout.get(...)`.\n\n## Accessing logged data\n\nLogged signals are available through `out.logsout`. Access them directly by name — no intermediate variables needed:\n\n```matlab\n% Plot a logged signal\nplot(out.logsout.get('signalName').Values)\n\n% Get time and data separately\nsig = out.logsout.get('signalName').Values;\nplot(sig.Time, sig.Data)\n```\n\nDo not validate `out` with try-catch or `isfield` — `sim` either returns a valid `SimulationOutput` or throws an error. `Simulink.SimulationOutput` has no `isfield` method.\n\n## Accessing To Workspace Outputs\n\nIf the model uses `To Workspace` blocks and `ReturnWorkspaceOutputs` is on, retrieve those outputs directly from the `SimulationOutput` object:\n\n```matlab\nin = Simulink.SimulationInput('MyModel');\nin = in.setModelParameter('ReturnWorkspaceOutputs', 'on');\nout = sim(in);\n\nT = out.simout_T;\nQ = out.simout_Qbase;\n```\n\nNormalize the exported value before post-processing because `To Workspace` may return a `timeseries`, a `Simulink.SimulationData.Signal`, or a numeric matrix depending on block settings:\n\n```matlab\nif isa(T, 'timeseries')\n    t = T.Time(:);\n    y = T.Data(:);\nelseif isa(T, 'Simulink.SimulationData.Signal')\n    t = T.Values.Time(:);\n    y = T.Values.Data(:);\nelse\n    t = T(:,1);\n    y = T(:,2);\nend\n```\n\n## Multiple simulations\n\nWhen running many simulations, create an array of `Simulink.SimulationInput` objects using the `repmat` function instead of looping over `sim`:\n\n```matlab\nin = repmat(Simulink.SimulationInput('MyModel'),N,1);\nfor k = 1:N\n    in(k) = Simulink.SimulationInput('MyModel');\n    in(k) = in(k).setVariable('gain', gains(k));\nend\nout = sim(in);\n```\n\nWhen collecting results from multiple cases into a struct array, preallocate a homogeneous struct shape before the loop. MATLAB will throw \"subscripted assignment between dissimilar structures\" if later cases add fields or nested layouts that the first element did not have.\n\n## Parallel simulation (parsim)\n\nTo run multiple simulations, use `parsim` instead of looping over `sim`:\n\n```matlab\nfor k = 1:N\n    in(k) = Simulink.SimulationInput('MyModel');\n    in(k) = in(k).setVariable('gain', gains(k));\nend\nout = parsim(in);\n```\n\n## Rebuild-and-Simulate Pitfalls\n\nIf a script repeatedly rebuilds and reruns a model:\n\n- Save or clear the dirty flag before `close_system`, otherwise MATLAB can warn that the changed model cannot be closed.\n- Avoid model names that shadow scripts or functions on the MATLAB path; model\u002Fscript name collisions can produce confusing warnings during `sim` and `run`.\n- When a generated model relies on MATLAB Function blocks with workspace parameters, make sure those symbols are declared as block parameters during model construction; otherwise simulation can fail before `sim` starts with output-size\u002Ftype inference errors.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fsummer521521\u002FMATLAB_Simulink_plugin\u002Fskills\u002Fsimulink-simulation",491,"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 14:06:13",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill simulink-simulation",{"tool":60,"command":61},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill simulink-simulation",{"tool":63,"command":64},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill simulink-simulation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsummer521521\u002FMATLAB_Simulink_plugin\u002Fskills\u002Fsimulink-simulation\u002FSKILL.md",true,[],[69,79,87,95,103,111],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":78},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":78},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":78},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":78},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":78},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":78},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]