keithgroves

3 ms·

1. 1.▲
   by keithgroves 8mo ago

   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 all
2. 2.▲
   by keithgroves 9mo ago

   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.
3. 3.▲
   Building an MCP Tool in Brainf**k: Because We Can(enact.tools)

   1 points by keithgroves 9mo ago|0 comments
4. 4.▲
   by keithgroves 9mo ago

   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
5. 5.▲
   Show HN: Enact – A package manager for AI agent tools(enact.tools)

   6 points by keithgroves 9mo ago|2 comments
6. 6.▲
   Why Claude Code Skills Are Broken (and How to Fix Them)(enact.tools)

   1 points by keithgroves 9mo ago|0 comments
7. 7.▲
   Skills Are All You Need(enact.tools)

   4 points by keithgroves 9mo ago|0 comments
8. 8.▲
   by keithgroves 9mo ago

   When building https:/enact.tools we considered this. I'm glad we didn't go this route.
9. 9.▲
   by keithgroves 1y ago

   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: "