brianbolze
- 14 skills
- 0 followers
- 6 hours ago last updated
- ▌ Drift Sweep · brianbolzeCatch drift after a change to the web-research engine. Run it once you've edited a contract, script, or doc and want to know what went stale: the deterministic gate (linters + tests + checks) first, then a quick doc-staleness pass scoped to what changed. Trigger on "/drift-sweep", "sweep for drift", "check the repo for staleness", "did my change break any pointers/docs", "drift check after my edits". An explicit maintenance verb for THIS engine — not for capturing or querying companies, and it never auto-fixes (it proposes). Use after engine edits; skip for company captures/queries.
- ▌ Query Companies · brianbolze bundleUse for named-company comparison or lookup prompts that can be answered from the local web-research company store, especially pricing, offerings, ownership, catalog breadth, cohort cuts, price-visibility, and broad single-company briefs: "tell me about X", "compare X and Y", "what do these competitors charge / offer", "which brands sell <thing>", "who owns X", "is X in the web-research store", "what has the store captured on X". Answers are captured-state snapshots from cited primary-source dossiers instead of WebSearch. Do not browse, WebSearch, curl, or open live company pages just to verify; resolve with store.py find, answer from store files, and cite local paths plus governing capture clocks. Read-only: never scrapes, never spends. If current/latest or missing/stale capture is required, suggest /research-company refresh; for incomplete rosters suggest /deepen-offerings; for external signals use tools/. Not for general web search, news/funding events, financials, judgments, or non-company topics.
- ▌ Visual Evidence · brianbolze bundleMine an already-captured company's screenshots into a blind, cited visual-evidence layer at store/<domain>/visual.md — falsifiable cards across typography / layout / color-brand-imagery / iconography, plus a ~5-second Visual & brand impression. Use when the user wants a visual-quality read, a brand/design impression, or "how good does X's site look" from captured screenshots: "/visual-evidence acme.com", "visual evidence for X", "mine X's design", "what's my read on X's site". Reads cached captures (Tier-A) and re-renders contaminated pages in a real browser (Tier-B); zero Firecrawl spend. It emits observable visual STATE — evidence + impression — and never a score, quality field, or ranking (that layer is parked). Runs on a company already in the store; if there's no capture yet, capture it first with /research-company.
- ▌ Deepen Offerings · brianbolzeRe-capture one company to make its offerings.md roster comprehensive — drive it to "complete at the indexed level" across ALL product lines, pulling in any line or subdomain a prior run left out of scope. Use when a roster looks incomplete: "deepen offerings for X", "enumerate more of X's catalog", "/deepen-offerings henrymeds", "make X's offerings comprehensive", "X's roster is missing SKUs". Takes any company form (slug / domain / name). A focused preset of research-company; it spends Firecrawl.
- ▌ Research Company · brianbolze bundleCapture a single company's website into the web-research store as a structured, cited dossier (store/<domain>/profile.md) using Firecrawl. Use whenever the user wants to capture or re-capture a company from its website — "research company X", "/research-company acme.com", "capture acme into the store", "profile this competitor", "add X to the company store". One company at a time, keyed by canonical domain. It captures durable STATE (what the company is/sells/how it's positioned, from its own site) — not events (news/funding/M&A) or judgments (threat/fit/relevance), which belong to downstream consumers. NOT for answering questions from already-captured data — "tell me about X", "what does X charge" — that's /query-companies; if a warm fresh capture exists, this verb stops and hands off there instead of presenting the dossier. Only stale/new companies spend Firecrawl credits.
- ▌
- ▌
- ▌ Review Change · brianbolzeUse when asked to review a new incoming change or PR in this Web Research / Truffle project.
- ▌
- ▌ Market Read Lab · brianbolze bundleUse when starting, scaffolding, running, reviewing, or running autonomous Market Read Lab cycles in this Web Research / Truffle project. Handles numbered run folders, Scout/Read/Review gates, repo templates, the append-only learning stream, and the no-auto-graduation convention.
- ▌ Agent Build Decide · brianbolzeSynthesize one Agentic Build change packet into a short decision surface for Brian and recommend a call. Brian decides — this verb does NOT decide, merge, or edit the packet's work. Use when explicitly asked to run agent-build-decide, or to turn a reviewed packet into Brian's decision surface. NOT the independent critique (that's agent-build-review).
- ▌
- ▌ Agent Build Propose · brianbolze bundleCreate or revise a review-ready Agentic Build proposal.md for one Truffle change packet. Use when explicitly asked to run agent-build-propose or draft an Agentic Build proposal; stop before implementation.
- ▌