How do I install the Swiftui API Gap skill?

Run npx skillmds@latest add majiayu000/swiftui-api-gap in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Swiftui API Gap safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Swiftui API Gap?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Swiftui API Gap free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Swiftui API Gap?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Swiftui API Gap by majiayu000 — Agent Skill

Name: Swiftui API Gap
Rating: 4.2 (5 reviews)
Author: majiayu000

Swiftui API Gap

Generate and maintain deterministic SwiftUI-vs-Raven API parity reports and automation. Use when users ask to audit missing SwiftUI components/APIs, refresh coverage reports, reduce report noise, tune matching logic (owner-qualified names, constructors, operators), or update the weekly GitHub Actions PR workflow that publishes Reports/swiftui-api-gap/gap_report.md.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

SwiftUI API Gap

Overview

Use this skill to keep Raven's SwiftUI parity tracking deterministic, actionable, and automated.

Primary implementation files:

Scripts/swiftui_api_gap_report.py
.github/workflows/swiftui-api-gap-report.yml
Documentation/SwiftUI-API-Gap-Automation.md

Primary artifact:

Reports/swiftui-api-gap/gap_report.md

Workflow

Run report generation.

Scripts/swiftui_api_gap_report.py --repo-root . --output-dir Reports/swiftui-api-gap

Validate outputs exist.

ls -lh Reports/swiftui-api-gap

Check report quality quickly.

Confirm summary section has counts and coverage.
Confirm named APIs are separate from operator-like overloads.
Confirm constructor coverage is owner-qualified (Type.init) and not globally skipped.

If asked to improve actionability, prioritize:

Owner-qualified matching for members (Type.func, Type.var, Type.init).
Noise separation for operator-like signatures.
Stable high-signal lists for components/modifiers.
Clear markdown sections that humans can triage.

Automation

Weekly workflow:

.github/workflows/swiftui-api-gap-report.yml
Runs Monday via cron.
Uses macOS runner compatible with Swift/Xcode tooling.
Uploads artifact bundle.
Opens/updates PR with refreshed report.

When editing automation:

Keep Reports/swiftui-api-gap/gap_report.md in add-paths for PR commits.
Keep workflow permissions at least:
- contents: write
- pull-requests: write
Keep workflow_dispatch so maintainers can run immediately.

Matching Rules

Use these rules unless user asks to change methodology:

Source of truth: swift-api-digester against Apple SwiftUI module.
Build SwiftUI inventory from digester output.
Build Raven inventory from public declarations under Sources/Raven/**/*.swift.
Match by owner-qualified member names when possible.
Keep constructors scored by owner (Type.init) unless upgraded to full signature matching.
Keep operator overloads summarized separately from named actionable APIs.

Troubleshooting

If skill tooling scripts fail with missing yaml, use repo venv:

venv/bin/python -m pip install pyyaml

If report looks noisy, inspect:
- missing.operator_like in gap_report.json
- owner context fields in high-signal sections
If workflow cannot be triggered remotely, ensure workflow file is committed to default branch first.

---name: swiftui-api-gapdescription: Generate and maintain deterministic SwiftUI-vs-Raven API parity reports and automation. Use when users ask to audit missing SwiftUI components/APIs, refresh coverage reports, reduce report noise, tune matching logic (owner-qualified names, constructors, operators), or update the weekly GitHub Actions PR workflow that publishes Reports/swiftui-api-gap/gap_report.md.--- # SwiftUI API Gap ## Overview Use this skill to keep Raven's SwiftUI parity tracking deterministic, actionable, and automated. Primary implementation files: - `Scripts/swiftui_api_gap_report.py` - `.github/workflows/swiftui-api-gap-report.yml` - `Documentation/SwiftUI-API-Gap-Automation.md` Primary artifact: - `Reports/swiftui-api-gap/gap_report.md` ## Workflow 1. Run report generation. ```bash Scripts/swiftui_api_gap_report.py --repo-root . --output-dir Reports/swiftui-api-gap ``` 2. Validate outputs exist. ```bash ls -lh Reports/swiftui-api-gap ``` 3. Check report quality quickly. - Confirm summary section has counts and coverage. - Confirm named APIs are separate from operator-like overloads. - Confirm constructor coverage is owner-qualified (`Type.init`) and not globally skipped. 4. If asked to improve actionability, prioritize: - Owner-qualified matching for members (`Type.func`, `Type.var`, `Type.init`). - Noise separation for operator-like signatures. - Stable high-signal lists for components/modifiers. - Clear markdown sections that humans can triage. ## Automation Weekly workflow: - `.github/workflows/swiftui-api-gap-report.yml` - Runs Monday via cron. - Uses macOS runner compatible with Swift/Xcode tooling. - Uploads artifact bundle. - Opens/updates PR with refreshed report. When editing automation: 1. Keep `Reports/swiftui-api-gap/gap_report.md` in `add-paths` for PR commits. 2. Keep workflow `permissions` at least: - `contents: write` - `pull-requests: write` 3. Keep `workflow_dispatch` so maintainers can run immediately. ## Matching Rules Use these rules unless user asks to change methodology: - Source of truth: `swift-api-digester` against Apple `SwiftUI` module. - Build SwiftUI inventory from digester output. - Build Raven inventory from public declarations under `Sources/Raven/**/*.swift`. - Match by owner-qualified member names when possible. - Keep constructors scored by owner (`Type.init`) unless upgraded to full signature matching. - Keep operator overloads summarized separately from named actionable APIs. ## Troubleshooting - If skill tooling scripts fail with missing `yaml`, use repo venv: ```bash venv/bin/python -m pip install pyyaml ``` - If report looks noisy, inspect: - `missing.operator_like` in `gap_report.json` - owner context fields in high-signal sections - If workflow cannot be triggered remotely, ensure workflow file is committed to default branch first.

Frequently asked questions