← Products

Developer tools
⚙ Needs: a Swift project (Xcode or SwiftPM); basic familiarit…

Swift Concurrency diagnostics and Swift 6 migration

Diagnose Swift concurrency errors, refactor callbacks to async/await, and migrate to Swift 6 safely

At a glance
What
Diagnose Swift concurrency errors, refactor callbacks to async/await, and migrate to Swift 6 safely
Cost
Free
Needs
a Swift project (Xcode or SwiftPM); basic familiarity with async/await, actors and Swift 6 concurrency checking
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

A
Created by: Avdlee
⌁

Install

Prerequisites: a Swift project (Xcode or SwiftPM); basic familiarity with async/await, actors and Swift 6 concurrency checking Install "Swift Concurrency diagnostics and Swift 6 migration" for me. Give my agent the concurrency workflow — reading project settings before diagnosing, mapping common isolation/Sendable diagnostics to smallest safe fixes, choosing the right concurrency tool, and running the build-fix-rebuild-test loop for Swift 6 migration Repository: https://github.com/avdlee/swift-concurrency-agent-skill/blob/main/skills/swift-concurrency/SKILL.md 1. Fetch the SKILL.md file (and its references/ folder) for the avdlee-swift-concurrency-agent-skill-swift-concurrency skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files (references/) into the agent's skills directory, in a folder named "avdlee-swift-concurrency-agent-skill-swift-concurrency". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. confirm my project's Swift language mode and strict-concurrency settings before migration advice). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.