What counts as a change
Without a rule, every cosmetic edit is news. Define the threshold — a price change, a policy date, a new competitor entry — or the report will be long and unread.
Felo SuperAgent on WorkBuddy
WorkBuddy
WorkBuddyThe Monday brief that builds itself
Recurring reporting is the work nobody has time for and everybody needs. SuperAgent keeps the job on a canvas between runs, so each week it adds to what it already knows instead of starting from a blank document.
Felo SuperAgent on WorkBuddy
- 01Arrives as
- An uploaded package
- 02Runs on
- A persistent canvas
- 03Repeats
- On the schedule you set
- 04Reports
- Only what changed
No terminal needed
Skills → Add skill → Upload skill → felo-superagentWorkBuddy runs a bench of specialists on your desktop, in WeChat and WeCom. Skills arrive as packages with a permission list, so research becomes a capability the whole bench can call.
- Runs on
- Desktop, WeChat, WeCom, QQ, mini program
- Skills arrive by
- Package upload, with permissions listed
- Fits
- Founders, research and operations teams
A recurring job you can inspect stage by stage
The reason to trust a standing report is being able to see how this week's version was built, and which step is waiting on a person.
- Running
Collecting
Reads the sources agreed at setup and writes each finding to the canvas with its date.
- Running
Comparing
Diffs against last week's canvas, so the report leads with what moved rather than restating everything.
- Blocked
Needs a decision
A source changed the way it publishes. It asks whether to keep using it before silently switching.
- Done
Draft ready
Leaves a one-page draft in your workspace with the source list and the open questions attached.
Three things to decide at setup
Recurring work goes wrong slowly. These are the decisions that keep a standing report from becoming noise.
What happens when a source dies
Pages move and feeds break. Decide now whether the run should stop, substitute, or report the failure. Silence is the one option that looks like good news and is not.
When the job ends
Standing jobs outlive the project that justified them. Give it a review date, so a report nobody reads gets switched off instead of accumulating.
Add it on WorkBuddyImport it, then set the boundary before the schedule
A recurring skill is the one where the permissions conversation actually matters. Decide the cadence and the stopping condition at install time, not after the first month.
- 01
Take the skill folder
Get the felo-superagent folder from the repository. The manifest lists what a long-running job needs to keep its canvas.
- 02
Import under Skills
Skills → Add skill → Upload skill. Check that it asks for a standing canvas and network access, and nothing about sending messages.
- 03
Write the cadence into the first request
State the schedule, the sources, the output format, and what should happen when a source is unavailable. This is the one skill where the first prompt is really a contract.
Then check the first two runs closely
Every Monday at 8:00, research what changed in this market,
report only the changes, and list the sources you used.Reading the first three runs
The first runs tell you whether the boundary was written tightly enough.
Run two must know about run one
If the second report reads like a fresh summary, the canvas is not being used and you are paying for a search every week.
The failure path must be honest
Break a source on purpose. The run should say so rather than quietly produce a thinner report from old data.
The format must stay put
Readers notice when a familiar document changes shape. If the format drifted, say so plainly in the next request.
Standing jobs that suit a workspace
The best first run is something you already produce on a schedule by hand.
Produce a weekly competitor brief every Monday. Report only what changed, with a link for each item.What comes backA Monday document that is short in a quiet week and visibly short, which is itself information.
Keep track of the standards consultation. Tell me when the comment period closes and what changed since the last review.What comes backA quiet watch that speaks up only when there is a date worth acting on.
Feed the standing job
A recurring report is only as good as the sources it was given.
What WorkBuddy users ask about recurring work
Does it run when nobody is at the desk?
The job lives on the canvas, so it does not depend on your machine being awake. The draft is waiting in the workspace when you next open it.
Will it tell me when nothing happened?
It should, and that is worth asking for explicitly. A short report confirming no change is more useful than a padded one, and it stops the pattern of the reader skimming past a quiet week.
How do I stop it?
Turn the skill off in WorkBuddy and stop the run on the canvas. Because the output is a document rather than a live dashboard, stopping it does not take anything else down.
Every Felo skill for WorkBuddy
Five skills written for WorkBuddy. They follow the same pattern on this platform, so you can combine them in one session without re-explaining your setup.
Felo Search
Felo Slides
Felo YouTube Subtitling
Felo X SearchOne API key. A full agent toolkit.
Start with a skill, then compose the exact models, live data, knowledge, and output tools your WorkBuddy workflow needs — the same key every Felo skill already uses.
Models
Use cost-efficient LLM access when your agent needs custom reasoning or generation.
- LLM API
- Chat completions
- Model access
Live information
Give agents current web and social signals instead of relying on stale context.
- Web Search
- X Search
- Web Fetch
Knowledge and output
Ground work in reusable knowledge, then turn it into shareable deliverables.
- LiveDoc
- PPT generation
- Mindmaps
Creative tools
Extend the workflow from research to visual and office-ready results.
- Image generation
- Page tools
- Office outputs