https://developer.chrome.com/docs/modern-web-guidance/guides...
reply(we could make this clearer though)
Aye. I like the idea, Simon. The token cost of the index is high enough I wouldn't suggest the technique for regular use but.. agree that for occasional users it should suffice.
replyWe'll make this happen. :)
It looks like the markdown has cross references that assume that the cli approach is used, it would be nice to separate the content from the tooling to access.
replyIf you rename that file to "llms.txt" it'll be a bit more discoverable.
replyyeah that's fair. the infrastructure we are on isn't the most flexible (we will soon move to a newer more custom platform but that's a little way a way)
reply> That way I don't have to install anything at all
replyIt feels that something like this would be the holy grail of agents. A small agent that has only the minimum necessary built in knowledge. The rest, it just retrieves on the fly when it needs (+ caching)
It’s like storing pointers/links instead of the contents
In reality that's pretty much what we got here. Very progressive disclosure centric. There's a 'install' command exists because the ecosystem doesn't have good cross-agent ergonomics for installing skills. (Which bums me out).
replyBut yeah.. big corpus of valuable context × minimal agent footprint = happy place.
If created properly, skills are already something like that. You have a front matter summary always available to the agent. The agent can request the full skill content on demand, which might contain additional linked documents with details about APIs and schemas being used, deeper documents about niche subtopics, scripts to help with subtasks, etc.
replyWhat’s the point of modern Javascript without over complicating things?
reply