New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Atomui Upgrade Dependencies

by AtomUI in AtomUI/AtomUI

A skill your agent uses when upgrading AtomUI NuGet dependencies, source dependency projects, ReactiveUI, Avalonia, Splat, or any third-party version where compatibility must be evaluated before…

LGPL-3.0Auto-check passedDevelopment

Install Atomui Upgrade Dependencies

skills CLI
$ npx skills add AtomUI/AtomUI --skill atomui-upgrade-dependencies -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AtomUI/AtomUI atomui-upgrade-dependencies --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AtomUI/AtomUI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/upgrade-dependencies .claude/skills/atomui-upgrade-dependencies && rm -rf skills-src

Use ~/.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/

Facts

Skill name
atomui-upgrade-dependencies
GitHub stars
842
Token cost
~1.2k tokens
SKILL.md length
510 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
LGPL-3.0

At a glance

A skill your agent uses when upgrading AtomUI NuGet dependencies, source dependency projects, ReactiveUI, Avalonia, Splat, or any third-party version where compatibility must be evaluated before…

  • Works in 7 steps: Map the package family to its upstream… → Ensure .referenceprojects/ exists. → If it is missing, clone the upstream… → …
  • Upgrading AtomUI NuGet dependencies
  • SKILL.md covers Core Principle, Hard Rules, Version Sources and Reference Source Workflow, plus 4 more sections
  • Calls git and dotnet

What it does

Atomui Upgrade Dependencies is an agent skill from AtomUI/AtomUI. Use when upgrading AtomUI NuGet dependencies, source dependency projects, ReactiveUI, Avalonia, Splat, or any third-party version where compatibility must be evaluated before implementation.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Avalonia. The repository describes itself as: An enhancement and extension library for Avalonia, bringing the Ant Design design language, modern controls, theming, native integrations, and cross-platform UI capabilities to… The licence is LGPL-3.0.

When your agent uses it

  • Upgrading AtomUI NuGet dependencies
  • Source dependency projects
  • Any third-party version where compatibility must be evaluated before implementation

Example prompts

  • “/atomui-upgrade-dependencies”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Map the package family to its upstream source repository.
  2. Ensure .referenceprojects/ exists.
  3. If it is missing, clone the upstream repository directly under .referenceprojects.
  4. Run git fetch --tags --prune in the reference repository.
  5. Resolve both the current version and target version to tags, branches, or commits.
  6. If a version cannot be resolved, report the exact blocker; do not guess.
  7. Use source diffs as the primary evidence

What it can do on your machine

Read from SKILL.md and the folder at commit e82b36c. 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

    Shell commands in SKILL.md call:

    • git
    • dotnet

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

Atomui Upgrade Dependencies loads about 1.2k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 510 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

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 AtomUI/AtomUI at commit e82b36c, republished under its LGPL-3.0 licence (© AtomUI). 510 words, ~1,195 tokens.

Download SKILL.mdSave it as .claude/skills/atomui-upgrade-dependencies/SKILL.md (or your agent's skills folder).
name
atomui-upgrade-dependencies
description
Use when upgrading AtomUI NuGet dependencies, source dependency projects, ReactiveUI, Avalonia, Splat, or any third-party version where compatibility must be evaluated before implementation.

AtomUI Dependency Upgrade

Core Principle

Dependency upgrades in AtomUI are evidence-first work. The only objective basis for evaluating version changes is comparing the dependency project's source code between the current version and the target version. Changelogs, release notes, issues, and docs are useful references only; never use them as the primary compatibility basis.

Hard Rules

  • Do not modify dependency versions, AtomUI source, or generated files during evaluation.
  • Do not implement an upgrade until the user has reviewed and approved the upgrade task plan.
  • Do not commit unless the user explicitly asks for a commit.
  • Upgrade one dependency family at a time unless the user explicitly approves a grouped upgrade.
  • Preserve AtomUI behavior. Compatibility fixes are allowed; unrelated refactors and behavior improvements are not part of dependency upgrade work.
  • Check the dirty worktree first and do not revert unrelated user changes.
  • If planned work changes after discovery, stop and update the plan for user review before continuing.

Version Sources

Check these before evaluating an upgrade:

  • build/Version.props
  • Directory.Packages.props
  • Relevant *.csproj package references
  • Existing lock files, restore output, or generated props when relevant

Record the current version, requested target version, and the file that owns each version.

Reference Source Workflow

AtomUI keeps dependency source projects under .referenceprojects.

  1. Map the package family to its upstream source repository.
  2. Ensure .referenceprojects/<RepoName> exists.
  3. If it is missing, clone the upstream repository directly under .referenceprojects.
  4. Run git fetch --tags --prune in the reference repository.
  5. Resolve both the current version and target version to tags, branches, or commits.
  6. If a version cannot be resolved, report the exact blocker; do not guess.
  7. Use source diffs as the primary evidence:
bash
git diff <old-ref>..<new-ref> --name-status
git diff <old-ref>..<new-ref> -- <relevant paths>
git log --oneline <old-ref>..<new-ref>

For Avalonia, use .referenceprojects/Avalonia when present.

Show full SKILL.md (228 more words)Show less

Evaluation Checklist

Produce an evaluation before proposing implementation. Include:

  • Current version and target version.
  • Exact source refs compared.
  • Source diff summary:
    • public API changes
    • internal API changes AtomUI depends on
    • behavior changes
    • removed or renamed symbols
    • dependency constraint changes
    • target framework, runtime, platform, or tooling changes
  • AtomUI usage impact from rg searches for affected symbols, namespaces, XAML members, extension methods, reflection access, and package references.
  • Risk level with concrete reasons.
  • Required AtomUI changes, if any.
  • Verification commands and manual scenarios.
  • Changelog or release note references, clearly marked as secondary context.

Upgrade Plan Gate

After evaluation, create a complete trackable task plan and wait for user approval. The plan must be ordered and concrete enough to execute item by item.

Use this shape:

markdown
## Upgrade Plan: <Dependency> <current-version> -> <target-version>

- [ ] 1. Update version declarations in <files>.
- [ ] 2. Apply compatibility fix for <specific API or behavior>.
- [ ] 3. Update tests or Gallery scenarios for <specific affected area>.
- [ ] 4. Run restore/build verification.
- [ ] 5. Run targeted verification for <specific control or feature>.
- [ ] 6. Report residual risks and pre-existing failures.

The user must approve the plan before implementation. Approval must be explicit, such as "approved", "continue", "execute this plan", or equivalent wording.

Execution Rules

Once approved:

  • Execute the task list strictly from top to bottom.
  • Update task status incrementally as items complete.
  • Keep edits scoped to the approved plan.
  • If a new incompatibility appears, pause and revise the plan for user review.
  • If verification fails, distinguish upgrade-caused failures from pre-existing failures.

Verification

Choose verification based on the affected dependency. At minimum, use:

bash
dotnet restore
dotnet build controlgallery/AtomUIGallery.Desktop/AtomUIGallery.Desktop.csproj -c Debug --framework net10.0 /p:BuildInParallel=false /p:UseSharedCompilation=false

Add targeted tests, sample apps, Gallery scenarios, or reference-project inspections when the source diff shows control behavior, rendering, input, binding, platform, or threading changes.

© AtomUI, LGPL-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

Just SKILL.md in .agents/skills/upgrade-dependencies of AtomUI/AtomUI.

Open the folder on GitHubat commit e82b36c

Compare with similar skills

Atomui Upgrade Dependencies 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.

Atomui Upgrade Dependencies compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Atomui Upgrade Dependencies this skillAtomUI/AtomUI842—~1.2kAutomated safety check: PassLGPL-3.0
Docs Style LintAvaloniaUI/avalonia-docs166—~4.6kAutomated safety check: PassNone
Wfa Harden Decomposetautcony/ChapterTool113—~1.1kAutomated safety check: PassGPL-3.0
Winforms To Avaloniatautcony/ChapterTool113—~1.2kAutomated safety check: PassGPL-3.0
Fieldworks Code Commentingsillsdev/FieldWorks110—~2.4kAutomated safety check: PassCustom licence
Convert Slicesillsdev/FieldWorks110—~3.3kAutomated safety check: PassCustom licence

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.

    166 GitHub stars~4.6k tokensUpdated today
    DevelopmentAuto-check passed

  • 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…

    113 GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

  • 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.

    113 GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Fieldworks Code Commenting

    sillsdev/FieldWorks

    The FieldWorks code-comment standard for C, C/C++, IDL, PowerShell, and project-file/Avalonia-view XML comments.

    110 GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • 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.

    110 GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed

  • 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.

    113 GitHub stars~862 tokensUpdated today
    Testing & QAAuto-check passed

More from AtomUI/AtomUI

All 15 skills in this repo

  • Atomui Gallery Local Debug

    AtomUI/AtomUI

    A skill your agent uses when building, launching, debugging, or visually inspecting AtomUIGallery.Desktop from an AtomUI checkout where installed or mounted Gallery apps may share its name or bundle…

    842 GitHub stars~983 tokensUpdated today
    Auto-check passed

  • Atomui Commit Msg

    AtomUI/AtomUI

    Generate a single-line commit message for AtomUI by reading the project's git staged area and recent commit style.

    842 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Atomui Control Optimization

    AtomUI/AtomUI

    A skill your agent uses when optimizing, refactoring, reviewing, or fixing AtomUI controls, including control API contracts, member layout, file splitting, lifecycle, AXAML structure, correctness…

    842 GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Atomui Control Documentation

    AtomUI/AtomUI

    A skill your agent uses when creating, completing, splitting, reviewing, or synchronizing AtomUI control documentation under docs/controls, including overview.md, implementation.md, token.md…

    842 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • 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…

    842 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Version Release

    AtomUI/AtomUI

    A skill your agent uses when preparing or validating an AtomUI release, including version-scope confirmation, AtomUIVersion consistency, README version sync, CHANGELOG and Chinese release sections…

    842 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Atomui Upgrade Dependencies

What does Atomui Upgrade Dependencies do?

A skill your agent uses when upgrading AtomUI NuGet dependencies, source dependency projects, ReactiveUI, Avalonia, Splat, or any third-party version where compatibility must be evaluated before…. Atomui Upgrade Dependencies is an agent skill from AtomUI/AtomUI. Use when upgrading AtomUI NuGet dependencies, source dependency projects, ReactiveUI, Avalonia, Splat, or any third-party version where compatibility must be evaluated before implementation.

When should I use Atomui Upgrade Dependencies?

Atomui Upgrade Dependencies fits situations like: upgrading AtomUI NuGet dependencies; source dependency projects; any third-party version where compatibility must be evaluated before implementation.

How do I install Atomui Upgrade Dependencies in Claude Code?

Run `npx skills add AtomUI/AtomUI --skill atomui-upgrade-dependencies -a claude-code`. Or copy the skill folder (.agents/skills/upgrade-dependencies in AtomUI/AtomUI) into .claude/skills/atomui-upgrade-dependencies in your project. Claude Code loads it when a task matches its description.

How do I install Atomui Upgrade Dependencies in Codex?

Run `npx skills add AtomUI/AtomUI --skill atomui-upgrade-dependencies -a codex`. Or copy the skill folder (.agents/skills/upgrade-dependencies in AtomUI/AtomUI) into .agents/skills/atomui-upgrade-dependencies in your project. Codex loads it when a task matches its description.

Can I use Atomui Upgrade Dependencies 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 AtomUI/AtomUI --skill atomui-upgrade-dependencies -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/atomui-upgrade-dependencies, .gemini/skills/atomui-upgrade-dependencies, .github/skills/atomui-upgrade-dependencies and .opencode/skills/atomui-upgrade-dependencies in your project.

What does Atomui Upgrade Dependencies need to run?

Going by SKILL.md and its folder, Atomui Upgrade Dependencies needs the command-line tools its instructions call (git and dotnet).

Does Atomui Upgrade Dependencies access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Atomui Upgrade Dependencies 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 Atomui Upgrade Dependencies use?

Atomui Upgrade Dependencies is published under the LGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Atomui Upgrade Dependencies use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 Atomui Upgrade Dependencies?

Skills that share tags, products or a category with Atomui Upgrade Dependencies: Docs Style Lint (AvaloniaUI/avalonia-docs, 166 stars), Wfa Harden Decompose (tautcony/ChapterTool, 113 stars), Winforms To Avalonia (tautcony/ChapterTool, 113 stars) and Fieldworks Code Commenting (sillsdev/FieldWorks, 110 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Atomui Upgrade Dependencies?

AtomUI (a GitHub organization) maintains it in AtomUI/AtomUI, which has 842 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.

Source: AtomUI/AtomUI on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.