Skip to content
TrustedSkillsbeta
Back to all skills

migrating-to-swift-concurrency

Checked
kylehughes·v1.0.0·backend·MIT

Provides the complete Swift Concurrency Migration Guide. Use when migrating to Swift 6, resolving data-race safety errors, understanding Sendable and actor isolation, or incrementally adopting async/a

Install on your platform

Showing OpenClaw.

  1. 1

    Run this in your terminal

    terminal
    $

What we know about this skill

Publisher

kylehughes

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned kylehughes/the-unofficial-swift-concurrency-migration-skill at bcb4569878.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
bcb4569878
Manifest
migrating-to-swift-concurrency/SKILL.md
Scanned
18 files, 3,121 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides a comprehensive guide for migrating existing Swift codebases to Swift Concurrency. It covers the process of upgrading to Swift 6, addresses and resolves potential data-race safety issues that arise during migration, and explains the principles behind Sendable and actor isolation. The guide facilitates an incremental adoption approach, allowing developers to transition gradually.

When to use it

  • Swift 6 Upgrade: You're preparing your project for Swift 6 and need assistance with concurrency-related changes.
  • Data Race Resolution: Your code is flagged with data-race safety errors during compilation or testing.
  • Understanding Isolation: You want a deeper understanding of Sendable protocols and how actors enforce isolation.
  • Incremental Adoption: You prefer to introduce Swift Concurrency features in stages rather than a complete rewrite.

Key capabilities

  • Complete Swift Concurrency Migration Guide
  • Data-race safety error resolution
  • Explanation of Sendable protocol
  • Actor isolation principles
  • Incremental adoption strategy

Example prompts

  • "Guide me through migrating my existing dispatch queue code to actors."
  • "How do I resolve a data-race safety error related to shared mutable state?"
  • "Explain the difference between Sendable and awaiting in Swift Concurrency."

Tips & gotchas

The guide assumes familiarity with basic Swift programming concepts. Successfully migrating requires careful consideration of how shared mutable state is handled within your codebase, as this is a common source of data-race issues.