User-Facing Text Cleanup
guillaumemeyer/watermarks-remover
Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.
A skill your agent uses when you need to verify tui-use's ability to drive vim — opening files, editing text, navigation, undo/redo, search & replace, and saving.
Install Tui Use Vim Test
$ npx skills add onesuper/tui-use --skill tui-use-vim-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install onesuper/tui-use tui-use-vim-test --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/onesuper/tui-use.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/tui-use-vim-test .claude/skills/tui-use-vim-test && 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 "tui-use-vim-test" agent skill from https://github.com/onesuper/tui-use/tree/main/.claude/skills/tui-use-vim-test into .claude/skills/tui-use-vim-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tui-use-vim-test", 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/onesuper/tui-use/tree/main/.claude/skills/tui-use-vim-testType 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 onesuper/tui-use --skill tui-use-vim-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install onesuper/tui-use tui-use-vim-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/onesuper/tui-use.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/tui-use-vim-test .agents/skills/tui-use-vim-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tui-use-vim-test" agent skill from https://github.com/onesuper/tui-use/tree/main/.claude/skills/tui-use-vim-test into .agents/skills/tui-use-vim-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tui-use-vim-test", 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 onesuper/tui-use --skill tui-use-vim-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install onesuper/tui-use tui-use-vim-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/onesuper/tui-use.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/tui-use-vim-test .cursor/skills/tui-use-vim-test && 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 "tui-use-vim-test" agent skill from https://github.com/onesuper/tui-use/tree/main/.claude/skills/tui-use-vim-test into .cursor/skills/tui-use-vim-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tui-use-vim-test", 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/onesuper/tui-use.git --path .claude/skills/tui-use-vim-test--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 onesuper/tui-use --skill tui-use-vim-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install onesuper/tui-use tui-use-vim-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/onesuper/tui-use.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/tui-use-vim-test .gemini/skills/tui-use-vim-test && 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 "tui-use-vim-test" agent skill from https://github.com/onesuper/tui-use/tree/main/.claude/skills/tui-use-vim-test into .gemini/skills/tui-use-vim-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tui-use-vim-test", 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 onesuper/tui-use tui-use-vim-testInstalls 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 onesuper/tui-use --skill tui-use-vim-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/onesuper/tui-use.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/tui-use-vim-test .github/skills/tui-use-vim-test && 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 "tui-use-vim-test" agent skill from https://github.com/onesuper/tui-use/tree/main/.claude/skills/tui-use-vim-test into .github/skills/tui-use-vim-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tui-use-vim-test", 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 onesuper/tui-use --skill tui-use-vim-test -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install onesuper/tui-use tui-use-vim-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/onesuper/tui-use.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/tui-use-vim-test .opencode/skills/tui-use-vim-test && 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 "tui-use-vim-test" agent skill from https://github.com/onesuper/tui-use/tree/main/.claude/skills/tui-use-vim-test into .opencode/skills/tui-use-vim-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tui-use-vim-test", 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.
Facts
- Skill name
tui-use-vim-test- GitHub stars
- 266
- Token cost
- ~238 tokens
- SKILL.md length
- 68 words
- Files
- 4
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when you need to verify tui-use's ability to drive vim — opening files, editing text, navigation, undo/redo, search & replace, and saving.
- You need to verify tui-uses ability to drive vim — opening files
- SKILL.md covers Usage, Available Test Suites and Reporting
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Search & replace
What it does
Tui Use Vim Test is an agent skill from onesuper/tui-use. Use when you need to verify tui-use's ability to drive vim — opening files, editing text, navigation, undo/redo, search & replace, and saving.
Its SKILL.md is about 240 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `tests/edit.md`, `tests/navigate.md` and `tests/substitute.md`).
It sits in Writing & Content, covering Copy editing and proofreading. The repository describes itself as: tui-use lets agents interact with programs that expect a human at the keyboard — REPLs, debuggers, TUI apps, and anything else bash can't reach. The licence is MIT.
When your agent uses it
- You need to verify tui-uses ability to drive vim — opening files
- Search & replace
Example prompts
- “/tui-use-vim-test”
What it can do on your machine
Read from SKILL.md and the folder at commit 0170481. 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
No scripts in the folder and no shell commands in SKILL.md.
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
Tui Use Vim Test loads about 238 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 68 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.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from onesuper/tui-use at commit 0170481, republished under its MIT licence (© onesuper). 68 words, ~238 tokens.
Download SKILL.mdSave it as
.claude/skills/tui-use-vim-test/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- tui-use-vim-test
- description
- Use when you need to verify tui-use's ability to drive vim — opening files, editing text, navigation, undo/redo, search & replace, and saving.
tui-use vim Tests
Run tests to verify tui-use can drive vim for real editing tasks.
Usage
/tui-use-vim-test # Run all test suites
/tui-use-vim-test <suite> # Run specific test suiteAvailable Test Suites
| Suite | Description |
|---|---|
edit | Create file, insert text, save, verify content |
navigate | Line jumping, undo, redo with ctrl+r |
substitute | Global search & replace with :%s |
Test specifications are in tests/ directory.
Reporting
After running tests, report results as:
<suite>:
<scenario> — PASS / FAIL / PARTIAL
- <step description>: PASS / FAIL (<reason or actual output>)If any test fails, include the actual screen content and what was expected.
© onesuper, 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 3 other files in .claude/skills/tui-use-vim-test of onesuper/tui-use.
- SKILL.md
- tests/edit.md
- tests/navigate.md
- tests/substitute.md
Open the folder on GitHubat commit 0170481
Compare with similar skills
Tui Use Vim Test 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 |
|---|---|---|---|---|---|---|
| Tui Use Vim Test this skillonesuper/tui-use | 266 | — | ~238 | Automated safety check: Pass | MIT | |
| User-Facing Text Cleanupguillaumemeyer/watermarks-remover | 24k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Story Multi-Perspective Reviewzenstory-ai/oh-story-claudecode | 7.4k | 3 repos | ~3k | Automated safety check: Pass | MIT | |
| Chinese Text Humanizerop7418/Humanizer-zh | 19k | — | ~2k | Automated safety check: Pass | MIT | |
| Korean AI-Text Humanizerepoko77-ai/im-not-ai | 5.9k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Natural Japanese Business Writingcoji/natural-japanese | 1.9k | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Story Multi-Perspective Review
zenstory-ai/oh-story-claudecode
Reviews Chinese web-novel text with several reviewer agents in parallel, falling back to a single-agent pass, and reports structure, character, prose and setting problems with fixes.
Chinese Text Humanizer
op7418/Humanizer-zh
Edits Chinese articles, comments and documents to remove filler, repetition and template phrasing while keeping the facts, the level of certainty and the author's voice.
Korean AI-Text Humanizer
epoko77-ai/im-not-ai
Rewrites Korean text written by AI so it reads like a human wrote it, detecting translationese and other AI patterns while leaving the content untouched.
Natural Japanese Business Writing
coji/natural-japanese
Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.
Defensive Writing Editor
lennney/stop-that-shit
Cuts defensive disclaimers, stacked hedging and self-protective narration from proposals and summaries, keeping only limits that affect the reader's decision.
More from onesuper/tui-use
Tui Use
onesuper/tui-use
Operate interactive terminal programs (REPLs, installers, TUI apps) using PTY automation.
Tui Use
onesuper/tui-use
Operate interactive terminal programs (REPLs, debuggers, TUI apps) using PTY automation.
Tui Use Git Test
onesuper/tui-use
A skill your agent uses when you need to verify tui-use's ability to drive git workflows — interactive rebase, conflict resolution with vim, and verifying repository state.
Tui Use Integration Test
onesuper/tui-use
A skill your agent uses when you need to verify tui-use end-to-end behavior — driving interactive CLI programs, Python REPL, --text pattern matching, custom timeout, special key handling, and…
Related
Categories
Questions about Tui Use Vim Test
What does Tui Use Vim Test do?
A skill your agent uses when you need to verify tui-use's ability to drive vim — opening files, editing text, navigation, undo/redo, search & replace, and saving. Tui Use Vim Test is an agent skill from onesuper/tui-use. Use when you need to verify tui-use's ability to drive vim — opening files, editing text, navigation, undo/redo, search & replace, and saving.
When should I use Tui Use Vim Test?
Tui Use Vim Test fits situations like: you need to verify tui-uses ability to drive vim — opening files; search & replace.
How do I install Tui Use Vim Test in Claude Code?
Run `npx skills add onesuper/tui-use --skill tui-use-vim-test -a claude-code`. Or copy the skill folder (.claude/skills/tui-use-vim-test in onesuper/tui-use) into .claude/skills/tui-use-vim-test in your project. Claude Code loads it when a task matches its description.
How do I install Tui Use Vim Test in Codex?
Run `npx skills add onesuper/tui-use --skill tui-use-vim-test -a codex`. Or copy the skill folder (.claude/skills/tui-use-vim-test in onesuper/tui-use) into .agents/skills/tui-use-vim-test in your project. Codex loads it when a task matches its description.
Can I use Tui Use Vim Test 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 onesuper/tui-use --skill tui-use-vim-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tui-use-vim-test, .gemini/skills/tui-use-vim-test, .github/skills/tui-use-vim-test and .opencode/skills/tui-use-vim-test in your project.
What does Tui Use Vim Test need to run?
SKILL.md names no scripts, command-line tools or credentials: Tui Use Vim Test is instructions for the agent only.
Does Tui Use Vim Test 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 Tui Use Vim Test 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. Review the folder before installing.
What licence does Tui Use Vim Test use?
Tui Use Vim Test 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 Tui Use Vim Test use?
About 238 tokens (SKILL.md is roughly 952 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 Tui Use Vim Test?
Skills that share tags, products or a category with Tui Use Vim Test: User-Facing Text Cleanup (guillaumemeyer/watermarks-remover, 24k stars), Story Multi-Perspective Review (zenstory-ai/oh-story-claudecode, 7.4k stars), Chinese Text Humanizer (op7418/Humanizer-zh, 19k stars) and Korean AI-Text Humanizer (epoko77-ai/im-not-ai, 5.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tui Use Vim Test?
onesuper (a GitHub user) maintains it in onesuper/tui-use, which has 266 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on April 11, 2026.
Source: onesuper/tui-use on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.