Get the transcript of this talk and list every benchmark number it quotes, with the timestamp for each.What comes backA short table of figures, each linked to the minute it was said, so you can jump straight to the claim.
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.
What comes back is text the session can search, quote, and disagree with. The timestamps are what make it useful later: a quotation without one cannot be verified by anyone, including you.
We moved the scheduler off the monolith in the spring, and the first thing we lost was the retry budget.
The p99 did not move at all. What moved was the time we spent waiting on the queue.
So the win was operational rather than a latency win.
Exactly. Six weeks of work to make an incident stop happening every quarter.
If you take one number away from this talk: fourteen pages a quarter became two.
The p99 did not move at all. What moved was the time we spent waiting on the queue.
The order matters: get the text first, decide what matters second, and write it down third.
Someone sends a recording and the useful part is somewhere past the first ten minutes.
A summary drops the numbers and the hedges, which are usually the reason you are watching. Get the timestamped lines and decide what matters yourself.
Ask for every sentence containing a figure, a version, or a date. Once the captions are text, this is a text task — which is exactly the kind of task a small harness is good at.
One that carries the argument and one that names the limit. Keep the timestamps attached; a quote without one cannot be checked.
A transcript that lives only in this session disappears with it. Write the relevant lines into the repository next to the work they justify.
Leaves behindTimestamped lines you can search, the quotes worth repeating, and a note of which claims the speaker never supported.
Nothing about captions needs a special root. The one Pi-specific habit worth keeping is reading the bundle before it goes global, because a skill that reaches the network deserves a look.
~/.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-youtube-subtitlingBoth assume the video is a source rather than entertainment, and both end with something checkable.
Get the transcript of this talk and list every benchmark number it quotes, with the timestamp for each.What comes backA short table of figures, each linked to the minute it was said, so you can jump straight to the claim.
Does this recording say how they handled a rollback? Quote the answer with its timestamp.What comes backThe relevant lines with timestamps — or a plain statement that the topic never came up, which is also an answer.
Transcripts are evidence with known failure modes, and they are cheap to check.
Auto-generated captions mangle names and numbers. If a figure is going into a decision, check it against the recording before you repeat it anywhere that matters.
A recording without subtitles gives the skill nothing to fetch. That is a source problem, not something a longer prompt will fix.
The transcript says what was said, not whether the speaker's situation resembles yours. The skill removes the watching, not the judgement.
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.