CtrlK
BlogDocsLog inGet started
Tessl Logo

ios-debugger-agent

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

65

Quality

78%

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 a tight, fully actionable, well-sequenced workflow with concrete MCP tool calls, validation checkpoints, and error-recovery guidance, and it is appropriately organized for a simple single-purpose skill.

DimensionReasoningScore

Conciseness

The body is lean, using short bullets of exact MCP tool calls with no concept explanations or padding, matching anchor 5 ('Lean and efficient; assumes Claude's competence; every token earns its place'); it is not merely 'efficient with minor trims' (anchor 4).

5 / 5

Actionability

Concrete executable tool calls with parameters and failure fallbacks (e.g. 'mcp__XcodeBuildMCP__build_run_sim' and the bundle-id discovery sub-steps) cover common cases, matching anchor 5 ('Fully executable; copy-paste ready code or commands; specific examples cover the common cases').

5 / 5

Workflow Clarity

A clear numbered sequence (discover simulator, set defaults, build+run) includes explicit validation checkpoints ('verify the app launched by calling describe_ui or screenshot before proceeding') and error-recovery feedback loops, matching anchor 5 ('Clear sequence with explicit validation steps; feedback loops for error recovery').

5 / 5

Progressive Disclosure

No bundle files exist and the ~50-line body is well-organized with clear section headers (Overview, When to Use, Core Workflow, UI Interaction, Logs, Troubleshooting); per the simple-skill scoring note this earns a 5 for well-organized content with no need for external references.

5 / 5

Total

20

/

20

Passed

Description

57%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 specific and clearly targets a distinct iOS-simulator debugging niche, but it lacks an explicit 'Use when...' trigger clause and only names one main action, which caps completeness and trigger-term quality at 3.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers, e.g. 'Use when the user asks to run, debug, or inspect an iOS app on a simulator.'

Broaden trigger terms with synonyms users say naturally, such as 'iPhone simulator', 'Xcode', and 'run app'.

Name a couple more concrete actions (e.g. 'build, run, inspect the UI, and capture logs') to lift specificity toward 4-5.

DimensionReasoningScore

Specificity

Quotes 'Debug the current iOS project on a booted simulator with XcodeBuildMCP' name the domain and a concrete action plus tool, matching anchor 3 ('Names domain and 1-2 concrete actions, but not comprehensive'); it does not list several distinct actions required for a 4.

3 / 5

Completeness

The 'what' is clear but there is no 'Use when...' clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3, matching anchor 3 ('Has a clear what but when is missing or only weakly implied').

3 / 5

Trigger Term Quality

Natural terms like 'iOS', 'simulator', and 'Debug' are present, but common user variations such as 'iPhone', 'run app', or 'Xcode' are missing and 'XcodeBuildMCP' is tool jargon, fitting anchor 3 ('Some relevant keywords but missing common variations or synonyms') better than anchor 4.

3 / 5

Distinctiveness Conflict Risk

The niche (debugging an iOS project on a booted simulator via XcodeBuildMCP) is highly specific with distinct triggers and minimal conflict risk, matching anchor 5 ('Clear niche with distinct triggers; minimal conflict risk') rather than the broader anchor 4.

5 / 5

Total

14

/

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.

Validation15 / 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
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.