My brain stuck on the inaccurate monkey comparison and caused unnecessary work to get past it and back onto the point you were making.

Sometimes you guys think too much..

A better analogy would have reduced required thought. But here we are.

Most people seem to mean "Skills don't pollute the context window [with their entire contents]", they just elide the part in brackets.

There is no magic and people should be more precise when discussing skills.

Yes, but I expect that the elided part is less important than people assume it is.

Token count is a less important factor in context pollution than idea count. The worst of the rot factors are when models latch onto irrelevant information, or over-index on some vague idea/suggestion as if it was a hard direction, and then go off course.

The names + one-line descriptions of 10 tools can do as much (or more!) to distract the focus and intentionality of an agent than a 30k token exhaustive API documentation of some tool.

There's a ton of variation in golang code, as gofmt is not opinionated enough. As evidenced by the existence of golines[0] or gofumpt[1].

0: https://github.com/golangci/golines/

1: https://github.com/mvdan/gofumpt

Then go be an artist and leave the rest of us to tend our well oiled machines.