The Colleague Skill and Replaceable Work

The viral “colleague skill” idea is funny because it is uncomfortable.

Feed the agent a person’s documents, messages, habits, and work patterns. Then let it imitate how that person writes, responds, explains, or even avoids responsibility.

The joke lands because every workplace has recognizable patterns.

The uncomfortable part is what it says about replaceable work.

A skill can copy patterns

A skill is good at capturing explicit and semi-explicit behavior.

How someone formats an update.

Which phrases they use.

How they name files.

What they check before shipping.

Which excuses appear when a task slips.

If that is the whole job, then yes, a skill can reproduce a surprising amount of it.

Not perfectly. But enough to be unsettling.

The scarce part is not the routine

This pushes me to separate two kinds of work.

Routine behavior is the part that can be documented, replayed, and compressed into a procedure.

Judgment is the part that decides what matters when the procedure is not enough.

Most people want to believe their routine is judgment. Often it is not.

If a skill can capture the entire value of your work, the problem is not that AI became too strong. The problem is that the work had already been reduced to repeatable surface behavior.

What I would protect

I would not try to protect style.

Style is easy to imitate.

I would protect taste, context, trust, and ownership.

Taste means knowing which output should not ship even when it satisfies the prompt.

Context means remembering the real constraints behind the task, not just the visible instructions.

Trust means people believe you will handle the ugly edge case without hiding it.

Ownership means you close the loop when the work gets messy.

Those are harder to turn into a skill file.

Not impossible, but harder.

That is probably where the human bar moves.