swift-concurrency

Is swift-concurrency safe to install?

Review the source first: our audit of swift-concurrency's source files found 2 shell commands, 0 external URLs, file reads and writes (high risk). Every command and URL listed appears verbatim in the skill's source. The skill instructs the agent to read project configuration files like Package.swift and .pbxproj, and suggests running build and test commands.

How we audit skills: our security review methodology.

Who is this skill for?

Swift developers managing concurrency issues, refactoring callback-based code, or migrating projects to Swift 6.

What can you do with it?

• Diagnosing Swift concurrency compiler and linter warnings.
• Refactoring callback-based code to async/await.
• Resolving data races and thread safety issues.
• Managing actor isolation and @MainActor usage.
• Migrating projects to Swift 6 strict concurrency requirements.

How good is this skill?

Quality score: 5/10. The skill provides clear, actionable instructions and a structured approach to debugging and migration. It includes specific guardrails and a reference router for deeper learning.

What does the skill file contain?

# Swift Concurrency

## Fast Path

Before proposing a fix:

1. Analyze `Package.swift` or `.pbxproj` to determine Swift language mode, strict concurrency level, default isolation, and upcoming features. Do this always, not only for migration work.
2. Capture the exact diagnostic and offending symbol.
3. Determine the isolation boundary: `@MainActor`, custom actor, actor instance isolation, or `nonisolated`.
4. Confirm whether the code is UI-bound or intended to run off the main actor. When spawning unstructured tasks, inspect the synchronous prefix (everything before the first `await`): start ...

Frequently asked questions