Swift-Agent-Skills: A Link Directory for Swift Agent Skills, Not a Skill Itself

What Problem a Link List Solves for Swift Developers

Agent skills for Swift development exist, but they are scattered across individual GitHub accounts with no shared naming convention. Searching for SwiftUI agent skills returns a mix of tutorials, prompt dumps and unrelated repositories. This project answers one narrow question: which community skills exist, for which Apple frameworks, and who wrote each one. The README organizes entries under headings such as SwiftUI Skills, SwiftData Skills, Swift Concurrency Skills, Swift Testing Skills, Accessibility Skills, App Intents Skills, App Store Skills, Architecture Skills, Background Execution Skills, Core Data Skills, Focus Management Skills, Observability Skills, Performance Skills, Security Skills, Tool Skills, User Interface Skills and Widgets Skills. The intended reader is an iOS or macOS developer who already uses an agent-based coding tool and wants to bias its output toward current Apple platform idioms instead of generic Swift. The repository states its own scope plainly: it contains links to community-maintained agent skills, organized by framework and area. It does not contain the skills themselves.

How the Directory Is Organized and What Each Entry Tells You

Every entry follows the same shape: a skill name as the link text, the repository URL, and the author's name and GitHub handle. Under SwiftUI Skills, for example, the README lists SwiftUI Pro by Paul Hudson, SwiftUI UI Patterns and SwiftUI View Refactor by Thomas Ricouard, and SwiftUI Design Principles by Arjit Jaiswal. Under Swift Concurrency Skills there are three entries, two of them sharing the display name Swift Concurrency Expert but pointing at different repositories, one by Thomas Ricouard and one by Antoine van der Lee. That duplication is worth noticing: the directory does not rank, compare or deduplicate by function, so two entries under the same heading may overlap heavily, and picking between them means opening both repositories. Some authors appear repeatedly across categories. Paul Hudson has entries under SwiftUI, SwiftData, Swift Concurrency and Swift Testing. Anton Novoselov appears under Swift Language, App Intents, Background Execution and Observability. Several entries point into a shared repository rather than a dedicated one, as with Thomas Ricouard's Skills repository supplying SwiftUI UI Patterns, SwiftUI View Refactor, Swift Concurrency Expert, App Store Changelog and SwiftUI Performance Audit. The repository layout also includes an assets directory holding the logo referenced at the top of the README, and the table of contents links out to AGENTS.md files and a further reading section.

The Safety Note Is the Most Important Line in the README

The README carries a warning block near the top, and it is not boilerplate. It states that before installing a third-party agent skill you should read it thoroughly and trust the author, and that being listed is not an endorsement. It then asks readers to read the open-source skills and check that they benefit them before using them, and notes that you can create your own skill from them provided you respect the licences. This matters because of what an agent skill is in practice: instructions and often helper scripts that a coding agent loads and may execute on your machine, with access to your project files. A directory that aggregates such artifacts from dozens of independent authors cannot vouch for any of them, and this one does not pretend to. The framing is consistent with the repository's own MIT licence, which covers the directory content, not the linked projects. Each linked skill carries its own licence, which the README does not restate per entry. If you are evaluating this directory for a team, the honest summary is that the curation is editorial (someone chose to include these links) rather than technical (nobody here has audited the code).

Installing Skills: What This Repository Does and Does Not Give You

There is no package manifest here, no Swift Package Manager target, no Homebrew formula and no install script described in the material. Cloning this repository gets you a README, a logo asset and links. The actual installation path runs through the tool you use: the README points to a video titled Learn how to install and use agent skills with Xcode, Claude Code, Codex, and more, and the header names Claude Code, Codex, Cursor and Windsurf as supported tools. In other words, the mechanism is per-tool, and the directory deliberately does not document it. That is a defensible editorial choice for a link list, but it means the setup instructions you need live in each linked skill's repository and in your agent tool's documentation, not here. The README does surface one adjacent resource that is closer to configuration: a section of AGENTS.md files, which is the filename convention several agent tools use for project-level instructions. If you want something concrete to do after reading the list, opening the AGENTS.md section and the linked skill repositories is the path the README itself lays out.

Where the Directory Breaks Down

The first limitation is staleness. A link list has no build step, no test suite and no version pinning, so nothing detects when a linked repository is renamed, archived, made private or rewritten. The README also mixes granularities: some entries are single-purpose skills such as Swift FormatStyle Skill or Figma to SwiftUI Skill, while others, like Thomas Ricouard's Skills repository, are collections where one link points at a subtree of a larger project. The App Store Review entry points at a path inside 3paws-ai/mobile-ai-skills, and the Writing for Interfaces entry points at a path inside andrewgleave/skills; in both cases the link target is a directory inside someone else's monorepo, which is a moving target. Second, the categories are not mutually exclusive. A skill about SwiftData testing could reasonably sit under SwiftData Skills or Swift Testing Skills, and the README's placement is one person's judgement. Third, and most consequential, the directory gives you no quality signal beyond the author's name. There are no descriptions per entry, no last-updated dates, no indication of which Swift or Xcode version a skill assumes. If your project targets an older SDK, you have no way to tell from this page whether a given skill's guidance is current. The material does not say how entries are reviewed or how often the list is refreshed, so treat freshness as unverified.

What to Compare It Against

The obvious alternative is not another directory but a single maintained skill repository. Paul Hudson's SwiftUI-Agent-Skill, listed here as SwiftUI Pro, is the clearest contrast: it is one repository owned by one author, covering one framework, with its own README, its own licence and its own update cadence. The difference in approach is depth versus breadth. A single-author skill repository can be read in one sitting and its guidance checked against a known SwiftUI version; this directory spans roughly eighteen categories and several dozen authors, which makes it useful for discovery and useless for verification. A second alternative is writing your own skill from the project's conventions, which the README explicitly suggests, noting only that you should respect the licences of anything you adapt. That route costs more upfront but produces an artifact tuned to your codebase, your deployment target and your review rules, and it removes the third-party trust question entirely. A third option, for teams that already have style guides, is an AGENTS.md file at the repository root; the directory links to examples of these, and unlike a downloaded skill it lives in your own version control.

Maintenance, Licensing and What Changes Under You

The repository is MIT-licensed and, per the supplied metadata, was last pushed on 2026-09-04 with no releases retrieved. No release history means no changelog to read and no version to pin; if you reference this list in internal documentation, link to a commit rather than to main, because the contents are links and links move. Maintenance cost for the directory itself is low by design: adding an entry is a README edit. Maintenance cost for you is the part that matters. Every skill you adopt from the list is a separate dependency with a separate licence, and the README's own instruction is to respect those licences when reusing or adapting the material. The MIT licence here does not extend to linked projects, and the material does not state the licence of any individual entry. If your organisation has a policy on vendoring external prompts or scripts into a developer environment, this directory will trigger it once per skill rather than once per repository, which is more review work than a single dependency would be. Nothing in the supplied material describes a contribution process beyond a Contributing section referenced in the table of contents.

Editorial conclusion

Adopt this directory if you already run Claude Code, Codex, Cursor or Windsurf on an Apple platform codebase and want a starting list of skills grouped by framework, but treat it as an index, not a dependency: nothing here is installed by cloning the repository. Skip it if you need a maintained, versioned package with a test suite, or if your policy forbids pulling third-party prompts and scripts into a development environment. Before adding any single skill, open that skill's own repository, read its SKILL.md and any bundled scripts end to end, and confirm its licence separately, because the MIT licence on this directory does not travel with the entries it links to.

Official sources

1. Issues
2. License: MIT
3. README
4. twostraws/Swift-Agent-Skills on GitHub