Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable troubleshooting skill with excellent workflow clarity and a well-defined diagnostic sequence. Its main weakness is length — the reference sections at the bottom (error codes, known issues, platform checklists, common issues) account for roughly half the file and could be extracted into separate reference files to improve conciseness and progressive disclosure. The platform-specific files are referenced but not provided in the bundle, making it impossible to fully validate the progressive disclosure structure.
Suggestions
Extract the reference sections (SDK error codes, debug log interpretation, known platform issues, platform configuration checklists, common issues) into a separate REFERENCE.md file to reduce the main skill's token footprint.
Provide the referenced platform files (platforms/ios.md, platforms/android.md, etc.) in the bundle to complete the progressive disclosure structure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-structured and avoids explaining basic concepts, but it's quite long (~300 lines). Some sections like the reference tables and common issues could be tightened. The diagnostic report template is useful but verbose. The platform configuration checklists partially duplicate the universal checklist items (e.g., bundle ID matching, product status). | 2 / 3 |
Actionability | The skill provides highly concrete, executable guidance throughout: specific MCP tool calls with exact function names, real code snippets for cache refresh, exact error codes with solutions, specific paths to check in dashboards, and precise product ID formats. The diagnostic report template is copy-paste ready with clear fix actions. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced across 5 numbered phases with explicit ordering ('work them in order', 'most reports resolve before you reach platform specifics'). Phase B has systematic checklists with checkboxes. Step 5 (Verify the fix) provides explicit validation criteria before declaring success. The MCP diagnosis includes a confirm-before-fix pattern for destructive operations. | 3 / 3 |
Progressive Disclosure | The skill references platform-specific files (platforms/ios.md, platforms/android.md, etc.) which is good progressive disclosure, but no bundle files were provided to verify they exist. The main SKILL.md itself is quite long with extensive reference sections (error codes, known issues, configuration checklists, common issues) that could be split into separate reference files to keep the main skill leaner. | 2 / 3 |
Total | 10 / 12 Passed |