@robertcourson Been working on something similar to manage all my skills, identify crossover and stale unused tooling. Checking this out as a possible option to build upon
@ChatGPTapp Projects and @claudeai Projects had their moment.
For serious AI work, folders and markdown files are the better primitive within Codex and Cowork. Let the agent build a source inventory, conflict log, missing context list, and duplicate report before it writes
@ParthJadhav8 Dude yes! Good find. Gonna do this to all my websites. A strong repo, a skill, and a strong /goal prompt is the defining moment of AI in 2026 (so far)
Are people still using @Context7AI?
Context7 and supabase used to be all anyone would talk about for MCPs and managing tokens.
I fondly remember setting it up as my first ever MCP. Does it still bring value or do Opus and Codex not need it anymore
It's my bullshit/shill filter and saves everything I find interesting, important, insightful into my obsidian brain in a format that is uniquely and specifically designed for "me"
Love hate relationship with the word 'workflow' right now. I have to put it in single quotes every time I use it. Feels like I'm air quoting what I saw to CC
ok tinkerers, i've got a fun toy for you
introducing baby-menu - a mac menu bar icon, and it's just a baby
it can't do anything, but you can feed it prompts and help it grow. it's what i think hyper-personalized, self-evolving software can look like
details in thread ๐
Seriously... How are people managing their skills? '/skills' isnt cutting it. Syncing skills across claude, codex, cowork, and desktop apps feels impossible.