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 C of a WinForms-to-Avalonia migration: implement platform and infrastructure adapters for dependencies discovered in Phase A/B, such as persistence, process execution, dialogs, notifications…
GPL-3.0Auto-check passed
Install Wfa Platform Services
$ npx skills add tautcony/ChapterTool --skill wfa-platform-services -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tautcony/ChapterTool wfa-platform-services --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-platform-services .claude/skills/wfa-platform-services && 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-platform-services" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-platform-services into .claude/skills/wfa-platform-services/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-platform-services", 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-platform-servicesType 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-platform-services -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tautcony/ChapterTool wfa-platform-services --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-platform-services .agents/skills/wfa-platform-services && 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-platform-services" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-platform-services into .agents/skills/wfa-platform-services/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-platform-services", 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-platform-services -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tautcony/ChapterTool wfa-platform-services --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-platform-services .cursor/skills/wfa-platform-services && 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-platform-services" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-platform-services into .cursor/skills/wfa-platform-services/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-platform-services", 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-platform-services--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-platform-services -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tautcony/ChapterTool wfa-platform-services --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-platform-services .gemini/skills/wfa-platform-services && 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-platform-services" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-platform-services into .gemini/skills/wfa-platform-services/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-platform-services", 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-platform-servicesInstalls 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-platform-services -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-platform-services .github/skills/wfa-platform-services && 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-platform-services" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-platform-services into .github/skills/wfa-platform-services/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-platform-services", 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-platform-services -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-platform-services --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-platform-services .opencode/skills/wfa-platform-services && 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-platform-services" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-platform-services into .opencode/skills/wfa-platform-services/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-platform-services", 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-platform-services- GitHub stars
- 113
- Token cost
- ~1k tokens
- SKILL.md length
- 421 words
- Files
- 4 (incl. references)
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Phase C of a WinForms-to-Avalonia migration: implement platform and infrastructure adapters for dependencies discovered in Phase A/B, such as persistence, process execution, dialogs, notifications…
- Works in 7 steps: Catalog touchpoints → Interfaces vs implementations → Persisted state, when present → …
- SKILL.md covers Workflow, Corrections seen in practice, Deliverables and Handoff
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Wfa Platform Services is an agent skill from tautcony/ChapterTool. Phase C of a WinForms-to-Avalonia migration: implement platform and infrastructure adapters for dependencies discovered in Phase A/B, such as persistence, process execution, dialogs, notifications, or environment capabilities. Use only in an explicit migration when such dependencies leak into Forms/core or when the orchestrator routes here. Do not invent adapters for capabilities the product does not have, and do not implement main-window XAML.
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/external-processes.md`, `references/platform-abstraction.md` and `references/settings-migration.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-platform-services”
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 Platform Services loads about 1k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 118 tokens; SKILL.md has 421 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). 421 words, ~1,035 tokens.
Download SKILL.mdSave it as
.claude/skills/wfa-platform-services/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- wfa-platform-services
- description
- Phase C of a WinForms-to-Avalonia migration: implement platform and infrastructure adapters for dependencies discovered in Phase A/B, such as persistence, process execution, dialogs, notifications, or environment capabilities. Use only in an explicit migration when such dependencies leak into Forms/core or when the orchestrator routes here. Do not invent adapters for capabilities the product does not have, and do not implement main-window XAML.
Phase C — Platform / Infrastructure services
Replace legacy static helpers and environment coupling with injectable, testable adapters.
Read platform abstraction to define ports, external processes only when the product launches child processes, and settings migration only when settings exist.
Workflow
1. Catalog touchpoints
| Legacy pattern | Service direction |
|---|---|
| UI prompts hidden in helpers | host-owned interaction port |
| Static notifications or logging | structured diagnostic/logging port |
| Persisted application preferences | typed, versioned store |
| Filesystem or process calls | narrow adapter with cancellation and failure semantics |
| Environment capability checks | capability query plus supported/unsupported result |
| Legacy deployment integration | replace, isolate, or explicitly retire |
2. Interfaces vs implementations
- Abstractions consumable without Avalonia types where possible
- Implementations in Infrastructure, or in the UI host when they require a UI lifetime
3. Persisted state, when present
Evolve toward a versioned single document when multiple stores appear:
schemaVersion+ sections- Ordered migrators
- Reject future versions (do not overwrite with defaults)
- Preserve predecessor data while migration is being validated
- Validate the complete document before commit
- Write to a temporary sibling, flush as required, then atomically replace
- Preserve the last known-good state when parsing or migration fails
- Define in-process and cross-process coordination from the actual deployment model
4. External processes, when present
- Argument arrays, never shell string concatenation with user-controlled values
- Timeout + cancellation
- Distinguish not-found vs started-but-failed
- Document selection and fallback policy
Unavailable dependencies return a structured unavailable result without changing product state.
5. Dependency-backed adapters
Implement the ports defined in Phase B and test success, failure, cancellation, timeout, and partial-result cleanup with fakes or controlled integration fixtures.
Show full SKILL.md (169 more words)Show less
6. Secondary-surface API only
Use a narrow host interaction/window service for secondary surfaces; XAML belongs in Phase D.
7. Logging
Structured logging; bounded UI buffer with events after append; localize at display time.
Corrections seen in practice
- Resolve optional dependencies according to documented product policy, not a universal search order.
- Account for platform differences in process I/O, paths, permissions, and lifecycle when relevant.
- Prefer portable implementations when cross-platform support is an explicit requirement.
- Use one transaction boundary for one logical settings update.
- Treat migration as validated best effort, not a promise of lossless conversion.
- Do not silently change product defaults without an explicit decision.
Deliverables
- Service interfaces + registration
- Persisted-state store and migration story when persistence exists
- Required platform adapters implemented; absent capabilities were not invented
- Environment-dependent adapters covered with fakes or integration tests
- Unsupported platform behavior is explicit and recoverable
- Persisted writes are versioned, validated, and durable when persistence exists
- No UI prompts or direct environment calls leak into the application core
Handoff
- UI →
wfa-avalonia-ui - Post-port product evolution ->
wfa-post-port-evolve
© 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-platform-services of tautcony/ChapterTool.
- SKILL.md
- references/external-processes.md
- references/platform-abstraction.md
- references/settings-migration.md
Open the folder on GitHubat commit 75dd863
Compare with similar skills
Wfa Platform Services 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 Platform Services 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 Capture Contracts
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…
Related
Works with
Questions about Wfa Platform Services
What does Wfa Platform Services do?
Phase C of a WinForms-to-Avalonia migration: implement platform and infrastructure adapters for dependencies discovered in Phase A/B, such as persistence, process execution, dialogs, notifications…. Wfa Platform Services is an agent skill from tautcony/ChapterTool. Phase C of a WinForms-to-Avalonia migration: implement platform and infrastructure adapters for dependencies discovered in Phase A/B, such as persistence, process execution, dialogs, notifications, or environment capabilities.
How do I install Wfa Platform Services in Claude Code?
Run `npx skills add tautcony/ChapterTool --skill wfa-platform-services -a claude-code`. Or copy the skill folder (.codex/skills/wfa-platform-services in tautcony/ChapterTool) into .claude/skills/wfa-platform-services in your project. Claude Code loads it when a task matches its description.
How do I install Wfa Platform Services in Codex?
Run `npx skills add tautcony/ChapterTool --skill wfa-platform-services -a codex`. Or copy the skill folder (.codex/skills/wfa-platform-services in tautcony/ChapterTool) into .agents/skills/wfa-platform-services in your project. Codex loads it when a task matches its description.
Can I use Wfa Platform Services 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-platform-services -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-platform-services, .gemini/skills/wfa-platform-services, .github/skills/wfa-platform-services and .opencode/skills/wfa-platform-services in your project.
What does Wfa Platform Services need to run?
SKILL.md names no scripts, command-line tools or credentials: Wfa Platform Services is instructions for the agent only.
Does Wfa Platform Services 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 Platform Services 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 Platform Services use?
Wfa Platform Services 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 Platform Services 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 872 tokens, read only when the agent opens those files.
What are the alternatives to Wfa Platform Services?
Skills that share tags, products or a category with Wfa Platform Services: 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 Platform Services?
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.