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/searching.md
View on GitHub# Searching for documents
panel. This reveals several fields:
- **Has the Words** (`@e6` or similar) — free text search across document content
- **Date range** — From/Through date fields
- **Supplier** — filter by supplier name
- **Document type** — filter by type
```bash
# Open the advanced search panel
agent-browser snapshot -i
agent-browser click @e2 # click the search/magnifying glass button
agent-browser wait 1000
agent-browser snapshot -i # get refs for search fields
# Fill "Has the Words" and submit by pressing Enter
agent-browser fill @e6 "search term"
agent-browser press @e6 Enter # submit search (no Search button exists)
agent-browser wait 3000
```
The ref numbers may vary — use `snapshot -i` after opening the search panel
to identify the correct ref for the "Has the Words" field.
## Normal search vs ADVANCED search — they submit differently
**The advanced search panel HAS a Search button. Click it.**
| | Normal search (top search box) | Advanced search panel |
|---|---|---|
| Submit by | pressing `Enter` in the textbox | **clicking `button "Search"`** |
| Search button | none — there is no longer one | **exists, plainly labelled** |
Do NOT carry the "there is no Search button" fact over from the normal
search to the advanced panel — it applies ONLY to the normal search.
```bash
agent-browser click @e5 # magnifying glass -> advanced panel
agent-browser wait 2000
agent-browser snapshot -i -C # find BOTH the field AND the button
agent-browser fill @e6 "search term" # "Has the Words"
agent-browser scrollintoview @e16 # the Search button
agent-browser click @e16 # <- REQUIRED. Enter alone does nothing here.
agent-browser wait 4000
```
**Symptom of getting this wrong:** the term visibly appears in the "Has the
Words" textbox (a snapshot confirms `Has the Words: <your term>`) but the
document list never changes — it keeps showing the same unfiltered docs. That
is not a "no results" state and not a stale list; the query simply never ran.
**When snapshotting for the button, do not grep only for textboxes.** A grep
written for the expected field names will hide the Search button from you.
Grep for `button` and read what is actually there. Evidence (2026-07-17): two
searches were declared "not filtering", and the March doc wrongly suspected of
being absent, purely because `button "Search" [ref=e16]` was never looked for.
**Only once the search has actually RUN:** if no results appear in the
document list, the document is not in Hubdoc.
## Process
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 |