jb_hn

Very cool from a market intelligence perspective, but somewhat concerning from a 'creating adverse incentives' perspective -- e.g., what stops someone from placing bets on these markets then interfering with flights (calling out sick randomly, etc.)?

I'd imagine there's a positive correlation between "uses AI" and productivity, but I expect that to be somewhat moderated by how "well" they use AI.

It's very easy to churn out code that isn't particularly additive (or in some cases, actively destructive), so adjusting for that would be important.

Enterprises would be my guess. At its current price, though, I honestly don't find Fable worth it (it's good, just too expensive).

I feel like it's gotten marginally better (certainly, relative to a few months ago in the subreddits I frequent), but it's unclear how much of that is Reddit, Inc.-driven vs. per-subreddit-moderator-team-driven.

I think the situation can both be "bad" and "better than it was before," but to your point, some of the recent actions (e.g., curating histories) definitely seem counterproductive.

I think the “tool search” and “code mode” counter-arguments against the “MCP eats your context” argument is a bit hand-wavy.

Progressive disclosure has obvious benefits, but I think it would be more valuable to address how agents using either approach can still know which MCP server to search through. Maybe each tool has a search interface, and agents kick off searches in parallel for any ‘yet to be discovered’ tools, but there may be downsides to that as well

Perhaps I'm misunderstanding something, but this article appears to be misleading.

The title and content suggest that it's about AI-native distribution, and that MCP servers are the answer (i.e., the old world prioritized good docs; now, if you want to be discoverable by agents, you need an MCP server). But it assumes agents can just "discover" arbitrary MCP servers (as if Claude would "just know" that you have an MCP server).. which is not the case?

One recommendation would be to create a skill (name_of_your_internal_tool/SKILL.md) describing how the agent should use the tool(s) you're working with. This allows you to progressively disclose that context to the agent rather than filling its context (via its system prompt) with those instructions on every turn. If you use Claude Code, you can also try using it to interactively create the skill (it has a `skill-creator` skill). On the specific skills to make, you could align it with the specific tool (e.g., "Read this skill whenever the user asks you to use X tool...") or with a particular action (e.g., "Read this skill whenever the user asks you to [write, create, etc.]..."

Very cool! Seems like this would be a great way to support group planning (e.g., "work with friend-1-agent, ..., friend-n-agent to [plan a trip, organize a dinner, etc.]")