uploads-cli

Upload local files to uploads.sh and manage GitHub PR attachments.

11|Updated Jul 6, 2026

Search Tags:#automation #screenshots #github #cli #uploads #file-hosting

Ready to run

npx skills add https://github.com/buildinternet/uploads --skill uploads-cli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: uploads-cli
Source: https://github.com/buildinternet/uploads/tree/main/skills/uploads-cli
Command: npx skills add https://github.com/buildinternet/uploads --skill uploads-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of hosting local files and screenshots for AI agents that lack direct access to GitHub's browser-based image hosting, ensuring visual evidence is always available in PRs and issues.

Core Features & Use Cases

Stable File Hosting: Uploads local files to a persistent, hash-free URL that remains stable even if the file is updated.
Automated PR Attachments: Automatically manages a dedicated attachments comment in GitHub PRs and issues, keeping documentation clean and up-to-date.
Use Case: An agent capturing before-and-after screenshots during a refactor can use this skill to automatically stage and embed those images into the PR comment as it works, without requiring manual intervention.

Quick Start

Use the uploads cli to attach the local file named screenshot.png to the current git branch pull request.

Frequently Asked Questions about uploads-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I upload local files to GitHub PRs from a CLI agent?▼

To upload local files to GitHub PRs from a CLI agent, use a command-line interface that hosts files on a cloud service and embeds the stable URLs into PR comments. This workflow requires authenticated access to the uploads.sh API and the GitHub CLI.

Can I automate screenshot attachments for visual documentation in GitHub issues?▼

Yes, you can automate screenshot attachments for visual documentation in GitHub issues. The system automatically manages a dedicated attachments comment in issues, keeping visual evidence synchronized and clean without manual intervention.

What is the best way to keep image URLs stable when updating files for a pull request?▼

The best way to keep image URLs stable when updating files for a pull request is using a file-hosting service that provides persistent, hash-free URLs. The URLs remain unchanged even if the underlying local file is updated.

Do I need the GitHub CLI to manage pull request attachments?▼

Yes, you need the GitHub CLI to manage pull request attachments. Repository-specific operations, such as synchronizing comment attachments in pull requests and issues, require the GitHub CLI alongside authenticated access to the uploads.sh API.

How does automated file hosting work for coding agents without browser access?▼

Automated file hosting for coding agents without browser access works by providing a command-line interface to upload local files to a cloud service. It bypasses GitHub's browser-based image hosting, ensuring visual evidence is always available in PRs and issues.

What are the limitations of using CLI file hosting for GitHub PRs?▼

Limitations of using CLI file hosting for GitHub PRs include the strict dependency on authenticated access to the uploads.sh API and the GitHub CLI. Without these environment prerequisites, the automated visual documentation workflow cannot function.