Agent skills
A skill is a single Markdown file (SKILL.md) with YAML frontmatter that tells your AI agent when to use it and how. We ship three so any agent that supports the spec — Cursor, Claude Code, or your own — can author .screenshot documents the way our team does internally.
Skills are the unit of proceduralknowledge for an AI agent. Where rules describe always-on conventions (lint settings, naming policies), a skill describes a workflow the agent should follow when a specific situation comes up — “when the user asks for App Store screenshots, do these 12 steps in this order.”
A skill file is plain Markdown. The YAML frontmatter has two fields the agent reads: name and description. The description tells the agent whento fire the skill (it’s prompted to match the user’s request against the description); the body is the actual procedure. Agents support optional supporting files in a references/ or workflows/ subdirectory that the skill body links to.
Every skill below is a real file from our repo, used unchanged by our internal team. None of them require an API key or any runtime — they’re Markdown.
--- name: create-screenshot-file description: | Compose a .screenshot document for an app's App Store listing using the sscc CLI. Use when the user asks to create App Store screenshots, recreate a competitor's listing, or ship marketing screenshots for any Apple app. --- # Create a `.screenshot` file ## Core principle Screenshots are advertisements, not docs. ## Workflow ### Step 1 — Ask the user these questions ... ### Step 2 — Deconstruct any reference listing ...
Skills live in either a workspace folder (.cursor/skills/ for Cursor, .claude/skills/ for Claude Code) or a user-global folder (~/.cursor/skills/ or ~/.claude/skills/). Install per-project for portability or globally so every project gets it.
SKILL=create-screenshot-file DEST=.cursor/skills # or .claude/skills mkdir -p "$DEST/$SKILL" curl -L "https://raw.githubusercontent.com/luigiinred/screenshotcomposer-website/main/skills/$SKILL/SKILL.md" \ -o "$DEST/$SKILL/SKILL.md" # Pull the references/ folder too if you want the full skill. curl -L "https://github.com/luigiinred/screenshotcomposer-website/raw/main/skills/$SKILL.tar.gz" \ | tar -xz -C "$DEST"
SKILL=create-screenshot-file DEST=~/.cursor/skills # or ~/.claude/skills mkdir -p "$DEST" curl -L "https://github.com/luigiinred/screenshotcomposer-website/raw/main/skills/$SKILL.tar.gz" \ | tar -xz -C "$DEST"
After installing, restart your agent (or run a refresh command if your tool supports one). Then ask: “Use the create-screenshot-file skill to design a listing for MyApp.” The agent will read the skill on its own.
12-step workflow from app pitch to ASC-ready PNGs. Three editorial gates (discovery, design plan, copy approval), then composition, audit, and export. The skill the agent should reach for first.
Add or edit reusable bundled templates that ship inside the Mac app. Includes scripts to fetch every screenshot from any apps.apple.com URL across iPhone, iPad, and Mac in one call.
Field-by-field schema for the .screenshot package — JSON manifest, per-platform composition lists, layer schema, asset packaging, export pixel sizes, bezel catalog. Pure reference; agents read this when they're hand-writing JSON or debugging a save/load issue.
| If the user wants… | Use |
|---|---|
A one-off .screenshot file for a specific app | create-screenshot-file |
| A reusable bundled template that ships inside the Mac app | template-author |
| To recreate a competitor’s listing as a one-off file | create-screenshot-file + template-author scripts |
| To recreate a competitor’s listing as a reusable template | template-author |
| To hand-write a .screenshot JSON file (test fixture, demo content, port to another tool) | screenshot-format |
| Tips for driving any of this with an AI agent | AI workflow page → |