Agent skill

Cst Simulation Workflow

A skill your agent uses when driving CST Studio Suite through the CST MCP for electromagnetic simulation workflows: creating or opening CST projects, resolving missing inputs, selecting templates…

MITAuto-check passedDocuments & Office

Install Cst Simulation Workflow

skills CLI

$ npx skills add Cai-aa/CAE-Agent-Hub --skill cst-simulation-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Cai-aa/CAE-Agent-Hub cst-simulation-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Cai-aa/CAE-Agent-Hub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Skill/CST/cst-simulation-workflow .claude/skills/cst-simulation-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "cst-simulation-workflow" agent skill from https://github.com/Cai-aa/CAE-Agent-Hub/tree/main/Skill/CST/cst-simulation-workflow into .claude/skills/cst-simulation-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cst-simulation-workflow", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Cai-aa/CAE-Agent-Hub/tree/main/Skill/CST/cst-simulation-workflow

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Cai-aa/CAE-Agent-Hub --skill cst-simulation-workflow -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Cai-aa/CAE-Agent-Hub cst-simulation-workflow --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Cai-aa/CAE-Agent-Hub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Skill/CST/cst-simulation-workflow .agents/skills/cst-simulation-workflow && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "cst-simulation-workflow" agent skill from https://github.com/Cai-aa/CAE-Agent-Hub/tree/main/Skill/CST/cst-simulation-workflow into .agents/skills/cst-simulation-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cst-simulation-workflow", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Cai-aa/CAE-Agent-Hub --skill cst-simulation-workflow -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Cai-aa/CAE-Agent-Hub cst-simulation-workflow --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Cai-aa/CAE-Agent-Hub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Skill/CST/cst-simulation-workflow .cursor/skills/cst-simulation-workflow && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "cst-simulation-workflow" agent skill from https://github.com/Cai-aa/CAE-Agent-Hub/tree/main/Skill/CST/cst-simulation-workflow into .cursor/skills/cst-simulation-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cst-simulation-workflow", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Cai-aa/CAE-Agent-Hub.git --path Skill/CST/cst-simulation-workflow

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Cai-aa/CAE-Agent-Hub --skill cst-simulation-workflow -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Cai-aa/CAE-Agent-Hub cst-simulation-workflow --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Cai-aa/CAE-Agent-Hub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Skill/CST/cst-simulation-workflow .gemini/skills/cst-simulation-workflow && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "cst-simulation-workflow" agent skill from https://github.com/Cai-aa/CAE-Agent-Hub/tree/main/Skill/CST/cst-simulation-workflow into .gemini/skills/cst-simulation-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cst-simulation-workflow", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Cai-aa/CAE-Agent-Hub cst-simulation-workflow

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Cai-aa/CAE-Agent-Hub --skill cst-simulation-workflow -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Cai-aa/CAE-Agent-Hub.git skills-src && mkdir -p .github/skills && cp -r skills-src/Skill/CST/cst-simulation-workflow .github/skills/cst-simulation-workflow && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "cst-simulation-workflow" agent skill from https://github.com/Cai-aa/CAE-Agent-Hub/tree/main/Skill/CST/cst-simulation-workflow into .github/skills/cst-simulation-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cst-simulation-workflow", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Cai-aa/CAE-Agent-Hub --skill cst-simulation-workflow -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Cai-aa/CAE-Agent-Hub cst-simulation-workflow --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Cai-aa/CAE-Agent-Hub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Skill/CST/cst-simulation-workflow .opencode/skills/cst-simulation-workflow && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "cst-simulation-workflow" agent skill from https://github.com/Cai-aa/CAE-Agent-Hub/tree/main/Skill/CST/cst-simulation-workflow into .opencode/skills/cst-simulation-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cst-simulation-workflow", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: cst-simulation-workflow
GitHub stars: 998
Token cost: ~1.4k tokens
SKILL.md length: 675 words
Files: 9 (incl. references)
Skills in repo: 57
Repo updated: Sep 30, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when driving CST Studio Suite through the CST MCP for electromagnetic simulation workflows: creating or opening CST projects, resolving missing inputs, selecting templates…

Works in 12 steps: Detect CST MCP availability and CST… → Determine whether to create a new… → Identify the simulation class and select… → …
Driving CST Studio Suite through the CST MCP for electromagnetic simulation workflows: creating
SKILL.md covers Operating Modes, Standard Workflow, Reference Files and Input Policy, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Cst Simulation Workflow is an agent skill from Cai-aa/CAE-Agent-Hub. Use this skill when driving CST Studio Suite through the CST MCP for electromagnetic simulation workflows: creating or opening CST projects, resolving missing inputs, selecting templates, setting up geometry/materials/ports/boundaries/mesh/solvers/monitors, running or planning simulations, extracting S-parameters/far-field/near-field/eigenmode results, validating outputs, parameter sweeps, optimization handoff, and report generation.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `agents/openai.yaml`, `metadata.json` and `references/cst-red-lines.md`).

It sits in Documents & Office. It works with Model Context Protocol. The licence is MIT.

When your agent uses it

Driving CST Studio Suite through the CST MCP for electromagnetic simulation workflows: creating
Opening CST projects
Resolving missing inputs
Selecting templates

Example prompts

“/cst-simulation-workflow”

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

Detect CST MCP availability and CST Design Environment status.
Determine whether to create a new project, open a copy of an existing .cst, or only generate a plan.
Identify the simulation class and select a template when appropriate.
Resolve missing inputs using the parameter policy.
Present a compact defaults card before expensive solves unless the user already said to use defaults or run directly.
Build or modify geometry, materials, coordinate system, ports/excitations, boundaries, mesh, solver, and monitors.
Save the working project before running a solver.
Run the solver only when the user requested execution or accepted the defaults.
Extract result tree items and export requested data.
Validate results against the objective and evidence requirements.
Generate a concise report with assumptions, files, commands/tools used, result paths, and validation status.
Close/cleanup the CST project/session and report any nonblocking residual locks or access-denied cleanup messages.

What it can do on your machine

Read from SKILL.md and the folder at commit 194ef49. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cst Simulation Workflow loads about 1.4k tokens when it runs, and up to ~6.4k if it reads all its reference files. Until then it costs about 115 tokens; SKILL.md has 675 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~115
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~6.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Cai-aa/CAE-Agent-Hub at commit 194ef49, republished under its MIT licence (© Cai-aa). 675 words, ~1,350 tokens.

Download SKILL.mdSave it as .claude/skills/cst-simulation-workflow/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.

name: cst-simulation-workflow
description: Use this skill when driving CST Studio Suite through the CST MCP for electromagnetic simulation workflows: creating or opening CST projects, resolving missing inputs, selecting templates, setting up geometry/materials/ports/boundaries/mesh/solvers/monitors, running or planning simulations, extracting S-parameters/far-field/near-field/eigenmode results, validating outputs, parameter sweeps, optimization handoff, and report generation.

CST Simulation Workflow

Use this skill as the workflow and decision layer. Use the CST MCP as the execution layer.

Prefer the repository CST MCP native tools for live session control. Use the vendored cst_runtime_* or cst_toolbox_* wrappers for larger command catalogs, workspace pipelines, result export, parameter sweeps, and optimization helpers.

Operating Modes

First classify the request:

Mode	Use when	Action
Plan only	User asks for a scheme, script outline, or workflow	Do not run CST; produce the setup plan and assumptions
New project	User wants a new CST case	Select a template, resolve inputs, create a run project
Existing project	User provides a `.cst` path or asks to modify an open project	Inspect first, then work on a copy unless explicitly told otherwise
Parameter sweep	User asks for ranges, cases, or comparison	Use sweep preview before running cases
Optimization	User asks to improve S11, gain, bandwidth, coupling, etc.	Hand off to runtime optimization workflow after confirming objective and bounds

Standard Workflow

Detect CST MCP availability and CST Design Environment status.
Determine whether to create a new project, open a copy of an existing .cst, or only generate a plan.
Identify the simulation class and select a template when appropriate.
Resolve missing inputs using the parameter policy.
Present a compact defaults card before expensive solves unless the user already said to use defaults or run directly.
Build or modify geometry, materials, coordinate system, ports/excitations, boundaries, mesh, solver, and monitors.
Save the working project before running a solver.
Run the solver only when the user requested execution or accepted the defaults.
Extract result tree items and export requested data.
Validate results against the objective and evidence requirements.
Generate a concise report with assumptions, files, commands/tools used, result paths, and validation status.
Close/cleanup the CST project/session and report any nonblocking residual locks or access-denied cleanup messages.

Reference Files

Read only the reference file needed for the current task:

references/workflow.md for the end-to-end workflow and mode-specific execution details.
references/parameter-policy.md for required questions, defaults, derived values, and existing-project inspection.
references/mcp-tool-map.md for this repository's CST MCP tool names and when to prefer native vs runtime tools.
references/templates.md for V1 simulation templates and default values.
references/result-validation.md for S-parameter, far-field, near-field, eigenmode, sweep, and report validation.
references/cst-red-lines.md for correctness and safety rules that must not be violated.

Show full SKILL.md (283 more words)Show less

Input Policy

Ask at most one compact clarification when critical information is missing. If the user says "directly run", "use defaults", "先默认", or equivalent, use defaults and record them in the report.

Critical inputs that usually require confirmation:

simulation case type
target frequency or frequency band
new project vs existing project
primary result objective
whether to actually run the solver

Defaultable inputs include units, background, common metals, antenna boundaries, solver choice, monitor frequencies, mesh level, and standard result exports. See references/parameter-policy.md.

Execution Rules

Do not overwrite a user's source .cst project. Copy it to a run directory unless the user explicitly requests in-place edits.
Inspect existing projects before changing them.
Prefer CST Macro Recorder-style VBA history blocks for modeling operations when no higher-level MCP tool exists.
Save before solving.
Treat solver success as unverified until result files, result tree entries, or exported data confirm it.
For long or costly solves, state the assumptions and expected outputs before running.

Result Rules

Do not treat complex S-parameter values as dB. Convert with 20*log10(abs(S11)).
Do not report Abs(E) as gain. Use Realized Gain, Gain, or Directivity for far-field gain claims.
Keep model-building/session operations separate from result-reading operations when the tool surface exposes separate modes.
Include exact evidence paths for project files, exports, reports, and logs.

V1 Scope

Focus V1 on:

a single new standard antenna case, especially a 2.4 GHz Wi-Fi/IoT microstrip patch antenna;
opening an existing .cst, inspecting it, changing parameters, and rerunning on a copy;
S11, VSWR, far-field gain/directivity, radiation pattern, eigenmode frequency, and concise Markdown report outputs;
parameter sweep preview/run through the CST MCP sweep tools.

Use 77 GHz 1x4 radar patch array as a demonstration template after the basic workflow is stable.

Files

SKILL.md and 8 other files (references) in Skill/CST/cst-simulation-workflow of Cai-aa/CAE-Agent-Hub.

SKILL.md
agents/openai.yaml
metadata.json
references/cst-red-lines.md
references/mcp-tool-map.md
references/parameter-policy.md
references/result-validation.md
references/templates.md
references/workflow.md

Open the folder on GitHubat commit 194ef49

Compare with similar skills

Cst Simulation Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cst Simulation Workflow compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Cst Simulation Workflow this skillCai-aa/CAE-Agent-Hub	998	—	~1.4k	Automated safety check: Pass	MIT	7 days ago
Adk Docs WriterBrainDAO/adk-ts	119	—	~4.9k	Automated safety check: Pass	MIT	3 mo ago
MCP Gatewaytmustier/pi-for-excel	434	—	~241	Automated safety check: Pass	MIT	today
Google Workspaceswarmclawai/swarmclaw	688	—	~680	Automated safety check: Pass	MIT	3 mo ago
Workiq Copilotgithub/awesome-copilot	40k	1 repos	~1.4k	Automated safety check: Pass	MIT	today
Quickbooksasgeirtj/system_prompts_leaks	69k	—	~1.9k	Automated safety check: Pass	CC0-1.0	today

Similar skills

Adk Docs Writer
BrainDAO/adk-ts
ADK-TS documentation specialist for Fumadocs MDX pages. An agent skill from BrainDAO/adk-ts.
119 GitHub stars~4.9k tokensUpdated 3 mo ago
Documents & OfficeAuto-check passed
MCP Gateway
tmustier/pi-for-excel
Discover and call tools from configured MCP servers. An agent skill from tmustier/pi-for-excel.
434 GitHub stars~241 tokensUpdated today
Documents & OfficeAuto-check passed
Google Workspace
swarmclawai/swarmclaw
Use Google Workspace CLI (gws) for Drive, Docs, Sheets, Gmail, Calendar, Chat, and related Workspace API tasks.
688 GitHub stars~680 tokensUpdated 3 mo ago
Documents & OfficeAuto-check passed
Workiq Copilot
github/awesome-copilot
Official
Guides the Copilot CLI on how to use the WorkIQ CLI/MCP server to query Microsoft 365 Copilot data (emails, meetings, docs, Teams, people) for live context, summaries, and recommendations.
40k GitHub starsUsed in 1 repo~1.4k tokens
Documents & OfficeAuto-check passed
Quickbooks
asgeirtj/system_prompts_leaks
Read and manage the user's QuickBooks business through Intuit's official MCP server, including reports, invoices, customers, products, payment links, sales settings, and industry benchmarks.
69k GitHub stars~1.9k tokensUpdated today
Documents & OfficeAuto-check passed
Markdown To Confluence
testdouble/han
Publishes a local Markdown file to a user-specified Confluence location, creating a new page or updating an existing one through the Atlassian MCP server.
279 GitHub stars~2.4k tokensUpdated 7 days ago
Documents & OfficeAuto-check passed

More from Cai-aa/CAE-Agent-Hub

All 57 skills in this repo

Ansys Structural Workbench
Cai-aa/CAE-Agent-Hub
Operate or inspect live ANSYS Workbench Mechanical structural simulations through the configured MCP, including model setup, materials, connections, loads, mesh, solve, convergence, validation, and…
998 GitHub stars~2.2k tokensUpdated 7 days ago
Auto-check passed
Cylinder O Grid
Cai-aa/CAE-Agent-Hub
Plan, create, adapt, and quality-audit coin-style five-block O-grid hexahedral meshes for cylindrical CAE models.
998 GitHub stars~1.6k tokensUpdated 7 days ago
Auto-check passed
Comsol Motor Nvh Evidence
Cai-aa/CAE-Agent-Hub
Evidence-first COMSOL Java API and batch workflow for permanent-magnet motor NVH.
998 GitHub stars~1.3k tokensUpdated 7 days ago
Auto-check passed
Aedt Evidence Electromagnetics
Cai-aa/CAE-Agent-Hub
Evidence-first Ansys Electronics Desktop and PyAEDT automation for Maxwell, HFSS, Q3D, Icepak, and related electromagnetic workflows.
998 GitHub stars~591 tokensUpdated 7 days ago
Auto-check passed
Ansys Mechanical Evidence Structural
Cai-aa/CAE-Agent-Hub
Evidence-first Ansys Mechanical structural automation through Workbench RunWB2 journals, Mechanical Scripting/ACT ExtAPI, or PyMechanical gRPC.
998 GitHub stars~554 tokensUpdated 7 days ago
Auto-check passed
Run Fluent Autoclave
Cai-aa/CAE-Agent-Hub
Run, diagnose, reproduce, and validate ANSYS Fluent CFD simulations of forced-convection autoclaves using Fluent MCP or PyFluent.
998 GitHub stars~984 tokensUpdated 7 days ago
Auto-check passed

Works with

Model Context Protocol

Questions about Cst Simulation Workflow

What does Cst Simulation Workflow do?

A skill your agent uses when driving CST Studio Suite through the CST MCP for electromagnetic simulation workflows: creating or opening CST projects, resolving missing inputs, selecting templates…. Cst Simulation Workflow is an agent skill from Cai-aa/CAE-Agent-Hub. Use this skill when driving CST Studio Suite through the CST MCP for electromagnetic simulation workflows: creating or opening CST projects, resolving missing inputs, selecting templates, setting up geometry/materials/ports/boundaries/mesh/solvers/monitors, running or planning simulations, extracting S-parameters/far-field/near-field/eigenmode results, validating outputs, parameter sweeps, optimization handoff, and report generation.

When should I use Cst Simulation Workflow?

Cst Simulation Workflow fits situations like: driving CST Studio Suite through the CST MCP for electromagnetic simulation workflows: creating; opening CST projects; resolving missing inputs; selecting templates.

How do I install Cst Simulation Workflow in Claude Code?

Run `npx skills add Cai-aa/CAE-Agent-Hub --skill cst-simulation-workflow -a claude-code`. Or copy the skill folder (Skill/CST/cst-simulation-workflow in Cai-aa/CAE-Agent-Hub) into .claude/skills/cst-simulation-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Cst Simulation Workflow in Codex?

Run `npx skills add Cai-aa/CAE-Agent-Hub --skill cst-simulation-workflow -a codex`. Or copy the skill folder (Skill/CST/cst-simulation-workflow in Cai-aa/CAE-Agent-Hub) into .agents/skills/cst-simulation-workflow in your project. Codex loads it when a task matches its description.

Can I use Cst Simulation Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Cai-aa/CAE-Agent-Hub --skill cst-simulation-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cst-simulation-workflow, .gemini/skills/cst-simulation-workflow, .github/skills/cst-simulation-workflow and .opencode/skills/cst-simulation-workflow in your project.

What does Cst Simulation Workflow need to run?

SKILL.md names no scripts, command-line tools or credentials: Cst Simulation Workflow is instructions for the agent only.

Does Cst Simulation Workflow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cst Simulation Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cst Simulation Workflow use?

Cst Simulation Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cst Simulation Workflow use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5k tokens, read only when the agent opens those files.

What are the alternatives to Cst Simulation Workflow?

Skills that share tags, products or a category with Cst Simulation Workflow: Adk Docs Writer (BrainDAO/adk-ts, 119 stars), MCP Gateway (tmustier/pi-for-excel, 434 stars), Google Workspace (swarmclawai/swarmclaw, 688 stars) and Workiq Copilot (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cst Simulation Workflow?

Cai-aa (a GitHub user) maintains it in Cai-aa/CAE-Agent-Hub, which has 998 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on September 30, 2026.

Source: Cai-aa/CAE-Agent-Hub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Cst Simulation Workflow

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

CST Simulation Workflow

Operating Modes

Standard Workflow

Reference Files

Input Policy

Execution Rules

Result Rules

V1 Scope

Files

Compare with similar skills

Similar skills

More from Cai-aa/CAE-Agent-Hub

Related

Questions about Cst Simulation Workflow