> Every single skill I see just strikes me as a prompt
replyBoth of which are just blocks of text being stomped into an LLM.
I've got a feeling that prompting as we're doing currently (huge blocks of text with very little structure), at least when looking for a deterministic result, will be looked back on as if we were living in the Stone Age. Not sure what the alternative will be, but I'm imagining something like a CI pipeline definition in YAML.
A skill is usually auto-invoked and this one here has a bunch of trigger phrases. I personally dislike that. For this one especially I'd prefer explicit invocation.
replyThat is configurable in a good harness. (Or should be.) It's not intrinsic to the skill idea.
reply> If I need a longstanding process I will discuss with the agent and create a document.
replyIsn't this just what a skill is?
Nodding vigorously to that last comment. If I want to systematize something I put it in code. Natural language is not code.
reply