Pi Coding AgentA small core is a feature until the task depends on something that shipped last week. Felo Search hands the session dated answers with the page each claim came from, so an upgrade decision rests on the vendor's notes instead of a remembered API.
Felo Search on Pi
pi --skill /path/to/felo-searchPi 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.
The value of search inside a harness is not more text, it is that each claim can be checked. The dates matter as much as the links: a changelog entry from five days ago describes the version you are about to run, one from last year does not.
Put the requirement in the prompt rather than hoping for it: "cite a source and a date for every item, and mark anything you could not verify."
Both of these depend on something outside the working tree, and both come back checkable once the bundle is mounted.
We just bumped the driver to 3.x. List only the changes that touch anything under src/db/, and cite each one.What comes backA short list pointing at migration notes and release entries, with the changes that only affect code you do not have left out.
Is the retry behaviour that broke our wrapper a known issue in this version? Show me where you read that.What comes backThe issue thread or changelog entry next to what your own file does, so you can see whether the two actually match.
Add it on PiThere is nothing to compile and no registry account to create. The only decision is which root the bundle belongs in — and Pi's own rule is that project skills stay dormant until you trust the project.
~/.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-search
# additive even when you start with --no-skillsThis is the shape that works on Pi: narrow the question to a version, then force the answer to name its evidence.
A version in the lockfile moved, or is about to, and the changelog is longer than the time you have.
Read the installed version out of the lockfile first, then ask about that release and the ones after it. Asking about "the latest" gets you an answer about a version you are not running.
An unsourced claim about a library is a guess with good grammar. The dates let you throw away anything older than the release you are on.
Ask which of the changes touch paths the session can see in this repository. That is what turns a changelog into a to-do list.
Pi sessions do not share memory, so write the result into the repository — a note file, a comment, a commit message. A finding that lives only in scrollback is gone.
Leaves behindA filtered list of changes that affect this repository, each with a link and a date, plus an explicit note about what could not be verified.
Knowing the edge makes the answers easier to trust inside the part where they hold.
Search tells you what the vendor shipped. Whether that breaks your module is a code question, and it is worth asking as one, against the files in front of the session.
A dated changelog entry is strong evidence; a forum reply is a lead. The dates make the difference visible so you can weigh them instead of treating every link as equal.
The skill runs when the session decides a task needs current information. A refactor that never asks about the outside world costs nothing and stays offline.
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.
Felo Slides
Felo YouTube Subtitling
Felo X Search
Felo SuperAgent