Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
A skill your agent uses when the DSH host itself has been upgraded (or is about to be) and the whole installed fleet of Web/client plugins must be checked against the new host - one or more surfaces…
Install Plugin Fleet Sweep
$ npx skills add oh-my-dsh/dsh-plugin-upgrade-skill --skill plugin-fleet-sweep -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install oh-my-dsh/dsh-plugin-upgrade-skill plugin-fleet-sweep --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/oh-my-dsh/dsh-plugin-upgrade-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/plugin-fleet-sweep .claude/skills/plugin-fleet-sweep && 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 "plugin-fleet-sweep" agent skill from https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill/tree/main/skills/plugin-fleet-sweep into .claude/skills/plugin-fleet-sweep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-fleet-sweep", 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/oh-my-dsh/dsh-plugin-upgrade-skill/tree/main/skills/plugin-fleet-sweepType 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 oh-my-dsh/dsh-plugin-upgrade-skill --skill plugin-fleet-sweep -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install oh-my-dsh/dsh-plugin-upgrade-skill plugin-fleet-sweep --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/plugin-fleet-sweep .agents/skills/plugin-fleet-sweep && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plugin-fleet-sweep" agent skill from https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill/tree/main/skills/plugin-fleet-sweep into .agents/skills/plugin-fleet-sweep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-fleet-sweep", 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 oh-my-dsh/dsh-plugin-upgrade-skill --skill plugin-fleet-sweep -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install oh-my-dsh/dsh-plugin-upgrade-skill plugin-fleet-sweep --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/plugin-fleet-sweep .cursor/skills/plugin-fleet-sweep && 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 "plugin-fleet-sweep" agent skill from https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill/tree/main/skills/plugin-fleet-sweep into .cursor/skills/plugin-fleet-sweep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-fleet-sweep", 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/oh-my-dsh/dsh-plugin-upgrade-skill.git --path skills/plugin-fleet-sweep--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 oh-my-dsh/dsh-plugin-upgrade-skill --skill plugin-fleet-sweep -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install oh-my-dsh/dsh-plugin-upgrade-skill plugin-fleet-sweep --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/plugin-fleet-sweep .gemini/skills/plugin-fleet-sweep && 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 "plugin-fleet-sweep" agent skill from https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill/tree/main/skills/plugin-fleet-sweep into .gemini/skills/plugin-fleet-sweep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-fleet-sweep", 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 oh-my-dsh/dsh-plugin-upgrade-skill plugin-fleet-sweepInstalls 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 oh-my-dsh/dsh-plugin-upgrade-skill --skill plugin-fleet-sweep -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/plugin-fleet-sweep .github/skills/plugin-fleet-sweep && 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 "plugin-fleet-sweep" agent skill from https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill/tree/main/skills/plugin-fleet-sweep into .github/skills/plugin-fleet-sweep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-fleet-sweep", 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 oh-my-dsh/dsh-plugin-upgrade-skill --skill plugin-fleet-sweep -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install oh-my-dsh/dsh-plugin-upgrade-skill plugin-fleet-sweep --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/plugin-fleet-sweep .opencode/skills/plugin-fleet-sweep && 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 "plugin-fleet-sweep" agent skill from https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill/tree/main/skills/plugin-fleet-sweep into .opencode/skills/plugin-fleet-sweep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-fleet-sweep", 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
plugin-fleet-sweep- GitHub stars
- 248
- Token cost
- ~1.1k tokens
- SKILL.md length
- 556 words
- Files
- 3 (incl. references)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the DSH host itself has been upgraded (or is about to be) and the whole installed fleet of Web/client plugins must be checked against the new host - one or more surfaces…
- Works in 5 steps: Verify on the target host, not in… → One static sweep first, cheaply. Grep… → Absence of errors is weak evidence. A… → …
- More surfaces broke
- SKILL.md covers Standing rules, Workflow and Report
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Plugin Fleet Sweep is an agent skill from oh-my-dsh/dsh-plugin-upgrade-skill. Use when the DSH host itself has been upgraded (or is about to be) and the whole installed fleet of Web/client plugins must be checked against the new host - one or more surfaces broke, vanished, or need their compatibility re-verified and re-released. Also use after a host upgrade to sweep for silent breaks before the user reports them, and to run the per-plugin fix/release loop (branch, bump, changelog, tag, mirrors).
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `README.md` and `references/fleet-sweep-checklist.md`).
It sits in Development, covering Changelog and release notes. The repository describes itself as: 帮助插件自动随着dsh版本升级的skill. The licence is MIT.
When your agent uses it
- More surfaces broke
- Need their compatibility re-verified and re-released
Example prompts
- “/plugin-fleet-sweep”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Verify on the target host, not in sources. A plugin "loads" when its
- One static sweep first, cheaply. Grep every plugin source for the
- Absence of errors is weak evidence. A surface whose UI is
- Fix and release per plugin, never as a fleet commit. Each broken
- Compatibility builds over host-locked builds when the plugin must
What it can do on your machine
Read from SKILL.md and the folder at commit ef07576. 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
Plugin Fleet Sweep loads about 1.1k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 111 tokens; SKILL.md has 556 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 oh-my-dsh/dsh-plugin-upgrade-skill at commit ef07576, republished under its MIT licence (© oh-my-dsh). 556 words, ~1,123 tokens.
Download SKILL.mdSave it as
.claude/skills/plugin-fleet-sweep/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- plugin-fleet-sweep
- description
- Use when the DSH host itself has been upgraded (or is about to be) and the whole installed fleet of Web/client plugins must be checked against the new host - one or more surfaces broke, vanished, or need their compatibility re-verified and re-released. Also use after a host upgrade to sweep for silent breaks before the user reports them, and to run the per-plugin fix/release loop (branch, bump, changelog, tag, mirrors).
Sweep a Plugin Fleet Across a DSH Host Upgrade
A host upgrade changes the contracts every plugin rides on at once. The unit of work is not one plugin: it is the fleet, swept in a fixed order, with one verdict per plugin and one release loop per broken plugin. The sweep runs against the REAL upgraded host - sources and Node-based tests passing prove nothing about browser-engine and runtime-surface changes.
Standing rules
- Verify on the target host, not in sources. A plugin "loads" when its
client bundle is served, its CSS
style[data-plugin]tag exists, and zeroslot entry crashed/ activation-failure records appear. A plugin "works" only when its surface marker is in the DOM and its expected requests fire. Record which of the two you have proven. - One static sweep first, cheaply. Grep every plugin source for the
APIs the new host renamed or removed (from the target version's corridor
cards in
plugin-upgrade/references/) before touching a browser. Static hits are already verdicts: broken-until-fixed. - Absence of errors is weak evidence. A surface whose UI is interaction-gated (appears only after a paste, a file operation, a focus event) shows nothing in a idle sweep. For each plugin, know its trigger and either simulate it or mark the verdict "loaded, interaction path not exercised" instead of claiming success.
- Fix and release per plugin, never as a fleet commit. Each broken
plugin gets its own branch-or-main commit, version bump, changelog row,
tag, and mirror push (the repositories' own mirror flow;
sync-mirrors.mjsis specific to the author's plugin repositories - use whatever the target repository documents, or skip mirrors if it has none). Mixed fleet commits make per-plugin rollbacks impossible. - Compatibility builds over host-locked builds when the plugin must span host generations: resolve renamed host exports at runtime through a fallback chain (old name → new variants) instead of static named imports, and extend unit-test module mocks with every fallback name (strict mocks throw on undefined-export access and mask the real failure).
Show full SKILL.md (226 more words)Show less
Workflow
- Read the target host version's corridor cards
(
plugin-upgrade/references/v<target>.md) and derive the static sweep patterns from them - the cards name the renamed/removed surfaces. - Static sweep: grep every fleet repository for those patterns; record hits as broken-until-fixed with file:line.
- Live sweep: load the real GUI in a driven headless browser against the
upgraded host and per plugin assert (a) the client CSS/style tag present,
(b) zero
slot entry crashedconsole records, (c) the surface's DOM marker present, (d) the expected requests fired. Method: references/fleet-sweep-checklist.md (includes the authenticated-GUI access and instrumentation discipline fromplugin-runtime-debug/references/browser-forensics.md). - Re-verify interaction-gated surfaces with their trigger simulated (paste, file write, keyboard chord) or downgrade the verdict explicitly.
- For each broken plugin: diagnose against the host source
(
plugin-runtime-debugstanding rule), fix with a host-generation-compatible approach when the fleet spans host versions, run the plugin's typecheck/tests/build, then release: version bump, changelog/compatibility-table row naming the host version range, commit, tag, mirrors. - Re-run the live sweep after releases and record the final per-plugin verdict table (plugin, host versions supported, evidence).
Report
End with a per-plugin table: verdict (working / fixed+released / interaction-path-unexercised / broken), the host versions covered, and the evidence (which assertion passed where). Note any host bug found (report upstream with the minimal repro) and any hot-fix living in the install tree that the next host upgrade will overwrite - list the reapplication material.
© oh-my-dsh, 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 2 other files (references) in skills/plugin-fleet-sweep of oh-my-dsh/dsh-plugin-upgrade-skill.
- SKILL.md
- README.md
- references/fleet-sweep-checklist.md
Open the folder on GitHubat commit ef07576
Compare with similar skills
Plugin Fleet Sweep 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 |
|---|---|---|---|---|---|---|
| Plugin Fleet Sweep this skilloh-my-dsh/dsh-plugin-upgrade-skill | 248 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| StarRocks Release NotesStarRocks/starrocks | 12k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.5k | Automated safety check: Pass | GPL-3.0 |
Similar skills
StarRocks Release Notes
StarRocks/starrocks
Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
More from oh-my-dsh/dsh-plugin-upgrade-skill
Plugin Runtime Debug
oh-my-dsh/dsh-plugin-upgrade-skill
A skill your agent uses when an installed DSH Web plugin misbehaves only at runtime in the browser — paste/attachment/composer features that work once then fail, chips or panels showing stale…
Generic Migration
oh-my-dsh/dsh-plugin-upgrade-skill
Framework-agnostic methodology for migrating a plugin, extension, or integration across a breaking upstream release — inventory coupling points, classify changes, stage the migration, and verify in…
Related
Categories
Questions about Plugin Fleet Sweep
What does Plugin Fleet Sweep do?
A skill your agent uses when the DSH host itself has been upgraded (or is about to be) and the whole installed fleet of Web/client plugins must be checked against the new host - one or more surfaces…. Plugin Fleet Sweep is an agent skill from oh-my-dsh/dsh-plugin-upgrade-skill. Use when the DSH host itself has been upgraded (or is about to be) and the whole installed fleet of Web/client plugins must be checked against the new host - one or more surfaces broke, vanished, or need their compatibility re-verified and re-released.
When should I use Plugin Fleet Sweep?
Plugin Fleet Sweep fits situations like: more surfaces broke; need their compatibility re-verified and re-released.
How do I install Plugin Fleet Sweep in Claude Code?
Run `npx skills add oh-my-dsh/dsh-plugin-upgrade-skill --skill plugin-fleet-sweep -a claude-code`. Or copy the skill folder (skills/plugin-fleet-sweep in oh-my-dsh/dsh-plugin-upgrade-skill) into .claude/skills/plugin-fleet-sweep in your project. Claude Code loads it when a task matches its description.
How do I install Plugin Fleet Sweep in Codex?
Run `npx skills add oh-my-dsh/dsh-plugin-upgrade-skill --skill plugin-fleet-sweep -a codex`. Or copy the skill folder (skills/plugin-fleet-sweep in oh-my-dsh/dsh-plugin-upgrade-skill) into .agents/skills/plugin-fleet-sweep in your project. Codex loads it when a task matches its description.
Can I use Plugin Fleet Sweep 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 oh-my-dsh/dsh-plugin-upgrade-skill --skill plugin-fleet-sweep -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plugin-fleet-sweep, .gemini/skills/plugin-fleet-sweep, .github/skills/plugin-fleet-sweep and .opencode/skills/plugin-fleet-sweep in your project.
What does Plugin Fleet Sweep need to run?
SKILL.md names no scripts, command-line tools or credentials: Plugin Fleet Sweep is instructions for the agent only.
Does Plugin Fleet Sweep 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 Plugin Fleet Sweep 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 Plugin Fleet Sweep use?
Plugin Fleet Sweep 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 Plugin Fleet Sweep use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 781 tokens, read only when the agent opens those files.
What are the alternatives to Plugin Fleet Sweep?
Skills that share tags, products or a category with Plugin Fleet Sweep: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and React Router Release Notes Prep (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plugin Fleet Sweep?
oh-my-dsh (a GitHub organization) maintains it in oh-my-dsh/dsh-plugin-upgrade-skill, which has 248 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 5, 2026.
Source: oh-my-dsh/dsh-plugin-upgrade-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.