write-swift SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.
write-swift from emilkowalski/skill is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add emilkowalski/skill/write-swift@git:20261113.0f2e23bPins git:20261113.0f2e23b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- emilkowalski/skill
- Path
skills/write-swift/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261113.0f2e23b, committed Nov 13, 2026
- First version recorded
- Aug 21, 2026
- Size
- 42,776 bytes
- Repository stars
- 58,162
- License
- MIT
How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros, and the modern language features agents don't know about yet. Use when writing, reviewing, or migrating Swift, or when a concurrency error, a hang, a data race, a retain cycle, or a performance problem needs fixing.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Write Swift ## Initial Response When this skill is first invoked without a specific question, respond only with: > I'm ready to help you write modern Swift, the way the language wants to be written. Do not provide any other information until the user asks a question. How to write Swift the way the language wants to be written, current through Swift 6.4. **Toolchain baseline: Swift 6.3.** Check `swift --version`. Everything here compiles on 6.3 unless marked ⚠, which flags unreleased Swift 6.4 features. Concurrency guidance assumes the Swift 6.2 model — if the project is on 6.1 or earlier, §3's rules about `async` and `@concurrent` do not apply. The through-line: **Swift is a progressive-disclosure language. Start with the simplest, most static, most single-threaded thing that works, and buy dynamism — concurrency, reference semantics, existentials, unsafe pointers — only where you can point at the reason.** Every rule below is an application of that. Model this hierarchy of defaults. Move down a level only with a reason you can state: | Need | Reach for | Move down only when | …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_wxrpn5wwhwyrkrvm/ad8f3af70b627c165ecd73ecdba49449e35301dd845c397cf813f06582bbdac2.json
Then /plugin install write-swift@markdownregistry-wxrpn5wwhwyrkrvm in Claude Code. It installs git:20261113.0f2e23b, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add emilkowalski/skill/write-swift@sha256:ad8f3af70b627c16The line at the top of this page pins the label git:20261113.0f2e23b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_wxrpn5wwhwyrkrvm)
0 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in emilkowalski/skill/write-swift since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of write-swift from somewhere else? Ask it: where did my write-swift come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between Aug 21, 2026 and Nov 13, 2026, about one every 28 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261113.0f2e23b latest | 2026-11-13 | 0f2e23b | 42,776 B | A | view · diff |
| git:20260915.85e8e23 | 2026-09-15 | 85e8e23 | 42,445 B | A | view · diff |
| git:20260915.0b85d4b | 2026-09-15 | 0b85d4b | 42,548 B | A | view · diff |
| git:20260821.8e1ec02 | 2026-08-21 | 8e1ec02 | 42,185 B | A | view |
Copies
3 files in 3 other repositories hold the exact bytes of one of this file's versions, each committed after this file had them: 1 holds the newest version and 2 an older one.
- nebutra/nebutra-sailor · .agents/skills/write-swift/SKILL.md · 3 versions behind · 5 stars
- jaimejunr/claude-code-frontend-skills · plugins/emil-native/skills/write-swift/SKILL.md · 1 version behind · 5 stars
A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/write-swift/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (42776 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
emilkowalski/skill · 58,162 stars · license MIT · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wxrpn5wwhwyrkrvm GET https://markdownregistry.com/api/v1/resolve?ref=emilkowalski/skill/write-swift GET https://markdownregistry.com/api/v1/blob/ad8f3af70b627c165ecd73ecdba49449e35301dd845c397cf813f06582bbdac2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from emilkowalski/skill
Every file in emilkowalski/skill