SwiftUI API Update Maintainer
Scan Apple documentation and keep SwiftUI deprecated-API migrations current.
The skill clearly requires Apple documentation access and repository writes, and it transparently scopes edits to latest-apis.md. However, branch creation, commits, and gh PR creation are prescribed without explicit user confirmation, least-privilege controls, sensitive-data handling, rollback guidance, or external-effect safeguards, so points are deducted.
The workflow, scan manifest, tool parameters, and entry format make the happy path understandable. However, there is no diagnostic or recovery behavior for missing Sosumi access, invalid documentation paths, abnormal results, or write failures, and no committed tests cover the skill's key path; the static ceiling therefore applies.
Triggers, maintainer audience, and target file are clear. Fit is limited to environments with Sosumi MCP and repository write access; non-fit boundaries, acceptance criteria, Chinese-language support, and mainland-China network reachability are not established, so points are deducted.
The skill has clear structure, prerequisites, workflow, manifest, tool reference, and output-format guidance. Repository context supplies MIT licensing and maintenance signals, but the skill itself lacks versioning, changelog, named maintenance responsibility, update path, troubleshooting, and rollback guidance, so points are deducted.
The stated goal—scan deprecated APIs and update the reference—has a directly usable document format and lookup-table requirement. Static evidence does not establish scan completeness, replacement correctness, or usable PR results, and human review remains necessary, so only limited credit is awarded.
The skill identifies Apple documentation, WWDC transcripts, Sosumi tools, and an attribution line, providing some auditability. There are no execution records, covering tests, or independent corroboration demonstrating the key conclusions, so the score remains low.
- The workflow depends on Sosumi MCP; its availability, data boundaries, and reachability from mainland-China networks are not verified by the supplied material.
- Commits and pull requests are external side effects, but the skill does not require confirmation before performing them or document rollback steps.
- Maintainers must manually verify scan coverage, API replacements, and version judgments; the static evidence does not prove completeness or correctness.
What it does & when to 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.
Pros & cons
- 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 to install
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 to use
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.