메뉴
Use when running a live end-to-end SciStudio session — driving the GUI in Chrome via Chrome MCP, verifying a PR before merge, reproducing a hotfix bug live, or any time the user says "跑 e2e", "do an e2e", "verify in Chrome", "run e2e on PR
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Base identity for the SciStudio embedded agent. Lists the 6 task skills available and when to invoke each. Loaded once at session start; task skills load on demand when the user turn matches their trigger description.
Drive a live end-to-end SciStudio session — start the backend (and Vite if needed), open Chrome via Chrome MCP, walk the scenario file the user points at, capture screenshots/console/network as evidence, and write a pass/fail verdict back into that file. Trigger whenever the user says "跑 e2e", "do an e2e", "run e2e on PR
Use when the user wants to design a new workflow, choose block types, wire edges between blocks, or convert a verbal pipeline description into a valid workflow YAML. NOT for debugging existing runs (use scistudio-debug-run) or for writing custom blocks (use scistudio-write-block).
Use when the user wants to look at intermediate or output data — preview a slice of an image, peek at the first rows of a DataFrame, check the shape/dtype of an array, or trace where a data ref came from. NOT for debugging failed runs (use scistudio-debug-run).
Use when the user wants to author a NEW BLOCK FILE — Python source code (a class subclassing Block / ProcessBlock / IOBlock / AppBlock / CodeBlock with typed ports and a config_schema) that goes in ``<project>/blocks/<name>.py``. ALWAYS check if an existing block satisfies the contract first (call list_blocks first and reuse a match). NOT for ADDING AN EXISTING BLOCK TYPE AS A NODE in a workflow YAML — that's scistudio-build-workflow ("add an imaging.threshold node to my workflow"). NOT for editing an existing block's config (update_block_config). NOT for writing the workflow YAML itself (scistudio-build-workflow).
Use when a workflow run has failed, is stuck, or produced unexpected output, and you need to diagnose the cause. Covers run-status inspection, block-log retrieval, lineage navigation, common error signatures, and the finish_ai_block contract for AI block PTYs. NOT for designing new workflows (use scistudio-build-workflow).
| name | scistudio-e2e-test |
| description | Use when running a live end-to-end SciStudio session — driving the GUI in Chrome via Chrome MCP, verifying a PR before merge, reproducing a hotfix bug live, or any time the user says "跑 e2e", "do an e2e", "verify in Chrome", "run e2e on PR |
This skill is a hard pointer only. It does not define independent policy.
Before doing e2e work, load and follow:
The Chrome MCP recipes, dev-server lifecycle, screenshot recipes, and
final report template live alongside the canonical SKILL.md under
docs/ai-developer/skills/scistudio-e2e-test/references/. Read whichever
reference the current step needs.
Do not continue as the e2e tester until the canonical SKILL.md and the scenario template are loaded.
