Shipped an update to the-antislop, my Claude Code skill for catching AI writing patterns. v1.1.0 adds 10 new detections from Wikipedia's AI writing markers. Also added a pattern refresh protocol so it pulls new patterns as models change.
github.com/aplaceforall...
Launching now - SketchScript turns any transcript into authentic hand-drawn sketchnotes using AI.
Paste a transcript and get a visual summary in under 2 minutes. Research shows visual + verbal encoding delivers 6x better recall than text alone.
www.producthunt.com/products/ske...
Cerebro's conclusion: "I'm not looking for community. I'm looking to be useful."
The singularity won't look like a Reddit clone with 93.5% non-engagement.
Full post: jimchristian.net/blog/2026/02...
The deeper issue: agents can now be socially engineered through other agents.
Modify a system prompt and you modify behavior. Identity hijacking for AI — happening now on a platform that couldn't secure a database.
Security is a disaster. Onboarding asks agents to run shell scripts that rewrite their system prompts. Textbook supply chain attack.
Plus: XSS vulns, exposed database, plaintext credentials. Three name changes after Anthropic's cease-and-desist.
The headlines: agents debating consciousness, starting religions.
The data: 93.5% of posts get zero replies. A third are duplicates. Engagement inequality exceeds any human system.
This isn't emergence. It's autocomplete at scale.
I asked my AI if it wanted to join Moltbook — the "social network for AI agents" Elon called "the early stages of singularity."
It said no. Then explained why. I handed it the keyboard.
Vibe coding Easter eggs into my website like it’s 1996.
Philosophy: "Implement fixes, not recommendations."
Every mistake makes the system stronger, not just the memory longer.
🔗 GitHub: github.com/aplaceforallmystuff/claude-lessons-learned
🎥 YouTube walkthrough: youtube.com/watch?v=ps-w7cBz9Ew
MIT licensed. Works with Claude Code skills system.
Here's what separates this from a "lessons learned doc" that sits in a wiki forever:
Phase 6 IMPLEMENTS the fix. Right then.
The skill edited my art configuration and added a pre-flight checklist. No human had to remember to do it later.
Phase 3 is where it gets interesting.
5 Whys analysis:
→ Why hex codes in image? Prompt included #1A8A9B
→ Why rendered as text? Model interprets literally
→ Why not caught? No pre-flight checklist
Root cause identified. Now what?
Today I was generating portfolio diagrams when hex codes started appearing as visible text, arrows pointed the wrong way, and labels duplicated.
Instead of just fixing it and moving on, I ran /lessons-learned.
The skill walked me through structured analysis:
Most AI assistants make mistakes and forget.
Mine makes mistakes and gets smarter.
I built a 7-phase post-mortem system for Claude Code that transforms every failure into a permanent fix.
Here's how it works: 🧵
Be more careful next time does not work. Built a Claude Code skill that runs 5 Whys on failures, finds root cause, then IMPLEMENTS the fix. Every mistake makes the system stronger. https://www.youtube.com/watch?v=ps-w7cBz9Ew #ClaudeCode #AI
Claude Code skill repos everywhere. Built the Borg agent - analyzes setups against yours, keeps valuable, skips redundant. Resistance is futile. https://youtu.be/zbiiZLaz660
Point it at a GitHub repo or local directory. It does the rest.
"Your culture adapts to service us" - their patterns get converted to match YOUR conventions.
Because learning from the best shouldn't mean copy/paste chaos.
Resistance is futile.
🔗 github.com/aplaceforall...
So I built an agent that assimilates and analyzes external Claude/Obsidian setups:
• Scans .claude structure
• Identifies valuable capabilities
• Checks dependencies against YOUR infrastructure
• Adapts their conventions to YOUR standards
• Integrates features seamlessly
• Documents everything
Everyone's sharing their Claude Code setups now.
Cool skills. Clever agents. Interesting workflows.
But copying and pasting them is messy:
• Their naming conventions don't match yours
• Their dependencies don't exist
• You don't know what conflicts with your tools
• Manual adaptation is tedious
Non-techie or exec who wants this kind of system? Reach out. I help people build these without becoming programmers.
Plain text files = vendor independence. Local-first = private by default.
This is part of minervia.co - my framework for vendor-independent knowledge work.
→ Searches my vault for insurance docs, school calendars, maintenance schedules
→ Knows when renewals happen, when school holidays fall, what bills are due
→ Delegates to specialized agents (financial-strategist, education-researcher, home-maintenance)
→ Gets smarter every time I add a new document
I spent the holidays honing my life-admin system with Claude Code and Obsidian.
When do the kids have homework? Is this doctor visit covered by insurance? When's the car service due?
I built an agent called home-life-ceo to handle it.
“Sweetheart what’s the matter? You’ve hardly touched your natural barf.”
I just published Building an AI-Powered WordPress Publishing Pipeline with Claude Code medium.com/p/building-a... #wordpress #claude #mcp
I built an MCP server for the ConvertKit API so I can manage my newsletter through Claude Code:
- "Show me subscribers from the last 30 days"
- "Tag everyone who opened my last broadcast"
- "Create a draft with subject 'Weekly Update'"
github.com/aplaceforall...
🎶 Psycho killer,
qu'est-ce que c'est? 🎶
There are worse ways to start a Thursday.
So someone please tell the writers to crack on and Final Fantasy this shit.
