Week 45, updated 2 Nov 2026

What can you do with AI?

30 practical jobs, each with the best-scored tools, prompts to copy and a workflow.

Use cases
30
Tools behind them
49
Audiences
5
Browse by jobnumber of use cases
  1. Coding agents14 tools, top: gemini-cli 708
  2. Agent skills & MCP9 tools, top: superpowers 624
  3. Automation & agent frameworks14 tools, top: n8n 706
  4. Research & web data6 tools, top: firecrawl 785
  5. RAG, knowledge & memory3 tools, top: ragflow 693
  6. Local AI5 tools, top: ollama 733
  7. Media & creative1 tool, top: remotion 431

Top 10 by public usage data

What people actually use AI for, from published studies. Ranked by cited evidence, not by our scores.

Points from cited studies2 per direct, 1 per indirect publisher
  1. 1AI pair programming in the terminalAnthropic, McKinsey, Stack Overflow6
  2. 2AI web research reports with sourcesMcKinsey, OpenAI; indirect: Stack Overflow5
  3. 3AI customer support botMcKinsey, Microsoft4
  4. 4AI debugging with an agentAnthropic, Stack Overflow4
  5. 5Business process automation with AI agentsMcKinsey, Microsoft4

Pick by who you are

All 30 use cases

Grouped by job. The number is the highest tool score for that use case.

Coding agents

Questions about AI use cases

What are AI use cases?

Concrete jobs you can do with AI tools, such as reviewing code, researching a topic, answering questions from your documents or running a model privately. Each page here explains the job, gives example prompts and a workflow, and lists the tools we track for it.

How are the tools on these pages chosen and ranked?

Only tools in our weekly dataset (52 tracked GitHub projects) appear. Each has a quality score from public signals (maintenance, adoption, docs) and a separate automated safety label. Scores are relative and nobody here tested the tools hands-on. See the methodology page.

Are the example prompts tested?

No. Prompts are labelled "Example prompt" because they are starting points we wrote, not results from a test run. A prompt would only be labelled tested after someone ran it and we recorded when and with what.

Does a green safety label mean a tool is safe?

No. It means our automated scan of dependencies and code patterns found no issues. It is not an audit. Give agents the least access they need and review what they do.

Can I use these tools at work?

Often yes, but check each licence and your organisation's data rules first. Every tool card shows its detected licence and last activity.

How we pick tools
  • Quality and safety, separately. Every tool has a relative quality score from public GitHub signals and an independent automated safety label.
  • Real data only. Scores, labels, licences and dates on these pages are computed from our weekly dataset, never typed by hand.
  • Honest limits. Nobody here tested the tools hands-on and example prompts are untested. Read the methodology.

Get the board every Monday

One email a week: the new top 10, the biggest score changes and every safety label that changed.

Free. Double opt-in: you confirm by email first, unsubscribe in one click.