Swiftui Expert Skill
omarshahine/HomeClaw
A skill your agent uses when writing, reviewing, or refactoring SwiftUI code for iOS or macOS, including state management, view composition, performance, Liquid Glass adoption, or Instruments .trace…
A skill your agent uses when a change touches the WiFi Lens product itself (Swift app source, unit tests) before claiming that work is complete, before committing such a change, or when asked to…
Install Verify Build
$ npx skills add ShiinaLabs/wifi-lens --skill verify-build -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ShiinaLabs/wifi-lens verify-build --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ShiinaLabs/wifi-lens.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/verify-build .claude/skills/verify-build && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "verify-build" agent skill from https://github.com/ShiinaLabs/wifi-lens/tree/master/.agents/skills/verify-build into .claude/skills/verify-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-build", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ShiinaLabs/wifi-lens/tree/master/.agents/skills/verify-buildType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ShiinaLabs/wifi-lens --skill verify-build -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ShiinaLabs/wifi-lens verify-build --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ShiinaLabs/wifi-lens.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/verify-build .agents/skills/verify-build && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verify-build" agent skill from https://github.com/ShiinaLabs/wifi-lens/tree/master/.agents/skills/verify-build into .agents/skills/verify-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-build", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ShiinaLabs/wifi-lens --skill verify-build -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ShiinaLabs/wifi-lens verify-build --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ShiinaLabs/wifi-lens.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/verify-build .cursor/skills/verify-build && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verify-build" agent skill from https://github.com/ShiinaLabs/wifi-lens/tree/master/.agents/skills/verify-build into .cursor/skills/verify-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-build", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ShiinaLabs/wifi-lens.git --path .agents/skills/verify-build--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ShiinaLabs/wifi-lens --skill verify-build -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ShiinaLabs/wifi-lens verify-build --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ShiinaLabs/wifi-lens.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/verify-build .gemini/skills/verify-build && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verify-build" agent skill from https://github.com/ShiinaLabs/wifi-lens/tree/master/.agents/skills/verify-build into .gemini/skills/verify-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-build", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ShiinaLabs/wifi-lens verify-buildInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ShiinaLabs/wifi-lens --skill verify-build -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ShiinaLabs/wifi-lens.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/verify-build .github/skills/verify-build && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verify-build" agent skill from https://github.com/ShiinaLabs/wifi-lens/tree/master/.agents/skills/verify-build into .github/skills/verify-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-build", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ShiinaLabs/wifi-lens --skill verify-build -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ShiinaLabs/wifi-lens verify-build --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ShiinaLabs/wifi-lens.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/verify-build .opencode/skills/verify-build && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verify-build" agent skill from https://github.com/ShiinaLabs/wifi-lens/tree/master/.agents/skills/verify-build into .opencode/skills/verify-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-build", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
verify-build- GitHub stars
- 118
- Token cost
- ~963 tokens
- SKILL.md length
- 358 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when a change touches the WiFi Lens product itself (Swift app source, unit tests) before claiming that work is complete, before committing such a change, or when asked to…
- A change touches the WiFi Lens product itself (Swift app source
- SKILL.md covers Core Principle, What changed → what to run, Quick path (recommended) and Exact commands (when running…, plus 2 more sections
- Runs Shell scripts from its folder; calls swift and xcodebuild
- Unit tests) before claiming that work is complete
What it does
Verify Build is an agent skill from ShiinaLabs/wifi-lens. Use when a change touches the WiFi Lens product itself (Swift app source, unit tests) before claiming that work is complete, before committing such a change, or when asked to build, run tests, verify, or check compilation. Non-product changes (docs, agent assets, other repositories) do not trigger build verification.
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/verify.sh`).
It sits in Mobile, covering iOS development and Unit testing. It works with macOS and SwiftUI. The repository describes itself as: Native open-source network diagnostics app for macOS with built-in Wi-Fi analysis. The licence is Apache-2.0.
When your agent uses it
- A change touches the WiFi Lens product itself (Swift app source
- Unit tests) before claiming that work is complete
- Before committing such a change
- Check compilation
Example prompts
- “/verify-build”
Requirements
- A Bash shell
What it can do on your machine
Read from SKILL.md and the folder at commit 4783d30. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
swiftxcodebuild
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Verify Build loads about 963 tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 358 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from ShiinaLabs/wifi-lens at commit 4783d30, republished under its Apache-2.0 licence (© ShiinaLabs). 358 words, ~963 tokens.
Download SKILL.mdSave it as
.claude/skills/verify-build/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- verify-build
- description
- Use when a change touches the WiFi Lens product itself (Swift app source, unit tests) before claiming that work is complete, before committing such a change, or when asked to build, run tests, verify, or check compilation. Non-product changes (docs, agent assets, other repositories) do not trigger build verification.
Verify Build
Core Principle
The app is verified with xcodebuild, never swift build / swift test.
swift build in the repo root or app tree will not reflect the real target
configuration and gives misleading results. ChartLens is a remote Swift package
dependency, not a root-level checkout. Repository-owned modules are native
Framework targets; their tests are native unit-test bundles.
Silence is not success. A green exit code on the wrong scheme or the wrong test subset does not mean the change is verified. Match the command to what changed (table below).
What changed → what to run
| Change | Verify with |
|---|---|
Shared source under WiFiLensCore/ | Run Core Framework tests and build both app schemes |
| OSS or Pro app-shell source | Build the matching app scheme and relevant app-hosted tests |
| New/edited unit test file | Build and run the owning unit-test bundle with an explicit -only-testing selection |
| ChartLens integration | Verify through the owning WiFiLensCore Framework target or app scheme; ChartLens is a remote package dependency. |
.xcstrings only | Localization JSON validity + completeness scan (see i18n-completer) |
Docs / .agents/ / other non-product changes | No build checks required |
Default verification for an app source change = build + -only-testing:WiFiLensTests -only-testing:WiFiLensCoreTests.
Quick path (recommended)
# From repo root. Builds "WiFi Lens" + "WiFi Lens Pro" (Debug) and runs the
# WiFiLensTests and WiFiLensCoreTests unit bundles. This is the default "is my change good?" check.
.agents/skills/verify-build/scripts/verify.sh
# Only touched OSS-side or want a faster loop — build+test just "WiFi Lens":
.agents/skills/verify-build/scripts/verify.sh --quickExact commands (when running by hand)
Build (OSS):
xcodebuild -project WiFiLens.xcodeproj -scheme "WiFi Lens" \
-configuration Debug -destination 'platform=macOS' buildBuild (Pro) — always run this too when the change touches shared source, to verify the private app shell still integrates with the shared Framework:
xcodebuild -project WiFiLens.xcodeproj -scheme "WiFi Lens Pro" \
-configuration Debug -destination 'platform=macOS' buildUnit tests (the only tests run by default):
xcodebuild -project WiFiLens.xcodeproj -scheme "WiFi Lens" \
-configuration Debug -destination 'platform=macOS' \
-skipPackageUpdates test -only-testing:WiFiLensTests -only-testing:WiFiLensCoreTestsShow full SKILL.md (128 more words)Show less
Hard rules
- Never run
swift build/swift testto verify the app.xcodebuildonly. - Do not run UI test bundles (
WiFiLensUITests,WiFiLensProUITests) or a full schemetest(which pulls in UI tests) unless the user explicitly asks for UI tests. Default =-only-testing:WiFiLensTests -only-testing:WiFiLensCoreTests. - When shared product code changes, a passing OSS build alone is not enough — the Pro scheme must build too. Shared implementation is owned by WiFiLensCore, not duplicated in both app Sources phases.
- Use
-skipPackageUpdatesontestruns to avoid needless package resolution. -destination 'platform=macOS'— this is a macOS 14.6+ app, no simulator.
Reporting
State what was actually run and its result. "Build passed" is insufficient — say which schemes built and whether unit tests ran, e.g.:
OSS + Pro Debug builds succeeded; WiFiLensTests + WiFiLensCoreTests passed (N tests).
© ShiinaLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in .agents/skills/verify-build of ShiinaLabs/wifi-lens.
- SKILL.md
- scripts/verify.sh
Open the folder on GitHubat commit 4783d30
Compare with similar skills
Verify Build next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Verify Build this skillShiinaLabs/wifi-lens | 118 | — | ~963 | Automated safety check: Pass | Apache-2.0 | |
| Swiftui Expert Skillomarshahine/HomeClaw | 176 | 4 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Appkit Swiftui BridgeKartikLabhshetwar/better-shot | 2.4k | 2 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| macOS Notch UIfayazara/Screendrop | 2.1k | — | ~1.8k | Automated safety check: Pass | CC0-1.0 | |
| Swiftui Patternsrobinebers/openusage | 4.3k | — | ~3.4k | Automated safety check: Pass | MIT | |
| Hig Project Contextraintree-technology/hig-doctor | 143 | 5 repos | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Appkit Swiftui Bridge
KartikLabhshetwar/better-shot
Expert guidance for hybrid AppKit-SwiftUI development. An agent skill from KartikLabhshetwar/better-shot.
macOS Notch UI
fayazara/Screendrop
Add a Dynamic Island-style notch UI to a macOS app. An agent skill from fayazara/Screendrop.
Swiftui Patterns
robinebers/openusage
Best practices and example-driven guidance for building native macOS SwiftUI scenes and components, including windows, commands, toolbars, settings, split views, inspectors, menu bar extras, and…
Hig Project Context
raintree-technology/hig-doctor
Create or update a shared Apple design context document that other HIG skills use to tailor guidance.
Swiftui Expert Skill
Eslzzyl/Pixiv-SwiftUI
A skill your agent uses when writing, reviewing, or refactoring SwiftUI code for iOS or macOS, including state and @Observable data flow, view composition, resizable layouts, safe areas, display…
More from ShiinaLabs/wifi-lens
I18n Completer
ShiinaLabs/wifi-lens
A skill your agent uses when checking, completing, fixing, or adding translations in .xcstrings files, especially when localizations are missing or glossary terminology must be enforced.
Protect Knowledge Boundary
ShiinaLabs/wifi-lens
Invoke only when the user explicitly requests a WiFi Lens knowledge-boundary audit or the active task names that audit as a required deliverable.
Related
Categories
Questions about Verify Build
What does Verify Build do?
A skill your agent uses when a change touches the WiFi Lens product itself (Swift app source, unit tests) before claiming that work is complete, before committing such a change, or when asked to…. Verify Build is an agent skill from ShiinaLabs/wifi-lens. Use when a change touches the WiFi Lens product itself (Swift app source, unit tests) before claiming that work is complete, before committing such a change, or when asked to build, run tests, verify, or check compilation.
When should I use Verify Build?
Verify Build fits situations like: A change touches the WiFi Lens product itself (Swift app source; unit tests) before claiming that work is complete; before committing such a change; check compilation.
How do I install Verify Build in Claude Code?
Run `npx skills add ShiinaLabs/wifi-lens --skill verify-build -a claude-code`. Or copy the skill folder (.agents/skills/verify-build in ShiinaLabs/wifi-lens) into .claude/skills/verify-build in your project. Claude Code loads it when a task matches its description.
How do I install Verify Build in Codex?
Run `npx skills add ShiinaLabs/wifi-lens --skill verify-build -a codex`. Or copy the skill folder (.agents/skills/verify-build in ShiinaLabs/wifi-lens) into .agents/skills/verify-build in your project. Codex loads it when a task matches its description.
Can I use Verify Build in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ShiinaLabs/wifi-lens --skill verify-build -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-build, .gemini/skills/verify-build, .github/skills/verify-build and .opencode/skills/verify-build in your project.
What does Verify Build need to run?
Going by SKILL.md and its folder, Verify Build needs a shell for the scripts in its folder and the command-line tools its instructions call (swift and xcodebuild). Our summary lists: A Bash shell.
Does Verify Build access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Verify Build safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Verify Build use?
Verify Build is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Verify Build use?
About 963 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Verify Build?
Skills that share tags, products or a category with Verify Build: Swiftui Expert Skill (omarshahine/HomeClaw, 176 stars), Appkit Swiftui Bridge (KartikLabhshetwar/better-shot, 2.4k stars), macOS Notch UI (fayazara/Screendrop, 2.1k stars) and Swiftui Patterns (robinebers/openusage, 4.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verify Build?
ShiinaLabs (a GitHub organization) maintains it in ShiinaLabs/wifi-lens, which has 118 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.
Source: ShiinaLabs/wifi-lens on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.