Skip to content

aspiers/ai-config / .agents/skills/hubdoc-reviewer

hubdoc-reviewer

Verified

Review all unreviewed documents in Hubdoc. Use when reviewing, processing or publishing Hubdoc receipts and bills.

FileKindSize
SKILL.mdskill md8.1 KB
references/downloading.mdmarkdown1.5 KB
references/duplicates.mdmarkdown5.1 KB
references/failed-tab.mdmarkdown2.3 KB
references/fields.mdmarkdown5.1 KB
references/review-process.mdmarkdown19.6 KB
references/searching.mdmarkdown2.5 KB
references/uploading.mdmarkdown2.5 KB

references/downloading.md

View on GitHub
# Downloading and reading Hubdoc PDFs

document and read the PDF directly.

Workflow:

1. Open the document in the normal Hubdoc UI.
2. Use `snapshot -i -C` and identify the `Download` link/button from the
   document action bar.
3. Prefer downloading to an explicit absolute path under the repository's
   `tmp/` directory.
4. Use the **working sequence** below:

```bash
agent-browser click @eN
agent-browser wait --download "$PWD/tmp/document.pdf"
```

Do **not** assume `agent-browser download @eN /path` will always yield a
readable flat file in Hubdoc. The verified reliable method for Hubdoc is the
click-plus-wait flow above.

5. **Immediately verify the artifact on disk.** Do not assume the success
   message means the file is readable at the requested path.
6. Inspect the saved path. In Hubdoc, the download may appear as a wrapper
   directory at the requested path containing the actual downloaded file.
7. Be aware that Hubdoc download behavior is inconsistent across documents:
   some downloads materialize as the wrapper directory above, while others
   report success but do not appear at the requested path. If that happens,
   stop assuming the download worked and fall back to the on-page screenshot /
   visible text for the current task unless the PDF is essential.
8. Read the resulting PDF content from the downloaded artifact when the file
   is actually present.

Do this instead of guessing route/date details from partial preview text.

## Searching for documents
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 implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall