skills/ss/SKILL.md
Load screenshot images or other files from Dropbox screenshots directory. Use when user invokes /ss directly. NEVER manually list/read files from the screenshots dir — this skill handles Dropbox sync delays, freshness checks, retry logic that manual reads miss. Supports: /ss 2 (latest 2), /ss latest3, /ss filename.png (exact/substring), /ss full-path. Also non-image files (e.g., /ss pattern-4-variations.html).
npx skillsauth add takazudo/claude-resources ssInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Load screenshot images or other files from the Dropbox screenshots directory and present them in the conversation. Also supports non-image files (HTML, text, etc.) that the user shares via this directory.
Use $DROPBOX_SCREENSHOTS_DIR env var (set in .zshrc for both macOS and WSL2).
The following epoch was captured at the moment this command was invoked:
Invocation epoch: !date +%s
Use this as a cutoff for "Latest N" mode — only consider image files whose modification time is <= this epoch. This prevents picking up screenshots that appeared after the user typed /ss.
$ARGUMENTS determines which files to load:
| Pattern | Meaning | Example |
| --- | --- | --- |
| Bare number (2, 3) | Latest N images at invocation time | /ss 2 |
| latestN | Latest N images at invocation time | /ss latest3 |
| Full path starting with / | Exact file | /ss '/Users/.../file.png' |
| Non-image filename (.html, .txt, etc.) | Read a non-image file from screenshots dir | /ss pattern-4-variations.html |
| Other string (exact) | Exact filename in screenshots dir | /ss Screenshot 2026-03-14 at 3.27.17.png |
| Other string (partial) | Substring search in filenames | /ss foo-bar-moo.png |
| (empty) | Latest 1 image | /ss |
Default: When $ARGUMENTS is empty or blank, treat it as 1 (load the latest single screenshot). This is the most common use case.
Non-image files: When the argument has a non-image extension (e.g., .html, .txt, .json, .css, .js, .svg, .md), look for that file in $DROPBOX_SCREENSHOTS_DIR and read it as a text file using the Read tool. This is for when the user shares files (not just screenshots) via the Dropbox screenshots directory.
List all image files (png, jpg, jpeg, gif, webp, tiff) in the screenshots directory, filter to only those with modification time <= the invocation epoch, sort by modification time descending, take the first N.
CUTOFF=<invocation_epoch>
ls -t "$DROPBOX_SCREENSHOTS_DIR"/*.{png,jpg,jpeg,gif,webp,tiff} 2>/dev/null | while IFS= read -r f; do
[ "$(stat -f %m "$f")" -le "$CUTOFF" ] && echo "$f"
done | head -n $N
This ensures that even if new screenshots appear while Claude is processing, only files that existed at invocation time are selected.
When the argument has a non-image extension (not .png, .jpg, .jpeg, .gif, .webp, .tiff):
$DROPBOX_SCREENSHOTS_DIR/<filename>$DROPBOX_SCREENSHOTS_DIR/<filename>foo-bar-moo.png → foo-bar-moo)screenshot ↔ screenshots, image ↔ images)# Substring search example
SEARCH="foo-bar-moo"
find "$DROPBOX_SCREENSHOTS_DIR" -maxdepth 1 -type f \( -iname "*.png" -o -iname "*.jpg" -o -iname "*.jpeg" -o -iname "*.gif" -o -iname "*.webp" -o -iname "*.tiff" \) -iname "*${SEARCH}*" -print0 | xargs -0 ls -t 2>/dev/null | head -n 1
Use the path as-is.
The user typically takes a screenshot and immediately runs /ss. Dropbox sync introduces a delay of a few seconds (sometimes longer), so the file may not exist locally yet. This section handles that proactively.
For "Latest N" mode (bare number, latestN, or empty argument), always sleep 3 seconds before the first file lookup. This gives Dropbox a moment to sync the new screenshot. This simple delay avoids the most common case where old files are returned because the new one hasn't arrived yet.
# Always do this before the first file listing in "Latest N" mode
sleep 3
After listing files, check whether the results are fresh enough relative to the invocation epoch. A screenshot the user just took should have a modification time within ~60 seconds of the invocation epoch.
Freshness rule: At least one of the N files must have a modification time within 120 seconds before the invocation epoch. If ALL files are older than 120 seconds before the invocation epoch, the user's new screenshot likely hasn't synced yet — retry.
CUTOFF=<invocation_epoch>
FRESHNESS_THRESHOLD=$((CUTOFF - 120))
# After getting the N files, check the newest one:
NEWEST_MTIME=$(stat -f %m "$NEWEST_FILE")
if [ "$NEWEST_MTIME" -lt "$FRESHNESS_THRESHOLD" ]; then
# All results are stale — the new screenshot hasn't synced yet, retry
fi
If the file is not found (specific filename mode) or the freshness check fails (Latest N mode), poll with retries:
[ -f "$TARGET" ])# Specific filename mode
for i in $(seq 1 24); do
[ -f "$TARGET" ] && break
sleep 5
done
# Latest N mode (after initial 3-second delay already elapsed)
for i in $(seq 1 24); do
# Re-run the file listing and freshness check
FILES=$(ls -t "$DROPBOX_SCREENSHOTS_DIR"/*.{png,jpg,jpeg,gif,webp,tiff} 2>/dev/null | while IFS= read -r f; do
[ "$(stat -f %m "$f")" -le "$CUTOFF" ] && echo "$f"
done | head -n $N)
NEWEST=$(echo "$FILES" | head -n 1)
[ -n "$NEWEST" ] && [ "$(stat -f %m "$NEWEST")" -ge "$FRESHNESS_THRESHOLD" ] && break
sleep 5
done
Use the Read tool to read each file. The Read tool supports reading image files (PNG, JPG, etc.) visually, and text files as content.
After reading, briefly acknowledge which file(s) were loaded (filename only, not full path) and ask what the user would like to do with them.
After presenting files, you MUST treat them as the user's intended files. The user just took these screenshots and ran /ss — they expect you to work with whatever was loaded.
NEVER do this:
/ss wasn't invokedThe user's screenshots ARE the context. Even if the content seems unrelated to the prior conversation, the user may be introducing new context, switching topics, or showing something you don't yet understand.
Only if the files are obviously stale (e.g., timestamps are many hours old, content is clearly from a different session), follow this two-step recovery:
Step 1: Wait and recheck (Dropbox sync delay)
The user's actual screenshot may still be syncing. Wait 2 minutes, then re-list the directory for newer files:
# Wait for potential Dropbox sync delay
sleep 120
# Re-check for newly synced files (allow mtime up to 180s after invocation epoch)
LATE_CUTOFF=$((CUTOFF + 180))
ls -t "$DROPBOX_SCREENSHOTS_DIR"/*.{png,jpg,jpeg,gif,webp,tiff} 2>/dev/null | while IFS= read -r f; do
MTIME=$(stat -f %m "$f")
[ "$MTIME" -le "$LATE_CUTOFF" ] && [ "$MTIME" -gt "$CUTOFF" ] && echo "[NEW] $f"
done | head -n 3
If new files appeared, read and present them — these are likely the intended screenshots.
Step 2: Ask the user
If no new files appeared after waiting, present what you have and ask the user to confirm:
"I loaded [filenames]. These screenshots appear to be from [timestamp]. Are these the ones you meant, or should I wait longer for a newer screenshot to sync?"
Never skip both steps. If you suspect the files are wrong, you MUST either wait-and-recheck OR ask the user. Silently ignoring the user's /ss invocation is never acceptable.
development
Link Claude Code skill names mentioned in a CodeGrid article (data/{series}/{n}.md) to the author's public claude-resources repo, pinned to the latest commit hash so links don't rot. Use when: (1) user says 'linkify cc resources', 'link the skills', 'link skill names', or invokes /dev-linkify-cc-resources; (2) editing a CodeGrid article that mentions `/commits`, `/pr-complete`, `/skill-creator` or other Claude Code skills and they should point to claude-resources. Only links skills that actually exist in the public repo; skips hypothetical examples and code blocks.
development
Second opinion from Claude Opus on a plan or approach. Use when: (1) Planning phase of /big-plan needs a higher-quality review than /codex-2nd / /gco-2nd / /gcoc-2nd, (2) User says 'opus 2nd' or 'opus opinion', (3) Wanting Anthropic's larger model to critique a plan. Spawns a general-purpose Agent with model: opus that reads the plan file and returns structured feedback. Anthropic quota — not free.
tools
AI-based testing via subagent + a per-task test-flow skill. Use when the user wants to verify something that mechanical assertions can't fully capture — image recognition, visual size/position comparison, animation smoothness, multi-step manual flows that need AI judgment. Triggers: 'AI-based test', 'AI test', 'visual verify', 'image recognition test', 'manual operation test', 'human-eye check', 'verify visually', 'compare screenshots', 'looks the same', 'looks correct'. The skill's job is to (1) author a focused test-flow skill that captures the exact procedure + verdict criteria, then (2) dispatch a verification subagent via the Agent tool that loads BOTH the test-flow skill AND a browser-driving skill (/verify-ui primary, /headless-browser fallback) so the subagent has clear context and consistent verdicts. NEVER uses `claude -p` — subagent dispatch goes through the Agent tool exclusively.
development
End-of-workflow audit of touched GitHub issues, PRs, and branches via a Sonnet subagent. Use when: (1) /big-plan, /x-as-pr, or /x-wt-teams finishes its main work and needs to verify every touched resource is in the right state (closed when done, kept when ongoing, deleted when dead), (2) User says 'cleanup resources', 'audit cleanup', or 'check what should be closed', (3) A long workflow ends and the manager wants a structured paper trail of what it closed/kept/deleted. Auto-execute by default — the Sonnet agent proposes, the manager (you) executes safe actions and prints a final report.