| ▲ | simonw 4 hours ago |
| Distribution suggestion: in addition to the npm packages you have right now, set up GitHub Pages to publish a markdown index document of the skills at https://googlechrome.github.io/modern-web-guidance-src/skill... (currently a 404) That index page should link to plain markdown versions of all of the documents, and should be designed for search with grep to find the right answers. That way I don't have to install anything at all - provided my agent has the ability to make HTTP requests I can tell it "Look for tips on https://googlechrome.github.io/modern-web-guidance-src/skill..." and it will fetch the index, then navigate to the most relevant documents - no MCP or npm or installation required at all. |
|
| ▲ | kinlan 4 hours ago | parent | next [-] |
| https://developer.chrome.com/docs/modern-web-guidance/guides... (we could make this clearer though) |
| |
| ▲ | paulirish 4 hours ago | parent | next [-] | | 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. We'll make this happen. :) | |
| ▲ | jph00 3 hours ago | parent | prev | next [-] | | If you rename that file to "llms.txt" it'll be a bit more discoverable. | | |
| ▲ | kinlan 3 hours ago | parent [-] | | yeah 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) |
| |
| ▲ | kohukohunui 3 hours ago | parent | prev [-] | | 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. |
|
|
| ▲ | nico 4 hours ago | parent | prev | next [-] |
| > That way I don't have to install anything at all It 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 |
| |
| ▲ | mtrovo 3 hours ago | parent | next [-] | | 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. | |
| ▲ | paulirish 4 hours ago | parent | prev [-] | | 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). But yeah.. big corpus of valuable context × minimal agent footprint = happy place. |
|
|
| ▲ | trvz 4 hours ago | parent | prev [-] |
| What’s the point of modern Javascript without over complicating things? |
