buildinternet

@buildinternet source repo

20 skills
0 followers
11 hours ago last updated

▌
Releases CLI · buildinternet bundle
Use the `releases` CLI to search, browse, and read the Releases.sh changelog registry from the terminal — the keyless, agent-friendly peer of the Releases MCP. Activate when the user mentions "releases CLI", runs a `releases` command, asks how to install it, or wants to look up releases, sources, orgs, collections, or changelogs from a shell.

0
installs
▌
Releases MCP · buildinternet
Use when the user asks about recent releases, changelogs, what's new in a library, breaking changes, version updates, or wants to compare products. Activates for questions like "what changed in Next.js 15?", "latest Tailwind releases", "compare Bun vs Deno releases".

0
installs
▌
Analyzing Releases · buildinternet
Analyze release trends across multiple companies to produce competitive intelligence. Use when asked to compare companies, analyze a market segment, identify industry trends, forecast upcoming releases, or answer questions like "what is X shipping lately" or "how does X compare to Y." Also triggers on requests for competitive landscape analysis, feature gap analysis, or release velocity comparisons.

0
installs
▌
Uploads CLI · buildinternet
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, 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.

0
installs
▌
Docs Page Style · buildinternet
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.

0
installs
▌
Github Screenshots · buildinternet
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", "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

0
installs
▌
Annotate Screenshots · buildinternet
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.

0
installs
▌
Local Ingest · buildinternet bundle
Onboard or backfill a company's changelog locally in Claude Code by fetching pages and extracting releases with the agent itself (and parallel sub-agents), then writing through the batch-upsert endpoint — no remote fetch dispatch, no server-side extraction inference billing. Use when you want to onboard a source without triggering the remote update workflow's billed extraction, or recover from a remote fetch that burned tokens and wrote zero releases. Includes a mandatory robots.txt / Content-Signal opt-out gate.

0
installs
▌
Creating Releases JSON · buildinternet bundle
Create or update a releases.json manifest so registries and agents can find where a company or project publishes its release notes. Use this whenever someone wants to "list our product on Releases", "add a releases.json", "get indexed on releases.sh", "here's our website, make us a manifest", declare a changelog / updates page / RSS feed / GitHub releases / App Store listing / CHANGELOG for discovery, publish a /.well-known/releases.json, or edit an existing one — even if they don't say "releases.json" by name. The usual input is just a company website or domain (no codebase required); the manifest is a small, schema-validated file the owner hosts on their domain or repo. This skill discovers the real publish locations, models products without over-fragmenting, writes the correctly-scoped file, validates it locally, and guides publishing it.

0
installs
▌
Maintaining Orgs · buildinternet
Routine maintenance of indexed organizations — fetch all sources, regenerate overviews, verify data quality. Use when asked to "update", "refresh", or "maintain" one or more orgs, or when doing periodic sweeps of the registry.

0
installs
▌
Managing Sources · buildinternet
How to create, delete, list, validate, and manage changelog sources — covers ignored/blocked URLs, duplicate detection, and the validation workflow

0
installs
▌
Grouping Releases · buildinternet
Group releases that cover the same underlying launch so readers see one story instead of three. Use when manually curating an org's coverage — reconciling a window of recent releases, fixing a bad automatic grouping, or linking coverage the deterministic clusterer can't see. Decide which item is the best entry point for the average reader and mark it canonical. Local Claude Code operator skill; ingest-time grouping is deterministic code, not this skill.

0
installs
▌
Seeding Playbooks · buildinternet
Coordinate bulk playbook writing using parallel sub-agents — covers org discovery, prompt templates, model selection, batch dispatch, verification, and the parent-saves pattern for working around subagent permission limits. Currently wired up for Claude Code's Agent tool; the managed-agent fleet supports sub-agents too and the pattern can be adapted, but isn't wired up there yet.

0
installs
▌
Finding Changelogs · buildinternet
How to find, evaluate, and recommend the best ingestion method for changelog URLs — covers feed discovery, provider detection, GitHub API, markdown sources, and scraping fallback

0
installs
▌
Parsing Changelogs · buildinternet
How the Releases fetch and parse pipeline works — covers feed vs scrape adapters, incremental vs bulk parsing, dry-run testing, crawl mode, content hashing, and enrichment

0
installs
▌
Backfilling Sources · buildinternet
Backfill a changelog source's full history locally in Claude Code via the backfill-source / backfill-sweep dynamic Workflows — preflight-gated, window-capped, budget-gated extraction written through the idempotent /batch upsert, with no remote extraction inference bill. Use when a source has a lot of history to pull in and running the remote update workflow per window would be too expensive. Local Claude Code only.

0
installs
▌
Firecrawl Monitoring · buildinternet
Put a challenge-blocked or unreliable scrape source on the external Firecrawl monitoring backend, or triage one that's already on it. Use when a page sits behind a bot challenge our Browser Rendering can't clear, when render keeps returning an empty shell, when enabling/disabling/tuning a monitor, or when a Firecrawl-backed source went quiet or ingested wrong content. Operator skill; requires admin API access and prod-only Firecrawl bindings.

0
installs
▌
Regenerating Overviews · buildinternet
Generate or refresh an org's AI overview from recent releases. Use when asked to "regenerate", "rewrite", or "refresh the overview" for one or more orgs, or as the regen step inside a maintaining-orgs run.

0
installs
▌
Classify Media Relevance · buildinternet
Decide whether an image or video found on a release page is editorial content (screenshots, demos, diagrams, product shots) or site chrome (avatars, logos, tracking pixels, decorative badges). Used during parsing to populate a release's media array.

0
installs
▌
Generating Release Content · buildinternet
Generate the AI fields on releases — `title_generated`, `title_short`, `summary`, and `composition` — for one release, a window, or a backfill, via Claude Code sub-agents and direct SDK calls (OpenRouter/DeepSeek to match production summarize). Use when iterating on prompts, running provider/model experiments, or filling in a small-to-medium backfill outside the production ingest path. Large backfills: prefer scripts/generate-release-content.ts (OpenRouter by default; Anthropic Batches via --anthropic-batch). (Managed agents can spawn sub-agents now too; the dispatch scaffolding for this skill just isn't wired up on that side yet.)

0
installs

20 published skills