Live data from Hacker News

Context engineering is sleeping on the humble hyperlink

mbleigh.dev

41–50 of 69 posts

Re: Context engineering is sleeping on the humble hyperlink

#41
post #35

I wonder if I can instruct LLMs to use my MCP whenever they need to access anything online. So they can bypass AI blocks when I tell them to read some docs online.

This can already be done with Claude Code or most agentic tools. There will be restrictions for online platforms as LLMs are very vulnerable to prompt attacks.

Re: Context engineering is sleeping on the humble hyperlink

#42
post #32

The article seems a few months too late. Claude (and others) are already doing this: i've been instructing claude code to generate code following certain best practices provided through URLs or asking it to compare certain approaches from different URLs. Claude Skill uses file "URLs" to provide progressive disclosure: only include detailed texts into the context if needed. This helps reduce context size, and improves…

Codex run locally doesn't have access to any "web search" tool, but that doesn't stop it from trying to browse the web via cURL from time to time. Place hyperlinks in the documents in the repository and it'll try to reach them best it can. It doesn't seem overly eager doing so though, and only does that when absolutely needed and it can't find the information elsewhere. This has been my experience with gpt-5-high at least.

Re: Context engineering is sleeping on the humble hyperlink

#43
post #32

The article seems a few months too late. Claude (and others) are already doing this: i've been instructing claude code to generate code following certain best practices provided through URLs or asking it to compare certain approaches from different URLs. Claude Skill uses file "URLs" to provide progressive disclosure: only include detailed texts into the context if needed. This helps reduce context size, and improves…

Claude skills is bad mate, it needs to be put to bed. The approach this guy is talking about is better because it's open and explicit. https://sibylline.dev/articles/2025-10-20-claude-skills-cons...

Re: Context engineering is sleeping on the humble hyperlink

#44
What you're describing is basically very stripped down versions of pre-SPA web pages.

We don't need MCPs for this, just make a tool that uses Trafilatura to read web pages into markdown and create oldschool server side web UIs, and let the agents curl them.

Re: Context engineering is sleeping on the humble hyperlink

#45
post #36
post #32

The article seems a few months too late. Claude (and others) are already doing this: i've been instructing claude code to generate code following certain best practices provided through URLs or asking it to compare certain approaches from different URLs. Claude Skill uses file "URLs" to provide progressive disclosure: only include detailed texts into the context if needed. This helps reduce context size, and improves…

Heh, the problem with having a half drafted post on your machine for a few weeks is the industry moves fast! I had the post pretty much done, went on vacation for a week, and Claude Skills came out in the interim. That being said Skills are indeed an implementation of the patterns possible with linking, but they are narrower in scope than what's possible even with MCP Resources if they were properly made available to…

The problem with MCP resources is someone needs to stand up a server. That’s enough overhead and infrastructure that it slows down creating these kinds of resources and linking. Do any of the popular forge sites have like a GitHub pages but it’s MCP kind of capability? I think that would lower the hurdle for standing up such tooling so it would be much more appealing to actually do.

Re: Context engineering is sleeping on the humble hyperlink

#46
post #32

The article seems a few months too late. Claude (and others) are already doing this: i've been instructing claude code to generate code following certain best practices provided through URLs or asking it to compare certain approaches from different URLs. Claude Skill uses file "URLs" to provide progressive disclosure: only include detailed texts into the context if needed. This helps reduce context size, and improves…

Claude skills is bad mate, it needs to be put to bed. The approach this guy is talking about is better because it's open and explicit. https://sibylline.dev/articles/2025-10-20-claude-skills-cons...

That article appears to be very confused about how skills work.

It seems to think they are a vendor lockin play by Anthropic, running as an opaque black box.

To rebut their four complaints:

1. "Migrating away from Anthropic in the future wouldn't just mean swapping an API client; it would mean manually reconstructing your entire Skills system elsewhere." - that's just not true. Any LLM tool that can access a filesystem can use your skills, you just need to tell it to do so! The author advocates for creating your own hierarchy of READMEs, but that's identical to how skills work already.

2. "There's no record of the selection process, making the system inherently un-trustworthy." - you can see exactly when a skill was selected by looking in the tool logs for a Read(path/to/SKILL.md) call.

3. "This documentation is no longer readily accessible to humans or other AI agents outside the Claude API." - it's markdown files on disk! Hard to imagine how it could be more accessible to humans and other AI agents.

4. "You cannot optimize the prompt that selects Skills. You are entirely at the mercy of Anthropic's hidden, proprietary logic." - skills are selected by promoting driven by the system prompt. Your CLAUDE.md file is injected into that same system prompt. You can influence that as much as you like.

There's no deep, proprietary magic to skills. I frequently use claude-trace to dig around in Claude Code internals: https://simonwillison.net/2025/Jun/2/claude-trace/ - here's an example from last night: https://simonwillison.net/2025/Oct/24/claude-code-docs-map/

The closing section of that article revels where that author got confused They said: "Theoretically, we're losing potentially "free" server-side skill selection that Anthropic provides."

Skills are selected by Claude Code running on the client. They seem to think the it's a model feature that's proprietary to Anthropic - it's not, it's just another simple prompting hack.

That's why I like skills! They're a pattern that works with any AI agent already. Anthropic merely gave a name to the exact same pattern that this author calls "Agent-Agnostic Documentation" and advocates for instead.

Re: Context engineering is sleeping on the humble hyperlink

#47
post #32

The article seems a few months too late. Claude (and others) are already doing this: i've been instructing claude code to generate code following certain best practices provided through URLs or asking it to compare certain approaches from different URLs. Claude Skill uses file "URLs" to provide progressive disclosure: only include detailed texts into the context if needed. This helps reduce context size, and improves…

Codex run locally doesn't have access to any "web search" tool, but that doesn't stop it from trying to browse the web via cURL from time to time. Place hyperlinks in the documents in the repository and it'll try to reach them best it can. It doesn't seem overly eager doing so though, and only does that when absolutely needed and it can't find the information elsewhere. This has been my experience with gpt-5-high at…

You can run "codex --search" and it gains a search tool. I'm not sure why that isn't the default (like it is for Claude Code.)

Re: Context engineering is sleeping on the humble hyperlink

#48
post #4

I just discovered that I can paste a link into a Claude prompt and ask it to follow read the page so we can talk about it. I no longer have to copy the text of the page and paste it in. Claude uses the web_fetch command. So we're heading in the direction this article discusses.

Except that more often than not, Claude is blocked from reading the article. This used to work great two years ago when chatgpt first got the Web browsing feature. Nowadays, no eyeballs on ads: no content.

Claude Code running on your machine can switch to "curl" or even Playwright if it needs to.

Re: Context engineering is sleeping on the humble hyperlink

#49
If you ask Claude Code a question about its own features you can see it using hyperlinks directly, starting with this dedicated markdown index page:

https://docs.claude.com/en/docs/claude-code/claude_code_docs...

This is driven by instructions in the Claude Code system prompt:

> When the user directly asks about Claude Code (eg. "can Claude Code do...", "does Claude Code have..."), or asks in second person (eg. "are you able...", "can you do..."), or asks how to use a specific Claude Code feature (eg. implement a hook, or write a slash command), use the WebFetch tool to gather information to answer the question from Claude Code docs. The list of available docs is available at https://docs.claude.com/en/docs/claude-code/claude_code_docs....

Screenshot and notes here: https://simonwillison.net/2025/Oct/24/claude-code-docs-map/

Re: Context engineering is sleeping on the humble hyperlink

#50
post #46

Earlier quoted context omitted.

Claude skills is bad mate, it needs to be put to bed. The approach this guy is talking about is better because it's open and explicit. https://sibylline.dev/articles/2025-10-20-claude-skills-cons...

That article appears to be very confused about how skills work. It seems to think they are a vendor lockin play by Anthropic, running as an opaque black box. To rebut their four complaints: 1. "Migrating away from Anthropic in the future wouldn't just mean swapping an API client; it would mean manually reconstructing your entire Skills system elsewhere." - that's just not true. Any LLM tool that can access a filesyst…

This isn't an accurate take either. You can load client skills, sure, but the whole selling point from Anthropic is that skills are like memory, managed at the API layer "transparently" and that those skills are cross project. If you forced Claude to only use skills from the current project to try and be transparent, it would still be a black box that makes it harder to debug failures, and it'd still be agent and vendor specific rather than more human friendly and vendor agnostic.
Post reply on HN