aspiers/ai-config / .agents/skills/hubdoc-reviewer
hubdoc-reviewer
VerifiedReview all unreviewed documents in Hubdoc. Use when reviewing, processing or publishing Hubdoc receipts and bills.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.1 KB |
| references/downloading.md | markdown | 1.5 KB |
| references/duplicates.md | markdown | 5.1 KB |
| references/failed-tab.md | markdown | 2.3 KB |
| references/fields.md | markdown | 5.1 KB |
| references/review-process.md | markdown | 19.6 KB |
| references/searching.md | markdown | 2.5 KB |
| references/uploading.md | markdown | 2.5 KB |
references/uploading.md
View on GitHub# Uploading documents
1. Click the "Upload Document" button
2. In the upload modal, set the file on the hidden file input:
```bash
agent-browser upload "#upload-modal input[type='file']:not(#file-upload)" /path/to/file.pdf
agent-browser wait 5000
```
3. Read the modal: each file is listed with its result, e.g.
`Invoice.pdf - 403 Forbidden` on failure. Then verify the new entry in
the document list.
4. **Close the upload modal**: it does not close automatically, and
`Escape` does not close it either. Click its close button by selector,
then confirm it is hidden:
```bash
agent-browser click "#upload-modal button.close-modal"
agent-browser eval "getComputedStyle(document.querySelector('#upload-modal')).display" # "none"
```
Do **not** use the `link "X"` ref: that X sits next to each listed file
and removes the file from the upload list; the modal stays open. The
close button (a red circled ×, top right) has no snapshot ref. If the
modal is left open it will interfere with subsequent interactions.
## Upload refused with 403 Forbidden (Akamai edge)
Hubdoc sits behind Akamai, which can refuse an upload at the edge even
while browsing and searching work. Confirm the source before drawing
conclusions:
```bash
agent-browser network requests --status 400-499 # find the POST .../api/upload
agent-browser network request <requestId> --json # inspect the response
```
An Akamai refusal is a bare HTML `403 Forbidden` page that embeds the bot
sensor script, with an `x-akamai-transformed` response header; Hubdoc's own
errors come back inside the app. Do not retry or try to evade the block:
it is a deliberate control. **Do not assume it targets the automated
browser** — the same refusal has hit the user's own browser. Email the file
to the Hubdoc inbox address shown in the upload modal (emailed documents
bypass the web upload path), then continue reviewing and publishing once
the document appears.
Evidence (2026-10-06): uploading one two-page supplier invoice PDF
returned 403 from the Akamai edge in agent-browser **and** in the user's
regular Chrome, which had never seen this error before; emailing the same
file to the Hubdoc inbox worked. An hour later a different supplier's PDF
receipt uploaded normally from agent-browser, so the block was specific
to that file or temporary, not a blanket block on uploads. When one file
is refused, try the next file normally rather than switching everything
to email.
## Downloading and reading Hubdoc PDFs
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |