Run any Skill in Manus with one click

$pwd:

tuyaopen-env-setup

Name: Tuyaopen Env Setup
Author: tuya

// Set up and activate the TuyaOpen development environment, install system dependencies, and initialize tos.py. Use when the user mentions environment setup, activating the SDK, installing dependencies, export.sh, or when tos.py is not found. 环境搭建、环境初始化、激活开发环境、安装依赖。

Run Skill in Manus

$ git log --oneline --stat

stars:7

forks:1

updated:May 26, 2026 at 03:42

File Explorer

4 files

SKILL.md

readonly

name	tuyaopen/env-setup
description	Set up and activate the TuyaOpen development environment, install system dependencies, and initialize tos.py. Use when the user mentions environment setup, activating the SDK, installing dependencies, export.sh, or when tos.py is not found. 环境搭建、环境初始化、激活开发环境、安装依赖。
license	Apache-2.0
compatibility	["Ubuntu/Debian with apt-get (or macOS/Windows equivalent)","Python >= 3.6","git >= 2.0, cmake >= 3.28, make >= 3.0, ninja >= 1.6"]

TuyaOpen Environment Setup

Docs: https://tuyaopen.ai/docs/quick-start/enviroment-setup

Step 0: Check if already activated (do this first)

Variable	Set by activation	Meaning
`$OPEN_SDK_ROOT`	yes	SDK root path
`$OPEN_SDK_PYTHON`	yes	venv Python executable
`$VIRTUAL_ENV`	yes	active venv path

Linux / macOS:

if [ -n "$OPEN_SDK_ROOT" ] && [ -n "$VIRTUAL_ENV" ]; then
    echo "Already activated"
else
    cd "$(git rev-parse --show-toplevel)" && . ./export.sh
fi

Windows PowerShell:

if ($env:OPEN_SDK_ROOT -and $env:VIRTUAL_ENV) {
    Write-Host "Already activated"
} else {
    Set-Location (git rev-parse --show-toplevel); . .\export.ps1
}

Windows CMD:

if defined OPEN_SDK_ROOT if defined VIRTUAL_ENV (echo Already activated) else (
    for /f "delims=" %%i in ('git rev-parse --show-toplevel') do cd /d "%%i"
    call export.bat
)

Step 1: Install system dependencies

Ubuntu / Debian:

sudo apt-get install lcov cmake-curses-gui build-essential ninja-build \
    wget git python3 python3-pip python3-venv libc6-i386 libsystemd-dev

macOS / Windows: see official docs linked above.

Step 2: Activate

Run once per terminal session from the SDK root:

. ./export.sh      # Linux / macOS
.\export.ps1       # Windows PowerShell
export.bat         # Windows CMD

After activation: $OPEN_SDK_ROOT, $OPEN_SDK_PYTHON, $OPEN_SDK_PIP are set; SDK root is in PATH.

Step 3: Verify

tos.py version    # e.g. v1.3.0-23-g6bcb5aa
tos.py check      # validates tool versions + runs git submodule update --init

Or run the bundled check script:

Platform	Command
Linux / macOS	`.agents/skills/tuyaopen/env-setup/scripts/check_env.sh`
Windows CMD	`.agents\skills\tuyaopen\env-setup\scripts\check_env.bat`
Windows PowerShell	`.agents/skills/tuyaopen/env-setup/scripts/check_env.ps1`

Troubleshooting

Symptom	Fix
`python3-venv` missing	`sudo apt-get install python3-venv`
Activation fails, `.venv/` exists	`rm -rf .venv/ && . ./export.sh`
`tos.py: command not found`	Re-run `. ./export.sh`
Submodule download fails	`git submodule update --init`
`[Unknown version]`	No git tags — harmless

related-skills.json

same repository

tuyaopen-code-check.md

from "tuya/TuyaOpen-dev-skills"

2026-05-267

tuyaopen-dev-loop.md

from "tuya/TuyaOpen-dev-skills"

Automated build-flash-monitor-analyze development loop for TuyaOpen devices. Covers log analysis, error patterns, CLI testing, and iterative debugging. Use when the user mentions dev loop, automated testing, log analysis, debug cycle, iterative development, or CI loop. 开发闭环、自动化测试、日志分析、调试循环、迭代开发。

2026-05-267

tuyaopen-debug-helper.md

from "tuya/TuyaOpen-dev-skills"

Agent-friendly non-blocking serial log capture for TuyaOpen devices. Runs tos.py monitor in the background, writes logs to file, and lets the agent tail or stop it at any time. Use when the agent needs to capture device logs without blocking, run a debug session, or monitor UART output during a build-flash-analyze loop. 后台串口日志、非阻塞监控、设备日志捕获、agent日志分析。

2026-05-267

tuyaopen-add-board.md

from "tuya/TuyaOpen-dev-skills"

Add new board (BSP) support to TuyaOpen, including board directory structure, Kconfig, drivers, and config files. Use when the user mentions adding a board, new board, BSP, board support, hardware adaptation, or tos.py new board. 添加开发板、板级适配、新增BSP、硬件适配。

2026-05-267

tuyaopen-build.md

from "tuya/TuyaOpen-dev-skills"

Build and compile TuyaOpen projects, select build configurations, edit Kconfig options, clean artifacts, and run Linux ELF binaries. Use when the user mentions compiling, building, tos.py build, config choice, menuconfig, Kconfig, build error, or running a project. 项目编译、构建、编译配置、清理编译、编译错误、menuconfig、Kconfig。

2026-05-267

tuyaopen-device-auth.md

from "tuya/TuyaOpen-dev-skills"

Configure device authorization credentials (UUID, AuthKey, PID) and network provisioning for TuyaOpen devices. Use when the user mentions device auth, authorization, UUID, AuthKey, tuya_config.h, provisioning, pairing, or cloud connection. 设备授权、授权码、配网、UUID、AuthKey、云连接。

2026-05-267

package.json

"author": "tuya"

"repository": "tuya/TuyaOpen-dev-skills"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Network and Computer Systems AdministratorsComputer and Mathematical Occupations15-1244L4

name	tuyaopen/env-setup
description	Set up and activate the TuyaOpen development environment, install system dependencies, and initialize tos.py. Use when the user mentions environment setup, activating the SDK, installing dependencies, export.sh, or when tos.py is not found. 环境搭建、环境初始化、激活开发环境、安装依赖。
license	Apache-2.0
compatibility	["Ubuntu/Debian with apt-get (or macOS/Windows equivalent)","Python >= 3.6","git >= 2.0, cmake >= 3.28, make >= 3.0, ninja >= 1.6"]

TuyaOpen Environment Setup

Docs: https://tuyaopen.ai/docs/quick-start/enviroment-setup

Step 0: Check if already activated (do this first)

Variable	Set by activation	Meaning
`$OPEN_SDK_ROOT`	yes	SDK root path
`$OPEN_SDK_PYTHON`	yes	venv Python executable
`$VIRTUAL_ENV`	yes	active venv path

Linux / macOS:

if [ -n "$OPEN_SDK_ROOT" ] && [ -n "$VIRTUAL_ENV" ]; then
    echo "Already activated"
else
    cd "$(git rev-parse --show-toplevel)" && . ./export.sh
fi

Windows PowerShell:

if ($env:OPEN_SDK_ROOT -and $env:VIRTUAL_ENV) {
    Write-Host "Already activated"
} else {
    Set-Location (git rev-parse --show-toplevel); . .\export.ps1
}

Windows CMD:

if defined OPEN_SDK_ROOT if defined VIRTUAL_ENV (echo Already activated) else (
    for /f "delims=" %%i in ('git rev-parse --show-toplevel') do cd /d "%%i"
    call export.bat
)

Step 1: Install system dependencies

Ubuntu / Debian:

sudo apt-get install lcov cmake-curses-gui build-essential ninja-build \
    wget git python3 python3-pip python3-venv libc6-i386 libsystemd-dev

macOS / Windows: see official docs linked above.

Step 2: Activate

Run once per terminal session from the SDK root:

. ./export.sh      # Linux / macOS
.\export.ps1       # Windows PowerShell
export.bat         # Windows CMD

After activation: $OPEN_SDK_ROOT, $OPEN_SDK_PYTHON, $OPEN_SDK_PIP are set; SDK root is in PATH.

Step 3: Verify

tos.py version    # e.g. v1.3.0-23-g6bcb5aa
tos.py check      # validates tool versions + runs git submodule update --init

Or run the bundled check script:

Platform	Command
Linux / macOS	`.agents/skills/tuyaopen/env-setup/scripts/check_env.sh`
Windows CMD	`.agents\skills\tuyaopen\env-setup\scripts\check_env.bat`
Windows PowerShell	`.agents/skills/tuyaopen/env-setup/scripts/check_env.ps1`

Troubleshooting

Symptom	Fix
`python3-venv` missing	`sudo apt-get install python3-venv`
Activation fails, `.venv/` exists	`rm -rf .venv/ && . ./export.sh`
`tos.py: command not found`	Re-run `. ./export.sh`
Submodule download fails	`git submodule update --init`
`[Unknown version]`	No git tags — harmless

tuyaopen-env-setup

TuyaOpen Environment Setup

Step 0: Check if already activated (do this first)

Step 1: Install system dependencies

Step 2: Activate

Step 3: Verify

Troubleshooting

More from this repository

More from this repository

TuyaOpen Environment Setup

Step 0: Check if already activated (do this first)

Step 1: Install system dependencies

Step 2: Activate

Step 3: Verify

Troubleshooting