tizen-create-emulator
Tizen create emulator, 타이젠 에뮬레이터 생성, custom emulator, 커스텀 에뮬레이터, em-cli, 에뮬레이터 만들기, 에뮬레이터 VM 생성, emulator VM create, 에뮬레이터 사이즈, 에뮬레이터 해상도, emulator size, emulator resolution, 1080 에뮬레이터, 720 에뮬레이터, list platforms, list emulator templates, 에뮬레이터 템플릿, list VMs, list emulators, available emulators, 에뮬레이터 목록, delete emulator, 에뮬레이터 삭제, TV 에뮬레이터 생성, Samsung TV emulator create. Use this skill to CREATE a custom Tizen emulator VM with a user-selected screen size (default 1080) plus configurable platform and profile via em-cli. Lists screen sizes/platforms/templates/VMs, creates and deletes VMs. ANY "list the available / existing emulators" request ROUTES HERE — it is `list-vm --detail`, never a manual search or a raw em-cli call; report each VM's `profile` from the envelope (tizen-* is the unified tizen profile, not Mobile). Templates here are EMULATOR VM templates — for APP/project templates, use tizen-create-project instead. For LAUNCHING (booting) an existing emulator VM, use tizen-launch-
Samsung Electronics · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Samsung/tizen-agent-skills --skill tizen-create-emulator技能说明
name: tizen-create-emulator
description: Tizen create emulator, 타이젠 에뮬레이터 생성, custom emulator, 커스텀 에뮬레이터, em-cli, 에뮬레이터 만들기, 에뮬레이터 VM 생성, emulator VM create, 에뮬레이터 사이즈, 에뮬레이터 해상도, emulator size, emulator resolution, 1080 에뮬레이터, 720 에뮬레이터, list platforms, list emulator templates, 에뮬레이터 템플릿, list VMs, list emulators, available emulators, 에뮬레이터 목록, delete emulator, 에뮬레이터 삭제, TV 에뮬레이터 생성, Samsung TV emulator create. Use this skill to CREATE a custom Tizen emulator VM with a user-selected screen size (default 1080) plus configurable platform and profile via em-cli. Lists screen sizes/platforms/templates/VMs, creates and deletes VMs. ANY "list the available / existing emulators" request ROUTES HERE — it is list-vm --detail, never a manual search or a raw em-cli call; report each VM's profile from the envelope (tizen-* is the unified tizen profile, not Mobile). Templates here are EMULATOR VM templates — for APP/project templates, use tizen-create-project instead. For LAUNCHING (booting) an existing emulator VM, use tizen-launch-emulator instead.
metadata:
author: Samsung Electronics
last-updated: "2026-10-14"
keywords:
- Tizen create emulator
- custom emulator
- em-cli
- 에뮬레이터 생성
- 커스텀 에뮬레이터
- emulator VM
- list platform
- list template
- list VMs
- list emulators
- available emulators
- 에뮬레이터 목록
- delete emulator
- TV 에뮬레이터
Step 1 (create only): ask the user which screen size — MANDATORY
⚠️ CRITICAL: For the create action you MUST ask the user which screen size via
AskUserQuestion, and you MUST NOT run create until they have answered.
Running create without having asked is a bug — the whole point of this step is that
the user picks the size. This applies to EVERY create request, including bare ones like
"에뮬레이터 생성해줘" / "create an emulator".
This is enforced by the runner, not just by this document. create without --size
returns a user_input_required failure whose message already lists the supported sizes —
so if you forget to ask, you get the size menu back instead of a VM. Ask the user with
that menu, then re-run with --size.
The 1080 default is NOT permission to skip the question. It is the option you pre-select inside the question. "The user didn't mention a size" is the case this step exists for — it is not a reason to proceed. Never auto-pick, never assume, never "just use the default and mention it afterwards".
--assume-defaultsexists to use 1080 without asking. It is for non-interactive callers only (scripts, CI). If you have the AskUserQuestion tool, using it is a bug — ask instead.
The ONLY cases where you skip the question:
- The user's own message already named a size ("720 에뮬레이터 만들어줘", "3840으로 만들어줘") → pass that size straight through with
--size. - The user provided a raw disk image path (
--raw-image-path) → the disk image determines the VM, so size/template selection is skipped entirely. Do NOT ask for a size in this case.
Resolution is a property of the emulator's device template — em-cli create has no
width/height flag — so the size list must come from the SDK, not from memory.
-
Run the
list-templateaction for the target profile (see the CLI Runner section below for the runner path). This is the FIRST command you run for a create request — beforelist-vm, before anything else:node "$CLI" list-template --profile tizen # or --profile tvresult.template_detailsgives{name, profile, resolution, size, ram}per template, andresult.available_sizesthe bare size keys (e.g.["1080", "720"]). -
Present those sizes with AskUserQuestion, one option per size, each showing the resolution — e.g.
1080 — 1920x1080 (HD1080 Tizen). List1080first and label it(기본값/Recommended). Only present sizes the SDK actually reported; never invent one. If the SDK reported only one size, you may proceed with it without asking. -
Create with the chosen size:
--size <chosen>.
If the user answers "아무거나" / "기본으로" to your question, that IS an answer — use
--size 1080. The difference from skipping is that they were asked.
Claude Code (서브에이전트 위임)
Agent tool이 없으면 (예: Cline) 아래 "CLI Runner" 섹션으로 가세요.
- ⚠️ 필수: 먼저 위 Step 1대로 AskUserQuestion으로 사용자에게 사이즈를 물어보세요. 서브에이전트에는 AskUserQuestion tool이 없으므로, 사이즈 선택은 호출자(당신)의 책임입니다. 물어보지 않고 서브에이전트에 위임하면 사용자는 선택 기회를 영구히 잃습니다 — 이는 버그입니다.
- Agent tool로
tizen-create-emulator에이전트 호출 (개인 배포 또는tizen-sdk-skills:tizen-create-emulator) - 사용자의 요청 + 선택된 사이즈를 프롬프트로 전달 (예: "my-vm 이름으로 720 사이즈 에뮬레이터 생성")
- 서브에이전트의 JSON Envelope를 그대로 사용자에게 전달 — 아래 "결과 보고" 규칙을 따른다
(fenced
json블록으로 원문을 싣고, 그 아래 요약은 1~2줄만)
CLI Runner (Cline / Claude Code)
Pick the ONE block for the shell your terminal / tool runs — the prompt tells you: $ is Bash (Linux, macOS, Claude Code's Git Bash on Windows, Codex on Linux / macOS) → Bash block; PS C:\…> is PowerShell (Codex on Windows, Cline PowerShell terminal) → PowerShell block; C:\…> is cmd.exe (Cline cmd.exe terminal) → cmd.exe block. Run that block as-is: a block pasted into another shell, or wrapped in powershell -Command "…", is a parse error.
**Run the node line exactly as written and read the JSON envelope it prints to stdout. Do NOT redirect or capture the output (> file, 2>&1 | tee, Out-File, | Out-String), do NOT wrap the line in cmd /c, powershell -Command "…" or any second shell, and do NOT mix shell dialects: %TEMP% and 2>nul are cmd.exe only, $env:TEMP and Out-File are PowerShell only — in the other shell they are literal text or a parse error. A tool message that the command's completion or output "could not be observed / captured" means the terminal is still busy with an earlier command or its shell-integration hooks have broken, not that the runner failed: open a NEW terminal and re-run the SAME line unchanged. Runners that drive em-cli, sdb or a JVM