The problem with services and apps today: Our Attention is All They Need.
GenUI should have been the next shift in experience, a single chat interface that spins up dynamic components we can interact with, but it still clings to the one thing dearest to us: Attention.
So here’s the deal: Do you want my attention? Come to me.
GenUI was the right direction, but it needs an extra push. Don’t try to lure me to your site, don’t pull me out of my workspace. I work in Slack? Let me stay there. Teams? Sure thing — help me reduce context switching.
The solution? Expose your app as an agent in my space. Make it understand me, and satisfy my needs. Make it an extension of what I already do.
But with so many features to cover, how can a company expose them all?
There are multiple ways to bring your service to my doorstep. API-first and CLI are the classic options. Bots are often either too limited or too expensive to be truly useful. MCPs help, but they still consume a lot of tokens, which hurts both cost and the agent’s focus.
That leaves a more flexible path: combining your API with reliable logic and an adaptive agent layer.
This is where Agent Skills come in.
Agent Skills are open by nature. You share the logic that connects your solution to an agent, and users can adapt it to their own use cases. Users of agents like Claude Code, Codex, Kiro CLI, OpenCode, and OpenClaw can add those skills to their agents and shape them around their own needs.
With the right permissions, they can connect them to their preferred chat platforms. And because the skills are open source, users can see exactly what’s running.
This brings us back to the original idea, but with a twist: instead of building the bot yourself, you give my agent your capabilities.
With GitHub Issues, users can give feedback and help you improve. You also get the IKEA effect: people value more what they helped build.
Unconvinced? This is a great way to bring new features to our attention. Our agents will explain new features and help us integrate them into our systems.
Once we’ve integrated your Agent Skills, it becomes much harder to walk away. No one likes to break a working automation.
Agent Skills, in particular, shift control into users’ hands. You place the tools in our agents’ hands, and they bring those new powers to our workspace. Your app is no longer constrained by its UI or by a representative at my doorstep.
In my agent’s hands, it becomes as useful as my workflow and imagination allow. It adapts to my needs, and those needs keep growing.
Help us do greater things. Help us integrate your service into our day-to-day lives. Help us make your product far more valuable.
So here’s my call to you — every startup, every enterprise, every team shipping a product:
Publish your Agent Skills. Open your API. Let my agent talk to your service.
The companies that do this first won’t just keep their users — they’ll become part of how we think and work. The ones that don’t will keep begging for attention in a world that stopped caring.
Your move.