Think of Zero as a junior-to-mid teammate who never sleeps and already has all your tools authorized. Anything a person could do by combining your inbox, your repos, your dashboards, and your docs — Zero can do, and produce a real artifact at the end.

The categories below are the ten kinds of work that come up most. None of them require setup beyond connecting the right tools; all of them can become skills or run on a schedule.

Research

You need context on a person, company, market, or competitor — fast, with sources.

Account briefs before a sales call (funding, recent news, prior conversations from CRM/email)
Competitor scans — weekly cadence or on-demand, diff against last week's baseline
Customer intel: pull every touchpoint across CRM, support, and email into a single brief
Literature review of internal Notion + public docs on a topic
Market sizing using public sources, with the math shown

"Brief me on Acme Corp before my 3 p.m. — funding history, last 30 days of news, who at our company has emailed them, and any open support tickets. Cite every claim."

What you get back: a 300–500-word brief with inline links, organized by section, ready to skim before a call.

Reports & briefings

The recurring "what happened" write-up: daily, weekly, monthly. Same shape every time, fresh content.

Morning brief: inbox + Slack mentions + calendar + open PRs
Weekly metrics digest for engineering, marketing, finance, or support
Status update synthesizing issue tracker + Slack threads + commits
Incident retros from logs and timeline
Investor updates from a structured prompt + dashboard data

"Every Monday at 9 a.m., summarize last week's merged GitHub PRs grouped by team. Post to #eng-weekly."

What you get back: a structured digest sized for the channel — short for Slack, longer for email. Numbers compare to the prior period; surprises are called out.

Written content

Drafts that match a brand voice or a personal voice, edited and ready to ship.

Blog posts and long-form articles from an outline or research brief
Marketing emails, lifecycle nurture, and broadcast campaigns
LinkedIn / X / Threads posts in your voice
Internal memos, all-hands notes, decision records
Translations (EN ↔ ZH / JA / KO) preserving tone

"Take this Notion doc and turn it into a LinkedIn post in my voice — four short paragraphs, no hashtags, ending with one open question."

What you get back: a draft ready to post, with two-to-three variant options if you ask for them.

Presentations & decks

Slides for pitches, reviews, all-hands, and conference talks — generated from an outline or a raw doc.

Pitch decks for fundraising, sales, or board reviews
All-hands updates from the prior month's Notion changelog
Conference talks expanded from a draft outline
Internal training decks from KB articles

"Build a 12-slide pitch deck for Acme Corp using our standard template — pull two relevant case studies from Notion and a logo wall of customers in their industry."

What you get back: a sharable Gamma or Google Slides deck, with placeholders flagged where you need to make a final call.

Websites & landing pages

Microsites and one-off pages for launches, events, and internal tools.

Launch landing pages with hero / features / pricing / CTA
Event microsites with RSVP, speaker bios, agenda
Internal hub pages (onboarding, runbooks, dashboards)
One-off interactive demos for a feature in progress

"Spin up a landing page for the Spring launch with three sections — hero, feature grid, pricing — using the brand colors from our marketing site."

What you get back: a deployed page URL you can share immediately, plus the source ready to edit further.

Images & illustrations

Brand-consistent visuals for posts, blog headers, cards, and internal use.

Social cards announcing features, launches, hires, milestones
Blog headers and section illustrations
Editorial illustrations in a fixed brand style (consistent across a series)
Product mockups and reference screenshots
Diagrams (architecture, flowcharts) generated from a prose description

"Make four social cards announcing the new Slack channel feature — square, brand palette, hand-drawn ink style, one creature per card."

What you get back: a set of images delivered inline, ready to download. Re-run with a tweaked prompt as needed.

Video & audio

Short-form video and audio for product updates, training, and marketing.

Product demo videos with screen recording + voiceover
AI-avatar talking-head clips for launches and updates
Audio explainer narration in multiple languages
Podcast outlines and show notes
Auto-transcribed meeting summaries

"Turn this product changelog into a 60-second demo video with my avatar narrating and screen recordings inline."

What you get back: a final MP4 (or MP3 for audio) in your workspace files, ready to share or embed.

Code & PRs

Focused, scoped engineering tasks — not "write me the app," but the kind of work a junior engineer would handle in an hour.

Issue triage with reproduction steps and severity classification
Small, well-scoped fixes against named bugs
PR reviews focused on a specific concern (security, perf, naming)
Documentation updates and code-aligned README edits
Tests for an existing function or endpoint

"Review PR #4422 for SQL injection risk only — skip style, naming, and architecture. Post findings as a PR comment."

What you get back: an opened PR or a posted review comment, with reasoning visible in the session log.

Triage

Inbound work — emails, tickets, bug reports, alerts — sorted, labelled, and partially handled.

Inbox processing: archive newsletters, label by sender, draft urgent replies
Bug report classification with auto-filing to the right team
Support ticket batching by severity, customer tier, or topic
Alert summarization across PagerDuty + Sentry + Slack

"Every evening at 6 p.m., archive marketing newsletters, label personal mail, and draft a reply to anything from a customer."

What you get back: an inbox that's ready to act on in the morning, plus a short note about what Zero handled.

Operations

The glue work: reconciling systems, running checks, posting digests, filling forms.

Recurring health checks against dashboards or APIs, with paging on anomalies
Reconciling records between two systems (CRM ↔ billing, Linear ↔ GitHub)
Posting reminders and follow-ups on schedule
Form-filling and data entry from a structured input
Audit prep — pulling evidence from logs for a control

"Every 30 minutes, query the production health dashboard. If error rate is above 1%, page on-call via PagerDuty."

What you get back: a quiet workflow that does its job without your attention — and pings you only when something's wrong.

How to use this list

Every category above can run three ways:

One-off. Type the prompt in chat. Useful for trying something new or one-time work.
Skill. Save the workflow under a name your team can call later. Use when the same shape of work recurs.
Schedule. Run it on a cadence. Use when the work needs to happen even if no one asks.

For end-to-end walkthroughs of four full workflows, see Example workflows.