Felo Slides on QoderWorkQoderWork

The deck is a file on your machine. The argument in it still has to come from somewhere.

QoderWork already ships a pptx skill, so making the file was never the hard part. Felo Slides produces the outline from your own document and research, so what lands in the deck is the argument you actually wrote.

Built for QoderWorkOutline from your documentExports locally
Get an API keySee the platform guide

Felo Slides on QoderWork

01Install
Ask in the conversation
02Input
Your local document
03Comes back as
Slide-by-slide outline
04Then
The local pptx skill renders it
The install requestPlease download https://github.com/Felo-Inc/felo-skills/tree/main/felo-slides and put it in ~/.qoderwork/skills/, then confirm the skill is loaded.
QoderWork logo
This skill runs on

QoderWork

Desktop AI work assistant by Qoder

Read the QoderWork guide

QoderWork runs on your machine and edits local docx and pptx files. A Felo skill supplies the half a local file cannot: current sources, transcripts, and assets that land beside your document.

Platforms
macOS 14+, Windows 10+ (64-bit)
Skills live in
~/.qoderwork/skills/
Install by
Asking in the conversation
Add it on QoderWork

One request, and the folder is in place

The app handles the cloning and the placement itself. Your job is to describe the skill clearly enough that it lands in the right root, and to keep the list short afterwards.

You

Please download https://github.com/Felo-Inc/felo-skills/tree/main/felo-slides and put it in ~/.qoderwork/skills/, then confirm the skill is loaded.

QoderWork

Downloaded the repository and placed felo-slides in ~/.qoderwork/skills/felo-slides. The SKILL.md describes outline generation; the local pptx skill can render the result.

You

Build the outline from ~/Documents/q3-plan.md, six slides, and wait for me to approve the structure before exporting.

QoderWork

Outline ready. It follows the document's own headings and keeps the source list from the file. Nothing has been exported yet.

What ends up on disk

  • ~/.qoderwork/skills/felo-slides/Read it alongside the pptx skill you already have: this one produces the outline, that one produces the file.
  • ~/.qoderwork/skills/The root it matches from. QoderWork picks a skill by its description, so a short list makes the matching predictable rather than clever.
Then ask it to account for itselfWhich skill produced the outline, and which one will export the deck?
What you get back

The outline of the document, not a summary of its topic

Because the source is a file you wrote, the outline can follow your argument instead of a house template. It comes back as headings and one line each, and it lives as text until you approve the structure.

  1. 01

    What we are deciding

    The decision the document exists to support, stated in the words the file already uses.

  2. 02

    What the numbers say now

    The four figures that changed since the last review, with the source list behind them.

  3. 03

    What we assumed last time

    The two assumptions that no longer hold, named rather than quietly dropped.

  4. 04

    The options on the table

    Three choices, each with the cost of being wrong attached.

  5. 05

    What we recommend

    One recommendation, in the same terms as the document, so nobody has to translate.

  6. 06

    What we need from the room

    The decision, the owner, and the date it has to land by.

The deck and the document should not disagree. Building the outline from the file is what keeps the two versions of the argument identical.

Where it goes

Three destinations, all on your own machine

The unusual thing about a desktop assistant is that both the source and the output are files you can open.

Local deck

pptx

Rendered by the pptx skill once the outline stops moving, saved wherever your documents already live.

Source document

docx

Keep the outline inside the document it came from. The deck is a rendering of the argument; the argument belongs beside the notes.

Review pass

Tracked changes

A colleague editing the outline in the document produces a visible change. The same edit made during design produces a redesign.

The routine

Document to deck, without the two drifting apart

The failure mode is a deck that says something the document no longer does. The order below prevents it.

Runs when

A written document has been reviewed and somebody now wants it presented.

  1. 01

    Outline from the file, not from memory

    Point the request at the document. An outline written from a topic summary is a new argument, and it will contradict the one you already agreed.

  2. 02

    Fix the structure before the design

    Six headings and a line each. This is the last cheap moment to change your mind, and the first moment the argument is visible to other people.

  3. 03

    Export with the local pptx skill

    QoderWork already has the renderer. Keeping the two steps separate is what lets you regenerate the file after a wording change.

  4. 04

    Put the sources in the notes

    Whatever the document cited should survive into the deck's speaker notes, so the presenter can answer the first hard question.

Leaves behindA deck that matches the document it came from, with the sources still attached and the export repeatable.

In practice

Two requests that keep the deck tied to the file

The first produces the structure, the second the file. The gap between them is where review happens.

Type thisTurn ~/Documents/q3-plan.md into a six-slide outline and show me the structure before exporting anything.What comes back

An outline that follows your document's own logic, held at the reviewable stage.

Type thisThe market section changed. Regenerate the outline from the updated file and keep the rest of the deck as it was.What comes back

A targeted regeneration instead of a new deck, which is what makes a repeated export practical.

Where it stops

Three limits of a file-to-file workflow

Local files are inspectable, which also means their limits are visible and worth knowing.

The document is the ceiling

An outline built from a thin document is a thin deck. If the argument is not written down yet, write it first — the deck is not the place to discover it.

Two skills, two steps

Outline and export are separate skills here. Convenient, but it means the deck is only as current as the last export, so regenerate after edits rather than before.

Design is still a choice

The outline decides the argument, not the look. Expect to spend time on the template the first time and rarely after that.

FAQ

What QoderWork users ask about Felo Slides

Do I need this if I already have the pptx skill?
They do different jobs. The pptx skill renders a file; this one decides what the file should say, using your own document as the source. Most people end up using both.
Can it read a document I have not finished?
It can, but the outline will inherit the gaps. The useful order is to finish the argument in the document, then let the deck follow.
Where does the outline live afterwards?
Wherever you keep notes. Keeping it beside the document is what lets a later edit regenerate the deck rather than start over.
Does the export overwrite my existing deck?
Ask for the export path explicitly. Naming the output file is a small habit that prevents a surprise in a folder you share with other people.
More on QoderWork

Every Felo skill for QoderWork

Five skills written for QoderWork. They follow the same pattern on this platform, so you can combine them in one session without re-explaining your setup.

Beyond ready-made skills

One API key. A full agent toolkit.

Start with a skill, then compose the exact models, live data, knowledge, and output tools your QoderWork 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
Explore LLM API →

Live information

Give agents current web and social signals instead of relying on stale context.

  • Web Search
  • X Search
  • Web Fetch
Explore live data tools →

Knowledge and output

Ground work in reusable knowledge, then turn it into shareable deliverables.

  • LiveDoc
  • PPT generation
  • Mindmaps
Explore knowledge tools →

Creative tools

Extend the workflow from research to visual and office-ready results.

  • Image generation
  • Page tools
  • Office outputs
Explore platform tools →