Run E2E Tests
microsoft/vscode-python-environments
Run E2E tests to verify complete user workflows like environment discovery, creation, and selection.
Run and debug the Blockless VS Code extension release gate: CI-equivalent API and extension tests, V0 protocol smoke, live DeepSeek full-stack e2e, VSIX packaging, local reinstall, direct…
$ npx skills add FreakStudioCN/mpy-hardware-extension --skill blockless-extension-e2e -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FreakStudioCN/mpy-hardware-extension blockless-extension-e2e --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FreakStudioCN/mpy-hardware-extension.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/blockless-extension-e2e .claude/skills/blockless-extension-e2e && rm -rf skills-srcUse ~/.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/
Install the "blockless-extension-e2e" agent skill from https://github.com/FreakStudioCN/mpy-hardware-extension/tree/main/.agents/skills/blockless-extension-e2e into .claude/skills/blockless-extension-e2e/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blockless-extension-e2e", 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 install https://github.com/FreakStudioCN/mpy-hardware-extension/tree/main/.agents/skills/blockless-extension-e2eType 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.
$ npx skills add FreakStudioCN/mpy-hardware-extension --skill blockless-extension-e2e -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FreakStudioCN/mpy-hardware-extension blockless-extension-e2e --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FreakStudioCN/mpy-hardware-extension.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/blockless-extension-e2e .agents/skills/blockless-extension-e2e && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "blockless-extension-e2e" agent skill from https://github.com/FreakStudioCN/mpy-hardware-extension/tree/main/.agents/skills/blockless-extension-e2e into .agents/skills/blockless-extension-e2e/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blockless-extension-e2e", 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.
$ npx skills add FreakStudioCN/mpy-hardware-extension --skill blockless-extension-e2e -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FreakStudioCN/mpy-hardware-extension blockless-extension-e2e --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FreakStudioCN/mpy-hardware-extension.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/blockless-extension-e2e .cursor/skills/blockless-extension-e2e && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "blockless-extension-e2e" agent skill from https://github.com/FreakStudioCN/mpy-hardware-extension/tree/main/.agents/skills/blockless-extension-e2e into .cursor/skills/blockless-extension-e2e/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blockless-extension-e2e", 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 https://github.com/FreakStudioCN/mpy-hardware-extension.git --path .agents/skills/blockless-extension-e2e--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FreakStudioCN/mpy-hardware-extension --skill blockless-extension-e2e -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FreakStudioCN/mpy-hardware-extension blockless-extension-e2e --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FreakStudioCN/mpy-hardware-extension.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/blockless-extension-e2e .gemini/skills/blockless-extension-e2e && rm -rf skills-srcUse ~/.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/
Install the "blockless-extension-e2e" agent skill from https://github.com/FreakStudioCN/mpy-hardware-extension/tree/main/.agents/skills/blockless-extension-e2e into .gemini/skills/blockless-extension-e2e/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blockless-extension-e2e", 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.
$ gh skill install FreakStudioCN/mpy-hardware-extension blockless-extension-e2eInstalls 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).
$ npx skills add FreakStudioCN/mpy-hardware-extension --skill blockless-extension-e2e -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FreakStudioCN/mpy-hardware-extension.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/blockless-extension-e2e .github/skills/blockless-extension-e2e && rm -rf skills-srcUse ~/.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/
Install the "blockless-extension-e2e" agent skill from https://github.com/FreakStudioCN/mpy-hardware-extension/tree/main/.agents/skills/blockless-extension-e2e into .github/skills/blockless-extension-e2e/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blockless-extension-e2e", 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.
$ npx skills add FreakStudioCN/mpy-hardware-extension --skill blockless-extension-e2e -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FreakStudioCN/mpy-hardware-extension blockless-extension-e2e --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FreakStudioCN/mpy-hardware-extension.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/blockless-extension-e2e .opencode/skills/blockless-extension-e2e && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "blockless-extension-e2e" agent skill from https://github.com/FreakStudioCN/mpy-hardware-extension/tree/main/.agents/skills/blockless-extension-e2e into .opencode/skills/blockless-extension-e2e/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blockless-extension-e2e", 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.
blockless-extension-e2eRun and debug the Blockless VS Code extension release gate: CI-equivalent API and extension tests, V0 protocol smoke, live DeepSeek full-stack e2e, VSIX packaging, local reinstall, direct…
Blockless Extension E2E is an agent skill from FreakStudioCN/mpy-hardware-extension. Run and debug the Blockless VS Code extension release gate: CI-equivalent API and extension tests, V0 protocol smoke, live DeepSeek full-stack e2e, VSIX packaging, local reinstall, direct push-to-main verification, and GitHub Actions follow-up. Use when working in cursorforhardware/mpy-hardware-extension, when CI is failing, when the user asks to run e2e, push main, reinstall the plugin, or verify the extension against docs without editing extension docs.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `agents/openai.yaml`).
It sits in Testing & QA, covering End-to-end testing. It works with DeepSeek, GitHub Actions, Visual Studio Code and npm.
9 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit b661df6. It shows what the files ask for, not the result of running them.
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.
Ships 1 file in scripts/ (PowerShell), which the agent can run.
Shell commands in SKILL.md call:
npmgitnodepythonghFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm, git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
DEEPSEEK_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Blockless Extension E2E loads about 1.2k tokens when it runs. Until then it costs about 121 tokens; SKILL.md has 459 words of instructions outside code blocks.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
If API pytest fails only when `.env` was loaded, compare with CI environment before changing code. The dev `.env` may co:<port>` with env loaded from `mpyhw-api/.env`.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); the scripts in this folder are not scanned.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 459 words (~1,200 tokens).
“Use the bundled script for repeatable execution:”
SKILL.md and 2 other files (scripts) in .agents/skills/blockless-extension-e2e of FreakStudioCN/mpy-hardware-extension.
Open the folder on GitHubat commit b661df6
Blockless Extension E2E 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Blockless Extension E2E this skillFreakStudioCN/mpy-hardware-extension | 132 | — | ~1.2k | Automated safety check: Notes | Custom licence | |
| Run E2E Testsmicrosoft/vscode-python-environments | 141 | — | ~1.2k | Automated safety check: Pass | MIT | |
| OpenHarness End-to-End EvalsHKUDS/OpenHarness | 16k | 1 repos | ~2.1k | Automated safety check: Notes | MIT | |
| RStudio Selenium to Playwright Migrationrstudio/rstudio | 5.1k | — | ~3.6k | Automated safety check: Pass | Custom licence | |
| Simple Modern Uvjlevy/simple-modern-uv | 301 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Py Package Checkipea/geobr | 959 | — | ~1.4k | Automated safety check: Notes | None |
microsoft/vscode-python-environments
Run E2E tests to verify complete user workflows like environment discovery, creation, and selection.
HKUDS/OpenHarness
Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.
rstudio/rstudio
Converts RStudio Python Selenium electron tests into TypeScript Playwright tests, checking each against a live RStudio before counting it as migrated.
jlevy/simple-modern-uv
Start, selectively modernize, fully migrate, or update Python projects using simple-modern-uv practices: uv, ruff, BasedPyright, pytest, GitHub Actions CI, and tag-driven PyPI publishing.
ipea/geobr
Run the Python package release gate for geobr — sync the locked environment, run the offline and network test suites, build the distribution, and review the source against the Python conventions.
Prism-Shadow/model-message-stream-protocol
Fixed workflow for developing MMSP itself — adding or updating model support, and changing its pages.
FreakStudioCN/mpy-hardware-extension
用户报告 Blockless 扩展在云端实测时出问题(卡死/灰屏/跳步/构建失败),但本地复现不了、日志不在本地文件里时,用这个从云端托管数据库拉真实 session 定位症状与根因 / Use when a user reports an in-product Blockless bug from live cloud-backend testing and the real session…
FreakStudioCN/mpy-hardware-extension
A skill your agent uses when reviewing the open pull requests in this repo (mpy-hardware-extension / blockless extension) — "review the PRs", "review PRs with codex", triaging open PRs, gating PRs…
FreakStudioCN/mpy-hardware-extension
用本地前端插件连云端后端做端到端测试 / test the local VS Code extension against the deployed cloud backend.
FreakStudioCN/mpy-hardware-extension
启动 Blockless 本地开发栈 / bring up the local dev stack. An agent skill from FreakStudioCN/mpy-hardware-extension.
FreakStudioCN/mpy-hardware-extension
发布 Blockless VS Code 扩展到 Visual Studio Marketplace(含发布前测试)/ ship the Blockless extension to the VS Code Marketplace.
FreakStudioCN/mpy-hardware-extension
发布 Blockless VS Code 扩展的预检 + MS Marketplace 那一半 / preflight and the MS Marketplace half of shipping the Blockless extension.
Categories
Run and debug the Blockless VS Code extension release gate: CI-equivalent API and extension tests, V0 protocol smoke, live DeepSeek full-stack e2e, VSIX packaging, local reinstall, direct…. Blockless Extension E2E is an agent skill from FreakStudioCN/mpy-hardware-extension. Run and debug the Blockless VS Code extension release gate: CI-equivalent API and extension tests, V0 protocol smoke, live DeepSeek full-stack e2e, VSIX packaging, local reinstall, direct push-to-main verification, and GitHub Actions follow-up.
Blockless Extension E2E fits situations like: working in cursorforhardware/mpy-hardware-extension; the user asks to run e2e; reinstall the plugin; verify the extension against docs without editing extension docs.
Run `npx skills add FreakStudioCN/mpy-hardware-extension --skill blockless-extension-e2e -a claude-code`. Or copy the skill folder (.agents/skills/blockless-extension-e2e in FreakStudioCN/mpy-hardware-extension) into .claude/skills/blockless-extension-e2e in your project. Claude Code loads it when a task matches its description.
Run `npx skills add FreakStudioCN/mpy-hardware-extension --skill blockless-extension-e2e -a codex`. Or copy the skill folder (.agents/skills/blockless-extension-e2e in FreakStudioCN/mpy-hardware-extension) into .agents/skills/blockless-extension-e2e in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FreakStudioCN/mpy-hardware-extension --skill blockless-extension-e2e -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blockless-extension-e2e, .gemini/skills/blockless-extension-e2e, .github/skills/blockless-extension-e2e and .opencode/skills/blockless-extension-e2e in your project.
Going by SKILL.md and its folder, Blockless Extension E2E needs PowerShell for the scripts in its folder, the command-line tools its instructions call (npm, git, node, python and gh) and credentials named DEEPSEEK_API_KEY. Our summary lists: Python 3; PowerShell; Docker; A credential in DEEPSEEK_API_KEY.
SKILL.md contains no URLs. Its commands use npm, git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Blockless Extension E2E has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Blockless Extension E2E: Run E2E Tests (microsoft/vscode-python-environments, 141 stars), OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars), RStudio Selenium to Playwright Migration (rstudio/rstudio, 5.1k stars) and Simple Modern Uv (jlevy/simple-modern-uv, 301 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
FreakStudioCN (a GitHub organization) maintains it in FreakStudioCN/mpy-hardware-extension, which has 132 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 28, 2026.
Source: FreakStudioCN/mpy-hardware-extension on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.