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.
91
Quality
86%
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 hits all the marks. It provides specific capabilities, includes natural trigger terms users would actually say, explicitly answers both what and when questions, and clearly distinguishes itself from related skills (particularly iOS simulator tools). The explicit contrast with simulators and the specific tool mention (pymobiledevice3) make it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Take screenshots from physical iOS devices connected via USB using pymobiledevice3' with clear technical context including the tool (pymobiledevice3), connection method (USB), and device types (iPhones/iPads). | 3 / 3 |
Completeness | Clearly answers both what ('Take screenshots from physical iOS devices connected via USB using pymobiledevice3') and when ('Use when capturing screenshots from real iPhones/iPads, debugging on-device, or needing high-fidelity device captures'). Also includes explicit 'Triggers on' clause. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'screenshots', 'physical iOS device', 'iPhones/iPads', 'simulators', 'on-device', 'pymobiledevice3', 'USB-connected device capture'. Includes both technical and casual terminology. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: explicitly distinguishes from simulators, specifies physical devices via USB, and names the specific tool (pymobiledevice3). Very unlikely to conflict with simulator screenshot skills or general iOS development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable guidance for iOS device screenshots with good structure and executable examples. However, it contains contradictory information about the --udid flag behavior with tunneld that could confuse users, and has some redundant content between sections. The troubleshooting section is valuable but needs to be reconciled with the Quick Reference guidance.
Suggestions
Resolve the contradiction about --udid flag: Quick Reference says it 'doesn't work with tunneld' but Troubleshooting shows using '--udid' with '--tunnel ""'. Clarify which approach actually works.
Remove duplicate multiple-devices guidance - consolidate into one authoritative section with the correct approach.
Add a validation step after taking screenshots to confirm the file was created successfully, similar to the integration example's check.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy - the multiple devices section appears twice (Quick Reference and Troubleshooting), and there's contradictory information about --udid flag usage that adds confusion rather than clarity. | 2 / 3 |
Actionability | Provides fully executable commands throughout with copy-paste ready examples. Installation, prerequisites, and usage commands are all concrete and specific with actual paths and flags. | 3 / 3 |
Workflow Clarity | Steps are listed but there's a contradiction: Quick Reference says '--udid flag doesn't work with tunneld' while Troubleshooting shows using --udid with tunneld. The integration example has a validation check but the main workflow lacks explicit validation checkpoints. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from installation to prerequisites to usage to troubleshooting. Content is appropriately structured for a single-file skill with logical section ordering and a helpful integration example at the end. | 3 / 3 |
Total | 10 / 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
5342bca
- 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.