The outline arrives before the design
You should get headings and one line each, not styled output. If the first thing you see is finished slide furniture, the step worth reviewing has been skipped.
The session knows what changed and why; the people approving it do not. Felo Slides turns findings the session already gathered into a slide-by-slide outline you can cut before anyone spends time on design.
cp -r felo-skills/felo-slides ~/.pi/agent/skills/Pi keeps a deliberately small core and asks you to extend it, so a skill is the intended way to add reach without adding tools to maintain.
Slide generation is an ordinary bundle, so it takes the same route as anything else on Pi. Mount it globally if you write reviews often, keep it project-scoped if you only need it for one migration.
~/.pi/agent/skills/GlobalEvery project on this machine. Put a bundle here once you have read it and want it everywhere.
~/.agents/skills/SharedThe folder other harnesses read too, so one clone serves Pi and whatever else you run.
.pi/skills/ProjectThis repository only, and only after you trust the project. The right place to evaluate a bundle you have not read yet.
pi install npm:@scope/pkgPackageA package's skills/ directory, kept versioned and updatable. The cleaner route once a bundle earns a permanent place.
pi --skill /path/to/felo-slidesYou get headings and one line of argument each. That is deliberately not a finished deck — it is the version you can cut, reorder, and disagree with before it becomes somebody's afternoon.
Because the outline is built from the session, every line on it can be traced back to the command or the file that produced it.
A deck generator that ignores your work will still produce plausible slides, so the checks are about provenance.
You should get headings and one line each, not styled output. If the first thing you see is finished slide furniture, the step worth reviewing has been skipped.
Pick a claim and ask which file or command it came from. A slide that cannot be traced is the slide that embarrasses you in the room.
If the session found nothing for a heading, the right output is a gap you can see. A plausible sentence filling the hole is worse than an empty slide.
The outline is useful before it is a deck, and it is worth deciding the destination first.
Paste the outline into the description so a reviewer reads the argument before the diff, and can point at the slide they disagree with.
Expand the accepted outline into slides once the argument stops moving. Designing before that means redesigning twice.
Keep the outline next to the code so the next session starts from the reasoning instead of reconstructing it from the diff.
A deck is only as strong as the evidence under it, and the outline is only as strong as the sources behind that.
Five skills written for Pi Coding Agent. 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 Pi 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.