Agent skill

Wispterm Notify Setup

by xuzhougeng in xuzhougeng/wispterm

A skill your agent uses when the user wants to install, repair, or re-apply WispTerm notification reminders (Claude Code Stop + Notification, and Codex turn-complete) in a local…

MITAuto-check passed

Install Wispterm Notify Setup

skills CLI
$ npx skills add xuzhougeng/wispterm --skill wispterm-notify-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install xuzhougeng/wispterm wispterm-notify-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/xuzhougeng/wispterm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/skills/wispterm-notify-setup .claude/skills/wispterm-notify-setup && rm -rf skills-src

Use ~/.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/

Facts

Skill name
wispterm-notify-setup
GitHub stars
443
Token cost
~1.3k tokens
SKILL.md length
638 words
Files
8 (incl. scripts)
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user wants to install, repair, or re-apply WispTerm notification reminders (Claude Code Stop + Notification, and Codex turn-complete) in a local…

  • Works in 4 steps: Determine the target from the user's… → Install using the target-specific… → Relay what it changed: the notify… → …
  • The user wants to install
  • SKILL.md covers Overview, Workflow, WeChat forwarding (optional) and Notes
  • Runs PowerShell and Shell scripts from its folder; calls claude

What it does

Wispterm Notify Setup is an agent skill from xuzhougeng/wispterm. Use when the user wants to install, repair, or re-apply WispTerm notification reminders (Claude Code Stop + Notification, and Codex turn-complete) in a local WSL/macOS/Linux/PowerShell shell or a saved WispTerm SSH profile, so finishes and confirmation prompts surface inside WispTerm.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts (for example `agents/openai.yaml`, `scripts/install-wispterm-notify.sh` and `scripts/test-install.sh`).

It works with macOS, PowerShell and Linux. The repository describes itself as: A cross-platform terminal workspace for remote development and AI agent workflows, powered by libghostty-vt. The licence is MIT.

When your agent uses it

  • The user wants to install
  • Re-apply WispTerm notification reminders (Claude Code Stop + Notification
  • Codex turn-complete) in a local WSL/macOS/Linux/PowerShell shell
  • A saved WispTerm SSH profile

Example prompts

  • “/wispterm-notify-setup”

Requirements

  • A Bash shell
  • PowerShell

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Determine the target from the user's words and WispTerm state.
  2. Install using the target-specific transfer path.
  3. Relay what it changed: the notify program path
  4. Verify — run the printed test command and ask the user to confirm they saw a

What it can do on your machine

Read from SKILL.md and the folder at commit 4168f80. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Ships 6 files in scripts/ (PowerShell and Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • claude

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Wispterm Notify Setup loads about 1.3k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 638 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~77
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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.

SKILL.md

The full file from xuzhougeng/wispterm at commit 4168f80, republished under its MIT licence (© xuzhougeng). 638 words, ~1,349 tokens.

Download SKILL.mdSave it as .claude/skills/wispterm-notify-setup/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
wispterm-notify-setup
description
Use when the user wants to install, repair, or re-apply WispTerm notification reminders (Claude Code Stop + Notification, and Codex turn-complete) in a local WSL/macOS/Linux/PowerShell shell or a saved WispTerm SSH profile, so finishes and confirmation prompts surface inside WispTerm.

WispTerm Notify Setup

Overview

Install a small notifier that makes Claude Code and Codex surface a WispTerm notification (OSC 777 toast + terminal bell badge) when a turn finishes or a confirmation is needed. The notifier is agent-agnostic and the installers are idempotent — safe to re-run.

Workflow

  1. Determine the target from the user's words and WispTerm state.

    • If the user names an existing WispTerm tab/server/profile (for example CPU3), call terminal_list first and match by title/kind.
    • If a saved SSH profile is named but no SSH tab is already open, call ssh_profile_connect {"profile_name":"<name>"} and use the returned surface_id.
    • Never ask the user to re-provide SSH host/user/port/password when the target is an existing saved WispTerm profile. Ask only if the profile is missing or authentication fails.
  2. Install using the target-specific transfer path.

    • Local POSIX / macOS / WSL: copy the bundled POSIX scripts directly to the target shell, then run:

      bash
      sh ./install-wispterm-notify.sh

      When targeting an already-open WSL surface, use wsl_session_exec to run commands in that surface. Do not use scp for WSL.

    • Local Windows PowerShell: copy the bundled PowerShell scripts directly to the Windows profile and run install-wispterm-notify.ps1 with powershell_exec:

      powershell
      powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\install-wispterm-notify.ps1
    • Remote saved SSH profile: use scp, not pasted heredocs, to transfer the bundled POSIX scripts to the remote server, then run the POSIX installer in that SSH session. From Windows/WispTerm, prefer the bundled profile-aware helper because it reads %APPDATA%\wispterm\ssh_hosts, decodes the saved profile, supports saved-password profiles via SSH_ASKPASS, and uses scp.exe/ssh.exe without connection sharing:

      powershell
      powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\install-wispterm-notify-remote.ps1 -ProfileName "CPU3"

      If you are already inside the SSH tab, you may run the final installer with ssh_session_exec after the scp upload.

  3. Relay what it changed: the notify program path (~/.config/wispterm/wispterm-notify.sh on POSIX/remote, %APPDATA%\wispterm\wispterm-notify.ps1 on Windows), which Claude Code hooks were added vs already present, and whether Codex's notify was added, already set, or left untouched (a pre-existing different notify is never overwritten).

  4. Verify — run the printed test command and ask the user to confirm they saw a bell badge / toast in WispTerm:

    bash
    echo '{"hook_event_name":"Notification","title":"WispTerm","message":"setup ok"}' \
      | ~/.config/wispterm/wispterm-notify.sh
Show full SKILL.md (297 more words)Show less

WeChat forwarding (optional)

In addition to the in-terminal toast/bell, WispTerm can forward each agent finish / confirmation notification to a WeChat account you've already bound to WispTerm's built-in iLink direct connection — no third-party relay.

Prerequisites (all required):

  1. A WispTerm build that includes notification → WeChat forwarding.
  2. weixin-direct-enabled = true in your WispTerm config.
  3. Scan the QR (WispTerm's WeChat panel) to bind your WeChat account.
  4. Set weixin-allowed-user = <your iLink user id> — forwarding needs a bound owner as the push destination. The "auto-bind the first sender as owner" path is not yet wired, so the owner must be set explicitly here; while it is empty, pushes are silently skipped.
  5. weixin-notify-forward = true in your WispTerm config.
  6. Keep desktop-notifications = on (default) — forwarding rides the same notification pipeline and is skipped when desktop notifications are off.

Behavior: a push is sent only when the notification is from this notifier, the binding is live with a bound owner, and you are not actively viewing that pane (window unfocused, or a different tab/split). The phone message is <title>\n<body>, e.g. Claude Code / 完成,轮到你了.

Verify: run the test command below to trigger one notification while the WispTerm window is unfocused, and confirm the message arrives in WeChat.

Notes

  • Where it shows: only when Claude Code / Codex run inside WispTerm. The rich OSC 777 toast needs a WispTerm build with OSC 9/777 support; older builds still get the bell badge from the BEL.
  • Idempotent: re-running won't duplicate hooks; existing hooks and a pre-existing Codex notify are preserved.
  • Backups: settings.json.bak / config.toml.bak are written before edits.
  • Dependencies: the POSIX installer prefers python3 for the JSON merge, falls back to jq, then to printing a manual snippet. The PowerShell installers use built-in PowerShell JSON/text handling.
  • SSH transfers: keep OpenSSH stderr visible. Do not add ControlMaster/ControlPersist/ControlPath to ssh.exe/scp.exe.

© xuzhougeng, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts) in plugins/skills/wispterm-notify-setup of xuzhougeng/wispterm.

  • SKILL.md
  • agents/openai.yaml
  • scripts/install-wispterm-notify-remote.ps1
  • scripts/install-wispterm-notify.ps1
  • scripts/install-wispterm-notify.sh
  • scripts/test-install.sh
  • scripts/wispterm-notify.ps1
  • scripts/wispterm-notify.sh

Open the folder on GitHubat commit 4168f80

Compare with similar skills

Wispterm Notify Setup 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.

Wispterm Notify Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wispterm Notify Setup this skillxuzhougeng/wispterm443—~1.3kAutomated safety check: PassMIT
RmuxHelvesec/rmux2.7k—~1.3kAutomated safety check: PassCustom licence
Environment SetupNorman-bury/research-writing-skill3.4k—~840Automated safety check: PassMIT
Remote Hostslibnativeapi/nativeapi162—~1.3kAutomated safety check: PassMIT
Local Asrysyecust/lecture-to-notes273—~1.6kAutomated safety check: PassCustom licence
Zipicokooo5km/Skills4U183—~2.2kAutomated safety check: PassMIT

Similar skills

  • Rmux

    Helvesec/rmux

    Guide for using RMUX with Claude Code, including the tmux-compatible CLI, agent automation waits, the typed SDK, browser web-share, and the rmux claude launcher.

    2.7k GitHub stars~1.3k tokensUpdated 2 mo ago
    Auto-check passed
  • Environment Setup

    Norman-bury/research-writing-skill

    A skill your agent uses when Python environment setup is needed for data visualization or conda installation is required

    3.4k GitHub stars~840 tokensUpdated 4 mo ago
    Data & AnalyticsAuto-check passed
  • Remote Hosts

    libnativeapi/nativeapi

    Build, run, and GUI-test on another machine over SSH — the user's Windows laptop today, Linux or other macOS machines tomorrow — with one symmetric CLI for every OS: push scripts, run them either in…

    162 GitHub stars~1.3k tokensUpdated today
    MobileAuto-check passed
  • Local Asr

    ysyecust/lecture-to-notes

    把本地长视频/音频转写成文字稿 + 可选字幕,纯本地(不上传云端),用 sherpa-onnx X-ASR Zipformer transducer 模型(int8 量化、中英双语、自动标点)。已在 macOS Apple Silicon(int8 + AMX,~100× 实时)、Linux ARM64(CPU,~32× 实时)与 Windows(PowerShell…

    273 GitHub stars~1.6k tokensUpdated 6 days ago
    AI & LLM EngineeringAuto-check passed
  • Zipic

    okooo5km/Skills4U

    Local image compression and Zipic-app expert for macOS and native Windows.

    183 GitHub stars~2.2k tokensUpdated 2 days ago
    Media & CreativeAuto-check passed
  • Uv

    BiFangKNT/mtga

    在 Windows/macOS/Linux 上使用 uv 执行 Python 运行、依赖同步、锁文件管理、Python 版本管理与工具命令(uv run、uv sync、uv lock、uv python、uv tool)。当任务涉及“用 uv 运行脚本/命令”“临时依赖(--with)”“锁文件一致性(--locked/--frozen)”“跨平台…

    1.2k GitHub stars~541 tokensUpdated 3 mo ago
    Auto-check passed

More from xuzhougeng/wispterm

  • Inspect Computer Config

    xuzhougeng/wispterm

    A skill your agent uses when the user asks to inspect, summarize, audit, compare, or troubleshoot this computer's hardware, operating system, CPU, memory, GPU, disk, or local runtime configuration.

    443 GitHub stars~479 tokensUpdated 3 days ago
    Auto-check passed
  • Tbtools

    xuzhougeng/wispterm

    A skill your agent uses when the user asks about TBtools, TBtools-II, TBtools RPC API, TBtools CLI, or bioinformatics operations available through TBtools such as sequence manipulation, BLAST…

    443 GitHub stars~2.3k tokensUpdated 3 days ago
    Auto-check passed
  • Wispterm Diagnostics

    xuzhougeng/wispterm

    A skill your agent uses when a user wants to report, troubleshoot, or collect context for a WispTerm issue, including crashes, rendering/DPI glitches, high CPU, keyboard/input bugs…

    443 GitHub stars~3.1k tokensUpdated 3 days ago
    Auto-check passed

Questions about Wispterm Notify Setup

What does Wispterm Notify Setup do?

A skill your agent uses when the user wants to install, repair, or re-apply WispTerm notification reminders (Claude Code Stop + Notification, and Codex turn-complete) in a local…. Wispterm Notify Setup is an agent skill from xuzhougeng/wispterm. Use when the user wants to install, repair, or re-apply WispTerm notification reminders (Claude Code Stop + Notification, and Codex turn-complete) in a local WSL/macOS/Linux/PowerShell shell or a saved WispTerm SSH profile, so finishes and confirmation prompts surface inside WispTerm.

When should I use Wispterm Notify Setup?

Wispterm Notify Setup fits situations like: the user wants to install; re-apply WispTerm notification reminders (Claude Code Stop + Notification; Codex turn-complete) in a local WSL/macOS/Linux/PowerShell shell; A saved WispTerm SSH profile.

How do I install Wispterm Notify Setup in Claude Code?

Run `npx skills add xuzhougeng/wispterm --skill wispterm-notify-setup -a claude-code`. Or copy the skill folder (plugins/skills/wispterm-notify-setup in xuzhougeng/wispterm) into .claude/skills/wispterm-notify-setup in your project. Claude Code loads it when a task matches its description.

How do I install Wispterm Notify Setup in Codex?

Run `npx skills add xuzhougeng/wispterm --skill wispterm-notify-setup -a codex`. Or copy the skill folder (plugins/skills/wispterm-notify-setup in xuzhougeng/wispterm) into .agents/skills/wispterm-notify-setup in your project. Codex loads it when a task matches its description.

Can I use Wispterm Notify Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add xuzhougeng/wispterm --skill wispterm-notify-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wispterm-notify-setup, .gemini/skills/wispterm-notify-setup, .github/skills/wispterm-notify-setup and .opencode/skills/wispterm-notify-setup in your project.

What does Wispterm Notify Setup need to run?

Going by SKILL.md and its folder, Wispterm Notify Setup needs PowerShell and a shell for the scripts in its folder and the command-line tools its instructions call (claude). Our summary lists: A Bash shell; PowerShell.

Does Wispterm Notify Setup access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Wispterm Notify Setup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. 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.

What licence does Wispterm Notify Setup use?

Wispterm Notify Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Wispterm Notify Setup use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Wispterm Notify Setup?

Skills that share tags, products or a category with Wispterm Notify Setup: Rmux (Helvesec/rmux, 2.7k stars), Environment Setup (Norman-bury/research-writing-skill, 3.4k stars), Remote Hosts (libnativeapi/nativeapi, 162 stars) and Local Asr (ysyecust/lecture-to-notes, 273 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wispterm Notify Setup?

xuzhougeng (a GitHub user) maintains it in xuzhougeng/wispterm, which has 443 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.

Source: xuzhougeng/wispterm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.