alizainf
very much agree that I've been inspired by val.town's craft
A Platform for Bespoke Software
Show HN: Sk` – manage AI agent skills across Claude, codex, opencode, et all
https://github.com/803/skills-supply
I love skills, I have a whole collection of skills I've built myself for problems I experience while using AI agents. but the current method of managing skills in codex/opencode is pretty garbage (copy skills into the correct folder).so i built `sk`One manifest, multiple agents — Define skills once in agents.toml, sync to all your AI coding tools Cross-agent compatibility — Use Claude Code...
Show HN: Sensei, documentation agent for coding agents
https://sensei.eightzerothree.co
For the last 4 months, I've been programming exclusively with AI. One of the most painful parts has been getting correct and up-to-date documentation for third-party libraries. So I made an agent to fix that.You can add it as an MCP tool to anything.It works because it's just focused on doing research for code. You can check out the prompts...
There are indicators above each comment to show which index you're on right now, and "prev"/"next" buttons to give you a better sense of other trees on either side of the comment. It's harder to show more because of space limitations, though I will continue to iterate!
Denest: A different way to read threaded comments
Fsdb: Use the filesystem as a graph/document database
- data types used in binary representation (in order: u32, u16, u16, u8, u8, u16, u32)
- canonical string representation (xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx)
I am of the opinion that this has diluted the usefulness of UUID, especially in specific circumstances. With this in mind, ULID was designed for applications that require the following: - distributed ID generation amongst loosely coordinated servers (ie. those that don't have incentives to maliciously manipulate timestamps)
- sortability of items with assigned ID without any additional information (ex. no additional db joins/requests)
Finally, ULID was designed with the explicit intent of being as character efficient as possible, for use in URLs and such. By using the Base32 alphabet, it uses fewer characters than UUIDs, optimizes for human readability/clarity (Crockford's modifications) and remains case-insensitive.For any API driven web-app where both the client and server can generate new data, ULIDs can be ideal. A lot of people are already using something similar. I thought it would be nice to standardize it as a drop-in replacement.