AI Agent Hub
Back to skills
GitHub Image Hosting Upload icon

GitHub Image Hosting Upload

Development Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Install @user_15292d5a/yjkj-github-image-hosting by following https://skillhub.cn/install/skillhub.md in your AI assistant.

About this skill

Problem Solved

When adding screenshots to GitHub PRs, issues, or READMEs, local image links can expire, be inaccessible, or require extra static hosting setup. github-image-hosting uploads an image to img402.dev and returns a URL that can be embedded directly in Markdown, removing the need to manage temporary hosting manually.

How It Works

The workflow is compact: get the image → check size → upload → embed the link. It is designed for GitHub workflows, especially updating PR descriptions or issue comments with the gh CLI.

  • Free tier: up to 1 MB per image, 7-day retention, supports PNG, JPEG, GIF, and WebP, with 1,000 free uploads per day globally and no authentication.
  • Paid tiers: use an x402 client to obtain a token before uploading; the 1-year and Permanent options support up to 5 MB, which is useful for READMEs, architecture docs, and long-lived public images.
  • Embedding: after upload, use the returned URL in ![alt](url) and write it with gh pr edit, gh pr comment, or issue commands.

If a screenshot is too large, reduce its dimensions first, for example with sips -Z 1600. Prefer PNG for UI screenshots and JPEG for photographs.

Boundaries

This skill fits short-lived screenshots, review images, and documentation visuals, but it is not a substitute for a durable asset repository. Free links expire after 7 days, and paid retention is still subject to terms of service. For production documentation that requires absolute stability, pair it with self-hosted storage or a backup strategy.

Use Cases

  • When reviewing a PR, upload a UI screenshot as a hosted URL and add it to the PR description.
  • When filing an issue, compress a reproduction screenshot under 1 MB and embed it in the comment.
  • When maintaining a README, upload an architecture diagram as a long-lived link and replace local images.
  • When publishing a blog post, upload a 5 MB visual using a paid tier and embed it in Markdown.

Best For

  • Frontend engineers reviewing component PRs who need to attach UI screenshots quickly in the description.
  • QA engineers filing defect reports who need to embed reproduction screenshots in issue comments.
  • Open-source maintainers who need long-lived image links for architecture diagrams in READMEs.
  • Technical bloggers who need to upload larger visuals and embed them in Markdown posts.