skills.rest
benzwick
benzwickCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

generate-screenshots

Launch Slicer, capture UI screenshots, and generate manifest.json metadata.

Updated Jan 25, 2026
Search Tags:#automation#documentation#screenshots#extension#manifest#submission#slicer
One-click install
npx skills add https://github.com/benzwick/SlicerMouseMaster --skill generate-screenshots
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generate-screenshots
Source: https://github.com/benzwick/SlicerMouseMaster/tree/main/.claude/skills/generate-screenshots
Command: npx skills add https://github.com/benzwick/SlicerMouseMaster --skill generate-screenshots

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates the creation of screenshots for Extension Index submissions and documentation, ensuring consistent visuals with minimal manual effort.

Core Features & Use Cases

  • Automates main UI capture, including main UI, button mappings, and preset interfaces.
  • Generates a Screenshots/ manifest.json and organizes outputs for submission and review.
  • Use Case: When updating documentation after UI changes, run the automated capture to refresh all submission images.

Quick Start

Run the automated capture script from the project root to generate main UI, button mapping, and preset screenshots.

Frequently Asked Questions about generate-screenshots

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate screenshots for a Slicer extension submission?▼

You can automate extension screenshots by running a Bash script that launches Slicer, loads the extension, captures UI states like button mappings and presets, and saves images to a Screenshots/ directory.

What is the best way to generate a manifest.json for extension documentation images?▼

Generating a manifest.json for documentation is handled automatically by the capture script, which organizes output screenshots of various UI configurations and generates the metadata file during the Slicer session.

Can I capture different UI states and presets for my extension automatically?▼

Yes, the automated capture process records different module states, button mappings, and preset interfaces by coordinating Slicer to load the extension and capture each interface configuration sequentially.

Do I need to manually configure Slicer to take screenshots of the MouseMaster extension?▼

No, the script automates the entire process by launching Slicer, loading the MouseMaster extension directly, and programmatically capturing the required screenshots without manual UI interaction.

How do I refresh documentation images after updating my extension UI?▼

To refresh documentation images after UI changes, run the automated capture script from the project root to regenerate all submission screenshots and update the manifest.json file.

What limitations exist when using a Bash script for Slicer extension screenshot automation?▼

The Bash script coordinates Slicer automation specifically for extension submissions, meaning it requires a compatible Bash environment and Slicer installation to execute the capture and metadata generation correctly.

Related Skills

Explore More Content & Communication Skills→
julianobarbosajulianobarbosa
7

Iterm2

Manage iTerm2 and tmux workflows with native -CC integration.

Community
Intermediate
LeoyishouLeoyishou
27

api-deploy-obsidian

Automate Obsidian plugin publishing with releases and community PRs.

Community
Advanced
benzwickbenzwick

test-bindings

Test mouse button bindings in Slicer MouseMaster to verify mappings and diagnose issues.

Community
Intermediate
dimagi-internaldimagi-internal
1

connect-baseline-screenshots

Capture per-version Connect UI navigation screenshots as indexed PNG assets with a manifest.

Official
Advanced