ios-debugger-agent
Debug iOS Apps on Simulator
iOS simulator debugging often requires many separate build, launch, UI, and log steps. This skill gives Claude a clear XcodeBuildMCP workflow for inspecting app behavior in one guided session.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "ios-debugger-agent" from https://skillstore.io/skills/dimillian-ios-debugger-agent.md and its manifest at https://skillstore.io/api/skills/dimillian-ios-debugger-agent/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "ios-debugger-agent". Run the app and verify the home screen opens.
Expected outcome:
The app built and launched on the booted simulator. The home screen is visible, and the main navigation controls are present.
Using "ios-debugger-agent". Check why tapping sign in does nothing.
Expected outcome:
- The sign-in button is visible and hittable.
- After tapping, the screen did not change.
- The captured logs show a validation warning that should be investigated.
Using "ios-debugger-agent". Capture the current UI state for this bug report.
Expected outcome:
The simulator screenshot confirms the error banner is displayed above the form. The UI description shows the retry button is available.
Security Audit
SafeStatic findings are false positives caused by markdown inline code references to XcodeBuildMCP tools and iOS simulator parameters. The skill guides authorized local simulator debugging, UI inspection, screenshots, and log capture without arbitrary command execution, network upload, or prompt injection content.
Risk Factors
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/dimillian-ios-debugger-agent/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dimillian-ios-debugger-agent?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dimillian-ios-debugger-agent?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dimillian-ios-debugger-agent/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dimillian-ios-debugger-agent.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Dimillian. (2026). ios-debugger-agent security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dimillian-ios-debugger-agent/audits/10BibTeX citation
@techreport{dimillian-dimillian-ios-debugger-agent-2026,
author = {Dimillian},
title = {ios-debugger-agent security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/dimillian-ios-debugger-agent/audits/10},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "ios-debugger-agent security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "Dimillian"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/dimillian-ios-debugger-agent/audits/10"
identifiers:
- type: other
value: "skillstore:dimillian-ios-debugger-agent:audit:10"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Validate a New iOS Screen
Build and run the app, inspect the visible UI, and confirm that key elements appear on the simulator.
Investigate Runtime Behavior
Launch the app, capture console logs, interact with the UI, and summarize errors or warnings.
Reproduce a Simulator Bug
Follow a reported interaction path, use screenshots for confirmation, and collect simulator logs for diagnosis.
Try These Prompts
Run this iOS app on the booted simulator and tell me whether it launches successfully.
Use the simulator tools to describe the current UI and point out anything that looks broken.
Build and run the app, open the settings screen, tap the account option, and capture logs if the app fails.
Set the XcodeBuildMCP session defaults, run the Debug configuration, capture console output, and summarize likely causes of the launch failure.
Best Practices
- Start with the booted simulator and confirm the target scheme before building.
- Use UI description before tapping so interactions target visible elements.
- Capture logs only for the app and summarize relevant lines instead of pasting noisy output.
Avoid
- Do not run simulator actions without confirming a booted device exists.
- Do not rely on coordinates when labels or element identifiers are available.
- Do not treat simulator success as proof that behavior works on every physical device.