Judgement. Critical thinking. Adaptability. Communication. Creativity. AI literacy. Every article names these, nobody defines them, and so nobody can tell whether they have one or are simply confident.
A skill you cannot test is not a skill you can develop, because you have no way of knowing whether you improved. So the useful version of this list is not the words. It is what each looks like when somebody has it, and what to check.
Domain judgement: knowing when a plausible answer is wrong
This is the load-bearing one, and it is the least discussed because it cannot be taught in a workshop. It is the ability to look at a well-structured, confident answer in your field and feel that something is off before you can say what.
It exists only where somebody has done the work, made the mistake and seen the consequence. That is why it does not transfer between fields and why it takes years, and it is also why it is now the scarcest thing on this list.
The test: when you last disagreed with a generated answer, could you say specifically what was wrong with it, or only that you did not like it? Specific beats uneasy.

Framing: turning a vague situation into an answerable question
Models reward precision and punish vagueness, which turned question-framing from a soft skill into a direct multiplier on the quality of what you get back. It was always the harder half of analysis; now the gap is visible in the output.
It is also what separates people who find AI transformative from people who find it disappointing. The tool is the same. The question is not.
The test: give the same brief to two people and compare what they asked before starting. The better framer asks about constraints, users and what would count as success. The weaker one asks about format.

Communication under disagreement, which is not the same as writing well
Writing clearly used to be a reasonable proxy for thinking clearly. That proxy is gone, because clear prose is now free and available to anyone.
What survived is the live version: explaining why a conclusion holds to somebody who does not want it to, staying specific under pressure, and changing your position when the other person is right without treating it as a defeat.
The test: in your last real disagreement at work, did you end up with a better answer, the same answer, or a worse relationship? Only the first one counts.
AI literacy: knowing what the tools are reliably bad at
AI literacy is usually taught as what the tools can do, which is the half that markets itself. The valuable half is the opposite: knowing the failure modes well enough to predict them.
That means knowing that models are confident when wrong, that they smooth over ambiguity rather than flagging it, that they are strongest on what resembles their training and weakest exactly where you most need help, and that they cannot tell you what they do not know.
The test: can you name three things you would not use a model for in your own job, and say why? Somebody who cannot has not used one seriously.
What to do with this
None of these improve from reading. They improve from repetitions with feedback, which means the work is to arrange feedback where there currently is none.
- Write down a prediction before each significant decision, and check it later. This is the only way judgement gets a scorecard.
- Before generating anything, write the question you are actually trying to answer. Compare it to the prompt you were about to use.
- Ask for the objection rather than the approval. Approval teaches nothing.
- Keep a short list of the times a model was confidently wrong in your field. It becomes the most practical AI literacy training available.


