Translation Source Sync
Devolutions/UniGetUI
Synchronizes the UniGetUI English language file with source-code usage, identifies missing translation keys, removes unused entries, reports localization drift, and can reorder locale files to match…
Keep a FieldWorks dialog's WinForms (old) and Avalonia (new) implementations in sync whenever either is changed.
Custom licenceAuto-check passed
Install Dialog Update
$ npx skills add sillsdev/FieldWorks --skill dialog-update -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sillsdev/FieldWorks dialog-update --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/sillsdev/FieldWorks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/dialog-update .claude/skills/dialog-update && 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 "dialog-update" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/dialog-update into .claude/skills/dialog-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dialog-update", 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/sillsdev/FieldWorks/tree/main/.claude/skills/dialog-updateType 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 sillsdev/FieldWorks --skill dialog-update -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sillsdev/FieldWorks dialog-update --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sillsdev/FieldWorks.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/dialog-update .agents/skills/dialog-update && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dialog-update" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/dialog-update into .agents/skills/dialog-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dialog-update", 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 sillsdev/FieldWorks --skill dialog-update -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sillsdev/FieldWorks dialog-update --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sillsdev/FieldWorks.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/dialog-update .cursor/skills/dialog-update && 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 "dialog-update" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/dialog-update into .cursor/skills/dialog-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dialog-update", 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/sillsdev/FieldWorks.git --path .claude/skills/dialog-update--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 sillsdev/FieldWorks --skill dialog-update -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sillsdev/FieldWorks dialog-update --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sillsdev/FieldWorks.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/dialog-update .gemini/skills/dialog-update && 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 "dialog-update" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/dialog-update into .gemini/skills/dialog-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dialog-update", 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 sillsdev/FieldWorks dialog-updateInstalls 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 sillsdev/FieldWorks --skill dialog-update -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sillsdev/FieldWorks.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/dialog-update .github/skills/dialog-update && 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 "dialog-update" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/dialog-update into .github/skills/dialog-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dialog-update", 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 sillsdev/FieldWorks --skill dialog-update -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sillsdev/FieldWorks dialog-update --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sillsdev/FieldWorks.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/dialog-update .opencode/skills/dialog-update && 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 "dialog-update" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/dialog-update into .opencode/skills/dialog-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dialog-update", 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
dialog-update- GitHub stars
- 110
- Token cost
- ~2.3k tokens
- SKILL.md length
- 1,024 words
- Files
- 1
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Keep a FieldWorks dialog's WinForms (old) and Avalonia (new) implementations in sync whenever either is changed.
- Works in 8 steps: Setting silently not saved. A new field… → Control missing entirely. A… → Behavioral divergence. One applies live,… → …
- Review a control
- SKILL.md covers Non-negotiable rule, The dialog pairs (start here), What fails when one side is… and Concrete ways to keep them in…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Dialog Update is an agent skill from sillsdev/FieldWorks. Keep a FieldWorks dialog's WinForms (old) and Avalonia (new) implementations in sync whenever either is changed. Use whenever you add, edit, or review a control, field, button, validation rule, apply-order step, or string in a dialog that exists in BOTH a WinForms form (e.g. LexOptionsDlg) and its Avalonia replacement (e.g. LexOptionsDlgView + AvaloniaOptionsDialogLauncher) — even for a one-line change. Also use before claiming a migrated dialog is at parity, and when deciding whether a difference between the two…
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Avalonia. The repository describes itself as: FieldWorks is a suite of software tools for language and cultural data, with support for complex scripts.
When your agent uses it
- Review a control
- Validation rule
- Apply-order step
- String in a dialog that exists in BOTH a WinForms form (e.g
Example prompts
- “/dialog-update”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Setting silently not saved. A new field added to WinForms OK/apply but
- Control missing entirely. A button/checkbox added to one view and not the
- Behavioral divergence. One applies live, the other prompts a restart; one
- Visibility/enable drift. One side gates a control's visibility or enabled
- String/localization drift. Wording, mnemonics, or the .resx/XLIFF key
- State DTO / persisted-key mismatch. The DTO field, the settings property,
- Test blind spot. Headless Avalonia tests pass while the WinForms form (or
- Divergence comment rot. A "sanctioned divergence" note that was never
What it can do on your machine
Read from SKILL.md and the folder at commit 489ed1b. 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
Dialog Update loads about 2.3k tokens when it runs. Until then it costs about 140 tokens; SKILL.md has 1,024 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,024 words (~2,333 tokens).
“During the WinForms → Avalonia coexistence, many dialogs exist twice: the legacy WinForms form and the migrated Avalonia view. Both ship, and which one runs is chosen at launch (usually by UIMode). A change to one that is not mirrored…”
- name
- dialog-update
Files
Just SKILL.md in .claude/skills/dialog-update of sillsdev/FieldWorks.
Open the folder on GitHubat commit 489ed1b
Compare with similar skills
Dialog Update 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 |
|---|---|---|---|---|---|---|
| Dialog Update this skillsillsdev/FieldWorks | 110 | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Translation Source SyncDevolutions/UniGetUI | 26k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Docs Style LintAvaloniaUI/avalonia-docs | 166 | — | ~4.6k | Automated safety check: Pass | None | |
| Format StylePixeval/Pixeval | 3.2k | — | ~1.2k | Automated safety check: Pass | GPL-3.0 | |
| Docusaurus StylingAvaloniaUI/avalonia-docs | 166 | — | ~3.3k | Automated safety check: Pass | None | |
| Code StylePixeval/Pixeval | 3.2k | — | ~730 | Automated safety check: Pass | GPL-3.0 |
Similar skills
Docs Style Lint
AvaloniaUI/avalonia-docs
Reviews and lints Avalonia documentation pages against house style rules, content boundaries, anti-marketing standards, accessibility, and SEO.
Format Style
Pixeval/Pixeval
工程代码格式化风格指引
Docusaurus Styling
AvaloniaUI/avalonia-docs
Style Docusaurus sites to match Avalonia Customer Portal theme using TailwindCSS, CSS variables, and component swizzling.
Code Style
Pixeval/Pixeval
工程代码编写风格指引（不含简单的格式化风格）
Atomui Resource Lifecycle
AtomUI/AtomUI
A skill your agent uses when changing AtomUI or Avalonia resource bindings, DynamicResource, TokenResourceBinder, non-Visual AvaloniaObject lifecycle, IResourceHost/IThemeVariantHost…
More from sillsdev/FieldWorks
All 29 skills in this repoAtlassian Readonly Skills
sillsdev/FieldWorks
Read-only Python utilities for Jira (SIL Data Center): fetch an issue, search with JQL, read transitions, links, worklogs, agile boards and projects.
Atlassian Skills
sillsdev/FieldWorks
Python utilities for Jira (SIL Data Center) covering issue management, JQL search, workflows and transitions, links, agile boards, worklogs and projects.
Fieldworks Winapp
sillsdev/FieldWorks
Control and document the FieldWorks desktop application with WinForms MCP or WinApp MCP.
Convert Slice
sillsdev/FieldWorks
Drive the conversion of one legacy slice type to the Avalonia detail view through analysis, developer alignment, integration-test planning, route/exemplar mapping, design, and scaffold/implement.
Dependabot Consolidation
sillsdev/FieldWorks
Combine several open Dependabot pull requests into a single branch and PR: enumerate the open Dependabot PRs, cherry-pick them onto fresh main, rewrite commit messages to satisfy…
Fieldworks Semantic Render Parity
sillsdev/FieldWorks
Capture or review FieldWorks parity evidence: semantic snapshots, render/visual baselines, layout parity, failure artifacts, XML view definitions, and the Avalonia presentation IR.
Related
Works with
Questions about Dialog Update
What does Dialog Update do?
Keep a FieldWorks dialog's WinForms (old) and Avalonia (new) implementations in sync whenever either is changed. Dialog Update is an agent skill from sillsdev/FieldWorks. Keep a FieldWorks dialog's WinForms (old) and Avalonia (new) implementations in sync whenever either is changed.
When should I use Dialog Update?
Dialog Update fits situations like: review a control; validation rule; apply-order step; string in a dialog that exists in BOTH a WinForms form (e.g.
How do I install Dialog Update in Claude Code?
Run `npx skills add sillsdev/FieldWorks --skill dialog-update -a claude-code`. Or copy the skill folder (.claude/skills/dialog-update in sillsdev/FieldWorks) into .claude/skills/dialog-update in your project. Claude Code loads it when a task matches its description.
How do I install Dialog Update in Codex?
Run `npx skills add sillsdev/FieldWorks --skill dialog-update -a codex`. Or copy the skill folder (.claude/skills/dialog-update in sillsdev/FieldWorks) into .agents/skills/dialog-update in your project. Codex loads it when a task matches its description.
Can I use Dialog Update 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 sillsdev/FieldWorks --skill dialog-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dialog-update, .gemini/skills/dialog-update, .github/skills/dialog-update and .opencode/skills/dialog-update in your project.
What does Dialog Update need to run?
SKILL.md names no scripts, command-line tools or credentials: Dialog Update is instructions for the agent only.
Does Dialog Update 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 Dialog Update 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 Dialog Update use?
Dialog Update has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Dialog Update use?
About 2.3k tokens (SKILL.md is roughly 9.3k 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 Dialog Update?
Skills that share tags, products or a category with Dialog Update: Translation Source Sync (Devolutions/UniGetUI, 26k stars), Docs Style Lint (AvaloniaUI/avalonia-docs, 166 stars), Format Style (Pixeval/Pixeval, 3.2k stars) and Docusaurus Styling (AvaloniaUI/avalonia-docs, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dialog Update?
sillsdev (a GitHub organization) maintains it in sillsdev/FieldWorks, which has 110 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 7, 2026.
Source: sillsdev/FieldWorks on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.