~/project/.dsh/skills/ProjectLoads for this repository only. The right place to read a bundle before you trust it with the whole machine.
The hard part of a review deck is not the design, it is remembering what you found three hours ago. Felo Slides builds the outline from the work the session just did, so the deck starts from evidence rather than a blank page.
cp -r felo-skills/felo-slides .dsh/skills/Open-source agent harness (developer preview)
dsh reads skills straight out of folders you point it at, so a Felo bundle is one copy away from being callable in a session — and one delete away from being gone.
You get headings and one line of argument per slide. That is deliberately not a finished deck — it is the version you can cut, reorder, and disagree with while changes are still cheap.
Because the outline comes from the session, every claim on it can be traced back to the command or file that produced it.
Slide generation is a normal Felo bundle, so it mounts the same way. Nothing about deck output needs a different root or a longer setup.
~/project/.dsh/skills/ProjectLoads for this repository only. The right place to read a bundle before you trust it with the whole machine.
~/.agents/skills/UserLoads in every project, and is the same folder other harnesses on this machine look at.
mkdir -p .dsh/skills
cp -r felo-skills/felo-slides .dsh/skills/List the skills you can call from this project.The outline is only as good as the session behind it. These two prompts work because the work has already happened.
Turn the last hour of this session into a six-slide review: what we changed, what we measured, what we still do not know.What comes backAn outline whose slides map onto work that actually happened, so you spend your time editing rather than remembering.
Draft the same review for a non-engineering audience. Drop the implementation detail and keep the trade-offs.What comes backA second outline at a different altitude, which is usually faster than rewriting the first one by hand.
Being clear about this is why the deck is usable. Everything the skill does not do is something you should keep owning.
The outline reflects what the session found. If the session found the wrong thing, the deck is wrong in a tidy, well-spaced way.
Brand templates and slide masters are applied at export. Bring your own, or the deck will look generic in a way everyone recognises.
A six-slide deck and a twenty-slide deck are both one prompt away. Deciding which one the meeting needs is still your job.
Slides are the last step. These two are the ones that fill it in.
Five skills written for DeepSeek Harness. 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 dsh 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.