| ▲ | stingraycharles 3 hours ago | |||||||||||||||||||||||||||||||||||||
I don’t get it. “ Dependency Resolution: The harness resolves the DAG (Directed Acyclic Graph) automatically. No more relying on an LLM to "guess" the next logical step.Uses the Target: Dependency + Recipe model to ensure Agents follow a strict execution order without skipping steps.” How does it do that? Does it just generate a Makefile? If so, why not just put the actual Makefile as a resource in the skill package and provide execution commands? That way the Makefile doesn’t need to be read at all. If not, and you rely on an LLM interpreting the execution order, wouldn’t that statement just be false? | ||||||||||||||||||||||||||||||||||||||
| ▲ | hrimfaxi 2 hours ago | parent | next [-] | |||||||||||||||||||||||||||||||||||||
It seems like it relies on an LLM to guess the next logical step and codify it. https://github.com/Teaonly/SKILL.make/blob/06872841537273376... | ||||||||||||||||||||||||||||||||||||||
| ▲ | teaonly 3 hours ago | parent | prev [-] | |||||||||||||||||||||||||||||||||||||
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. | ||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||