buildinternet/uploads

Bake hand-drawn boxes, arrows, labels, freeform strokes, and redactions onto a screenshot so a PR reviewer or teammate sees exactly what changed and where to look, instead of reading a caption and hunting for it. Use this whenever a screenshot needs a callout — "point at the new button", "circle the bug", "arrow to the diff", "blur out the API key in this screenshot", "mark up this image before I attach it". Covers both annotating a live page during capture (uploads screenshot --annotate, CSS selector targeting) and annotating an image you already have (uploads annotate, pixel/freeform coordinates only). For getting the resulting image into a GitHub PR or issue, hand off to the github-screenshots skill — this skill only covers producing the annotated image.

House style and structure for uploads.sh documentation pages — the MDX subject pages under apps/web/src/content/docs/ (and the docs.astro hub) built on DocsLayout. Use this whenever you write, restructure, trim, or review a docs page: requests like "clean up the galleries docs", "this docs page has too much prose", "rework the agents page", "the flow on /docs/comment-config feels complicated", "make the reference page scannable", or any edit to a file under apps/web/src/content/docs/. Encodes the page structure (understand → set up → do), the Stripe-style intro voice, the copy-affordance and inline-code rules, the prose diet, and the DocsLayout component vocabulary, so every docs page reads like one deliberate, scannable system rather than a wall of prose. Reach for it even mid-task when you notice a docs page drifting toward heavy paragraphs, fabricated terminal output, or a copy button on every line.

Embed screenshots, images, diagrams, GIFs, and screen recordings in GitHub PRs and issues — or stage them ahead of a PR, collect them into one attachments comment, or get a durable public link to share a visual with a person. Use this whenever a visual needs to end up in a PR description, issue body, or PR/issue comment, in front of a teammate, or saved for a PR that doesn't exist yet. Triggers include "attach a screenshot to the PR", "add a before/after to the issue", "include a screenshot of …", "share a GIF of the flow", "record the bug and put it in the issue", "get me a link I can paste in Slack", "share a live feed of this PR's screenshots", "create a change feed", "stage screenshots for the PR", "attach this when I open the PR", "save this for the PR", "collect the PR's media", or having just captured or changed something visual that a shot would make clearer — even mid-task, before a PR exists. Also applies when an agent has no local filesystem and is uploading via the hosted MCP (agents.uploads.sh). Reach for this instead of drag-and-drop or hand-rolling cloud-storage uploads. GitHub CLI 2.99+ can attach a single image to an existing PR or issue with gh … --attach; this skill says when that is enough and when it is not. Capture the visual with whatever browser or screenshot tooling you have; this skill covers hosting and embedding it.

Reference for the uploads CLI and its stdio/hosted MCP tools — exact flags, keys, and contracts for put and attach, screenshot capture, stable PR/issue keys, the managed attachments comment, metadata and search, galleries, change feeds (repo-wide or one PR/issue), config defaults, login/doctor, and output formats. Use when driving the uploads CLI or its MCP tools (including the hosted MCP at agents.uploads.sh for agents without local filesystem/git access), when you need a public URL for a local file ("upload this", "host this image", "give me a public URL for this file"), when the CLI itself prints a hint or nudge you need to act on (a hint field in --format json, or the stderr note suggesting --pr/attach --branch), or when you need exact flags, key layouts, or setup and auth details. For the when-and-how of getting a screenshot or recording into a GitHub PR or issue, start with the github-screenshots skill — it defers here for CLI detail.