What is explore-apple-swift-docs?

A guide for finding and using Apple and Swift documentation from sources such as Xcode documentation, Dash, source repositories, generated docs, and official web pages.

Use it to look up Apple or Swift APIs, guides, tutorials, symbols, and concepts, or to get help with local documentation and Dash docsets.

It gives documentation lookup a defined order and fallback path when one source is unavailable or incomplete.

explore-apple-swift-docs — Skill by gaelic-ghost/socket

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add gaelic-ghost/socket --skill explore-apple-swift-docs

Clone the repo

git clone --depth 1 https://github.com/gaelic-ghost/socket

Made for: Claude Code, Codex.

Or install apple-dev-skills, the plugin that ships this one along with the rest of its 65 skills, 2 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gaelic-ghost/socket/explore-apple-swift-docs/github.svg)](https://agentmods.dev/skills/gaelic-ghost/socket/explore-apple-swift-docs)

Your own site

<a href="https://agentmods.dev/skills/gaelic-ghost/socket/explore-apple-swift-docs"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/explore-apple-swift-docs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gaelic-ghost/socket/explore-apple-swift-docs"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/explore-apple-swift-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,919 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00078	$0.01919
Opus 5.5	$0.00031	$0.00768
Sonnet 5.5	$0.00016	$0.00384
Haiku 4.5	$0.00008	$0.00192

Measured 1mo ago against content hash bd41a2cc9d28, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

explore-apple-swift-docs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/apple-dev-skills/skills/explore-apple-swift-docs/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Explore Apple Swift Docs

Purpose

Explore Apple and Swift documentation through one top-level entry point. Prefer direct docs access methods in this order: Xcode MCP DocumentationSearch first, Dash.app MCP second, Dash localhost HTTP only when the Dash.app MCP is unavailable or incomplete, then checked-out source, generated DocC, GitHub/source repositories, or release notes, and finally readable online documentation. scripts/run-workflow.fsx remains a maintainer helper for structured dry runs, fallback planning, and Dash follow-up automation, but it is not the primary way the agent should perform ordinary Apple or Swift docs lookup.

When To Use

Use this skill for Apple or Swift API reference lookup requests.
Use this skill for Apple or Swift guide, tutorial, symbol, or concept search requests.
Use this skill when the user wants local docs first, wants official docs first, or wants to compare available Apple or Swift docs sources.
Use this skill when the user wants Dash-compatible Apple or Swift docs access, install guidance for a missing Dash docset, or generation guidance when a Dash docset is unavailable.
Recommend xcode-build-run-workflow when the user needs Apple or Swift execution, diagnostics, build, run, toolchain help, or mutation decisions inside an existing Xcode project.
Recommend xcode-testing-workflow when the user needs Swift Testing, XCTest, XCUITest, .xctestplan, or test diagnosis inside an existing Xcode project.
Recommend bootstrap-xcode-workspace when the user is starting a native Apple product or aligning an existing canonical workspace.

Single-Path Workflow

Classify the request into one docs workflow mode:
- explore
- dash-install
- dash-generate
If no mode is explicit, start at explore.
For explore, use the documented direct docs path instead of routing ordinary lookups through a wrapper script:
- xcode-mcp-docs: use Xcode MCP DocumentationSearch first when it is available and the user has not asked for another source
- dash: use the Dash.app MCP directly after Xcode MCP when its installed docsets cover the question
- dash-http: use the documented Dash localhost HTTP structure directly when Dash MCP is unavailable or incomplete
- source-repo: use GitHub/source repositories, generated DocC, release notes, or checked-out source when the request is about open source Swift projects, tools, or packages
- official-web: use official Apple or Swift web docs when the local-docs and source-repo paths are unavailable, the user explicitly prefers the web source, and the page content is actually readable through the available tool
Use scripts/run-workflow.fsx only when a structured non-interactive planning result is useful, or when the request is specifically about dash-install or dash-generate follow-up behavior.
If the selected mode cannot complete, hand off forward through one clear next step:
- explore -> dash-install
- dash-install -> dash-generate
Return one status, one path_type, one source_used, and one output contract for the mode that ran.

Read the full file on GitHub · 128 lines

Files

What ships with it

18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 128 lines · 78 tokens per session scan A bd41a2cc9d28

Subscribe to this mod's changes

explore-apple-swift-docs is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,919 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Kotlin and Swift Languages Research agent-skill claude-code-plugin claude-plugin claude-skills codex codex-plugin

kotlin-dev

Use when implementing any feature or bugfix in a Kotlin/Spring Boot service, covers layer conventions, idioms, testing, and observability.

pranav8494/team-of-agents · 32 tokens

kotlin-reviewer

Use when reviewing a Kotlin/Spring Boot pull request, systematic checklist covering architecture, idioms, testing, security, and observability.

pranav8494/team-of-agents · 31 tokens

swiftui-macos

Expert SwiftUI guidance for macOS apps — covers writing and reviewing code with runtime-level understanding of observation, concurrency, performance, and platform integration. Use when user asks to "build a SwiftUI view", "review my SwiftUI code", "fix observation issues", "bridge AppKit", "architect state…

kageroumado/swiftui-macos-skill · 150 tokens

craft

Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…

kardebadas/claude-plugin · 83 tokens

pipeline

Use when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.

kardebadas/claude-plugin · 24 tokens

turbo-pipeline

Use when the user wants a feature built end to end after answering one round of questions and then being left alone — "turbo", "ask me once, then just build it", "I'll answer up front, don't come back to me", "decide the rest yourself". Not for a run that wants a spec approval and no tests (superb:fast-pipeline), one…

kardebadas/claude-plugin · 114 tokens