Use cases
Build real things, one recipe at a time
Each use case is a complete recipe: the job, the APIs, the order to call them, and the code. Copy it as a prompt for your AI, or run the steps yourself. Start with the one closest to what you are building.
Every use case copies as one prompt — setup, recipe, and safety rules included.
- recipes
- 16 recipes
- APIs covered
- 8 APIs covered
- code blocks
- 77 code blocks
How to use a use case
- 01
Pick the outcome
Choose the result you need — a sourced brief, a slide deck, a daily digest, a grounded support answer.
- 02
Copy the prompt
Each use case copies as one prompt: the full recipe, the setup steps, and the safety rules. No terminal commands to learn.
- 03
Paste into your AI
Claude Code, Codex, or any AI with terminal access installs the Felo skill, configures the key, and runs the recipe. You approve the plan before credits are spent.
For teams
Start from your team's page
Pick the team closest to your work. Each page collects the workflows that team runs most often, with the roles and sources already mapped.
Founders & operators
Research a market, size a decision, and get a first draft before the team exists.
5 workflowsMarketing & content
Turn research, social chatter and source material into campaigns, briefs, and pages.
10 workflowsSales & partnerships
Walk into a conversation with sourced context, a competitor angle, and a clear next step.
4 workflowsSupport & success
Answer from your own docs, triage the queue, and keep the knowledge base current.
3 workflowsCommerce & product
Check demand, compare competing stores, and validate a product before you commit stock.
2 workflowsBuilders & platform
Wire Felo into an agent or product, keep model spend visible, and ship a reviewable flow.
1 workflowsAll use cases
Grouped by the job to be done. Every recipe is self-contained.
Research6
Questions that need sources, not guesses.
Turn one question into a sourced research brief
Ask the web, pull the pages behind the answer as Markdown, add what X is saying, then keep the evidence in a LiveDoc you can query again later.
For Founders & operators · Market researchers +1
Build a competitor teardown your sales team can use
Collect a competitor's own pages, the coverage around them, and what buyers say on X, then assemble a teardown where every claim carries a source, a date, and a status.
For Product marketers · Competitive intelligence +1
Turn a market question into a go-to-market brief
Ask the market a precise question, read the category and pricing pages behind the answer, collect how buyers describe the problem on X, then save a GTM brief with sourced claims and open questions.
For Founders & operators · Product marketers +1
Research a product niche before you stock it
Source the category context, capture competitor pages on a stated date, read what buyers complain about on X, then keep the evidence and the memo in one LiveDoc you can revisit before ordering inventory.
For Ecommerce operators · Product researchers +1
Turn one search query into an SEO content brief
See which pages currently answer a query, read them as Markdown, map the questions they answer and miss, then write a brief your writer can outline from.
For Content marketers · SEO specialists +1
Research a target account before your first outreach
Read the company's own site, recent coverage, and what they post publicly, then write an account brief with recent moves, likely priorities, conversation starters, and honest unknowns.
For Founders & operators · Account executives +1
Content6
Turn source material into something publishable.
Ship a daily AI news digest your team actually reads
Get a sourced roundup, add what practitioners are posting on X, pull one video transcript, then compose the issue in Markdown and archive it in a LiveDoc.
For Marketing & growth · Creators +1
Turn social chatter into a weekly listening brief
Search the last week of X posts about your brand and competitors, add the sourced web context, read the pages behind it, and archive each brief so next week starts from what you already know.
For Brand & comms teams · Product marketers +1
Turn a YouTube video into a publishable article
Pull the timestamped transcript, shape it into readable blocks, outline and draft with a model you control, then leave the result in a LiveDoc for review.
For Content teams · Newsletter writers +1
Fill a month of content from the questions your audience asks
Map the themes around a topic with Chat, find the questions your audience asks on X, pull one reference video transcript for a real angle, then compose a four-week calendar where every row names its evidence.
For Content leads · Social media managers +1
Turn a product brief into a landing page
Research the audience, keep the brief in a LiveDoc, then create a Landing Page task from that context and poll until the hosted page is ready.
For Founders · Product marketers +1
Make a motion-graphics video with HTML and Opus 5.5
Write a beat sheet, have Opus 5.5 write one deterministic HTML scene through the Felo API, then capture frames with Playwright and encode an MP4 with ffmpeg. Run it inside WorkBuddy, ChatGPT with code execution, Codex, Pi Agent, or Claude Code.
For Creators · Motion designers +1
Office1
Deliverables your team already asks for.
Support2
Answers grounded in your own knowledge.
Answer support questions from your own documentation
Create a LiveDoc, load your help center and internal runbook, retrieve the passages that answer the ticket, and let a model answer only from that evidence.
For Support teams · Success teams +1
Triage a support ticket into a grounded reply draft
Redact the ticket, classify intent and priority with Chat, retrieve the passages that answer it from your documentation, check for public incident chatter, then leave a routed reply draft for a human to approve.
For Support leads · Helpdesk agents +1
Cost1
Keep model spend predictable as usage grows.
Start with the recipe closest to what you are building
Every recipe runs on the same key. Create one, top up from $1, and swap the example input for your own.