agentsclimarketplace

Github screenshot

Skill jerseycheese/agent-skills/skills/github-screenshot

Generates GitHub-compatible markdown for screenshots using raw.githubusercontent.com URLs via the generate-github-image-markdown.sh script. Trigger on: "add a screenshot to this PR", "embed image in issue", "attach screenshot", "paste image into GitHub", "add screenshot to docs", "insert image in markdown", "show a screenshot in the PR", "add image to issue".From its SKILL.md

Install
npx -y skills add jerseycheese/agent-skills --skill github-screenshot

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.6 KB, as published. Nobody here has run it

GitHub Screenshot Helper

When to Use This Skill

Use this skill when:

  • Adding screenshots to PR descriptions
  • Including images in GitHub issues
  • Documenting features with screenshots
  • Creating visual documentation in markdown

Setup

This skill wraps a local generate-github-image-markdown.sh script. Update the path below to match your own installation before using.

Directory convention

When the image is being committed purely so it can render in an issue/PR body (not an existing app asset the user is pointing you at), commit it under a top-level github-screenshots/<topic-or-issue>/ directory — e.g. github-screenshots/hover-text-invisible/before-hover.png. The name says what these files are for: throwaway evidence for a GitHub body, not app screenshots or fixtures, so they're easy to find and prune later without touching anything else in the repo. Don't reuse a generic screenshots/ dir for this — that name doesn't self-document, and it collides with whatever ad-hoc convention a given repo might already have for actual app screenshots.

If the target repo already has an established convention for this (check with the user or look for precedent — e.g. git log --diff-filter=A --name-only --all | grep -iE 'screenshot'), follow that instead of introducing a second one.

What This Skill Does

Runs your generate-github-image-markdown.sh script to:

  • Generate proper raw.githubusercontent.com URLs
  • Create markdown with alt text and captions
  • Handle git repository detection automatically
  • Include helpful comments with local paths

Usage Flow

Step 1: Gather Information

Ask the user for:

  1. Image path (required) - relative or absolute
  2. Alt text (optional) - defaults to "Screenshot"
  3. Caption (optional) - italicized description below image

Step 2: Run the Script

Execute:

~/tools/screenshots/generate-github-image-markdown.sh \
  "$IMAGE_PATH" \
  "$ALT_TEXT" \
  "$CAPTION"

Permission pattern needed (update path to match your setup):

Bash(~/tools/screenshots/generate-github-image-markdown.sh:*)

Step 3: Present the Result

Show the generated markdown to the user:

## Generated Screenshot Markdown

```markdown
![Alt Text](https://raw.githubusercontent.com/user/repo/branch/path/image.png)

*Caption text*

<!-- GitHub URL: https://raw.githubusercontent.com/... -->
<!-- Local path: ./github-screenshots/image.png -->

Then ask: "Should I insert this somewhere, or just copy it?"

### Step 4: Optional Insertion

If user wants it inserted:
- Ask where to insert (e.g., "in the PR description I'm writing")
- Use Edit tool to insert at appropriate location
- Confirm insertion complete

## Example Interaction

**User:** `/github-screenshot`

**Claude:**

I'll help you generate GitHub screenshot markdown.

What's the image path?


**User:** `./github-screenshots/dashboard-before.png`

**Claude:**

Alt text for the screenshot? (default: "Screenshot")


**User:** `Dashboard before refactor`

**Claude:**

Optional caption? (press enter to skip)


**User:** `Shows the original dashboard layout`

**Claude:** *Runs script and presents result*
```markdown
## Generated Screenshot Markdown

![Dashboard before refactor](https://raw.githubusercontent.com/user/repo/main/github-screenshots/dashboard-before.png)

*Shows the original dashboard layout*

<!-- GitHub URL: https://raw.githubusercontent.com/user/repo/main/github-screenshots/dashboard-before.png -->
<!-- Local path: ./github-screenshots/dashboard-before.png -->

Would you like me to insert this somewhere?

Error Handling

File Not Found

If image doesn't exist:

❌ Error: Image file not found at ./github-screenshots/missing.png

Please check the path and try again.

Not in Git Repository

If script can't detect git repo:

⚠️ Warning: Couldn't generate GitHub URL (not in a git repository)

Generated markdown with relative path instead:
![Alt Text](./github-screenshots/image.png)

Note: This may not display correctly in GitHub

Script Not Found

If the script is missing:

❌ Error: Screenshot script not found at expected location.

Please verify the script exists at the path configured in this skill,
or update the path in Step 2 to match your installation.

Common Use Cases

PR Description with Screenshot

User: "Add this screenshot to the PR description"
Claude: [runs skill, gets markdown, inserts into PR description being drafted]

Multiple Screenshots

User: "Add 3 screenshots"
Claude: [runs skill 3 times, collecting all markdown, then inserts all at once]

Quick Copy

User: "Just generate the markdown, I'll paste it myself"
Claude: [runs skill, presents markdown, doesn't insert anywhere]

Integration with Your Workflow

This skill encodes the full screenshot workflow — you just invoke it instead of remembering the script path, argument order, and permission pattern every time.

Notes

  • This skill wraps a local script
  • The script handles all the git complexity (remote detection, branch detection, path conversion)
  • Permission pattern is encoded in the skill, so you don't need to remember it
  • Works in any git repository, automatically detects repo details

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most docs writing skills give

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

  • Use third-person for skill descriptionsin 54 of 1951, across 35 files
  • Start descriptions with Use whenin 43 of 1951, across 29 files
  • Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
  • Use active voicein 40 of 1951, across 36 files
  • Map file responsibilities before defining tasksin 36 of 1951, across 29 files
  • Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
  • Ask one question at a timein 35 of 1951
  • Offer execution options after saving the planin 33 of 1951, across 24 files
  • Include complete code in every stepin 33 of 1951, across 27 files
  • Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
  • Announce the skill usage at the startin 30 of 1951
  • Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

  • Ask user for image path
  • Ask user for alt text
  • Execute the image markdown script
  • Present generated markdown to user
  • Ask user if insertion is required
  • Use edit tool to insert markdown

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 611,884. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.