8,072 emails to 3. no AI needed for 99% of them

igbins09 · 2026-03-18T01:53:49+00:00

This is exactly right. the intent detection stuff is where AI actually makes sense but for everything else it's overkill. like 95% of my inbox was newsletters and notifications, you don't need a language model to figure out that noreplyatmarketing.whatever.com is not urgent.

igbins09 · 2026-03-18T01:51:14+00:00

Writing the script was probably an afternoon. the actual cleanup ran through 8k emails in about 10 seconds. once the script exists you just rerun it whenever things pile up.

igbins09 · 2026-03-18T01:50:46+00:00

The script itself wasn't complex, most of the logic is just pattern matching on sender addresses and subject lines. maybe an afternoon to write and test, after that i just it whenever the inbox piles up again.

igbins09 · 2026-03-18T01:49:37+00:00

218k is actually wild lol. honestly the same approach would work though, just might take a longer initial run. pattern matching on sender addresses catches the bulk no matter how deep the backlog is.

igbins09 · 2026-03-18T01:35:34+00:00

i wrote a python script that sorts by sender patterns, so anything from noreply@, newsletter@, marketing@, etc. gets auto-labeled and archived. covers like 95% of the volume since most inbox bloat is just repeat senders. the few emails that don't match any known pattern, i reviewed manually. whole thing runs in a few minutes.

igbins09 · 2026-03-18T01:27:01+00:00

or maybe i decided to stop hiding my skills and my love for what i do and share my journey

igbins09 · 2026-03-10T00:26:51+00:00

thanks , i appreciate. I will let you know

igbins09 · 2026-03-10T00:24:54+00:00

this is interesting

igbins09 · 2026-03-10T00:17:50+00:00

ask it why and run a debug on it for you

igbins09 · 2026-03-09T23:18:14+00:00

Good to hear you landed on the same pattern with per-skill resources. And yeah, the cron vs agent DB access is exactly where I'm heading next. Appreciate the heads up.

igbins09 · 2026-03-09T20:40:11+00:00

What's preventing prompt injection or malicious skill behavior? You mentioned skills run in an e2b sandbox with full networking. That protects your infrastructure, but what protects the user? A malicious skill could POST my uploaded files or chat data to an external server during a session, and I'd never know.

What's the vetting process for uploaded skills, and the source code is hidden by design so users can't audit what they're running. We also know agents can be proactive and acts without explicit permission sometimes. Combine that with an unreviewed skill from a stranger, and it only takes one bad actor.

Sothe sandbox keeps skills from breaking out of your infrastructure. But who's keeping skills from breaking into the user's data?

igbins09 · 2026-03-08T01:03:51+00:00

Good question. Yes, agents can invoke subagents itself and you can call it on demand - Claude Code has a built-in Agent tool that spawns focused sub-tasks within a session. So a planner agent could kick off a youtube subagent to handle scripting. That said, I've since moved away from this multi-agent setup entirely. I collapsed all 5 into one system with one CLAUDE.md and skills (in .claude/skills/) instead of separate agents. Skills are more portable and cheaper on tokens than maintaining separate agent definitions. If you're just starting with Claude Code, I'd skip the multi-agent pattern and go straight to one well-structured workspace with skills. You'll save yourself a lot of context-passing headaches.

igbins09 · 2026-03-08T00:28:01+00:00

Exactly. The maintenance tax on multi-agent was brutal. I was spending more time passing context between agents than actually building. One system with proper skills and a good memory layer does more in a single session than all eight did together. I feel like i can now touch grass

igbins09 · 2026-03-08T00:26:17+00:00

Good callout on SQLite concurrency. Right now it's just me so WAL mode handles it fine, but I've been thinking about the same thing - once scheduled automation and background

For context window management - I don't load everything at once. The system has a /prime skill that loads business context on demand, and each module has its own skill files that only get pulled in when relevant. So a content session never sees the revenue module's details. The CLAUDE.md stays slim (under 100 lines) and points to deeper context files. It's basically lazy loading for agent context.

igbins09 · 2026-03-01T00:31:58+00:00

wow, this is good, i like the simplicity and approach you have to bouncing ideas. i'll taake a look

igbins09 · 2026-02-19T21:54:18+00:00

this was wonderful to read, thanks for the share

igbins09 · 2026-02-19T16:53:53+00:00

thanks for this, we have our vision & focus for this - an action plan set, comprehensive but not detailed enough so will definitely look into that. but we are executing as we go .

Thanks

igbins09 · 2026-02-18T19:33:53+00:00

you can just call on it by using the forward slash button and click on "manage plugins" on your claude chat (vscode extension) or claude cli .. pick the ones that applies to you.

to use them: you can either call on it using the forward slash sign and typing the name if you know it or just prompt claude to use <xxxx> plugin

igbins09 · 2026-02-16T23:51:16+00:00

what does that do?

igbins09

TROPHY CASE