New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Inspector Implementation

by ipedro in ipedro/Inspector

A skill your agent uses when an agent needs to implement or modify the Inspector library itself — panel UI, hierarchy/runtime behavior, custom property models, macros, or Example-app dogfooding.

MITAuto-check passedMobile

Install Inspector Implementation

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

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

GitHub CLI
$ gh skill install ipedro/Inspector inspector-implementation --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-implementation .claude/skills/inspector-implementation && 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/

Facts

Skill name
inspector-implementation
GitHub stars
170
Token cost
~729 tokens
SKILL.md length
172 words
Files
2 (incl. references)
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when an agent needs to implement or modify the Inspector library itself — panel UI, hierarchy/runtime behavior, custom property models, macros, or Example-app dogfooding.

  • An agent needs to implement
  • SKILL.md covers Overview, Fast architecture map, When touching specific features and Verification, plus 1 more section
  • Calls swift and xcodebuild
  • Modify the Inspector library itself — panel UI

What it does

Inspector Implementation is an agent skill from ipedro/Inspector. Use when an agent needs to implement or modify the Inspector library itself — panel UI, hierarchy/runtime behavior, custom property models, macros, or Example-app dogfooding. Especially useful when changing Sources/Inspector/, Sources/InspectorInterface/, or Sources/InspectorMacros/ and you need the repo's architecture and verification workflow in one place.

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

It sits in Mobile, covering iOS development. It works with iOS. 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 implement
  • Modify the Inspector library itself — panel UI
  • Hierarchy/runtime behavior
  • Custom property models

Example prompts

  • “/inspector-implementation”

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

    Shell commands in SKILL.md call:

    • swift
    • xcodebuild

    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 Implementation loads about 729 tokens when it runs, and up to ~1k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 172 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~98
When it runs · the whole SKILL.md, loaded when a task matches
~729
With references · SKILL.md plus every file in references/, read only if the agent opens them
~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). 172 words, ~729 tokens.

Download SKILL.mdSave it as .claude/skills/inspector-implementation/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
inspector-implementation
description
Use when an agent needs to implement or modify the Inspector library itself — panel UI, hierarchy/runtime behavior, custom property models, macros, or Example-app dogfooding. Especially useful when changing `Sources/Inspector/`, `Sources/InspectorInterface/`, or `Sources/InspectorMacros/` and you need the repo's architecture and verification workflow in one place.

Inspector Implementation

Overview

Use this skill when the work is inside the Inspector repo, not in a consumer app. Typical tasks:

  • changing runtime behavior in Sources/Inspector/
  • adding or adjusting Inspector UI panels
  • extending custom property/action flows
  • changing macro-generated Inspector integration (@InspectorPanel, @InspectorProperty)
  • dogfooding changes through the Example app

Fast architecture map

Start from these zones:

  • Sources/Inspector/Manager/ — top-level orchestration and presentation flow
  • Sources/Inspector/ViewHierarchy/ — live hierarchy capture and element references
  • Sources/Inspector/ElementInspector/ — element panel UI and interactions
  • Sources/Inspector/ElementLibraries/ — per-type property/section definitions
  • Sources/Inspector/Bridge/ — Inspector MCP bridge/runtime semantic layer
  • Sources/InspectorInterface/ — public macro declarations / debug-facing interface surface
  • Sources/InspectorMacros/ — macro expansion logic
  • Example/Example/ — dogfooding app and runtime verification target

When touching specific features

Runtime / bridge / semantic tooling

Look first in:

  • Sources/Inspector/Bridge/
  • Tests/InspectorTests/InspectorBridgeServiceTests.swift
  • Tests/InspectorTests/InspectorMCPTransportTests.swift
  • Tests/InspectorMCPServerTests/
  • Tests/InspectorMCPWireTests/
Panel UI / element inspector behavior

Look first in:

  • Sources/Inspector/ElementInspector/
  • Sources/Inspector/CommonUI/
  • Sources/Inspector/TransitionCoordinator/
Built-in editable properties / sections

Look first in:

  • Sources/Inspector/ElementLibraries/Sections/
  • Sources/Inspector/Extensions/InspectorElementViewModelProperty/
Customer-extensibility / macros

Look first in:

  • Sources/InspectorInterface/
  • Sources/InspectorMacros/
  • Example/Example/PlaygroundViewController.swift
  • Example/Example/RoundedButton.swift

Verification

SwiftPM/server-side verification
bash
swift build --product InspectorMCPServer
swift build --target InspectorMCPWireTests
swift build --target InspectorMCPServerTests
Example app / iOS verification
bash
xcodebuild test \
  -project Example/Example.xcodeproj \
  -scheme Example \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro,OS=26.4.1'

Prefer focused -only-testing: runs while iterating, then broaden when the slice stabilizes.

References

Read only when needed:

  • references/architecture.md

© ipedro, MIT. 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 (references) in Plugins/inspector-mcp/skills/inspector-implementation of ipedro/Inspector.

  • SKILL.md
  • references/architecture.md

Open the folder on GitHubat commit bb220e4

Compare with similar skills

Inspector Implementation 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 Implementation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Inspector Implementation this skillipedro/Inspector170—~729Automated safety check: PassMIT
Hig Project Contextraintree-technology/hig-doctor1425 repos~1.2kAutomated safety check: PassMIT
Hig Components Contentraintree-technology/hig-doctor1425 repos~1.3kAutomated safety check: PassMIT
iOS Simulator Skilln0an/VivaDicta1261 repos~2.5kAutomated safety check: PassMIT
Device InteractionInfomaniak/desktop-kDrive1201 repos~1.9kAutomated safety check: PassGPL-3.0
Run iOS SimulatoriPlug2/iPlug2OOS158—~711Automated safety check: PassNone

Similar skills

  • 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

  • Hig Components Content

    raintree-technology/hig-doctor

    Apple Human Interface Guidelines for content display components.

    142 GitHub starsUsed in 5 repos~1.3k tokens
    MobileAuto-check passed

  • iOS Simulator Skill

    n0an/VivaDicta

    21 production-ready scripts for iOS app testing, building, and automation.

    126 GitHub starsUsed in 1 repo~2.5k tokens
    MobileAuto-check passed

  • Device Interaction

    Infomaniak/desktop-kDrive

    Verify iOS app behavior on device or simulator via screenshots, UI hierarchy, and touch interactions.

    120 GitHub starsUsed in 1 repo~1.9k tokens
    MobileAuto-check passed

  • Run iOS Simulator

    iPlug2/iPlug2OOS

    Build and run an iPlug2 iOS app in the iOS Simulator. An agent skill from iPlug2/iPlug2OOS.

    158 GitHub stars~711 tokensUpdated 22 days ago
    MobileAuto-check passed

  • Evaluating SDK Internal Updates

    bitwarden/ios

    Official

    Evaluates a bitwarden/ios "Update SDK to" PR against the sdk-swift commit range for compile-time, runtime and serialization breaking changes, maps affected symbols to iOS call sites, and applies…

    694 GitHub stars~2.6k tokensUpdated today
    MobileAuto-check passed

More from ipedro/Inspector

  • Inspector MCP

    ipedro/Inspector

    A skill your agent uses when an agent needs to inspect a live iOS app through the Inspector MCP bridge, register or troubleshoot InspectorMCPServer for a consumer Xcode project, or query, resolve…

    170 GitHub stars~3.4k tokensUpdated 5 mo ago
    Auto-check passed

  • Inspector Integration

    ipedro/Inspector

    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…

    170 GitHub stars~724 tokensUpdated 5 mo ago
    Auto-check passed

  • Inspector MCP Consumer

    ipedro/Inspector

    A skill your agent uses when an agent needs to patch a consumer iOS app so it exposes the Inspector MCP bridge, add or verify the app-side Inspector startup configuration, or choose the correct…

    170 GitHub stars~926 tokensUpdated 5 mo ago
    Auto-check passed

Works with

Categories

Questions about Inspector Implementation

What does Inspector Implementation do?

A skill your agent uses when an agent needs to implement or modify the Inspector library itself — panel UI, hierarchy/runtime behavior, custom property models, macros, or Example-app dogfooding. Inspector Implementation is an agent skill from ipedro/Inspector. Use when an agent needs to implement or modify the Inspector library itself — panel UI, hierarchy/runtime behavior, custom property models, macros, or Example-app dogfooding.

When should I use Inspector Implementation?

Inspector Implementation fits situations like: an agent needs to implement; modify the Inspector library itself — panel UI; hierarchy/runtime behavior; custom property models.

How do I install Inspector Implementation in Claude Code?

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

How do I install Inspector Implementation in Codex?

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

Can I use Inspector Implementation 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-implementation -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-implementation, .gemini/skills/inspector-implementation, .github/skills/inspector-implementation and .opencode/skills/inspector-implementation in your project.

What does Inspector Implementation need to run?

Going by SKILL.md and its folder, Inspector Implementation needs the command-line tools its instructions call (swift and xcodebuild).

Does Inspector Implementation 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 Implementation 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 Implementation use?

Inspector Implementation 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 Implementation use?

About 729 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 272 tokens, read only when the agent opens those files.

What are the alternatives to Inspector Implementation?

Skills that share tags, products or a category with Inspector Implementation: Hig Project Context (raintree-technology/hig-doctor, 142 stars), Hig Components Content (raintree-technology/hig-doctor, 142 stars), iOS Simulator Skill (n0an/VivaDicta, 126 stars) and Device Interaction (Infomaniak/desktop-kDrive, 120 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Inspector Implementation?

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.