Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
End-to-end playbook for migrating any FieldWorks WinForms UI (DataTree slices, XMLViews browse/table, dialogs, choosers, launchers, shell panes) to Avalonia using the established detail/seam…
Install Fieldworks Winforms To Avalonia Migration
$ npx skills add sillsdev/FieldWorks --skill fieldworks-winforms-to-avalonia-migration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sillsdev/FieldWorks fieldworks-winforms-to-avalonia-migration --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/fieldworks-winforms-to-avalonia-migration .claude/skills/fieldworks-winforms-to-avalonia-migration && 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 "fieldworks-winforms-to-avalonia-migration" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/fieldworks-winforms-to-avalonia-migration into .claude/skills/fieldworks-winforms-to-avalonia-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fieldworks-winforms-to-avalonia-migration", 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/fieldworks-winforms-to-avalonia-migrationType 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 fieldworks-winforms-to-avalonia-migration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sillsdev/FieldWorks fieldworks-winforms-to-avalonia-migration --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/fieldworks-winforms-to-avalonia-migration .agents/skills/fieldworks-winforms-to-avalonia-migration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fieldworks-winforms-to-avalonia-migration" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/fieldworks-winforms-to-avalonia-migration into .agents/skills/fieldworks-winforms-to-avalonia-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fieldworks-winforms-to-avalonia-migration", 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 fieldworks-winforms-to-avalonia-migration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sillsdev/FieldWorks fieldworks-winforms-to-avalonia-migration --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/fieldworks-winforms-to-avalonia-migration .cursor/skills/fieldworks-winforms-to-avalonia-migration && 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 "fieldworks-winforms-to-avalonia-migration" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/fieldworks-winforms-to-avalonia-migration into .cursor/skills/fieldworks-winforms-to-avalonia-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fieldworks-winforms-to-avalonia-migration", 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/fieldworks-winforms-to-avalonia-migration--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 fieldworks-winforms-to-avalonia-migration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sillsdev/FieldWorks fieldworks-winforms-to-avalonia-migration --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/fieldworks-winforms-to-avalonia-migration .gemini/skills/fieldworks-winforms-to-avalonia-migration && 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 "fieldworks-winforms-to-avalonia-migration" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/fieldworks-winforms-to-avalonia-migration into .gemini/skills/fieldworks-winforms-to-avalonia-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fieldworks-winforms-to-avalonia-migration", 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 fieldworks-winforms-to-avalonia-migrationInstalls 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 fieldworks-winforms-to-avalonia-migration -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/fieldworks-winforms-to-avalonia-migration .github/skills/fieldworks-winforms-to-avalonia-migration && 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 "fieldworks-winforms-to-avalonia-migration" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/fieldworks-winforms-to-avalonia-migration into .github/skills/fieldworks-winforms-to-avalonia-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fieldworks-winforms-to-avalonia-migration", 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 fieldworks-winforms-to-avalonia-migration -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 fieldworks-winforms-to-avalonia-migration --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/fieldworks-winforms-to-avalonia-migration .opencode/skills/fieldworks-winforms-to-avalonia-migration && 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 "fieldworks-winforms-to-avalonia-migration" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/fieldworks-winforms-to-avalonia-migration into .opencode/skills/fieldworks-winforms-to-avalonia-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fieldworks-winforms-to-avalonia-migration", 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
fieldworks-winforms-to-avalonia-migration- GitHub stars
- 110
- Token cost
- ~3.7k tokens
- SKILL.md length
- 1,752 words
- Files
- 7 (incl. references)
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
End-to-end playbook for migrating any FieldWorks WinForms UI (DataTree slices, XMLViews browse/table, dialogs, choosers, launchers, shell panes) to Avalonia using the established detail/seam…
- Works in 10 steps: Inventory and scope. Identify the legacy… → Characterize before refactor. Lock… → Extract seams. Reuse the existing… → …
- Reviewing WinForms-to-Avalonia work — including seam extraction
- SKILL.md covers Core Rule, Established Architecture —…, Workflow and Phase-1 Landing Strategy…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Fieldworks Winforms To Avalonia Migration is an agent skill from sillsdev/FieldWorks. End-to-end playbook for migrating any FieldWorks WinForms UI (DataTree slices, XMLViews browse/table, dialogs, choosers, launchers, shell panes) to Avalonia using the established detail/seam architecture. Use whenever planning, implementing, or reviewing WinForms-to-Avalonia work — including seam extraction, region composition, owned controls, plugin editors, parity evidence, or retiring legacy UI — even if the request only says port, modernize, replace WinForms, or new Avalonia view. Also use after finishing a…
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/architecture-patterns.md`, `references/control-exemplar-map.md` and `references/lessons-learned.md`).
It sits in Product & Project Management, covering Retrospectives. 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
- Reviewing WinForms-to-Avalonia work — including seam extraction
- Region composition
- Parity evidence
- Retiring legacy UI — even if the request only says port
Example prompts
- “/fieldworks-winforms-to-avalonia-migration”
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Inventory and scope. Identify the legacy UI, its entry points,
- Characterize before refactor. Lock current behavior in executable
- Extract seams. Reuse the existing contracts in
- Select controls. Look the control up in
- Compose the region. Walk the compiled IR in a composer, project into
- Wire the host. Explicit per-host contract: supported Avalonia,
- Prove parity. Build the evidence bundle defined in
- Localize. Apply fieldworks-localization-review; field labels stay
- Retire and gate. Run the symbol audit
- Retrospective. Update these skills — see "Keep this skill set
What it can do on your machine
Read from SKILL.md and the folder at commit bd0608d. 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
Fieldworks Winforms To Avalonia Migration loads about 3.7k tokens when it runs, and up to ~25k if it reads all its reference files. Until then it costs about 161 tokens; SKILL.md has 1,752 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,752 words (~3,730 tokens).
“This is the hub skill for the migration program. It tells you what architecture already exists (do not reinvent it), what order to work in, which companion skill to apply at each step, and how to keep this skill set…”
- name
- fieldworks-winforms-to-avalonia-migration
Files
SKILL.md and 6 other files (references) in .claude/skills/fieldworks-winforms-to-avalonia-migration of sillsdev/FieldWorks.
- SKILL.md
- references/architecture-patterns.md
- references/control-exemplar-map.md
- references/lessons-learned.md
- references/migration-checklist.md
- references/parity-evidence.md
- references/seam-catalog.md
Open the folder on GitHubat commit bd0608d
Compare with similar skills
Fieldworks Winforms To Avalonia Migration 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 |
|---|---|---|---|---|---|---|
| Fieldworks Winforms To Avalonia Migration this skillsillsdev/FieldWorks | 110 | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Weekly Engineering Retrogarrytan/gstack | 136k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Dough Execute Planterryyin/lizard | 2.5k | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| Oral Paper SkillAdkid-Zephyr/oral-paper-skill | 357 | — | ~1.9k | Automated safety check: Pass | None | |
| Deck Retroasheshgoplani/agent-deck | 1.1k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Dough Execution Retrospectiveterryyin/lizard | 2.5k | — | ~4k | Automated safety check: Pass | Custom licence |
Similar skills
Dough Execute Plan
terryyin/lizard
Executes one selected story or bounded retrospective correction through an executable plan, or one authorized planless slice from a selected simple story or a contextual instruction, with…
Oral Paper Skill
Adkid-Zephyr/oral-paper-skill
Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection.
Deck Retro
asheshgoplani/agent-deck
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs.
Dough Execution Retrospective
terryyin/lizard
Reviews planned, completed planless quick, or quick-to-planned execution against original intent, aggregate commits, current whole-product architecture, and tests, including after cleanup.
Criticism Self Criticism
HughYau/qiushi-skill
批评与自我批评：在工作完成、阶段验收、收到批评或同类错误反复出现时，对成果和过程做诚实、具体、基于事实的审视，输出可执行的改进项，并处理外来批评而不辩解。触发信号包括 review、复盘、审查、"帮我看看有没有问题"、"你确定吗"；任务刚开始或只是单步查询时不触发。
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
Categories
Questions about Fieldworks Winforms To Avalonia Migration
What does Fieldworks Winforms To Avalonia Migration do?
End-to-end playbook for migrating any FieldWorks WinForms UI (DataTree slices, XMLViews browse/table, dialogs, choosers, launchers, shell panes) to Avalonia using the established detail/seam…. Fieldworks Winforms To Avalonia Migration is an agent skill from sillsdev/FieldWorks. End-to-end playbook for migrating any FieldWorks WinForms UI (DataTree slices, XMLViews browse/table, dialogs, choosers, launchers, shell panes) to Avalonia using the established detail/seam architecture.
When should I use Fieldworks Winforms To Avalonia Migration?
Fieldworks Winforms To Avalonia Migration fits situations like: reviewing WinForms-to-Avalonia work — including seam extraction; region composition; parity evidence; retiring legacy UI — even if the request only says port.
How do I install Fieldworks Winforms To Avalonia Migration in Claude Code?
Run `npx skills add sillsdev/FieldWorks --skill fieldworks-winforms-to-avalonia-migration -a claude-code`. Or copy the skill folder (.claude/skills/fieldworks-winforms-to-avalonia-migration in sillsdev/FieldWorks) into .claude/skills/fieldworks-winforms-to-avalonia-migration in your project. Claude Code loads it when a task matches its description.
How do I install Fieldworks Winforms To Avalonia Migration in Codex?
Run `npx skills add sillsdev/FieldWorks --skill fieldworks-winforms-to-avalonia-migration -a codex`. Or copy the skill folder (.claude/skills/fieldworks-winforms-to-avalonia-migration in sillsdev/FieldWorks) into .agents/skills/fieldworks-winforms-to-avalonia-migration in your project. Codex loads it when a task matches its description.
Can I use Fieldworks Winforms To Avalonia Migration 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 fieldworks-winforms-to-avalonia-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fieldworks-winforms-to-avalonia-migration, .gemini/skills/fieldworks-winforms-to-avalonia-migration, .github/skills/fieldworks-winforms-to-avalonia-migration and .opencode/skills/fieldworks-winforms-to-avalonia-migration in your project.
What does Fieldworks Winforms To Avalonia Migration need to run?
SKILL.md names no scripts, command-line tools or credentials: Fieldworks Winforms To Avalonia Migration is instructions for the agent only.
Does Fieldworks Winforms To Avalonia Migration 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 Fieldworks Winforms To Avalonia Migration 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 Fieldworks Winforms To Avalonia Migration use?
Fieldworks Winforms To Avalonia Migration 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 Fieldworks Winforms To Avalonia Migration use?
About 3.7k tokens (SKILL.md is roughly 15k 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 21k tokens, read only when the agent opens those files.
What are the alternatives to Fieldworks Winforms To Avalonia Migration?
Skills that share tags, products or a category with Fieldworks Winforms To Avalonia Migration: Weekly Engineering Retro (garrytan/gstack, 136k stars), Dough Execute Plan (terryyin/lizard, 2.5k stars), Oral Paper Skill (Adkid-Zephyr/oral-paper-skill, 357 stars) and Deck Retro (asheshgoplani/agent-deck, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fieldworks Winforms To Avalonia Migration?
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 9, 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.