CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ios-debugger-agent

Debug the current iOS project on a booted simulator with XcodeBuildMCP.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/ios-debugger-agent/SKILL.md

The canonical home for this skill is ios-debugger-agent in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an excellent example of a lean, actionable skill: exact tool invocations, a clearly sequenced workflow with validation and escalation checkpoints, and no wasted tokens. No bundle files exist, and none are needed at this size.

DimensionReasoningScore

Conciseness

The ~50-line body is lean with zero concept explanation or padding; every line is a concrete tool call, parameter, or decision rule, assuming Claude's competence throughout.

5 / 5

Actionability

Guidance is fully executable: exact MCP tool names (e.g., mcp__XcodeBuildMCP__build_run_sim, describe_ui) with concrete parameters, fallback sequences for unknown bundle ids, and coverage of the common cases (build, run, launch, UI interaction, logs, troubleshooting).

5 / 5

Workflow Clarity

The core workflow is explicitly numbered (discover simulator, set defaults, build+run) with validation checkpoints (retry or escalate on build failure; verify launch via describe_ui/screenshot before UI interaction) and a troubleshooting section providing feedback loops.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and content is well organized into clear sections (Overview, When to Use, Core Workflow, UI Interaction, Logs, Troubleshooting), satisfying the simple-skill exception.

5 / 5

Total

20

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and names a specific, distinct niche, but it undersells the skill's actual capabilities and entirely lacks a "when to use" trigger clause. Adding trigger guidance and mentioning the build/run/UI/logs capabilities would materially improve it.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to run, debug, or test an iOS app on a simulator, or to inspect simulator UI, screenshots, or logs.'

Surface the skill's main capabilities (build and run the scheme, interact with the UI, capture simulator logs) so the description matches what the body delivers.

Include natural trigger variations such as 'run my app', 'launch on the simulator', and 'Xcode' to broaden keyword coverage.

DimensionReasoningScore

Specificity

"Debug the current iOS project on a booted simulator with XcodeBuildMCP" names the domain and one concrete action, but omits the build, run, UI interaction, and log capture capabilities the body actually covers, so coverage is not comprehensive.

3 / 5

Completeness

It clearly answers "what" (debug an iOS project on a booted simulator via XcodeBuildMCP) but contains no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"Debug", "iOS", "simulator", and "XcodeBuildMCP" are relevant keywords, but common natural variations users would say are missing (e.g., "run my app", "launch", "Xcode", "console logs"), matching the anchor for some relevant keywords with missing synonyms.

3 / 5

Distinctiveness Conflict Risk

iOS simulator debugging through a specific MCP server is a clear niche with mostly distinct triggers; only minor overlap risk with closely related Xcode build/test skills prevents a 5.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/ios-debugger-agent/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.