Videos
Share the link while you scroll. The tool someone demoed is what Sopie is after, not the clip.
The tool or technique shown, a short summary and a link back. The video stays where it was posted.
Share a Reel, a repo, a web page or a voice note. Sopie keeps one tidy entry per tool or technique, with every source linked, so your agents can read it later.
Whatever you share, Sopie reads it for the tool or technique inside. The colour stays with the source all the way to the entry.
Share the link while you scroll. The tool someone demoed is what Sopie is after, not the clip.
The tool or technique shown, a short summary and a link back. The video stays where it was posted.
Paste a repository link. Sopie reads what it is for and what it needs to run.
What the repo does, what it needs and a link to its README.
Save the page that has the trick in it, even when the trick is buried halfway down a long thread.
Just the trick, as a technique entry, joined to any tool it uses, with the page to check.
Say the idea out loud, on a walk or in the car. No typing, no tidying up afterwards.
The idea in plain words, linked to your note.
Four parts, every time. Pick one to see what it holds.
Screenshot diff testing
techniqueCompare a fresh screenshot with a saved one to catch visual changes before they ship.
Name and kind
Every entry is a tool or a technique. Tools are things you install or call. Techniques are ways of doing something. The name stays plain so your agent can match it to a question.
Summary
One or two sentences on what it is and what it is for. Not a transcript of the Reel, not a copy of the README.
Sources
Each source stays attached and keeps its colour, so you and your agent can always open the original Reel, repo, page or voice note. The clip itself stays where it was posted.
Relations
What it replaces, what it needs and what it pairs with. Your agent gets the neighbours, not just the match.
Saw the same tool in three places? Sopie joins each new source to the entry you already have, so you never end up with a pile of duplicates.
Same tool, many saves, one entry
ExamplePlaywright MCP
toolLets an agent drive a real browser: open pages, click, type and read what is on screen.
Same entry, one more source. No second copy.
Another Reel, a repo link or a voice note about a tool you already have.
It works out that the new source is about the same tool or technique.
One entry, one more source, one more dot. Nothing to tidy up later.
Not folders, not tags. Each entry says what it replaces, what it needs and what it pairs with.
Relations of one entry
ExamplePlaywright MCP tool
What this makes unnecessary, so your agent can suggest the better option instead of the old one.
What has to be in place first, so your agent knows before it starts.
What works well beside it, so your agent gets the neighbours, not just the match.
Fix it, remove it or take it with you. Nothing about your entries is locked in.
Rename an entry, reword the summary or change a relation whenever Sopie got it slightly wrong.
Remove a single entry, or everything, whenever you like. Your original posts are untouched.
Take any entry out as a plain SKILL.md file your agent can load. An open format, so it works without Sopie.
--- name: screenshot-diff-testing description: Spot visual changes. ---
Sopie isn't released yet. Join the waitlist and we will write to you when it is ready for you.