Content
100%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a lean, fully actionable reference card for the XcodeBuildMCP toolset: exact tool names and parameters, a sequenced workflow with explicit validation gates and error-recovery loops, and a well-organized section layout appropriate to its size. No padding, no inferred-only capabilities, and no need for bundle files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line conveys tool-specific facts Claude cannot know (exact MCP tool names, parameter names, workflow order, failure handling); there is no concept explanation or padding, and the 47-line body assumes Claude's competence throughout. | 5 / 5 |
Actionability | Fully executable guidance: exact tool callables (mcp__XcodeBuildMCP__build_run_sim, session-set-defaults) with enumerated parameters (projectPath, scheme, simulatorId, configuration, useLatestOS), concrete option values like preferXcodebuild: true, a fallback chain for unknown bundle ids, and coverage of common cases including build failure and UI troubleshooting. | 5 / 5 |
Workflow Clarity | A clearly numbered Core Workflow with explicit validation checkpoints and feedback loops: check error output and retry or escalate before any UI interaction after a build failure, verify the app launched via describe_ui or screenshot before proceeding, run describe_ui before tapping, and re-run describe_ui after layout changes. | 5 / 5 |
Progressive Disclosure | A simple under-50-line skill with no need for external reference files: content is well organized into Overview, Core Workflow, UI Interaction & Debugging, Logs & Console Output, and Troubleshooting sections, which satisfies the simple-skill exception for a full score. | 5 / 5 |
Total | 20 / 20 Passed |