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…
Phase A of a WinForms-to-Avalonia migration: inventory the legacy application, split responsibilities, capture command and state contracts, build a coverage matrix, and define acceptance evidence…
GPL-3.0Auto-check passed
Install Wfa Capture Contracts
$ npx skills add tautcony/ChapterTool --skill wfa-capture-contracts -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tautcony/ChapterTool wfa-capture-contracts --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/tautcony/ChapterTool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/wfa-capture-contracts .claude/skills/wfa-capture-contracts && 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 "wfa-capture-contracts" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-capture-contracts into .claude/skills/wfa-capture-contracts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-capture-contracts", 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/tautcony/ChapterTool/tree/master/.codex/skills/wfa-capture-contractsType 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 tautcony/ChapterTool --skill wfa-capture-contracts -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tautcony/ChapterTool wfa-capture-contracts --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/wfa-capture-contracts .agents/skills/wfa-capture-contracts && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wfa-capture-contracts" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-capture-contracts into .agents/skills/wfa-capture-contracts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-capture-contracts", 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 tautcony/ChapterTool --skill wfa-capture-contracts -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tautcony/ChapterTool wfa-capture-contracts --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/wfa-capture-contracts .cursor/skills/wfa-capture-contracts && 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 "wfa-capture-contracts" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-capture-contracts into .cursor/skills/wfa-capture-contracts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-capture-contracts", 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/tautcony/ChapterTool.git --path .codex/skills/wfa-capture-contracts--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 tautcony/ChapterTool --skill wfa-capture-contracts -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tautcony/ChapterTool wfa-capture-contracts --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/wfa-capture-contracts .gemini/skills/wfa-capture-contracts && 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 "wfa-capture-contracts" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-capture-contracts into .gemini/skills/wfa-capture-contracts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-capture-contracts", 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 tautcony/ChapterTool wfa-capture-contractsInstalls 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 tautcony/ChapterTool --skill wfa-capture-contracts -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/wfa-capture-contracts .github/skills/wfa-capture-contracts && 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 "wfa-capture-contracts" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-capture-contracts into .github/skills/wfa-capture-contracts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-capture-contracts", 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 tautcony/ChapterTool --skill wfa-capture-contracts -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tautcony/ChapterTool wfa-capture-contracts --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/wfa-capture-contracts .opencode/skills/wfa-capture-contracts && 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 "wfa-capture-contracts" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-capture-contracts into .opencode/skills/wfa-capture-contracts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-capture-contracts", 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
wfa-capture-contracts- GitHub stars
- 113
- Token cost
- ~1k tokens
- SKILL.md length
- 418 words
- Files
- 4 (incl. references)
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Phase A of a WinForms-to-Avalonia migration: inventory the legacy application, split responsibilities, capture command and state contracts, build a coverage matrix, and define acceptance evidence…
- Works in 7 steps: Inventory → Split modules → Command catalog → …
- SKILL.md covers Workflow, Deliverables and Handoff
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Wfa Capture Contracts is an agent skill from tautcony/ChapterTool. Phase A of a WinForms-to-Avalonia migration: inventory the legacy application, split responsibilities, capture command and state contracts, build a coverage matrix, and define acceptance evidence without implementing Avalonia UI. Use only in an explicit WinForms-to- Avalonia migration when behavior is undocumented or the orchestrator routes here. Generated artifacts must use the current repository's real paths, terminology, and capabilities.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/contract-templates.md`, `references/coverage-matrix.md` and `references/module-split.md`).
It works with Avalonia. The repository describes itself as: Cross-platform chapter editing and conversion toolkit for desktop, CLI, WebAssembly, and Node.js, with support for Blu-ray and common media chapter formats. The licence is GPL-3.0.
Example prompts
- “/wfa-capture-contracts”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 75dd863. 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
Wfa Capture Contracts loads about 1k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 117 tokens; SKILL.md has 418 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 tautcony/ChapterTool at commit 75dd863, republished under its GPL-3.0 licence (© tautcony). 418 words, ~1,021 tokens.
Download SKILL.mdSave it as
.claude/skills/wfa-capture-contracts/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- wfa-capture-contracts
- description
- Phase A of a WinForms-to-Avalonia migration: inventory the legacy application, split responsibilities, capture command and state contracts, build a coverage matrix, and define acceptance evidence without implementing Avalonia UI. Use only in an explicit WinForms-to- Avalonia migration when behavior is undocumented or the orchestrator routes here. Generated artifacts must use the current repository's real paths, terminology, and capabilities.
Phase A — Capture legacy contracts
Turn a WinForms app into documented contracts so the rewrite does not depend on copying event handlers. Prefer Designer metadata, resources, handlers, helpers, services, and tests over screenshots alone.
Read contract templates when writing behavior contracts, coverage matrix when checking file ownership, and module split when defining responsibility boundaries.
Workflow
1. Inventory
Classify legacy files:
| Category | Typical contents |
|---|---|
| Entry / shell | Program, main Form, startup args, runtime checks |
| Domain models | Entities and value objects mutated by legacy workflows |
| Application behavior | Use cases, policies, validation, calculations |
| State and data | In-memory state, persistence, mapping, synchronization |
| External boundaries | Filesystem, network, process, device, or service integrations actually present |
| Supporting UI | Secondary windows, dialogs, notifications, settings surfaces |
| Platform | Environment-specific capabilities and lifecycle behavior |
| Build / distribution | Projects, packaging, CI, deployment assets |
| Tests / fixtures | Unit, integration, UI tests, representative scenarios |
Assign every production file a primary module.
2. Split modules
Suggested shape (rename to the product):
- UI shell and interactions
- Application core and state transitions
- Boundary ports and adapters, grouped by dependency
- Supporting UI and platform services
- Tests, build, distribution, and assets
Each module doc: purpose, rewrite boundary, reviewed files, behaviors, UI coupling to strip,
risks/decisions. See references/module-split.md.
3. Command catalog
For every user-visible action:
- Entry point or user gesture
- Preconditions and authorization
- State transitions
- Observable outputs and external effects
- Cancellation, failure, and recovery behavior
- Platform-specific or intentionally hidden behavior
Also list semantic window state (context, selection, modes, pending changes, status) rather than only control names.
Show full SKILL.md (170 more words)Show less
4. Coverage matrix
| File | Primary module | Referenced | Notes |
Mechanically verify against a full legacy file listing.
5. Acceptance samples and fixture policy
For each major workflow: success, validation failure, cancellation, dependency failure, and recovery from partial or stale state. Derive scenarios from the application, not this skill.
Plan a stable fixture/scenario layout. Prefer the smallest representative data that exercises real behavior over inventory-only checks.
6. Decision log
Supported platforms, accessibility expectations, hidden gesture policy, deployment strategy, external dependencies, compatibility obligations, and known bugs to preserve or fix.
7. Capability / apply order
Map modules to implementable capabilities ordered by dependency:
- Scaffolding + core contracts
- Platform services
- Pure application behavior and boundary contracts
- Infrastructure adapters required by those contracts
- UI shell
- Later product evolution and structural hardening
Document parallel lanes and shared-contract locks.
Deliverables
- Rewrite index linking modules
- Module docs with boundaries
- Coverage matrix without orphans
- Command + state contracts
- Fixture/acceptance list
- Risk and decision list
- Capability apply order
Handoff
Load wfa-extract-domain. Do not implement Avalonia Views here.
© tautcony, GPL-3.0. 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 (references) in .codex/skills/wfa-capture-contracts of tautcony/ChapterTool.
- SKILL.md
- references/contract-templates.md
- references/coverage-matrix.md
- references/module-split.md
Open the folder on GitHubat commit 75dd863
Compare with similar skills
Wfa Capture Contracts 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 |
|---|---|---|---|---|---|---|
| Wfa Capture Contracts this skilltautcony/ChapterTool | 113 | — | ~1k | Automated safety check: Pass | GPL-3.0 | |
| 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 tautcony/ChapterTool
All 9 skills in this repoReclaim Code Entropy
tautcony/ChapterTool
Find, rank, and safely remove accidental codebase complexity by proving real consumers, dynamic entrypoints, compatibility obligations, duplicate representations, speculative surfaces, and lifecycle…
Wfa Harden Decompose
tautcony/ChapterTool
Phase G of a WinForms-to-Avalonia migration: decompose oversized UI state and orchestration, harden asynchronous workflows and external boundaries, preserve composition lifetimes, keep Headless…
Wfa Post Port Evolve
tautcony/ChapterTool
Phase F of a WinForms-to-Avalonia migration: evolve the Avalonia trunk after cutover without reintroducing WinForms coupling or bypassing established layers.
Winforms To Avalonia
tautcony/ChapterTool
Orchestrate a phased WinForms-to-Avalonia migration: behavior contracts, UI-independent application logic, platform adapters, MVVM shell, parity/cutover, evolution, and hardening.
Wfa Avalonia UI
tautcony/ChapterTool
Phase D of a WinForms-to-Avalonia migration: build the Avalonia UI shell with composition, MVVM state and commands, responsive XAML, accessibility, localization boundaries, and behavior-focused…
Wfa Extract Domain
tautcony/ChapterTool
Phase B of a WinForms-to-Avalonia migration: extract UI-independent application behavior, state rules, use cases, and boundary contracts with TDD and no WinForms/Avalonia references.
Related
Works with
Questions about Wfa Capture Contracts
What does Wfa Capture Contracts do?
Phase A of a WinForms-to-Avalonia migration: inventory the legacy application, split responsibilities, capture command and state contracts, build a coverage matrix, and define acceptance evidence…. Wfa Capture Contracts is an agent skill from tautcony/ChapterTool. Phase A of a WinForms-to-Avalonia migration: inventory the legacy application, split responsibilities, capture command and state contracts, build a coverage matrix, and define acceptance evidence without implementing Avalonia UI.
How do I install Wfa Capture Contracts in Claude Code?
Run `npx skills add tautcony/ChapterTool --skill wfa-capture-contracts -a claude-code`. Or copy the skill folder (.codex/skills/wfa-capture-contracts in tautcony/ChapterTool) into .claude/skills/wfa-capture-contracts in your project. Claude Code loads it when a task matches its description.
How do I install Wfa Capture Contracts in Codex?
Run `npx skills add tautcony/ChapterTool --skill wfa-capture-contracts -a codex`. Or copy the skill folder (.codex/skills/wfa-capture-contracts in tautcony/ChapterTool) into .agents/skills/wfa-capture-contracts in your project. Codex loads it when a task matches its description.
Can I use Wfa Capture Contracts 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 tautcony/ChapterTool --skill wfa-capture-contracts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wfa-capture-contracts, .gemini/skills/wfa-capture-contracts, .github/skills/wfa-capture-contracts and .opencode/skills/wfa-capture-contracts in your project.
What does Wfa Capture Contracts need to run?
SKILL.md names no scripts, command-line tools or credentials: Wfa Capture Contracts is instructions for the agent only.
Does Wfa Capture Contracts 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 Wfa Capture Contracts 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 Wfa Capture Contracts use?
Wfa Capture Contracts is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wfa Capture Contracts use?
About 1k tokens (SKILL.md is roughly 4.1k 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 889 tokens, read only when the agent opens those files.
What are the alternatives to Wfa Capture Contracts?
Skills that share tags, products or a category with Wfa Capture Contracts: 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 Wfa Capture Contracts?
tautcony (a GitHub user) maintains it in tautcony/ChapterTool, which has 113 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 8, 2026.
Source: tautcony/ChapterTool on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.