takazudo/gh-issue-with-imgs
skills/gh-issue-with-imgs/SKILL.md
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'.
$ install --global
skillsauthnpx skillsauth add takazudo/claude-resources gh-issue-with-imgsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 7, 2026, 4:56 AM289.7s2 files scanned
SKILL.md
- name:
- gh-issue-with-imgs
- description:
- 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'.
- user-invocable:
- true
- argument-hint:
- <owner/repo> <title> --body <body> --img <path> [--img <path>...]
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>
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
_attachmentsrelease 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.shhelper is shared: the gh-fetch-issue skill reuses it to embed/ssscreenshot placeholders into existing issues
Related Skills
takazudo/finalize-codex-work
tools
VerifiedTrustedCommunity
Acceptance gate for a branch produced by an OpenAI Codex CLI run — usually Codex implementing a /big-plan epic that was handed off to it. Codex reports the work 'done' (or the user flags it WIP with corrections); this skill confirms the branch actually fulfils the original spec, fixes what falls short, and routes larger discoveries into GitHub issues. Use when: (1) User says '/finalize-codex-work', 'finalize codex work', 'confirm the codex work', 'check the codex branch', or 'codex said it's done', (2) A branch is the result of a Codex CLI session and needs verification against its spec issue/PR, (3) After assigning a /big-plan epic to Codex CLI. Pass -m/--merge to run /pr-complete -c at the end.
11SKILL.mdUpdated Jul 10, 2026
takazudo/fig-url-refer
tools
VerifiedTrustedCommunity
Read a Figma design node directly from a share URL via the Figma REST API — no Dev Mode subscription, no MCP, no desktop app. Renders the node to PNG and dumps its full style/layout JSON so the design can be described, compared, or implemented. Use whenever the user gives a Figma design URL (figma.com/design/... or /file/...) and wants to see, read, inspect, reference, or implement that node — including `/fig-url-refer <url>`. This is the URL-based counterpart to `/figrefer` (which needs a Dev-plan desktop MCP); prefer this one when the input is a URL rather than a live desktop selection.
11SKILL.mdUpdated Jul 10, 2026
takazudo/dev-codex-sync-settings-from-claude
tools
VerifiedTrustedCommunity
Sync the user's Claude Code workflow skills into the OpenAI Codex CLI settings repo ($HOME/.codex) as Codex-native ports, fix the Codex .gitignore for new local state, then commit and push. Use when: (1) user says '/dev-codex-sync-settings-from-claude', 'sync codex settings', 'sync claude skills to codex', 'port skills to codex', or 'update codex from claude'; (2) after updating ~/.claude workflow skills (big-plan, x, x-as-pr, x-wt-teams) and Codex should catch up; (3) the $HOME/.codex repo has drifted behind $HOME/.claude. The ports are condensed Codex-native REWRITES, never file copies.
11SKILL.mdUpdated Jul 10, 2026
takazudo/video-reader
development
VerifiedTrustedCommunity
Analyze a video file (mov, mp4, webm, etc.) or a YouTube video by extracting still frames with ffmpeg and reading them chronologically with vision — Claude cannot ingest video files directly. Use whenever the user provides a video file path or YouTube URL and wants to know what happens in it: "read this video", "watch this video", "check this recording", "what happens in this .mov/.mp4", analyzing a screen recording of a UI bug, or verifying UI behavior captured in a video, even if they don't name this skill.
11SKILL.mdUpdated Jul 7, 2026