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.

2.17x

Quality

90%

Does it follow best practices?

Impact

100%

2.17x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Quality

Content

86%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.

A highly actionable, well-structured single-file skill with executable commands covering the common iOS 17+/16 cases and multi-device selection, plus a tunneld-aware integration example. Minor redundancy in the Key Discovery section and slightly thin validation checkpoints are the only weaknesses.

Suggestions

Trim the 'Key Discovery' section or fold its fails-vs-works example into Usage, since the screenshot-vs-dvt distinction is already shown earlier — reducing token redundancy.

Add an explicit validation checkpoint in the main iOS 17+ workflow (e.g., verify the output file exists and is non-empty, or check the tunneld connection) before declaring success.

Consolidate the overlapping single-device screenshot command between the iOS 17+ Usage block and Quick Reference to avoid repeated identical commands.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands and minimal concept explanation, but the "Key Discovery" section restates the screenshot-vs-dvt distinction already shown in Usage and Quick Reference, and the iOS-17+/iOS-16 split plus Quick Reference contains some command repetition; fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean top anchor.	4 / 5
Actionability	Provides fully executable, copy-paste-ready bash commands covering installation, tunneld startup, single-device and multi-device (UDID) capture, mounting, and troubleshooting; matches the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	Clear sequence for iOS 17+ (start tunneld in Terminal 1, capture via DVT in Terminal 2) with an integration example that checks whether tunneld is running before proceeding, but there is no explicit validation that the screenshot file was produced beyond the integration example's file existence check, leaving a minor validation gap; fits 'clear sequence with most checkpoints present; minor validation gaps' rather than the explicit-validate top anchor.	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent) and the single SKILL.md is a well-organized single-purpose skill with clear section headers (Installation, Prerequisites, Usage, Quick Reference, Troubleshooting, Key Discovery, Integration Example); per the simple-skill scoring note a well-organized single file with no need for external references can score 5.	5 / 5
	Total	18 / 20 Passed

Description

95%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.

A tight, specific description that clearly states both what the skill does and when to trigger it, with rich natural keyword coverage and a distinctive niche. Only minor room for improvement on enumerating multiple distinct capabilities rather than one well-described action.

Dimension	Reasoning	Score
Specificity	"Take screenshots from physical iOS devices connected via USB using pymobiledevice3" names several concrete actions (capturing screenshots, debugging on-device, high-fidelity device captures) with only minor gaps in coverage, fitting the 'several specific actions; minor gaps' anchor; not a 5 because the action list is effectively one core action with a few use-case framings rather than multiple distinct capabilities.	4 / 5
Completeness	Explicitly answers 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. Triggers on...") with concrete trigger phrases; matches the top anchor.	5 / 5
Trigger Term Quality	Covers natural terms including "real iPhones/iPads", "physical iOS device", "pymobiledevice3", "USB-connected device", and "simulators" — comprehensive coverage of how users phrase this request with synonyms and tool name; matches the top anchor.	5 / 5
Distinctiveness Conflict Risk	Narrowly scoped to physical iOS devices via USB with pymobiledevice3 and explicitly excludes simulators, giving a clear niche with minimal overlap risk against simulator or non-iOS screenshot skills; matches the top anchor.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Path: data/skills-md/0xbigboss/claude-code/ios-device-screenshot/SKILL.md
Commit: 2f57aec

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.