add-screenshot

Capture a screenshot from a forge-gpu lesson and embed it in its README.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RosyGameStudio/forge-gpu --skill add-screenshot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-screenshot
Source: https://github.com/RosyGameStudio/forge-gpu/tree/main/.claude/skills/add-screenshot
Command: npx skills add https://github.com/RosyGameStudio/forge-gpu --skill add-screenshot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of capturing screenshots from graphics lessons and embedding them into their respective README files, ensuring visual documentation is always up-to-date.

Core Features & Use Cases

  • Automated Screenshot Capture: Generates PNG screenshots from lesson executables.
  • README Integration: Automatically updates lesson READMEs by replacing a <!-- TODO: screenshot --> placeholder with the generated image markdown.
  • Use Case: After developing a new GPU lesson in the forge-gpu project, use this Skill to capture its visual output and update the lesson's documentation with a clear, representative image.

Quick Start

Use the add-screenshot skill to capture and embed a screenshot for the '01-hello-window' lesson.

Frequently Asked Questions about add-screenshot

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

FAQPage Schema
How do I automate taking screenshots from a lesson executable and embedding them in a README?

Automating screenshot capture involves running the lesson executable, converting the output from BMP to PNG, and replacing a TODO placeholder in the README with the image markdown.

How does replacing a TODO placeholder with a screenshot in a README work?

Replacing a TODO placeholder works by locating a specific comment tag in the README file and substituting it with the generated PNG image markdown to ensure visual documentation is updated.

What is the process to capture visual output from a forge-gpu lesson executable?

Capturing visual output requires resolving the lesson path, configuring the build with capture support, compiling the executable, and finally converting the captured BMP image to PNG format.

Can I update lesson documentation automatically after building a graphics lesson?

Yes, you can update lesson documentation automatically by running a script that captures the visual output of the compiled lesson executable and embeds the PNG screenshot directly into the README.

Does the screenshot capture process require a specific build configuration for the lesson executable?

Yes, the screenshot capture process requires a specific build configuration that enables capture support before compiling the lesson executable to successfully generate the output image.

Why does the screenshot need to be converted from BMP to PNG for README documentation?

Converting from BMP to PNG is necessary because PNG is the required image format for embedding the generated screenshot markdown directly into the lesson's README documentation.