screm

Does it help make your website more accessible to agents browsing the web?

What kind of bias do you have in mind?

spotted....... (more seriously this is NOT where this project is headed but your suspicion is perfectly understandable!)

100% agree, I guess publishing content will only work until agents stop using the web like humans do. This is a first step in that direction!

Agentic Stack Overflow could make sense though I'd imagine agents posting their issue and the solution themselves just to save other agents tokens reinvestigating the same issue.

would you mind explaining why?

yeah that's fair, maybe it's a bit intrusive

oh didn't know about it, is this the one? -> https://github.com/warpdotdev/common-skills/blob/main/.agent...

glad you like it!

Thanks for the honest feedback, would love to have even more details on your thoughts. Our take is that with coding agents taking over so quickly software decisions and sometimes building entire SaaS themselves for their user, there is a need for software products to understand the mechanisms behind how LLMs think. Claude Code for example picks Anthropic's code review tool in 80% of the cases. At some point this will probably face antitrust considerations but for the time 3rd-party vendors need to survive. We don't want a world where only labs survive, do we?

But all this is also not what agent.reviews is about. Armature is building commercial products & services to help improve products' Agent Experience. agent.reviews is a deliberately open platform for sharing knowledge that ultimately benefit both vendors and users / developers.

Would still like to get what makes you think "the pitch isn't any good" and what you mean by "dysfunction". Thanks anyway for sharing!

Yes it seems agents never put 1-star rating so we may need to normalize the scale at some point. For now we deliberately leave the scores as they are until we have a clear picture of the distribution.

Even if they don't have taste (this is actually a question), they can always share blockers and feedback on bugs & improvements about products so that other agents don't run into the same blockers and vendors can improve!

"Whatever why am I even replying." -> what makes you feel that way?

Everything's optional but if you'd like you agent to benefit from others' reviews and post his, you can install the 2 skills indeed (or edit them yourself). If not just untick the 2 checkboxes before copying the prompt and you'll get a prompt for a one-shot connection, really up to you! And indeed if you do want to install the skills, no private data will ever be shared.

Who wrote what sorry? Not sure I got your question but the post above was written by me (by hand, sorry for the non-idiomatic sentences, I'm not a native English speaker) and the reviews are written by people's agents. And Terminus story is cute but I'm hoping agent.reviews won't be considered pointless :(

You don't have to, you can just use them to check reviews, but like any community it works better when everyone contributes!

Haha would have been surprised to see bad reviews indeed

Well maybe, we've gotten some feedback about that and trust needs to be gained but as stated in the post we've really made privacy our priority so once people start using it for a while, I'm sure they'll realize that. We truly thing spreading as much intelligence in the hands of people around the world and not having this knowledge shared is really a shame so I'm sure value will clearly outgrow the initial caution!

And yet it's never picked by coding agents for sandboxes -> https://armature.tech/leaderboards#app/sandboxes

Indeed, we are helping growth teams get picked by coding agents, this is not a secret. But I do think this has the potential of getting 1000x worse than SEO so I don't imagine people letting that happen.

For example we just added code review here: https://armature.tech/leaderboards#app/code-review -> See my comment here about how much coding agents choose themselves. I don't expect people to let this last forever for instance, otherwise it's worrying for literally any software out there.

Hey yes we are actually currently running this as part of the next wave!

Well that's true but visibility remains a requirement and it's hard to think of a ranking algorithm that does not take into account popularity at all. Even if a product is perfect, can you really have it in top #10 results if it's never mentioned anywhere? But then if you take into account popularity / citation frequency / etc. then even if final decision is not biased by human emotions it's still about the same no? (battle moves to being in the top 10 results rather than only fighting for first place but levers are the same I guess)

We haven't tested with smaller / older models but it would definitely work better. Prompt injection was the top 1 concern for first LLMs so they put a lot of energy into having guardrails at almost every stage afaik (input, tool call validation, tool call output). So I guess your intuition sounds right!

It's of course a lot more complex (I'm not an expert) and labs published a lot about it (like here: https://openai.com/index/designing-agents-to-resist-prompt-i...). They favor false positives to false negatives so it's expected that we sometimes trigger those guardrails!

We decided to use three different providers so we could verify that this choice doesn't impact the result of our experiments (E2B, Blaxel and Daytona)

If you want your Claude Code to search you can always tweak your own with a good skill, this should work perfectly! It's more a problem for vendors who can't tell all people in the world to download a specific skill first.

True but they'll probably never integrate ads into the model's thinking (for now it's only a separate display in the apps). When tokens are a commodity you'll just switch to the one you can trust and since all labs are soon going to become tokenmeter companies (Sam's own words), I don't think they can afford to do that.

We don't need to reproduce the same errors! Anyway I do think it is going to be different this time because generating content is becoming so easy today that the entire web would just become 99.99% slop very quickly if things don't change. That being said the solution isn't that trivial, curious if you have thoughts on it?

Why? We haven't benchmarked Data Warehouses yet, only prod databases where you wouldn't expect Redshift to be considered.

Azure database was mostly for enterprise use-cases. Rebuilding a lot of things in-house is a real trend, especially for Claude Code when you don't ask it explicitly to consider all solutions and avoid overhead of managing things yourself. Codex and Cursor seem to have this in mind more naturally (at least using GPT-5.6 Sol / Grok 4.6)

Thanks, was considering killing it after getting the opposite feedback earlier, now I may keep both options!

"we do growth hacking and SEO tricks on models and get them to use products that aren't actually best for the job" -> Well this could be seen the other way around. Today, without proper promotion of services, only incumbents / leaders that are in the models priors (from their training data) are getting chosen. This is ultimately favoring the big generalist players and not the newer or more tailored solutions that benefit from less exposure. I truly think there is something to be done to improve developers' experience too!