7 hours from my first commit to merged into Omarchy by @dhh
This is why OSS is so great you wish something had X or looked like Y make a PR and it becomes a permanent part of the OS configuration that anyone can install on a new machine and have up and running within 2 minutes
Update: excited to share that I'm joining Aide as an AI Engineer.
Aide is focused on building self-optimizing CX systems that empower teams to deliver exceptional experiences and maintain human-level quality on customer-facing interactions.
Excited to be part of a team that's building the future of agentic CX and building models to power customer interactions at scale.
OpenAI is shipping these pens to 4,000 of the earliest GPT Pro subscribers.
A pretty cool, and slightly ironic, gift to receive from the company automating writing.
The Higgsfield CLI + Marketing Skills will be added upstream to the Marketing-Cli tonight
if like me your losing track of all the open source marketing tooling available and having a hard time leveraging them highly recommend
https://t.co/MoPFKfF6ww
the entire cli runs with a single orchestrator agent skill /CMO that orchestrates all the best marketing skills / cli tools and surfaces relevant ones at the best times with the best practices
built on top of:
• marketing-skills by @CoreyHainesHQ - inspired many of the 50 skills
• Postiz by @gitroomhq - 30+ social provider integrations
• last30days-skill by @mvanhorn - live research across Reddit, X, YouTube, HN, GitHub
• @steipete/summarize by @steipete - text compression
• @firecrawl - cli tool for scraping brand assets logos etc
• @typefully - integration with their studio if you use that
• @resend uses the resend cli for setting up email campaigns etc
https://t.co/t8MsTVScrY
open-sourced marketing-cli
your AI agent gets a full marketing department.
50 skills. Brand memory across sessions. Local studio dashboard.
One install:
$ npm i -g marketing-cli
https://t.co/oh4IiLp7l0
vercel just got breached. if you haven't yet, rotate all your env vars and regen your tokens.
/vercel-breach-best-practices is a Claude Code skill that does it for you:
- preserves audit evidence first
- rotates upstream secrets in blast-radius order
- empties vercel env vars without deleting them
- hands you a [DONE] / [MANUAL] / [BLOCKED] checklist
needs you authed into the vercel cli.
npx skills add MoizIbnYousaf/vercel-breach-best-practices
Claude Code starts executing your tools before the model finishes generating its response.
As soon as a tool_use block arrives in the stream, execution begins. The rest of the model output generates in parallel. This overlaps tool I/O with generation latency.
That is why Claude Code feels fast even on complex multi-tool responses. It is not waiting for the full response before acting.
One of 43 patterns in /reverse-claude.
https://t.co/Nz0vbcwbL3
"Fix the login bug."
That prompt is missing four things: where the bug is, what symptom to look for, how to verify the fix, and what not to touch.
We built a skill that adds all four automatically. It reads your codebase, finds the relevant files, and rewrites the prompt with specific paths, test commands, and constraints.
Before: fix the login bug
After: users report login fails after session timeout. Check src/auth/, especially token refresh. Write a failing test first. Verify by running the auth test suite.
/best-practices fix the login bug
npx skills add best-practices
Claude Code has 6 layers of settings. Most people only know about one.
Policy beats local. Local beats project. Project beats user. User beats plugin. Plugin beats default.
settings.local.json is always gitignored. That is where your API keys and personal preferences go. Not in settings.json. Not in CLAUDE.md.
Hooks run on 4 event types: after a command, after a prompt, after an agent spawns, after an HTTP request. PostToolUse for auto-formatting. PreToolUse for blocking dangerous commands.
/reverse-claude set up PostToolUse hooks for auto-formatting
https://t.co/Nz0vbcwbL3
Claude Code burned 250,000+ wasted API calls per day before they added a circuit breaker to the compaction system.
Long sessions hit a loop: context too big, compact fails, retry, compact fails again. Infinite cycle. The fix was a 3-failure max circuit breaker that kills the loop and falls back to a cheaper strategy.
Four compaction tiers exist. Micro. Session memory. Full. Reactive. Each one more expensive than the last. The system escalates only when the cheaper one fails.
We mapped the full hierarchy in /reverse-claude.
https://t.co/Nz0vbcwbL3
We reverse-engineered 28,000 lines of Claude Code's production source into a single SKILL . MD
Permissions. Plugins. Agents. Context compaction. Retry logic. Configuration. Cost tracking.
7 modules. 43 patterns. One skill you can point at Claude Code itself.
/reverse-claude what features are in the source but not in the docs yet?
npx skills add skillcreatorai/reverse-claude
https://t.co/Nz0vbcwbL3
Claude Code runs every shell command through a 10-step permission cascade before it executes.
Deny rules strip ALL environment variables. Allow rules only strip the safe ones. That asymmetry is intentional. It prevents DOCKER_HOST=evil docker ps from matching your allow(docker:*) rule.
We documented the full cascade with pseudocode in /reverse-claude.
/reverse-claude how does the permission cascade work?
https://t.co/Nz0vbcwbL3
We reverse-engineered 28,000 lines of Claude Code's production source into a single SKILL . MD
Permissions. Plugins. Agents. Context compaction. Retry logic. Configuration. Cost tracking.
7 modules. 43 patterns. One skill you can point at Claude Code itself.
/reverse-claude what features are in the source but not in the docs yet?
npx skills add skillcreatorai/reverse-claude
https://t.co/Nz0vbcwbL3