How do I install the Send To Vdi skill?

Run npx skillmds@latest add yenhao-huang/send-to-vdi in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Send To Vdi safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Send To Vdi?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Send To Vdi free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Send To Vdi?

yenhao-huang (@yenhao-huang) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Send To Vdi by yenhao-huang — Agent Skill

Name: Send To Vdi
Author: yenhao-huang

Send To Vdi

Use when the user asks to send, upload, copy, or transfer a file to VDI using send_to_vdi, including requests mentioning VDI, send_to_vdi, 192.168.1.2, Projects專案, !AI專區, or the fixed VDI image folder. This skill forbids remote-side operations on VDI and requires file transfer through send_to_vdi.

yenhao-huang Updated Sep 21, 2026

File contents

Send To VDI

Required Behavior

When this skill triggers, transfer files only through:

send_to_vdi <argument>

<argument> must come from the user's request. It is usually a file path, filename, or explicit argument string the user wants passed to send_to_vdi.

Local commands are allowed when needed to prepare or identify the file, such as creating a requested small test file, checking that a local file exists, or invoking an interactive shell so the send_to_vdi function is available.

Remote Restrictions

Do not operate commands on the VDI or remote SMB share except through send_to_vdi.

Forbidden remote-side examples include:

Do not use ssh to run commands on VDI.
Do not use direct smbclient commands to browse, list, create, delete, rename, move, chmod, or inspect files on the remote share.
Do not create remote directories.
Do not delete, rename, move, or chmod remote files.
Do not start a remote service or server.
Do not validate the remote folder before or after transfer by running remote commands.
Do not replace send_to_vdi with scp, rsync, curl, direct smbclient, HTTP server transfer, or any other transfer path.

Missing Argument

If the user asks to send something but does not provide the argument to pass to send_to_vdi, ask for the exact argument unless the user also asked you to create the file locally.

Quoting

If the provided argument contains spaces, shell metacharacters, or non-ASCII text, quote it safely while still running only send_to_vdi <argument>.

Examples:

send_to_vdi /tmp2/howard/file.tar.gz
send_to_vdi './file with spaces.tar.gz'

Failure Handling

If send_to_vdi <argument> fails, local diagnosis is allowed. Do not run remote-side commands or use an alternate transfer method unless the user explicitly changes the instruction.

---name: send-to-vdidescription: Use when the user asks to send, upload, copy, or transfer a file to VDI using send_to_vdi, including requests mentioning VDI, send_to_vdi, 192.168.1.2, Projects專案, !AI專區, or the fixed VDI image folder. This skill forbids remote-side operations on VDI and requires file transfer through send_to_vdi.---# Send To VDI## Required BehaviorWhen this skill triggers, transfer files only through:```bashsend_to_vdi <argument>````<argument>` must come from the user's request. It is usually a file path, filename, or explicit argument string the user wants passed to `send_to_vdi`.Local commands are allowed when needed to prepare or identify the file, such as creating a requested small test file, checking that a local file exists, or invoking an interactive shell so the `send_to_vdi` function is available.## Remote RestrictionsDo not operate commands on the VDI or remote SMB share except through `send_to_vdi`.Forbidden remote-side examples include:- Do not use `ssh` to run commands on VDI.- Do not use direct `smbclient` commands to browse, list, create, delete, rename, move, chmod, or inspect files on the remote share.- Do not create remote directories.- Do not delete, rename, move, or chmod remote files.- Do not start a remote service or server.- Do not validate the remote folder before or after transfer by running remote commands.- Do not replace `send_to_vdi` with `scp`, `rsync`, `curl`, direct `smbclient`, HTTP server transfer, or any other transfer path.## Missing ArgumentIf the user asks to send something but does not provide the argument to pass to `send_to_vdi`, ask for the exact argument unless the user also asked you to create the file locally.## QuotingIf the provided argument contains spaces, shell metacharacters, or non-ASCII text, quote it safely while still running only `send_to_vdi <argument>`.Examples:```bashsend_to_vdi /tmp2/howard/file.tar.gzsend_to_vdi './file with spaces.tar.gz'```## Failure HandlingIf `send_to_vdi <argument>` fails, local diagnosis is allowed. Do not run remote-side commands or use an alternate transfer method unless the user explicitly changes the instruction.

Frequently asked questions