What people try before a skill router

Three fixes people reach for

If your agent has started ignoring the instructions you wrote, or the skills you installed just sit there unused, there is a small set of things people actually try. Not because imagination is short. The problem only offers so many angles, and most people work through all three before anyone tells them there is a fourth option: giving up on fixing it at all.

None of the three is a bad instinct. Each one buys something real. None of them holds.

Install a bigger directory

The first move is often to go looking for more. A bigger list of plugins, a directory with more skills than the one you already had. It feels like progress, because you now have more capability sitting on disk than you did an hour ago.

Every skill and plugin directory, including the honest ones, does the same job: it gets a file onto your machine and stops there. Browsing a second or third directory does not change whether the model remembers, three prompts into a task, that the file exists and is relevant right now. It just means you now have more idle files instead of fewer. The install command was never the hard part.

Write a louder CLAUDE.md

The second move is to fix the instructions themselves. Capital letters. The word "IMPORTANT" in front of the rule that keeps getting broken. The same line repeated near the top of the file and again near the bottom, in case the model only reads the end.

This is close to the most common complaint on record about coding agents. A Hacker News thread's title reads almost word for word "Claude often ignores CLAUDE.md," and the same sentence shows up on r/ClaudeAI and r/ClaudeCode in different phrasing: it forgets what you told it after a while, the agent goes wild and does its own thing. Making the instruction louder treats this as an attention problem. Published measurements of instruction compliance suggest it is closer to a memory problem: compliance runs near 95 percent early in a session and drops toward 20 to 60 percent by message six to ten, and that pattern shows up across tools, not one vendor. A louder sentence read once at the start of a session is still read once. It does not get more durable by getting more emphatic.

Say it again yourself

The third move, once the file stops being enough on its own, is to stop trusting the file and start doing the reminding by hand. You repeat the constraint in the prompt. You paste the relevant instructions back into the chat the moment you notice the agent drifting.

This one actually works, in the narrow sense that the agent listens the moment you say it. The cost is that you have become the mechanism. It holds for as long as you are paying close attention and typing the reminder, which is not the same thing as holding. It does not survive a long session, a distracted afternoon, or a teammate who never learned the unwritten rule you have been retyping all week.

The real competitor is not another tool

Put those three together and a pattern shows up. A bigger directory does not fix retrieval. A louder file does not fix decay. Doing it by hand does not scale past the one person doing it. Each is a real attempt at a real problem, and each runs into the same wall from a different direction.

There is a fourth response, and it never shows up in a comparison chart because it is not a tool. It is deciding the friction is tolerable. You already wrote the CLAUDE.md once. You already know which two or three things the agent tends to forget, so you keep half an eye on them and move on. That is not a solution, but it is a reasonable reaction to trying three fixes that each had a ceiling. For a lot of people, the honest competitor to any routing tool is not a rival directory. It is the version of the workflow where nothing changes and they just stay alert.

What the fix actually needs

The three attempts above fail for a shared reason. A file that gets read once is not the same as a file that gets enforced. A directory that only installs is not the same as one that decides when to use what it installed. A person who has to remember to remind the agent is doing the router's job by hand, which is the job nobody wants to keep doing.

What is missing in all three is persistence: something that puts the relevant instruction back in front of the model at the moment of the decision, every time, not only at the start. It also needs a small enough set to choose from that picking correctly is actually easy, not a list of a thousand tangentially related skills where the right one and the wrong one look about the same.

That is the shape we build at Flowy: a hand-picked set of skills with a router file that maps intent to skill, kept in front of the model on every prompt by a hook instead of read once and forgotten. We think that shape answers the three attempts above better than any of them answer themselves. If you build the same shape yourself with your own tools, it will work whether or not our name is on it. The point was never the brand. It was the persistence.