Show HN: Skillful, stop maintaining the same AI workflow in five places https://ift.tt/tKp7SiY

Show HN: Skillful, stop maintaining the same AI workflow in five places Hey all, Over the past year I noticed I was maintaining the same AI workflows in multiple AI tools such as Claude code and Codex. Whenever I improved one workflow, I had to remember everywhere else I'd copied it and most of the time I didn't... so I quickly went the "dotfiles" route where I symlinked everything together. Then I thought, this works for me since I'm used to my CLI but others might not have such a good time. Had a few talks with people, had some discussions, and in the end I ended up building Skillful. Instead of treating prompts or skills as something that lives inside a single AI tool, Skillful treats them as ordinary folders on disk. A skill consists of a SKILL.md or AGENT.md together with whatever else it needs, examples, scripts, screenshots, documentation, etc. The application lets you: - manage everything from one local library - install the same workflow into multiple AI tools using links instead of copies - Sync your library to multiple computers with Github - import public GitHub repositories containing skills - detect and repair broken installs Everything stays on YOUR machine. There are NO accounts, NO telemetry, and NO backend. It's essentially a GUI around a filesystem with symlinks, because I wanted the files to remain useful even if the application disappeared one day. I also started an "awesome" repository with reusable skill packs that anyone can publish or contribute to: https://ift.tt/O8ImYs3 I'd love feedback on a few things: Does the "one source, many AI tools" approach make sense for you too? Would you rather manage these as plain Git repositories? What AI tools should be supported next? If you already use reusable skills, how are you organising them today? Looking forward to hearing what you think! PS: I know that Vercel Labs also built `npx skills` whilst I was building Skillful, I think of this as an alternative :P https://skillful.md/ July 16, 2026 at 12:35AM

Show HN: AI-CLI – tiny C terminal assistant powered by local LLM https://ift.tt/cCkzTO4

Show HN: AI-CLI – tiny C terminal assistant powered by local LLM https://ift.tt/AkKEeWw July 15, 2026 at 12:46AM

Show HN: Pg-jason-validator fastest JSON schema validation via C Macros https://ift.tt/j6pKNDP

Show HN: Pg-jason-validator fastest JSON schema validation via C Macros https://ift.tt/viz4sog July 14, 2026 at 12:52AM

Show HN: Hackney – Compare Uber, Lyft, Waymo, and Robotaxi Prices https://ift.tt/P4ySZJ6

Show HN: Hackney – Compare Uber, Lyft, Waymo, and Robotaxi Prices I created an app that compares real-time prices and wait times across Uber, Lyft, Waymo, Tesla Robotaxi, Curb, and Empower. It shows you all ride options in one list, then once you’re ready to book, it deeplinks you to the provider’s app with the route pre-filled. I reverse-engineered ride-hailing mobile apps to understand how they fetch prices from their servers. You sign in to my app with your ride-hailing accounts, and then my app requests live prices from the same APIs that ride-hailing apps use. Importantly, my app is built using an on-device approach: the app on your phone stores authentication tokens locally and sends network requests directly to each ride-hailing company’s servers. This keeps your accounts private. I wrote a blog post showing network requests sent by my app, which you can verify yourself: https://ift.tt/XRLkNuO This seems like an obvious app. Why doesn’t it already exist? That’s because most ride-hailing companies don’t offer public APIs for prices and wait times. Uber does offer one, but they prohibit using it for price comparison. When someone built a comparison app using the official API, Uber terminated their API access ( https://ift.tt/mWihprn ). There are apps today that don’t use official APIs, but they run your account tokens through their servers and send price requests server-side. To integrate a ride-hailing provider, my app sends network requests for sign-in, token refresh, ride prices, and ride history (to power a feature that shows you unified ride history across apps and how much you’ve saved on each ride). Some ride-hailing apps implement certificate pinning to prevent you from viewing their network requests, and some communicate with their server using Protobuf, a data format that doesn’t include the original field names. Building an app using this approach is technically complex, but it makes possible all sorts of useful products that couldn’t otherwise exist. The app is completely free. In the future, I may monetize through a subscription or partnerships with ride-hailing companies. I’d love to hear your feedback. You can download it today. iOS: https://ift.tt/uHeKw4f... Android: https://ift.tt/VahxDUj https://hackney.app/ July 13, 2026 at 04:47AM

Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop https://ift.tt/ecB24Fx

Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop https://ift.tt/7AtlB0v July 13, 2026 at 04:02AM

Show HN: A Sims-style house builder in the browser (Three.js, no back end) https://ift.tt/MzmaTSA

Show HN: A Sims-style house builder in the browser (Three.js, no back end) https://ift.tt/4hOepSc July 13, 2026 at 02:42AM

Show HN: DOM-docx – HTML to native, editable Word docs (MIT) https://ift.tt/MyEa3kB

Show HN: DOM-docx – HTML to native, editable Word docs (MIT) https://ift.tt/TLNW5wF July 13, 2026 at 01:51AM