Why Wikipedia + dassi
Wikipedia 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 Wikipedia
- Glossary building: Define terms and create context-aware explanations while you read.
- Flashcards for learning: Turn sections into Q/A cards to reinforce recall.
- Source-aware summaries: Create short briefs with key facts and links for later.
Quick start
- Open Wikipedia in Chrome.
- Open the dassi sidebar.
- Start with a safe workflow: summarize → propose → draft → review → act.
Prompt recipes (copy/paste)
- “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)
- “Generate 12 flashcards from this article and quiz me.” (from Any Article Becomes Flashcards)
- “Focus flashcards on definitions + key claims.” (from Any Article Becomes Flashcards)
- “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)
- “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.