Rjv github image upload

Skill rjvim/ai-skills/skills/rjv-github-image-upload

Install

npx -y skills add rjvim/ai-skills --skill rjv-github-image-upload

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

0 stars0 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.

What its author says it does

Copied from the file, not written here

Upload local images to GitHub and embed them in a PR/issue/comment as canonical github.com/user-attachments URLs (private repos stay private), via the gh-image CLI. Triggers: 'attach a screenshot to the PR', 'add an image to the PR/issue', 'show test results in the PR', 'embed before/after screenshots'.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.9 KB, as published. Nobody here has run it

Upload images to GitHub (gh-image)

GitHub has no public API for image uploads — the web UI uses an internal endpoint that mints user-attachments URLs scoped to the repo's visibility. gh-image (MIT, © drogers0) replicates that flow as a gh CLI extension, so you can upload from the terminal and get a ready-to-embed ![name](url) back.

This skill drives gh-image and then embeds the result into a PR/issue/comment.

Prerequisites — verify these before uploading

Run these checks; only act on the ones that fail.

gh CLI installed & authenticated
```
gh auth status
```
If it fails, tell the user to run gh auth login (do not attempt it unattended).

The gh-image extension installed (idempotent — skip if already present)

gh extension list | grep -q 'drogers0/gh-image' || gh extension install drogers0/gh-image

A GitHub session for the upload. gh-image does NOT use the gh token for the upload (that endpoint rejects tokens); it needs the browser user_session cookie. Resolution order (first match wins):
- --token <value> flag, or
- GH_SESSION_TOKEN env var (use this in CI / headless), or
- the cookie store of a logged-in browser (Chrome/Brave/Chromium/Edge/Firefox/ Opera/Safari) — the default for local use. On macOS the first read may show a Keychain prompt; the user should click Always Allow.
⚠️ A user_session cookie grants full account access (it is not scoped like a PAT). Treat it like a password; in CI use a dedicated bot account.

Step 1 — Normalize the image path

Use an absolute path. If a glob is given, resolve it first. Paths with spaces or Unicode (e.g. CleanShot's narrow spaces) work, but quote them.

Step 2 — Upload

# One or more images; --repo is optional inside a repo working dir (inferred from the remote).
gh image "/abs/path/screenshot.png" --repo <owner>/<repo>

gh image prints markdown to stdout, e.g.:

![screenshot.png](https://github.com/user-attachments/assets/<uuid>)

Capture that output — it is the embeddable reference. For multiple files it prints one line per image.

Step 3 — Embed into the PR / issue / comment

gh-image only prints the markdown; you embed it. Pick the target the user asked for.

Append to a PR description (preserves the existing body):

MD="$(gh image "/abs/path/shot.png" --repo owner/repo)"
BODY="$(gh pr view <pr> --repo owner/repo --json body -q .body)"
printf '%s\n\n## Screenshots\n\n%s\n' "$BODY" "$MD" \
  | gh pr edit <pr> --repo owner/repo --body-file -

Post as a new PR comment:

MD="$(gh image "/abs/path/shot.png" --repo owner/repo)"
printf '## Screenshots\n\n%s\n' "$MD" | gh pr comment <pr> --repo owner/repo --body-file -

Add to an issue body / comment: same pattern with gh issue edit <n> --body-file - or gh issue comment <n> --body-file -.

Always use --body-file - (not inline --body) so multi-line bodies and special characters can't break shell quoting.

Step 4 — Verify

gh pr view <pr> --repo owner/repo --json body -q .body   # confirm the URL is present

The user-attachments URL inherits the repo's visibility, so on a private repo it renders only for authorized viewers (an anonymous fetch returns 404/403 — that is expected, not a failure).

Sizing (optional)

To control display size, embed an HTML tag instead of the bare markdown:

<img width="800" alt="screenshot" src="https://github.com/user-attachments/assets/<uuid>" />

Troubleshooting

Symptom	Cause / fix
`<org> enforces SAML SSO and your session is not authorized…`	The org requires SSO and your session isn't authorized. Open the `https://github.com/orgs/<org>/sso` URL from the message in a browser, authorize (lasts ~24h), then retry. Write access alone is not enough — this is not a permissions problem.
`uploadToken not found … do you have write access?`	The generic no-token case. Confirm you have write access; if the repo's org uses SSO, authorize at `https://github.com/orgs/<org>/sso` (the message includes this hint) and retry.
No `user_session` cookie found	Log into GitHub in a supported browser, or set `GH_SESSION_TOKEN`.
Windows + Chrome 127+ can't read cookies	Known cookie-library limitation — use another browser or `GH_SESSION_TOKEN`.
CI / headless run	Set `GH_SESSION_TOKEN` (dedicated bot account); the browser cookie path won't exist.
`gh: command not found`	Install the GitHub CLI (`brew install gh`, etc.).