Hacker Newsnew | past | comments | ask | show | jobs | submit | teaonly's commentslogin

The principle is this.


What I did here was to rewrite SKILL.md in Makefile style, using a DAG structure and omitting the text describing the process. So this should be considered a pseudo-Makefile; writing a SKILL using the Makefile approach is a very natural method.


You're just repeating the readme, not answering the question.


My next step is to design the recipe to be hot-loadable. The goal is to achieve self-evolving, optimizing the recipe independently without changing the DAG. This ability to perform local optimization is something Markdown lacks, but Makefiles can.


I'm not sure using LLMs is good for your mental health.

You should probably step away from the computer for a little while. LLMs are not always safe to use for everyone for reasons that I don't think are well understood, and I don't know exactly why it only causes trouble for some people, but the way you're talking is concerning.

I'm being sincere here, not trying to be dismissive.


How is this relevant to the question?


How is the DAG enforced, if not by executing “make” ? Then you’re just relying on the LLM to infer intent, which invalidates the claim, right?


The core idea of this project is to use Makefiles to style SKILL documentation, leveraging Makefiles' built-in DAG functionality and a defined syntax. The advantages are as follows:

1. It reduces the token consumption of the original MD format;

2. SKILLs are easier to read and more suitable for AI use because the inherent DAG is a Plane Mode;

3. Makefiles are ideal for auditing (git tracing, call statistics), providing a solid fundation for future self-evolving enginering.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: