Local deck
pptxRendered by the pptx skill once the outline stops moving, saved wherever your documents already live.
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.
Felo Slides on QoderWork
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 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.
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.
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.
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.
Build the outline from ~/Documents/q3-plan.md, six slides, and wait for me to approve the structure before exporting.
Outline ready. It follows the document's own headings and keeps the source list from the file. Nothing has been exported yet.
~/.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.Which skill produced the outline, and which one will export the deck?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.
The deck and the document should not disagree. Building the outline from the file is what keeps the two versions of the argument identical.
The unusual thing about a desktop assistant is that both the source and the output are files you can open.
Rendered by the pptx skill once the outline stops moving, saved wherever your documents already live.
Keep the outline inside the document it came from. The deck is a rendering of the argument; the argument belongs beside the notes.
A colleague editing the outline in the document produces a visible change. The same edit made during design produces a redesign.
The failure mode is a deck that says something the document no longer does. The order below prevents it.
A written document has been reviewed and somebody now wants it presented.
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.
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.
QoderWork already has the renderer. Keeping the two steps separate is what lets you regenerate the file after a wording change.
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.
The first produces the structure, the second the file. The gap between them is where review happens.
Turn ~/Documents/q3-plan.md into a six-slide outline and show me the structure before exporting anything.What comes backAn outline that follows your document's own logic, held at the reviewable stage.
The market section changed. Regenerate the outline from the updated file and keep the rest of the deck as it was.What comes backA targeted regeneration instead of a new deck, which is what makes a repeated export practical.
Local files are inspectable, which also means their limits are visible and worth knowing.
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.
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.
The outline decides the argument, not the look. Expect to spend time on the template the first time and rarely after that.
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.
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.
Use cost-efficient LLM access when your agent needs custom reasoning or generation.
Give agents current web and social signals instead of relying on stale context.
Ground work in reusable knowledge, then turn it into shareable deliverables.
Extend the workflow from research to visual and office-ready results.