keithgroves

Cool! I built with https://enact.tools and can see several other competitors here.

I think this really has a future. Skills are going to be the way forward for portable ai tools. I think the skills standard needs to adapt to allow forward slashes so we can name things @vercel/somecategory/sometool. I've already brought it up in the agentskills GitHub.

posted last month: https://news.ycombinator.com/item?id=46435383

I like using gemini because it's so much cheaper when I'm running tests on enact protocol. I ask it to build multiple tools and let it run.

I really appreciate this feedback!

I made enact independently and realized how similar it was to skills when they were released, so tried to go with the flow rather than ask people to understand yet another new concept. Enact.md -> Skill.md

Not really sure what the path forward is but this feedback is very helpful.

When building https:/enact.tools we considered this. I'm glad we didn't go this route.

I'm building the Enact Protocol: https://enactprotocol.com

Turn any command into an AI-discoverable MCP tool with a few lines of YAML:

   name: hello-world
   description: "Greets the world"  
   command: "echo 'Hello, World"

Any AI agent can search for "greeting" and use your tool. I'm also building the first registry at https://enact.tools