Don't Hire Me
The Old Model Is One-to-One
Traditional hiring is a bottleneck. You find a great engineer, negotiate a salary, onboard them for weeks, and then they work on one thing at a time. Their expertise lives in their head. When they leave, most of it leaves with them.
This model made sense when the only way to apply expertise was to have the expert sit at a keyboard. But that constraint is dissolving.
Expertise as Configuration
A SKILL.md file captures the things that make a specific engineer valuable: their architectural preferences, their patterns for handling edge cases, their opinions on testing and code quality, their domain knowledge. It’s not a resume. It’s an executable specification of how someone thinks about software.
I wrote about this in If You Can’t One-Shot Your Feature, It’s a SKILL.md Issue — the real leverage in AI-assisted development comes from teaching the tools well. That same idea scales beyond your own projects. When you publish your SKILL.md, you’re making your expertise available to anyone who wants to spin up an agent that thinks the way you do.
An Army of You
The provocative part isn’t the SKILL.md itself. It’s the multiplier. Once your expertise is encoded, it’s no longer bound to a single thread of execution. Someone can run multiple agents in parallel, each one carrying your patterns into a different part of the codebase. Your judgment scales horizontally.
This isn’t science fiction. It’s the natural extension of what happens when you combine good context engineering with AI agents that can act on it. The bottleneck stops being “how many hours does this person have” and becomes “how well have they encoded what they know.”
What You’re Really Selling
If code was never the goal, then selling your time at a keyboard was always a rough proxy for what you actually provide: judgment. The ability to make the right call on architecture, testing strategy, error handling, and tradeoffs.
A SKILL.md makes that judgment portable. It separates what you know from where you happen to be sitting. An engineer with deep expertise in resilience patterns and platform tooling doesn’t need to join your team full-time to influence how your systems get built. They just need to publish a good SKILL.md.
The Catch
This only works if the SKILL.md is good. A vague, generic skill file produces vague, generic output. The same way a bad hire is expensive, a bad skill file wastes tokens and produces code that has to be thrown away. The engineers who invest in encoding their expertise well will have outsized impact — not because they write more code, but because their thinking runs everywhere.
Don’t hire me. Spin up as many instances of me as you’d like.
This article was originally posted on LinkedIn.