How do I install the Gh Issue With Imgs skill?

Run npx skillmds@latest add takazudo/gh-issue-with-imgs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gh Issue With Imgs safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gh Issue With Imgs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gh Issue With Imgs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gh Issue With Imgs?

takazudo (@takazudo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gh Issue With Imgs by takazudo — Agent Skill

Name: Gh Issue With Imgs
Author: takazudo

Gh Issue With Imgs

Create GitHub issues with embedded images via CLI. Uploads images as GitHub release assets and embeds them in the issue body. Use when: (1) Creating an issue that needs screenshots, (2) Programmatically attaching images without browser UI, (3) User says 'issue with images', 'gh issue with imgs', or 'create issue with screenshots'.

takazudo Updated Sep 17, 2026

File contents

GitHub Issue with Images

Create GitHub issues with embedded images using release assets as image hosting.

GitHub CLI does not support attaching images to issues natively. This skill works around that by uploading images to a dedicated release, then embedding the asset URLs in the issue body markdown.

Usage

Arguments: <owner/repo> <title> --body <body> --img <path> [--img <path>...]

Multiple --img flags supported. If no --body, use empty string.

Process

Step 1: Parse Arguments

Extract from the skill arguments:

owner/repo (required) - the target repository
Title (required) - the issue title
--body (optional) - issue body text
--img (one or more) - paths to image files

Step 2: Upload Images and Get URLs

Upload all --img paths with the helper script — it ensures the non-draft _attachments release exists (cleaning up any legacy draft release), uploads each file under a unique name, and prints one public download URL per input path, in order:

bash $HOME/.claude/skills/gh-issue-with-imgs/scripts/upload-to-release.sh <owner/repo> <path> [<path> ...]

Why a script rather than gh release upload <file>#<name>: the #<name> suffix only sets the asset's display label — the asset name (and download URL) stays the sanitized original basename, so same-named files collide. The script copies each file to a unique, URL-safe temp name and uploads that, yielding a predictable URL. Capture stdout; each line is the browser_download_url for the matching input.

Step 3: Build Issue Body

Append image markdown to the body:

<original body text>

![<filename>](<asset_url>)

For multiple images, add each on its own line.

Step 4: Create the Issue

gh issue create \
  --repo <owner/repo> \
  --title "<title>" \
  --body "$(cat <<'EOF'
<constructed body with embedded images>
EOF
)"

Print the created issue URL.

Notes

The _attachments release is a real (non-draft) release so asset URLs are publicly accessible without authentication
Never use --draft — draft release assets return 404 for unauthenticated requests (e.g., Claude API vision, curl), even though they appear to work in browsers where the user is logged in
Asset URLs are permanent as long as the release exists
Works for both public and private repos (private repo assets require authentication to view)
Image size limit: same as GitHub release assets (2 GB per file)
Supported formats: any image format (png, jpg, gif, svg, webp, etc.)
The scripts/upload-to-release.sh helper is shared: the gh-fetch-issue skill reuses it to embed /ss screenshot placeholders into existing issues

---name: gh-issue-with-imgsdescription: Create GitHub issues with embedded images via CLI. Uploads images as GitHub release assets and embeds them in the issue body. Use when: (1) Creating an issue that needs screenshots, (2) Programmatically attaching images without browser UI, (3) User says 'issue with images', 'gh issue with imgs', or 'create issue with screenshots'.---# GitHub Issue with ImagesCreate GitHub issues with embedded images using release assets as image hosting.GitHub CLI does not support attaching images to issues natively. This skill works around that by uploading images to a dedicated release, then embedding the asset URLs in the issue body markdown.## UsageArguments: `<owner/repo> <title> --body <body> --img <path> [--img <path>...]`Multiple `--img` flags supported. If no `--body`, use empty string.## Process### Step 1: Parse ArgumentsExtract from the skill arguments:- `owner/repo` (required) - the target repository- Title (required) - the issue title- `--body` (optional) - issue body text- `--img` (one or more) - paths to image files### Step 2: Upload Images and Get URLsUpload all `--img` paths with the helper script — it ensures the non-draft`_attachments` release exists (cleaning up any legacy draft release), uploadseach file under a unique name, and prints one public download URL per inputpath, in order:```bashbash $HOME/.claude/skills/gh-issue-with-imgs/scripts/upload-to-release.sh <owner/repo> <path> [<path> ...]```Why a script rather than `gh release upload <file>#<name>`: the `#<name>` suffixonly sets the asset's *display label* — the asset `name` (and download URL) staysthe sanitized original basename, so same-named files collide. The script copieseach file to a unique, URL-safe temp name and uploads that, yielding a predictableURL. Capture stdout; each line is the `browser_download_url` for the matching input.### Step 3: Build Issue BodyAppend image markdown to the body:```markdown<original body text>![<filename>](<asset_url>)```For multiple images, add each on its own line.### Step 4: Create the Issue```bashgh issue create \ --repo <owner/repo> \ --title "<title>" \ --body "$(cat <<'EOF'<constructed body with embedded images>EOF)"```Print the created issue URL.## Notes- The `_attachments` release is a real (non-draft) release so asset URLs are publicly accessible without authentication- Never use `--draft` — draft release assets return 404 for unauthenticated requests (e.g., Claude API vision, curl), even though they appear to work in browsers where the user is logged in- Asset URLs are permanent as long as the release exists- Works for both public and private repos (private repo assets require authentication to view)- Image size limit: same as GitHub release assets (2 GB per file)- Supported formats: any image format (png, jpg, gif, svg, webp, etc.)- The `scripts/upload-to-release.sh` helper is shared: the gh-fetch-issue skill reuses it to embed `/ss` screenshot placeholders into existing issues

Frequently asked questions