The skill sync that lands in staging
A MIT app that writes a different skill copy per machine, and leaves the live folder alone until you say so.
- Category
- Developer tools
- Who it is for
- A person who keeps skills for both Claude Code and Codex.
- Possible model
- Open source
- Difficulty
- Medium
- Inspired by
- Ratatoskr · Ratatoskr
- Original launch
- Watch the launch · Oct 22, 2026
Difficulty is an editorial estimate of technical and operational complexity, not a score.
Startup idea analysis by Startup Ideas. Last reviewed Oct 22, 2026. How we read a launch.
The startup idea
Oana posted Ratatoskr on October 22. She uses Codex and Claude Code, and keeping their skills in sync is the problem. Machines differ. Some skills should not be on every one. Free and open source. The repository is oana-ffg/ratatoskr-skill-sync. The readme says MIT, and the app is pre-1.0. One Git source renders a tailored copy for each machine, OS, and agent. Identical copies are not good enough. A new profile writes to a staging folder, so the real agent folders stay untouched until you switch to live. Sync refuses a dirty, diverged, or wrong-branch checkout instead of guessing. The download table is macOS, Apple Silicon and Intel, and Windows x64. Updates are signed, but Apple notarization and Microsoft publisher signing are not configured, so the first open can warn. The post says different operating systems. The app you download is two of them. This page did not sync a folder.
The opportunity is one skill that is allowed to differ per machine. A smaller product is staging on, a live switch you make yourself, and a refusal when git is dirty. Overwriting the agent's real folder on the first run is the failure the readme already avoids.
Do not say there is a Linux app. The table does not list one. Do not hide the first-open warning.
The problem
Claude Code and Codex want different instructions, and the machines are not the same.
Who would pay for this?
- Primary
- A person who keeps skills for both Claude Code and Codex.
- Secondary
- Someone with more than one Mac or a Windows machine, who uses git.
- Early adopter
- One skill in staging, then a live switch after a look.
How could it make money?
Possible models. Nothing here is a claim about what Ratatoskr charges.
- No price. MIT.
- Pre-1.0.
- The post does not name a team plan.
What would the MVP look like?
- One content repo and one machine profile.
- A staging folder, not the live agent folder.
- A refusal on a dirty checkout.
- The notarization warning.
How to validate the idea
- Ask five people whether the first sync changed the agent's real folder.
- If it did, staging was off.
- Do not call two identical files a success. The readme says they should be able to differ.
How to differentiate
- The copy is rendered per agent and per machine.
- Live is a second step.
- A dirty git tree stops the sync.
- Do not become the agent.
Original product launch
This launch is inspiration and evidence that someone shipped, not a partnership. The idea above is our reading of the broader opportunity. Ratatoskr did not write it.
- Product
- Ratatoskr
- Source
- Ratatoskr
- Film
- Ratatoskr, the first copy is staging
- Posted
- Oct 22, 2026 · 1:11
Product that inspired this idea
Oana's post says keeping Codex and Claude Code skills in sync is the hard part, across machines and operating systems. She built Ratatoskr. Free and open source. The readme says MIT, and it is pre-1.0. One Git source renders a different copy for each machine, OS, and agent. Identical copies are not the point. A new machine writes to a staging folder, so the real agent folders stay untouched until you switch to live. A sync refuses a dirty, diverged, or wrong-branch checkout. The downloads are macOS and Windows. Apple notarization and Microsoft publisher signing are not configured, so the first open can warn. The post does not say the live folders stay untouched, or that Linux is not a download. This page did not sync a skill.
Posted by @OanaGoge. Watch the original launch. No separate product site is listed unless the post itself is the source.
- agents
- sync
Related startup ideas
- A drive that files the document and cites the page
Upload a pile of files, have them land in a folder a person would recognize, and answer a question with the page it came from.
- A visible team of agents in a world you can walk into
Use a shared world, not a log file, when several agents need a person to come over and decide.
- An Android remote for coding agents
A phone client for checking projects and steering agents when the laptop is closed.
- An inbox so the agents stay quiet
Collapse every coding-agent thread into one list, and only interrupt when one of them is stuck.
- Coding agents in the menu bar
Show which coding session is working, which is stuck, and let a person reply without opening the app.
- Cut the launch film from the app you already have
A skill that rebuilds the screens in a frame, times them to a track, and renders on the machine the coding agent already uses.
Looking for more ideas?
The full list is startup ideas for 2026, each one tied to a launch you can watch.
Browse startup ideas for 2026