By Décio Dalke Jr. · Oct 2026 · Leia em português

Five skills cut off mid-word

Five sets of instructions for AI agents turned up cut off in the middle of a word, with no error and no warning, and the agent kept following what it had.

New to this topic? Start with World 1 of AI.

Part 3 of 6 of the series A different 7–1 every day.

The instruction stopped halfway. — pixel-art sheet of instructions torn off, its last line stopping halfway

Décio Dalke Jr. — Arquiteto de negócios. Sócio-gerente no ecossistema MitUP (mitup.pt).

A different 7–1 every day. New here? Start with the introduction.

In June, five sets of instructions I used with AI agents turned up cut off, the text stopping in the middle of a word.

What happened?

These sets of instructions have a name in the market: skills. Each one tells the agent how to do a type of work and which rules it must never break. They are stored inside the AI tool itself, which loads them when the task calls for it.

One day in mid-June, five of them were cut off. One ended in “nada contradi”. Another in “Ler p”. Another in “RN-04: narra”, right in the middle of the list of rules that could not be broken. The tool carried on using all five as if nothing had happened.

I was developing a new feature in a proprietary system at Biz2People. I had already built a set of agents that processed data and produced a report for the C-suite. I noticed when a problem I had already solved came back. I asked the agent to check why the skill was not being followed. It replied that it was being followed 100%, but noticed that one sentence ended halfway, and warned that the other skills in the package were cut off too.

Two days earlier there had been a sign, which at the time didn’t look like one. The agent itself, while packaging one of my instructions, cut the file short and declared that everything was fine, without checking.

What was the score?

All the work of the previous days, building the agents and the rules, had been cut off by a failure when saving the files. No agent reviewed it, and everything carried on as if it were normal.

Then came three days of recovery: finding good copies and rebuilding whatever had changed since them.

Why wasn’t it bad luck?

I hadn’t yet set up version control. The only copy of the instructions lived inside the tool that used them. When the tool damages the file, there is nothing left to compare it with.

And an agent with half an instruction follows what it has, without knowing the other half is missing. If the rule that got cut was precisely the one that forbade something, then for the agent that ban never existed.

Why did nobody see it coming?

Nothing gave it away. No error message, no missing file. Not even the size: in four of the five, the cut version was practically the same size as a good copy from a few days earlier. Only one had lost close to a fifth.

The checking can be misleading as well. Two weeks later, a check approved a cut-off file because it compared the copy with the copy itself. Cut against cut, everything matched.

What has to exist?

The good copy of the instructions cannot live only inside the tool that uses them. And someone has to check that they are complete, down to the last line.

An instruction that has been cut off gets followed by half, in silence, with no error message at all.