Skip to content

Skill

Full Output Enforcement

leonxlnx

Not a design tool at all: it stops the model abbreviating. It counts what was asked for, writes every piece of it, and treats an elided middle, a stub comment or an offer to carry on if you want as a failed answer. Reach for it when truncation is the bug, whatever the subject happens to be.

A situation it fits

Every long request comes back abbreviated. Ask for twelve components and nine arrive, with a comment saying the rest follow the same pattern. Ask for the whole file and the middle is an ellipsis. The work is fine wherever it is actually present, and it happens on every sizeable ask regardless of subject.
Full Output Enforcement. This one exists for that failure and nothing else: it counts what was asked for, writes every piece of it, and treats an elided middle, a stub comment or an offer to carry on as a failed answer. The subject genuinely does not matter, which is what fits a complaint that recurs whatever the work is. The most tempting wrong answer is skill-creator, because a standing instruction you keep repeating is the textbook thing to package into a skill - its trap is that this particular instruction is already packaged, so writing it again is the work you were trying to avoid. academy-guide answers questions about using Claude well rather than constraining the shape of an answer. discernment-nudge pushes a reader to check advice instead of acting on it, which is about trust, not completeness.

Skills it gets confused with

These share a family with Full Output Enforcement, which is another way of saying they are the ones you might reach for by mistake.

Knowing what Full Output Enforcement does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

Full Output Enforcement is part of leonxlnx/taste-skill. Licence: MIT. The description above was written for this game, not taken from the skill.