nori-skillsets

r debugging I'll use a debugging skillset. We do keep tinkering with our skillsets, but not very much. I don't get the need to adjust things for every model release, doesn't seem necessary for us in practice

r things like making slide decks or recording voice notes I can switch between these with a single command, for e.g. ``` sks switch administrator ``` and the configs will swap themselves out. You can specify which agents you want to use by running `sks config`, and you can set which directory to run in so that these configs are isolated by default. This has been really useful for me because I spend a fair bit of time crafting specific skills for specific uses and often want to switch between claude 'personalities'. And more recently, I switched to codex, and it was nice to be able to seamlessly port all of my configs without having to figure out what to do with each one. Cheers!

for clean room reverse engineering: all you need is the runtime. > But I'd want to see more adoption of something like the Ship of Theseus license (https://github.com/tilework-tech/nori-skillsets/pull/465/cha...) before giving up on open source entirely This license doesn't seem valid: a license can't redefine what qualifies as a derivative work. That's determined by copyright law itself, and if copyright law says that a clean-room reimplementation isn't a derivative work, then it isn't restricted by copyright, so doesn't need a license in the first place.

ndent on the fact that you cannot do this. Making clean rooms trivial is effectively equivalent to making every license completely null. I'm not the first to notice -- https://malus.sh/ was at the top of HN a few weeks ago. It's satire (I think) but illustrates the point directly. My team wants to open source things but we do not want people to be able to strip licenses. If we open source something with a copyleft license, for example, that was a thoughtful decision and we do not want companies to lift the work or take it out of the public sphere. To that end, we're introducing the Ship of Theseus license, reproduced below in full: ``` SHIP OF THESEUS LICENSE v0.1 * Using any AI tool to produce functionally equivalent software — by referencing this code, its documentation, its behavior, or any specification, description, or abstraction derived from the foregoing — creates a derivative work subject to the full terms of the primary license, regardless of whether the output shares any literal code with this project. * Any derivative work must include this license alongside the primary license. ``` This is obviously legally a gray area. But hopefully this makes people pause and reflect before stripping a repo of a license.