القائمة
SSH into the Windows 11 ARM64 test VM for PowerShell-based checks (e.g. gitlab-lsp Windows regression tests). Manual-invoke only.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate a standalone HTML report from a markdown file with d2 diagrams, SVGs, and syntax-highlighted code blocks. Use when the user asks for a report, a visual writeup, or a document with diagrams.
Interact with GitLab REST API using GITLAB_TOKEN - use for TODOs, repositories, CI/pipelines, MRs, issues, and other API queries
GitLab Development Kit is a folder and set of utilities that contain most of the GitLab production systems. This skill is useful for testing with local GitLab deployment and when researching how feature works in the GitLab monolith, AIGW, workhorse and other services
CRUD GitLab issues,MRs,pipelines,jobs,epics,issue comments
my projects — gitlab namespace and ID, where they live on the local drive. Use whenever a question references a project by name, alias, or path, or when you need to locate a repo locally. Keywords - project, repo, where does X live, local path, gitlab-lsp, glab, cli, vscode extension, note, task, duo cli, dotfiles.
code changes review, use this skill any time I ask you to review a change
| name | windows-testing |
| description | SSH into the Windows 11 ARM64 test VM for PowerShell-based checks (e.g. gitlab-lsp Windows regression tests). Manual-invoke only. |
| disable-model-invocation | true |
Personal skill for driving the Windows 11 ARM64 test VM (UTM/Parallels) from
macOS over SSH. The VM runs OpenSSH Server with PowerShell as the default
remote shell. It's typically used for gitlab-lsp Windows regression checks
(e.g. the MCP SDK upgrade windowsHide test in
~/workspace/test/test-mcp/windows/).
ssh <vm-user>@<vm-ip> # interactive PowerShell
ssh -t <vm-user>@<vm-ip> # allocate TTY (required for TUIs like duo)
ssh <vm-user>@<vm-ip> 'powershell-command' # one-shot command
Check reachability with ssh or Test-NetConnection -Port 22 — not
ping: Windows Firewall blocks ICMP by default even when TCP/22 is open.
If the VM's IP/hostname or user isn't known, ask the user — it varies per machine and isn't stored in this skill.
cd to the checkout (e.g.
C:\Users\<user>\workspace\test-mcp)..\windows\mcp-test.ps1).ssh -t and run duo's
non-interactive one-shot mode (PowerShell stdin into a TUI is
unreliable — prefer duo run -g "..." over interactive sessions).Native Windows builds often fail on unrelated toolchain issues. The
standard workaround is to build on macOS and scp the artifacts in:
scp <files> <vm-user>@<vm-ip>:C:/Users/<vm-user>/AppData/Local/Temp/...
Forward slashes work in scp destinations even on Windows.
HKLM:\SOFTWARE\OpenSSH\DefaultShell)..ps1 files need a UTF-8 BOM or they're read as ANSI by PowerShell 5.1..gitattributes in test repos forces CRLF for *.ps1 — run
git add --renormalize . if a script suddenly fails to parse.See references/windows-ssh-setup.md for the one-time OpenSSH Server +
key-auth + default-shell configuration on the Windows VM, plus the
matching macOS ~/.ssh/config entry.