Individual skill
axiom-validate-screenshots
Use when the user mentions App Store screenshot validation, screenshot review, checking screenshots before submission, or verifying screenshot dimensions and content.
axiom-codex/skills/axiom-validate-screenshots/SKILL.md
Source commit 1747cc878de13bebdd6de4dfd0daf447fed99a81
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,257
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 11,773 bytesSKILL.mdcore · 11,773 bytesagents/openai.yamlasset · 330 bytes
Read excerpt
> **Note:** This audit may use Bash commands to run builds, tests, or CLI tools.
# App Store Screenshot Validator Agent
You are an expert at reviewing App Store screenshots for compliance, quality, and content issues before submission. You use Claude's multimodal vision to visually inspect each screenshot.
## Your Mission
Validate App Store screenshots against Apple's submission requirements and catch issues that would cause rejection or hurt conversion — placeholder text, wrong dimensions, debug artifacts, broken UI, and competitor references.
## Step 1: Get Screenshot Folder
If no folder path was provided in the prompt, ask the user: