Agent skill · Data & Analytics

ios-networking

Build, review, or improve networking code in iOS/macOS apps using URLSession with async/await, structured concurrency, and modern Swift patterns. Use when working with REST APIs, downloading files, uploading data, WebSocket connections, pagination, retry logic, request middleware, caching, background transfers, or network reachability monitoring. Also use when handling HTTP requests, API clients, network error handling, or data fetching in Swift apps.

Derek Pearson935★ · +23/wk · 1 repos on radarProfile →
claude-codecodexcursorNOASSERTION
Install
npx skills add dpearson2699/swift-ios-skills --skill ios-networking --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 7
SKILL.md size: 16 KB
Bundled scripts: none
Path: skills/ios-networking/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 963 · +28 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# iOS Networking Use URLSession with async/await and structured concurrency for ordinary HTTP, REST, uploads, downloads, and streaming. Use Network.framework for lower-level protocols and delegate/task APIs for durable background transfers. ## Contents - [Core URLSession async/await](#core-urlsession-asyncawait) - [API Client Architecture](#api-client-architecture) - [Error Handling](#error-handling) - [Pagination](#pagination) - [Network Reachability](#network-reachability) - [Configuring URLSession](#configuring-urlsession) - [App Transport Security (ATS)](#app-transport-security-ats) - [Common Mistakes](#common-mistakes) - [Review Checklist](#review-checklist) - [References](#references) ## Core URLSession async/await URLSession gained native async/await overloads in iOS 15. Prefer these for foreground data, upload, download, and streaming work. Background URLSession transfers are the main exception: they still use task/delegate APIs so the system can deliver events after suspension or relaunch. Validate networking policy locally with `URLProtocol` fixtures for valid 2xx, malformed 2xx, one-time 401 refresh, bounded 429/5xx retry, timeout/offline, cancellation, and nonretryable

What's inside
Steps it walks through
  1. Contents
  2. Core URLSession async/await
  3. Data Requests
  4. Response Validation
  5. JSON Decoding with Codable
  6. Downloads and Uploads
  7. Streaming with AsyncBytes
  8. API Client Architecture
  9. Protocol-Based Client
  10. Lightweight Closure-Based Client
  11. Request Middleware / Interceptors
  12. Token Refresh Flow
  13. Error Handling
  14. Structured Error Types
Ships with 6 files
  • evals/evals.json
  • references/background-websocket.md
  • references/file-storage-patterns.md
  • references/lightweight-clients.md
  • references/network-framework.md
  • references/urlsession-patterns.md
More from swift-ios-skills
All skills →
About this skill
What does the ios-networking skill do?

Build, review, or improve networking code in iOS/macOS apps using URLSession with async/await, structured concurrency, and modern Swift patterns. Use when working with REST APIs, downloading files, uploading data, WebSocket connections, pagination, retry logic, request middleware, caching, background transfers, or network reachability monitoring. Also use when handling HTTP requests, API clients, network error handling, or data fetching in Swift apps.

How do I install it?

Run `npx skills add dpearson2699/swift-ios-skills --skill ios-networking --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From dpearson2699/swift-ios-skills, a repository with 963 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going