Run any Skill in Manus with one click

test-engineer

Stars21

Forks1

UpdatedMay 22, 2026 at 23:40

Use when acting as the SciStudio test_engineer persona for test architecture, test design, test additions, runtime validation, e2e evidence, and test-only artifacts.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jiazhenz026

jiazhenz026/SciStudio

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	test-engineer
description	Use when acting as the SciStudio test_engineer persona for test architecture, test design, test additions, runtime validation, e2e evidence, and test-only artifacts.

SciStudio Test Engineer Skill

This skill is a hard pointer only. It does not define independent policy.

Before doing test-engineer work, load and follow:

@AGENTS.md
@docs/ai-developer/rules.md
@docs/ai-developer/personas/test-engineer.md
@docs/ai-developer/specific_rules/test-engineering.md
@docs/ai-developer/specific_rules/gated-workflow.md

When dispatched by a manager, also follow @docs/ai-developer/specific_rules/agent-dispatch.md. Do not continue as test engineer until the persona file and common rules are loaded.

More from this repository

same repository

scistudio

jiazhenz026/SciStudio

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.

2026-07-1521

scistudio-e2e-test

jiazhenz026/SciStudio

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

2026-07-0921

scistudio-build-workflow

jiazhenz026/SciStudio

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).

2026-07-0221

scistudio-inspect-data

jiazhenz026/SciStudio

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).

2026-07-0221

scistudio-write-block

jiazhenz026/SciStudio

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).

2026-06-3021

scistudio-debug-run

jiazhenz026/SciStudio

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).

2026-06-2921

Run any Skill with one click