Don't hire me
Key takeaway: Write down your engineering judgment in a specific SKILL.md so your expertise can work in codebases you never touch.
Don’t hire me. Spin up as many instances of me as you’d like. A good SKILL.md makes an engineer’s judgment portable, so it runs in parallel instead of one task at a time.
Hiring is a bottleneck. You find a great engineer, onboard them for weeks, and they work on one thing at a time. Their expertise lives in their head, and when they leave, most of it leaves too, unless they taught it and wrote it down.
A SKILL.md captures what makes an engineer valuable: their architecture preferences, how they handle edge cases, their opinions on testing and quality, their domain knowledge. Think of it less as a résumé and more as a working spec of how someone thinks about software. That’s the idea from If you can’t one-shot your feature, it’s a SKILL.md issue, scaled past your own projects.
Once it’s written down, it isn’t tied to one person at one keyboard. Someone can run several agents in parallel, each carrying your patterns into a different part of the codebase. The limit stops being how many hours you have and becomes how well you wrote down what you know.
If code was never the goal, selling time at a keyboard was always a rough stand-in for what you provide, which is judgment.
The catch is that the skill file has to be good. A vague one produces vague code, wastes tokens, and gets thrown away, the same way a bad hire is expensive. Engineers who write theirs well get their judgment into far more work than they could cover alone.