Feed aggregator
Ente – Opening Our Books
Article URL: https://ente.com/open/
Comments URL: https://news.ycombinator.com/item?id=48932697
Points: 1
# Comments: 0
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://github.com/Mastermindzh/awesome-skillful
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
Comments URL: https://news.ycombinator.com/item?id=48932688
Points: 1
# Comments: 0
Deleting Systems You Don't Understand
Article URL: https://idiallo.com/blog/deleting-systems-you-dont-understand
Comments URL: https://news.ycombinator.com/item?id=48932657
Points: 1
# Comments: 0
AI Knows What You Did Online. Now Your Employer Does, Too
Article URL: https://www.wsj.com/lifestyle/careers/ai-knows-what-you-did-online-now-your-employer-does-too-49796adc
Comments URL: https://news.ycombinator.com/item?id=48932611
Points: 4
# Comments: 1
Show HN: A tool that generates nice photos for guys who dislike posing for pics
Article URL: https://vibeflirting.com/
Comments URL: https://news.ycombinator.com/item?id=48932603
Points: 1
# Comments: 3
I built a Rust log analyzer that explains security threats in plain English
Article URL: https://github.com/Senaraufi/Security-Log-Analyser
Comments URL: https://news.ycombinator.com/item?id=48932600
Points: 1
# Comments: 0
Best Streaming Services for Kids in 2026
To fix grid crisis caused by mismanagement under her previous administrations, Danish prime minister opens third term in office with laws against datacentres
Another mammoth Patch Tuesday update, likely topping 600 flaws in total, sends defenders into the weeds
Show HN: Keyline, share .env files encrypted before they leave your laptop
Article URL: https://keyline.sh/
Comments URL: https://news.ycombinator.com/item?id=48932384
Points: 1
# Comments: 0
TSMC Hikes Sales, Spending Outlook to Catch AI 'Megatrend'
Article URL: https://www.bloomberg.com/news/articles/2026-07-16/tsmc-beats-lofty-estimates-in-latest-sign-of-sustained-ai-demand
Comments URL: https://news.ycombinator.com/item?id=48932380
Points: 1
# Comments: 0
Lakehouse as Context Store
Article URL: https://altertable.ai/blog/2026-07-15-lakehouse-as-context-store
Comments URL: https://news.ycombinator.com/item?id=48932378
Points: 1
# Comments: 0
Productivity multi-tool – from the makers of flipper
Article URL: https://busy.app/
Comments URL: https://news.ycombinator.com/item?id=48932341
Points: 1
# Comments: 1
15 Years of Free Software Projects: A Review
Article URL: https://blog.frankrousseau.fr/15-years-of-free-software-projects-a-review/
Comments URL: https://news.ycombinator.com/item?id=48932317
Points: 2
# Comments: 0
Show HN: Pokayoke – turn code conventions into checks for agents
Hey HN,
Something I've been tinkering with in the background is a system to manage the "messy-middle" of TypeScript toolchains. Quite often, when I'm using Biome or any of the other linter / formatters, there will be repo conventions that I want to enforce (especially with AI agents), but which aren't supported by them, such as:
- Enforcing lines-of-code limits in modules - Never using custom TailWind colors - Only using lowercase underscores in filenames
Like, this is quite "random" but also bread-and-butter stuff that it's easy to think or talk about when you're working by yourself or with a few other human teammates, but I've found that agents consistently miss these conventions if I put them in an AGENTS.md file for example.
I wanted to make my esoteric repo conventions less stochastic, and more deterministic. I realised that agents are adept at writing the kind of code needed to run arbitrary checks on the TypeScript AST or workspace environment -- the kind of code that is cumbersome to write as a human.
So, I've made Pokayoke (https://pokayoke.codes) and would like your feedback! It's a small library that gives agents a place to test and store rules for enforcing conventions, and provides a skill to create those rules super easily. So you can come up with any arbitrary rule you like, get your agent to write a piece of code that enforces it, and then have it be included in your Pokayoke checks that get done (with one command) next to your other linting and formatting checks!
Fun fact: the name comes from the Japanese term for "mistake-proofing" or "error-prevention"[0].
[0] - https://en.wikipedia.org/wiki/Poka-yoke
Comments URL: https://news.ycombinator.com/item?id=48932314
Points: 1
# Comments: 0
AI-Generated UI Is Inaccessible by Default
Article URL: https://master.dev/blog/ai-generated-ui-is-inaccessible-by-default/
Comments URL: https://news.ycombinator.com/item?id=48932310
Points: 1
# Comments: 0
Uber Announces Acquisition Offer for Delivery Hero at $14.8B
Show HN: Enhanced YARA to detect threats in JavaScript using context and content
I started working on this project last year and open-sourced it this year.
It’s a library to scan byte payloads within JS using YARA-syntax rules, enabling YARA malware detection rules to run anywhere that JS runs (e.g. browsers, email clients, Office add-ons etc). However, it goes beyond core YARA by adding runtime context signals to the rule evaluation, so users can write detections like “encrypted PDF being downloaded from an unfamiliar website” or “executable downloaded from service-worker enabled site”. It started for security applications, but can also be applied to DLP and compliance.
I come from the EDR and web security world, so I take inspiration from gaps that I find there. In this case, I wanted to improve threat detection in payloads downloaded via the browser.
File scanners sit outside the browser and rely on OS notifications to trigger a scan when a file is downloaded. The file scanner knows it came from Chrome but doesn’t know the website, referral chain or user interaction preceding the download. This context information could be useful in identifying 0-day threats where signatures are not yet available. I started exploring if it were possible to embed an inline scanner within the browser to use flexible rules and block downloads before they materialized on disk. I did not want to invent a new rule language, so I picked YARA as it is well-established and open-source. I first coded the YARA engine in vanilla JS, including modules, so it could be run in any JS runtime. I thought of cross-compiling to WASM but stuck with vanilla JS because I wanted to add runtime-specific customizations, which were easier to do in vanilla JS. Once the YARA engine was ready, I added an extra metadata object that could be passed and used in the rule syntax. This was done using the custom module route, to maintain compatibility with YARA. This became Intercept.js.
The open-source repo includes a lot more information about the implementation, videos, some coding examples and a hosted instance on Cloudflare Workers to try out
It would be great to find collaborators interested in refining the project. I am presenting this at BlackHat Arsenal and DEFCON Demo Labs, so I’m happy to meet folks there to dive into more technical details.
Thanks!
Comments URL: https://news.ycombinator.com/item?id=48932269
Points: 1
# Comments: 0
Slower AI Improvement Means More Spending
Article URL: https://www.bargo.ai/research/slow-takeoff-fast-spending
Comments URL: https://news.ycombinator.com/item?id=48932261
Points: 1
# Comments: 0
