ChanderG

I was searching the blog but couldn't find details on the fine-tuning process. What was the hardware and software used? Any learnings there?

Faced the same error "No building here" whereever I tried to place a block (common area or my lot)...

Why? Why is the premise that Fine-tuned models should be geared towards new discoveries?

The point of Fine-tuning small models is for specific downstream tasks, which SOTA models can do, but at higher costs. It is purely an economic play, not an attempt at pushing boundaries of SOTA.

I think there is another angle here..., fine-tuning is not in the interest of the AI Megacorps who are in it to grab everything.

Depending on a corporation to do your programming (and burning half the planet in the process, pardon the hyperbole) is the very opposite end of the "hacker" ethos where Lisp stands. Very surprising to see this sort of comment on HN, of all places.

@brailsafe has accurately captured where I am coming from.

I want more blogs/discussion from the community about the existing tools.

In 3/6 months, how many skills have you written? How many times have you used each skill? Did you have edit skills later due to unseen corner cases, or did they generalize? Are skills being used predominantly at the individual level, or are entire teams/orgs able to use a skill as is? What are the usecases where skills are not good at? What are the shortcomings?

(You being the metaphorical HN reader here of course.)

HN has always been a place of greater technical depth than other internet sites and I would like to see more of this sort of thing on the front page along with day one calls.

Please do open-source your skill and blog about it. Also, would like to hear from your experience after a few months of use. Like - how many times did you use the skill, did you run into some problems later (due to some unexpected thing in the markdown), did the skill generalize - or do you have to make tweaks for particular inputs.

I looked at superpowers, but it felt way too generic. Thanks for sharing unwind. More discussion/blogs about these kind of skills is what I am looking for. I would encourage you to write a blog on unwind, explaining in detail how it has helped you. Even better if you do it after 3 months of use, explaining the journey/evolution of the skill.

I thought skills were supposed to be sharable, but (a) ones that are being shared openly are too generic and not useful, (b) people are writing super specific skills and not sharing them.

Would strongly encourage you to open-source/write blog posts on some concrete examples from your experience to bridge this gap.

I looked that the official repo of skills, but I found those very generic and artificial.

I would encourage you to write up a blog post of your experience and share a version of the skill you have built. And then follow up with a blog post after 3 months with analysis like how well the skill generalized for your daily use, whether you had to make some changes, what didn't work etc. This is the sort of content we need more of here.

Nice - this is the kind of blogs we need more of. Getting into real experience.

First thing I did here is a grep for "Skills" and no hits. Simon's posts are well upvoted here and Anthropic/Claude is a bit of HN darling, but I think they are playing the hype game a bit too well here.

3 months ago, Anthropic and Simon claimed that Skills were the next big thing and going to completely change the game. So far, from my exploration, I don't see any good examples out there, nor is a there a big growing/active community of users.

Today, we are talking about Cowork. My prediction is that 3 months from now, there will be yet another new Anthropic positioning, followed up with a detailed blog from Simon, followed by HN discussing possibilities. Rinse and Repeat.

This is something I have experienced first hand participating in the Vim/Emacs/Ricing communities. The newbie spends hours installing and tuning workflows with the mental justification of long-term savings, only to throw it all away in a few weeks when they see a new, shinier thing. I have been there and done that. For many, many years.

The mature user configures and installs 1 or 2 shiny new things, possibly spending several hours even. Then he goes back to work. 6 months later, he reviews his workflow and decides what has worked well, what hasn't and looks for the new shiny things in the market. Because, you need to use your tools in anger, in the ups and downs, to truly evaluate them in various real scenarios. Scenarios that won't show up until serious use.

My point is that Anthropic is incentivized in continuously moving goalposts. Simon is incentivized in writing new blogs every other day. But none of that is healthy for you and me.

Is there an Anthropic document that says this? I mean about the "training" portion. The docs I am seeing talks about Claude Code or Desktop being able to use skills - that's a totally different matter.

Opened this excitedly, thinking I was going to get something related to S-expressions/Lisp, was disappointed...