Why Google Search + dassi
Google Search is already where the work happens. dassi adds the missing layer: it can read what’s on the page and then take actions (draft, classify, fill, log, summarize) without you rebuilding context in a chat box.
What to automate in Google Search
- SERP → research brief: Open top results, extract key points, and produce a structured brief with citations.
- Inline claim checking: Cross-check claims you encounter and add trustworthy references.
- Product comparison scouting: Compare options found via search and generate a decision table.
Quick start
- Open Google Search in Chrome.
- Open the dassi sidebar.
- Start with a safe workflow: summarize → propose → draft → review → act.
Prompt recipes (copy/paste)
- “Fact-check the numeric claims in this article and add sources.” (from News Article With Inline Fact-Check Annotations)
- “Flag any misleading comparisons or missing baselines.” (from News Article With Inline Fact-Check Annotations)
- “Pin this product. Build a comparison table for the pinned items.” (from Side-by-Side Product Comparison, Built on the Fly)
- “Highlight which one is best for gaming vs. office work.” (from Side-by-Side Product Comparison, Built on the Fly)
- “Define the key terms in this paper in context, inline.” (from Academic Paper With Inline Jargon Definitions)
- “Build a glossary of the top 15 terms used here.” (from Academic Paper With Inline Jargon Definitions)
- “Summarize what’s on screen and propose next actions.”
- “Do the safe part first (draft / label / preview), then ask me before any irreversible action.”
- “Turn this page into a clean checklist I can follow.”
Safety checklist
- Tell dassi: “Never submit/send without confirmation.”
- If the page contains sensitive data, ask for redaction or aggregated outputs (totals-only, no PII).
- Prefer reversible actions first (drafting, labeling, notes) before destructive ones.