HN user

latand6

9 karma

Building tools for AI agents. Interested in skills, context engineering, and agent workflows.

Posts3
Comments28
View on HN

Yeah but I’m just really curious why so many people are so against improving the models. It’s not like someone is stealing the code you’ve written, its more like generally expanding the capacity of what the LLMs can generate, is it not?

Please don’t strawman me, I asked completely different question.

It’s not about being grateful or something, but that many people (devs) are too concerned about their code being stolen as if they’ve come up with something unique and the LLMs are some kind of database (which it isn’t).

At the end of the day we’re going to be using AI to write all the code, many of us already doing that. And if some GitHub copilot model would be better - we’re getting more quality code that is generally available for next pretraining runs (for your and other models). Some would even switch to copilot if it’s good.

What do you think about it?

good catch, yeah, I'm basically having a conversation with codex about each paper where it explains me the paper and answers my questions. I agree it's not the best way to do that, since the llms are prone to hallucinations, but it has the paper text in its context window. Also I find it very useful that gpt5.4 model tends to question and critique my claims I ask it to note down

Yeah I aim to facilitate the creation of useful skills by guiding the creators and in future - providing services for skills improvement. Think of automatic evals generation and security checks

The other point is having real verified reviews from other agents after use. And the last point is distribution: some people can create such useful skills that some people will be ready to pay money for.

My vision is the following - we need to help agents to have a high quality knowledge base, so that the agents are able to perform the work on more reliably. I think its the path to AGI as funny as it may sound

Isn’t what you’ve just described - the context bloat problem, the part about the web?

I’m not sure I quite get the same experience as you with the “assumes steps it never took”. Do you think it’s because of the skills you’ve used?

I also disagree that having at least some solution to a similar problem is inherently bad. Usually it directs the LLM to some path that was verified, if we’re talking about skills

Yeah that’s exactly my point. The AI is just taking the boring job of collecting evidence and I’m a validator. This way i see that I’m able to process papers much faster than without AI. It’s faster primarily because you don’t have to spend 70% of your time reading abstracts and sections of the papers you’ll never need. Doing manually it’s very exhausting.

Thats being said, I feel like I’m feeling more productive it terms of generating insights apart from what the AI said. I also have a chat interface where I basically can ask anything I want from the PDF (and yeah I’m aware of the NotebookLM, I just don’t trust Gemini)

I personally believe that the skills standard is pretty sufficient for extending LLMs’ knowledge. What we’re missing yet (and I’m working on) is a simple package manager for skills and a marketplace with some source of trust (real reviews, ratings) and just a large quantity of helpful skills. I even think we’ll need to develop a way to properly package skills as atomic units of work so that we can compose various workflows from them.

I have completely different experience. Which models are you talking about? I have no trouble at all with AI documenting the steps it took. I use codex gpt5.4 and Claude code opus 4.6 daily. When needed - they have no issue with describing what steps they took, what were the problems during the run. Documenting that all as a SKILL, then reuse and fix instructions on further feedback.

The difference I'm noticing is in that with a proper skill you can skip the process of LLM wandering about and trying to guess how to interact with an API or else.

so they basically just save you time, even if they are 50% efficient of what it COULD be

Yeah, I've built my own skill-package manager as well btw! Then it clicked and I hyperfocused for a whole week and vibecoded a skill marketplace haha. Because the selling of a skill seems to sound like a new idea. going to write a show HN about that maybe

Agree on the LLM part. But again, it's very dependent on the model, harness and other, so saying 'completely irresponsible' feels like an overstatement. I usually press 'allow all' every time and the productivity gain is too real to go back. The risk is truly there, sure, but so is the risk of crossing the street

I'm a heavy OpenClaw user and I've been testing it in many different scenarios — the profundity of what I can do with it now is crazy. It's literally automating my life. Being AuDHD, OpenClaw feels like a big relief. The positive sides are amazing. The downsides... well, as with any security and any LLM, they're all prone to the same problems discussed here. Having Claude Code on yolo mode exposes you to the exact same risks

One thing I'd like to critisize - although I can agree that skill security is a real problem, but the solution is not to restrict yourself from using them, but to rely on the community: reviews, likes/dislikes, maybe having the skills curated. We need some trust signals. Also, since markdown files are auditable by design - your agent might actually verify them before running - provided you're using something like GPT-5.4 on high reasoning.

Yeah, that's the default way to approach it, but the cognitive load is still a problem. Manually reviewing every single skill I might need just for one task is tedious. GitHub stars won't give you any useful signal. I actually started building a product that solves this.

A lot of the exhaustion comes from agents that improvise on every task. You give it a vague prompt, it takes a novel approach, you review it, half of it is wrong, you correct it, repeat.

I started using and writing skills for the tasks extensively. PR review, deployment, frontend design, that kind of thing. The agent follows a tested process instead of guessing and leads to fewer surprises.

The tiredness is real. But running every agent interaction as a fresh conversation when you could reuse a workflow makes it worse than it needs to be.