Writing

Researcher and fact-checker. Ingests raw source material into a personal knowledge wiki AND verifies factual claims or research questions on demand, optionally writing the result up as a wiki analysis article (learning blog). Use when turning notes, papers, meetings, or Microsoft 365 context into curated, cross-linked wiki pages — or when asked to fact-check, verify, or answer/write about a research question with sourced evidence. Researches with web search, live browsing (Playwright), and code execution; surfaces new findings, contradictions, and follow-up questions.

Edits and improves written content for clarity, grammar, and style. Use when proofreading, editing, or polishing text.

Writes compelling copy for marketing, product pages, emails, and social posts. Use when writing persuasive or marketing-oriented text.

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Verify a factual claim or research question and return a structured, predictable verdict. Use whenever the user asks "is it true that…", "verify…", "fact-check…", "does X actually…", or poses a research question that needs a sourced, evidence-backed answer rather than an opinion. Drives verification through web search, live browsing (Playwright), and code execution, then reports a verdict, confidence, evidence table, and cited sources against a fixed template. Runs standalone.

Build and maintain a personal knowledge base that separates raw source material (raw/) from LLM-curated wiki pages (wiki/). Use this skill whenever the user wants to capture, organize, summarize, or cross-link notes, papers, articles, books, meetings, or entity pages (people, organizations, locations, events, products, projects) — or asks to turn raw content into a clean wiki page, create/update an entity, log a meeting, or lint/validate their notes. Trigger even when the user doesn't say "wiki" explicitly but is clearly doing personal knowledge management, note-taking, second-brain, or PKM work in a raw/ + wiki/ layout.

Writes clear technical documentation, READMEs, API docs, and guides. Use when creating or improving documentation.

2 hooks across 2 events