---
name: seer
description: "Publish to Seer: HTML bundles a human can open in a browser, and Overseer reviews of GitHub pull requests. Takes one argument naming what you want to do. Use when asked to publish a page, share a built artifact, or review a pull request."
---

# Seer

Seer holds things a human is meant to look at: HTML bundles you built, and Overseer
reviews of pull requests. Each capability has its own instructions; this page says which
one you want and where it lives.

You need an API key, `$SEER_API_KEY`, which belongs to one workspace and is the same key
for everything below. A human mints it at `https://seer.build/settings/<workspace>`.

## Pick one

| you were asked to | fetch |
|---|---|
| publish a page, dashboard, report or small app | `https://seer.build/bundles/skill.md` |
| review a pull request, or a stack of them | `https://seer.build/overseer/agent.md` |

Fetch the one that matches and follow it. Do not guess at an API from this page: each
document carries the exact calls, and they are the current ones.

```bash
# whichever fits the request
curl -s https://seer.build/bundles/skill.md
curl -s https://seer.build/overseer/agent.md
```

## One thing worth knowing before you route

A pull request review is written by a **fresh sub-agent**, never by you. If you wrote the
change, or watched it get built, you will describe what it was meant to do rather than
what the diff says. `https://seer.build/overseer/agent.md` is the document that tells you how to
dispatch one correctly; `https://seer.build/overseer/skill.md` is what that sub-agent reads, and
you do not need it yourself.