Agent skill

Inspector Integration

A skill your agent uses when an agent needs to integrate the Inspector library into an app without focusing on the MCP bridge: startup wiring, configuration/customization, debug-only gating, and…

MITAuto-check passedMobile

Install Inspector Integration

skills CLI

$ npx skills add ipedro/Inspector --skill inspector-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install ipedro/Inspector inspector-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/ipedro/Inspector.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Plugins/inspector-mcp/skills/inspector-integration .claude/skills/inspector-integration && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "inspector-integration" agent skill from https://github.com/ipedro/Inspector/tree/develop/Plugins/inspector-mcp/skills/inspector-integration into .claude/skills/inspector-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspector-integration", 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

$skill-installer install https://github.com/ipedro/Inspector/tree/develop/Plugins/inspector-mcp/skills/inspector-integration

Type 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.

skills CLI

$ npx skills add ipedro/Inspector --skill inspector-integration -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install ipedro/Inspector inspector-integration --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ipedro/Inspector.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Plugins/inspector-mcp/skills/inspector-integration .agents/skills/inspector-integration && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "inspector-integration" agent skill from https://github.com/ipedro/Inspector/tree/develop/Plugins/inspector-mcp/skills/inspector-integration into .agents/skills/inspector-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspector-integration", 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.

skills CLI

$ npx skills add ipedro/Inspector --skill inspector-integration -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install ipedro/Inspector inspector-integration --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ipedro/Inspector.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Plugins/inspector-mcp/skills/inspector-integration .cursor/skills/inspector-integration && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "inspector-integration" agent skill from https://github.com/ipedro/Inspector/tree/develop/Plugins/inspector-mcp/skills/inspector-integration into .cursor/skills/inspector-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspector-integration", 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

$ gemini skills install https://github.com/ipedro/Inspector.git --path Plugins/inspector-mcp/skills/inspector-integration

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add ipedro/Inspector --skill inspector-integration -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install ipedro/Inspector inspector-integration --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ipedro/Inspector.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Plugins/inspector-mcp/skills/inspector-integration .gemini/skills/inspector-integration && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "inspector-integration" agent skill from https://github.com/ipedro/Inspector/tree/develop/Plugins/inspector-mcp/skills/inspector-integration into .gemini/skills/inspector-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspector-integration", 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.

GitHub CLI

$ gh skill install ipedro/Inspector inspector-integration

Installs 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).

skills CLI

$ npx skills add ipedro/Inspector --skill inspector-integration -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/ipedro/Inspector.git skills-src && mkdir -p .github/skills && cp -r skills-src/Plugins/inspector-mcp/skills/inspector-integration .github/skills/inspector-integration && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "inspector-integration" agent skill from https://github.com/ipedro/Inspector/tree/develop/Plugins/inspector-mcp/skills/inspector-integration into .github/skills/inspector-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspector-integration", 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.

skills CLI

$ npx skills add ipedro/Inspector --skill inspector-integration -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install ipedro/Inspector inspector-integration --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ipedro/Inspector.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Plugins/inspector-mcp/skills/inspector-integration .opencode/skills/inspector-integration && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "inspector-integration" agent skill from https://github.com/ipedro/Inspector/tree/develop/Plugins/inspector-mcp/skills/inspector-integration into .opencode/skills/inspector-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspector-integration", 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: inspector-integration
GitHub stars: 170
Token cost: ~724 tokens
SKILL.md length: 272 words
Files: 2 (incl. references)
Skills in repo: 4
Repo updated: Apr 19, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when an agent needs to integrate the Inspector library into an app without focusing on the MCP bridge: startup wiring, configuration/customization, debug-only gating, and…

An agent needs to integrate the Inspector library into an app without focusing on the MCP bridge: startup wiring
SKILL.md covers Overview, Core startup pattern, Typical integration tasks and Common entry points, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Configuration/customization

What it does

Inspector Integration is an agent skill from ipedro/Inspector. Use when an agent needs to integrate the Inspector library into an app without focusing on the MCP bridge: startup wiring, configuration/customization, debug-only gating, and custom panel registration. Especially useful when patching another iOS app to call Inspector.start() correctly and optionally register custom Inspector libraries.

Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/integration-patterns.md`).

It sits in Mobile, covering iOS development. It works with iOS, Model Context Protocol and SwiftUI. The repository describes itself as: Inspector is a debugging library written in Swift. The licence is MIT.

When your agent uses it

An agent needs to integrate the Inspector library into an app without focusing on the MCP bridge: startup wiring
Configuration/customization
Debug-only gating
Custom panel registration

Example prompts

“/inspector-integration”

What it can do on your machine

Read from SKILL.md and the folder at commit bb220e4. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are swift).
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

Inspector Integration loads about 724 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 272 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~90
When it runs · the whole SKILL.md, loaded when a task matches: ~724
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~1.1k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from ipedro/Inspector at commit bb220e4, republished under its MIT licence (© ipedro). 272 words, ~724 tokens.

Download SKILL.mdSave it as .claude/skills/inspector-integration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: inspector-integration
description: Use when an agent needs to integrate the Inspector library into an app without focusing on the MCP bridge: startup wiring, configuration/customization, debug-only gating, and custom panel registration. Especially useful when patching another iOS app to call `Inspector.start()` correctly and optionally register custom Inspector libraries.

Inspector Integration

Overview

Use this skill when integrating Inspector the library into a consumer app. This is broader than MCP bridge setup and applies even when the app only needs:

Inspector.start() / Inspector.stop()
configuration via InspectorConfiguration
customization via InspectorCustomizationProviding
debug-only custom panels/libraries/macros
InspectorInterface macro adoption (@InspectorPanel, @InspectorProperty)

Core startup pattern

The safe baseline is:

swift

Inspector.setConfiguration(...)
Inspector.setCustomization(...)
Inspector.start()

Do configuration/customization before Inspector.start().

Typical integration tasks

add Inspector startup to UIKit or SwiftUI app entry points
keep startup debug-only
register custom libraries/panels through InspectorCustomizationProviding
integrate InspectorInterface macros cleanly in a consumer app
verify Example-like integration patterns in another app
preserve existing app startup behavior while inserting Inspector cleanly

Common entry points

UIKit lifecycle: SceneDelegate.scene(_:willConnectTo:)
older UIKit lifecycle: AppDelegate
SwiftUI lifecycle: @main App / app delegate adaptor or debug bootstrap path

Debug-only guidance

Prefer keeping Inspector setup in debug-only code paths so release builds stay clean. If the consumer app uses macro-based custom panels, ensure the same debug trait/build gating applies consistently.

Macro integration guidance

When the consumer app uses @InspectorPanel / @InspectorProperty:

import InspectorInterface for the macro declarations
import Inspector when the file also uses Inspector runtime APIs directly (Inspector.start(), customization types, etc.)
do not hide @InspectorProperty from the macro expander with local #if guards around the annotation itself unless you are certain the macro still sees the declaration
prefer gating the surrounding integration/bootstrap path rather than making the annotation invisible

The generated code references Inspector runtime symbols, so the consumer target must have the proper Inspector package products linked in its debug configuration.

Verification

app launches with Inspector enabled
no duplicate Inspector.start() calls
configuration/customization are applied before startup
custom panels/libraries appear when expected

References

Read only when needed:

references/integration-patterns.md

Files

SKILL.md and 1 other file (references) in Plugins/inspector-mcp/skills/inspector-integration of ipedro/Inspector.

SKILL.md
references/integration-patterns.md

Open the folder on GitHubat commit bb220e4

Compare with similar skills

Inspector Integration 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.

Inspector Integration compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Inspector Integration this skillipedro/Inspector	170	—	~724	Automated safety check: Pass	MIT	5 mo ago
Update Swiftui APIsAvdLee/SwiftUI-Agent-Skill	3.7k	—	~1.2k	Automated safety check: Pass	MIT	yesterday
Pp Apple Docsmvanhorn/printing-press-library	2.1k	—	~3.7k	Automated safety check: Notes	Apache-2.0	yesterday
Swiftui Expert SkillAvdLee/SwiftUI-Agent-Skill	3.7k	—	~2.9k	Automated safety check: Pass	MIT	yesterday
Swiftui Expert SkillEslzzyl/Pixiv-SwiftUI	111	5 repos	~3.1k	Automated safety check: Pass	AGPL-3.0	today
Swiftui Liquid Glassharperreed/dotfiles	334	8 repos	~941	Automated safety check: Pass	None	4 days ago

Similar skills

Update Swiftui APIs
AvdLee/SwiftUI-Agent-Skill
Scan Apple's SwiftUI documentation for deprecated APIs and update the SwiftUI Expert Skill with modern replacements.
3.7k GitHub stars~1.2k tokensUpdated yesterday
MobileAuto-check passed
Pp Apple Docs
mvanhorn/printing-press-library
Every Apple framework, indexed locally, with deprecation analysis and an MCP server no other Apple-docs tool has.
2.1k GitHub stars~3.7k tokensUpdated yesterday
MobileAuto-check: notes
Swiftui Expert Skill
AvdLee/SwiftUI-Agent-Skill
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…
3.7k GitHub stars~2.9k tokensUpdated yesterday
MobileAuto-check passed
Swiftui Expert Skill
Eslzzyl/Pixiv-SwiftUI
A skill your agent uses when writing, reviewing, or refactoring SwiftUI code for iOS or macOS, including state management and @Observable data flow, view composition and invalidation/performance…
111 GitHub starsUsed in 5 repos~3.1k tokens
MobileAuto-check passed
Swiftui Liquid Glass
harperreed/dotfiles
Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API.
334 GitHub starsUsed in 8 repos~941 tokens
MobileAuto-check passed
Hig Project Context
raintree-technology/hig-doctor
Create or update a shared Apple design context document that other HIG skills use to tailor guidance.
142 GitHub starsUsed in 5 repos~1.2k tokens
MobileAuto-check passed

Questions about Inspector Integration

What does Inspector Integration do?

A skill your agent uses when an agent needs to integrate the Inspector library into an app without focusing on the MCP bridge: startup wiring, configuration/customization, debug-only gating, and…. Inspector Integration is an agent skill from ipedro/Inspector. Use when an agent needs to integrate the Inspector library into an app without focusing on the MCP bridge: startup wiring, configuration/customization, debug-only gating, and custom panel registration.

When should I use Inspector Integration?

Inspector Integration fits situations like: an agent needs to integrate the Inspector library into an app without focusing on the MCP bridge: startup wiring; configuration/customization; debug-only gating; custom panel registration.

How do I install Inspector Integration in Claude Code?

Run `npx skills add ipedro/Inspector --skill inspector-integration -a claude-code`. Or copy the skill folder (Plugins/inspector-mcp/skills/inspector-integration in ipedro/Inspector) into .claude/skills/inspector-integration in your project. Claude Code loads it when a task matches its description.

How do I install Inspector Integration in Codex?

Run `npx skills add ipedro/Inspector --skill inspector-integration -a codex`. Or copy the skill folder (Plugins/inspector-mcp/skills/inspector-integration in ipedro/Inspector) into .agents/skills/inspector-integration in your project. Codex loads it when a task matches its description.

Can I use Inspector Integration 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 ipedro/Inspector --skill inspector-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inspector-integration, .gemini/skills/inspector-integration, .github/skills/inspector-integration and .opencode/skills/inspector-integration in your project.

What does Inspector Integration need to run?

SKILL.md names no scripts, command-line tools or credentials: Inspector Integration is instructions for the agent only.

Does Inspector Integration 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 Inspector Integration 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. Review the folder before installing.

What licence does Inspector Integration use?

Inspector Integration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Inspector Integration use?

About 724 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 365 tokens, read only when the agent opens those files.

What are the alternatives to Inspector Integration?

Skills that share tags, products or a category with Inspector Integration: Update Swiftui APIs (AvdLee/SwiftUI-Agent-Skill, 3.7k stars), Pp Apple Docs (mvanhorn/printing-press-library, 2.1k stars), Swiftui Expert Skill (AvdLee/SwiftUI-Agent-Skill, 3.7k stars) and Swiftui Expert Skill (Eslzzyl/Pixiv-SwiftUI, 111 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Inspector Integration?

ipedro (a GitHub user) maintains it in ipedro/Inspector, which has 170 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on April 19, 2026.

Source: ipedro/Inspector on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Inspector Integration

Install Inspector Integration

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Inspector Integration

Overview

Core startup pattern

Typical integration tasks

Common entry points

Debug-only guidance

Macro integration guidance

Verification

References

Files

Compare with similar skills

Similar skills

Update Swiftui APIs

Pp Apple Docs

Swiftui Expert Skill

Swiftui Expert Skill

Swiftui Liquid Glass

Hig Project Context

More from ipedro/Inspector

Inspector MCP

Inspector Implementation

Inspector MCP Consumer

Questions about Inspector Integration

Install Inspector Integration

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Inspector Integration

Overview

Core startup pattern

Typical integration tasks

Common entry points

Debug-only guidance

Macro integration guidance

Verification

References

Files

Compare with similar skills

Similar skills

More from ipedro/Inspector

Related

Questions about Inspector Integration