SwiftUI API Update Maintainer
Scan Apple documentation and keep SwiftUI deprecated-API migrations current.
Permissions are reasonably scoped: read/write within the repo, PR creation via gh, doc fetching via Sosumi MCP; no credential handling or covert exfiltration. Deductions: PR creation lacks an explicit user-confirmation gate; fetchExternalDocumentation accepts arbitrary https URLs without domain restriction guidance; no rollback or anomalous-result handling defined.
Workflow steps are self-consistent, the manifest is well categorized, and there is a tool reference table plus honest failure guidance ('note when no replacement exists'). Deductions: nothing executed; hard dependency on external Sosumi MCP availability is only noted as a prerequisite, with no defined failure feedback or degraded behavior when MCP is unavailable.
Trigger phrases are explicit ('update latest APIs', after new iOS/Xcode releases), prerequisites and target-file boundaries are clear. Deductions: core function entirely depends on Sosumi MCP reaching Apple's overseas documentation, a reachability risk for mainland-China networks that is not disclosed; non-fit ranges unstated.
Good layering (SKILL.md + scan-manifest.md), repository has MIT LICENSE, semver release CI, CONTRIBUTING, and a README maintenance section clarifying this skill is an internal repo utility not published externally. Deductions: no per-skill version or changelog, manifest relies on manual updates, and referenced latest-apis.md format could not be fully verified in scope.
The task (scan deprecated APIs, update latest-apis.md in a fixed format, open a PR) is fully specified with output templates; marginal value lies in systematically replacing manual doc reading. Deductions: static review cannot confirm output correctness; hard-coded doc-path anchors (e.g. toolbar(content:)-5w0tj) may break as Apple's site changes.
Only source files are auditable: the manifest's Apple doc paths and WWDC sessions serve as checkable primary material. Deductions: no tests or CI cover this skill (existing tests target the trace scripts only), no third-party execution evidence, and evidence types are too thin for higher marks under static calibration.
- The skill hard-depends on the Sosumi MCP reaching Apple's overseas documentation; verify MCP reachability, especially from mainland-China networks.
- PR creation is not gated by explicit user confirmation; review the diff before allowing a commit/push.
- Hard-coded documentation path anchors in the manifest may break when Apple restructures its site; outputs need human review.
- This maintenance skill is covered by no tests or CI; this is a static, unverified source review.
What does this skill do, and when should you use it?
This is a standalone maintenance skill in the AvdLee/SwiftUI-Agent-Skill repository, focused on keeping the SwiftUI expert skill’s API reference current. It uses the Sosumi MCP to scan Apple developer documentation, identify deprecated APIs and replacements, and update latest-apis.md. It also defines the required version sections, entry format, and quick lookup table. It fits teams refreshing API guidance after new iOS or Xcode releases, provided they have Sosumi MCP and repository write access.
Reads swiftui-expert-skill/references/latest-apis.md and references/scan-manifest.md; calls Sosumi MCP tools searchAppleDocumentation and fetchAppleDocumentation, with optional fetchAppleVideoTranscript; compares findings with existing entries and classifies new deprecations, corrections, and version sections; updates latest-apis.md; creates an update/latest-apis-YYYY-MM branch, commits the changes, and opens a pull request with gh pr create.
- A team maintaining the SwiftUI expert skill scans API changes after a new iOS or Xcode release.
- A developer needs to find SwiftUI APIs that are deprecated but not yet recorded, along with official modern replacements.
- A maintainer wants consistent version sections and quick lookup entries for API migration reviews.
- A contributor with Sosumi MCP and repository write access wants to submit maintenance changes as a pull request.
What are this skill's strengths and limitations?
- Provides a defined workflow covering scanning, comparison, formatting, commits, and pull requests.
- Uses Apple developer documentation and requires recording the iOS version for modern replacements.
- Uses a scan manifest to organize checks by API area.
- Sosumi MCP is required for the core documentation scan.
- Repository write access and GitHub CLI are required to complete the branch, commit, and pull-request workflow.
- The source provides no test suite or compatibility evidence for other MCP implementations.
- It maintains latest-apis.md rather than serving as a standalone general SwiftUI programming guide.
How do you install this skill?
The source does not document standalone installation for this maintenance skill. The repository as a whole supports installation through skills.sh, Claude Code, Cursor, Codex/OpenAI-compatible tools, pi, or manual setup; the README states that the maintenance skill remains a repository workflow utility.
How do you use this skill?
Run it in an environment where Sosumi MCP is enabled and the repository is writable. Trigger phrases include “update latest APIs,” “refresh deprecated SwiftUI APIs,” “check for new SwiftUI deprecations,” and “scan for API changes,” especially after a new iOS or Xcode release. The skill scans, compares, updates the reference file, and prepares a pull request.