Skip to content
cccskills
FreePublished on GitHub

upload-photo

Attach screenshots, images, or videos to GitHub pull requests and issues using GitHub CLI. It also covers embedding images within comment text, adding alternative text, and retrieving an uploaded asset’s URL from the posted comment.

OriginalShow the original description

Attach a screenshot/image/video to a PR or issue, or embed an image in a GitHub comment.

Works withGitHub
See how to install

Good for

  • Attach a screenshot to a pull request
  • Add a video to an issue report
  • Embed an image within a GitHub comment
  • Retrieve an uploaded image’s URL

Files included (1)

  • SKILL.md1014 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Upload Photo

Use GitHub CLI 2.99 or newer. Check and upgrade it if needed:

gh --version
brew upgrade gh

Attach a file to a new comment, putting alt text after #:

gh pr comment <n> --attach './shot.png#Alt text'
gh issue comment <n> --attach './shot.png#Alt text'

gh pr create, gh pr edit, gh issue create, and gh issue edit also accept repeatable --attach flags, with at most 50 files.

To place an image in the body, reference the same path:

printf '![Alt text](./shot.png)\n' | gh pr comment <n> --body-file - --attach './shot.png#Alt text'

GitHub rewrites that Markdown reference to the uploaded asset. Unreferenced attachments are appended to the comment.

There is no standalone “get a URL” command. The asset URL lives in the posted comment; read it back with gh api repos/{owner}/{repo}/issues/comments/<id> --jq .body.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

add-a-feature

FreeSummary

Manage OpenWork feature releases with feature flags, switches that control access to new behavior. Register features before coding, release them by organization and deployment, prepare a global shutdown option, and remove temporary flags after rollout.

  • Registering a feature before implementation
  • Releasing a feature to selected organizations
  • Separating cloud and self-hosted availability
different-ai/openwork24.2KUpdated Oct 19, 2026

Connect OpenCode browser tools to a locally running OpenWork Electron app to inspect its UI, enter a task, and check the response. This skill supports exploration and debugging through CDP, Chrome's remote control protocol.

  • Connecting browser tools to a local Electron development app
  • Inspecting screen state during debugging
  • Entering a task in the composer and running it
different-ai/openwork24.2KUpdated Oct 19, 2026

Check added lines in a change for information identifying customers, prospects, partners, or outside individuals. Report locations and generic remediation without reproducing identities, and escalate cases where the information is already public.

  • Checking changes for customer and partner identities
  • Reviewing documents and test data for identifying details
  • Reporting disclosure locations without repeating identities
different-ai/openwork24.2KUpdated Oct 19, 2026

Connects supported AI clients, including Claude Code and Codex, to OpenWork through MCP, a protocol for accessing external tools. It guides account sign-in and verifies that tools for finding and running organization capabilities are available.

  • Connecting an AI client to OpenWork organization resources
  • Signing in and verifying available MCP tools
  • Switching organizations or troubleshooting authentication
different-ai/openwork24.2KUpdated Oct 19, 2026

Review an outside contributor’s pull request before running its code. Identify concealed behavior, obfuscated code, risky dependencies, and build hooks, with file locations and specific checks for maintainers to follow up.

  • Screening an outside contributor’s pull request before execution
  • Checking encoded code and unexplained network calls
  • Reviewing dependency changes and installation scripts
different-ai/openwork24.2KUpdated Oct 19, 2026

create-plugin

FreeSummary

Create an OpenCode plugin for OpenWork with custom tools and hooks, which run code at specific events. The skill builds the plugin file and adds its entry to the project configuration.

  • Adding custom tools to OpenWork
  • Creating a plugin to save and list notes
  • Running custom code before or after tool execution
different-ai/openwork24.2KUpdated Oct 19, 2026

See all skills by different-ai

Report a problem with this skill