ios-device-screenshot
Take screenshots from physical iOS devices connected via USB using pymobiledevice3. Use when capturing screenshots from real iPhones/iPads (not simulators), debugging on-device, or needing high-fidelity device captures. Triggers on physical iOS device screenshots, pymobiledevice3 usage, or USB-connected device capture tasks.
88
82%
Does it follow best practices?
Impact
100%
2.17xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines a narrow, specific capability with strong trigger terms and explicit usage guidance. It effectively differentiates itself from related skills (e.g., simulator screenshots) through explicit scoping. The description uses proper third-person voice and includes both 'Use when' and 'Triggers on' clauses for comprehensive selection guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists concrete actions: 'Take screenshots from physical iOS devices connected via USB using pymobiledevice3.' Specifies the tool (pymobiledevice3), connection method (USB), and target (physical iOS devices). Multiple specific capabilities are described including debugging on-device and high-fidelity captures. | 3 / 3 |
Completeness | Clearly answers both 'what' (take screenshots from physical iOS devices via USB using pymobiledevice3) and 'when' (explicit 'Use when' clause covering real devices vs simulators, debugging on-device, high-fidelity captures, plus a 'Triggers on' clause listing specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms: 'screenshots', 'physical iOS devices', 'USB', 'iPhones/iPads', 'simulators' (as exclusion), 'pymobiledevice3', 'on-device', 'device captures'. These are terms users would naturally use when needing this specific functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by specifying physical iOS devices (not simulators), USB connection, and pymobiledevice3. The explicit exclusion of simulators and the specific tool mention create a clear niche that is unlikely to conflict with general screenshot tools or iOS simulator skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides strong actionable guidance with real, executable commands for iOS device screenshots using pymobiledevice3. Its main weaknesses are internal contradictions (the --udid vs --tunnel advice for multiple devices differs between sections), some redundancy between sections, and missing validation checkpoints in the workflow. The content would benefit from reconciling contradictory advice and adding explicit verification steps.
Suggestions
Resolve the contradiction between Quick Reference (pass UDID to --tunnel) and Troubleshooting (use --udid flag) for multiple device handling - pick one correct approach and be consistent.
Add explicit validation checkpoints to the workflow, e.g., verify device is detected before starting tunneld, confirm tunneld is ready before taking screenshot.
Remove the 'Key Discovery' section since the iOS 17+ DVT requirement is already covered in the Usage section - consolidate to reduce redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but has some redundancy. The 'Multiple devices connected' troubleshooting section contradicts the Quick Reference section (using --udid vs passing UDID to --tunnel), and the 'Key Discovery' section partially repeats information already covered in the Usage section. Some explanatory text like 'The `--tunnel ""` flag tells it to use the tunneld for device communication' is unnecessary. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready commands throughout. Installation, usage for different iOS versions, troubleshooting, and a complete integration script are all concrete and specific with real command-line examples. | 3 / 3 |
Workflow Clarity | The multi-step process (install → start tunneld → take screenshot) is present but lacks explicit validation checkpoints. The integration example has basic error checking but the main workflow doesn't include verification steps like confirming the device is connected or tunneld is actually ready before proceeding. The contradictory advice about --udid vs --tunnel for multiple devices also hurts clarity. | 2 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections, but it's somewhat long for a single file (~100 lines of content). The troubleshooting section, integration example, and quick reference could potentially be split out. However, for a skill of this complexity, keeping it in one file is borderline acceptable. The internal contradiction between sections hurts navigation trust. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
e437c3c
- 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.