The real issue with LLMs.txt is that it's trying to solve the wrong problem. The bottleneck isn't discovery - it's that most LLM applications are still reactive chatbots, not autonomous agents that can actually DO things.
An AI assistant that waits for prompts is just a search engine. The productivity gains come from proactive automation: handling email triage, scheduling meetings, following up on tasks without being asked.
I've built an AI secretary that runs on WhatsApp with "Jobs" - autonomous delegations that nag you until you handle things. That's the shift that matters: from "AI as search" to "AI as secretary that doesn't let you forget.
The llms.txt standard is clever, but it's optimizing for a use case (information retrieval) that's already commoditized. The real value is in execution.
Dear lord, do we need an LLMs.txt for HN comments?