agentleFS
Sign inStart free
jazzyalexjazzyalex/agent-sessions/skills/sc-skill/SKILL.md

sc-skill

Skill941 starsChanged 9 days agoMITView on GitHub

Capture deterministic macOS screenshots for testing, docs, release notes, and marketing assets. Use when asked to automate app screenshots, batch-generate screenshot sets, standardize window sizing/composition, or choose between Peekaboo and native macOS screenshot tooling.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. rahmanef63/si-coder-agent★ 13same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 6 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to produce repeatable screenshots for two modes:

    line 10
  2. Distinctive:

    Run a manifest batch:

    line 34
  3. Very specific:

    Start with --tool auto (defaults to Peekaboo when available and permitted).

    line 48
  4. Very specific:

    Use --tool native when you need zero external dependency and simple window-region capture.

    line 49
  5. Very specific:

    Always run sc_window_preset.sh first.

    line 52
  6. Distinctive:

    Use consistent presets across runs to reduce visual drift.

    line 53
  7. Very specific:

    Default output uses mode-based max edge (--max-edge auto): testing=1800, marketing=2560, optimized/compressed for sharing/upload.

    line 58
  8. Distinctive:

    Default transcript readiness remains fast-fail if loading still does not occur after nudge attempts.

    line 63
  9. Very specific:

    If transcript readiness times out, capture fails fast by default.

    line 64
  10. Distinctive:

    Never run captures from XCTest-driven launches when validating user-visible UI behavior.

    line 68
  11. Very specific:

    Keep screenshot naming stable and descriptive (screen-purpose-state.png).

    line 69
  12. Distinctive:

    Avoid manual resize/drag between shots.

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SC Skill

Overview

Use this skill to produce repeatable screenshots for two modes:

  • testing: stable evidence screenshots for QA/regression workflows.
  • marketing: polished, consistently framed screenshots for docs/site/release assets.

This skill is macOS-first and uses Peekaboo as primary automation with native screencapture fallback.

Quick Start

  1. Normalize window size and position:
skills/sc-skill/scripts/sc_window_preset.sh --app "AgentSessions" --preset marketing
  1. Capture one screenshot (auto-select tool):
skills/sc-skill/scripts/sc_capture.sh \
  --app "AgentSessions" \
  --mode marketing \
  --delay 0.25 \
  --max-edge auto \
  --window-preset auto \
  --output artifacts/screenshots/agent-sessions-main.png
  1. Run a manifest batch:
skills/sc-skill/scripts/sc_capture_suite.sh \
  --manifest skills/sc-skill/references/examples/agent-sessions.tsv \
  --outdir artifacts/screenshots

Workflow

  1. Choose mode:
  • testing: prioritize determinism and speed.
  • marketing: prioritize composition consistency.
  1. Choose tool:
  • Start with --tool auto (defaults to Peekaboo when available and permitted).
  • Use --tool native when you need zero external dependency and simple window-region capture.
  1. Enforce layout before capture:
  • Always run sc_window_preset.sh first.
  • Use consistent presets across runs to reduce visual drift.
  1. Capture and archive:
  • Save to artifacts/screenshots/....
  • Sidecar metadata (.json) is opt-in via --metadata; default runs keep artifacts cleaner.
  • Default output uses mode-based max edge (--max-edge auto): testing=1800, marketing=2560, optimized/compressed for sharing/upload.
  • AgentSessions windows are normalized to a realistic working preset before capture (mode-based testing/marketing) to avoid distorted/compressed UI composition.
  • Single capture closes the target app window by default (--no-close-window to keep it open).
  • Suite runs close captured app windows after all requested screenshots by default (--no-close-after-suite to keep them open).
  • For AgentSessions, transcript readiness retry includes a built-in selection nudge (key down + 0.5s pause) to force transcript loading before capture.
  • Default transcript readiness remains fast-fail if loading still does not occur after nudge attempts.
  • If transcript readiness times out, capture fails fast by default; pass --allow-blank-transcript only when blank transcript output is acceptable.

Guardrails

  • Never run captures from XCTest-driven launches when validating user-visible UI behavior; use a normal app launch.
  • Keep screenshot naming stable and descriptive (screen-purpose-state.png).
  • Avoid manual resize/drag between shots; use presets.
  • For multi-shot runs, use the suite manifest instead of ad-hoc commands.

Resources

  • scripts/sc_window_preset.sh: deterministic window sizing/placement.
  • scripts/sc_capture.sh: single-shot capture with Peekaboo/native fallback.
  • scripts/sc_capture_suite.sh: manifest-driven batch capture.
  • references/tool-matrix.md: tooling decision matrix and tradeoffs.
  • references/workflow-checklist.md: repeatable QA/marketing checklist.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free