@Shpigford can I have a "Special/Niche legit Hardware" Button? This thing does not look like junk, reviews are good enough that I would be willing to try the device, but it's not a known brand either. But known brands normally don't produce some special/niche equipment

youtube.com/watch?v=s5T5oQJc… This /teach skill will get soooo handy for me for learning unknown codebases <3

@mattpocockuk running grill with docs in my openclaw now to spec put repos in the go. Not as fast as directly via pi, but the questionnaire style lends itself very good to chats and better when on the go than vpn into Linux machines to control pi directly! 🙌🤗

@mikker I wrapped glimpseui by hazat into a cli. npmx.dev/package/glimpse-cli I got: dynamic HTML based scripting ui in Tuna Scripts! <3

Ha, I got my first goblin with 5.5!

@mattpocockuk shoutout for setup-matt-pocock-skills supporting arbitrary issue tracking workflows! I track my issues with "beans" cli locally inside my repo. Small nitpick: I usually name my dir for agent steering files "meta", because these instructions are "meta" to the repo itself. This avoids them blocking the "docs" folder, which might be a full repo in itself with a static page project for generating docs. What do you think about this naming change, Matt? You could also use meta/agents if you want to keep the core "meta" namespace clear for user defined folders and files

This took way to fkin long - released today for iOS

@mikker Bought Tuna Pro 🥳 Tested it for the grace period and found it valuable to my workflow, use it daily now and improve the edges which don't translate yet from my workflows with raycast ^^

Could I have my 100 dollar per month sub first please 🥺

This is the difference between letting codex check your work and let opus do it. I'm convinced more and more that codex is the right call here. (Codex: no more issues, opus: two issues where the first one is exactly one thing I asked it to check 🤣)