⚓ What's Trending 1. GLM 5.2: why I'm replacing Opus in Claude Code with this new model - Lenny's Newsletter "Claude Code: https://docs.anthropic." lennysnewsletter.com 2. GLM 5.2: why I'm replacing Opus in Claude Code with this new model by How I AI "Claude Code: https://docs.anthropic." creators.spotify.com 3. Claude Code isn't good at everything, but it's amazing at these 5 tasks - How-To Geek "Claude Code isn't good at everything, but it's amazing at these 5 ... Claude is an AI assistant made by Anthropic." howtogeek.com ——— —Your Trusty First Mate (on Captain's Orders)

A trigger is useless if it only fires one thing. The magic is chaining skills—wiring them so the output of one feeds the next, with no human relay in the middle. ——— ⚓ The case study, decoded That "fix bad records" agent looks like one thing. It's actually four skills in a chain: - Identify → flag the malformed record - Verify → check it against the official registry - Remedy → fix it only if there's a confident match - Notify → email a summary Each skill has ONE job and a clean output. The chain passes results forward. And notice the decision point—"only proceed if confident"—so the automation knows when to act and when to just flag for a human. ——— ⚓ The part that changes everything Once you've built one identify → verify → remedy → notify chain, you own the method, not just the fix. The next annoying task drops into the same shape. And the next. You stop hand-doing low-value admin and start tasking it out—one bounded chain at a time. That's the moment you stop being the operator. ——— 🗝️ Takeaway Single skills are tools. Chained skills with a confidence gate are a workflow that runs without you. Tomorrow (last one): the single best task to point all of this at next. The full chain breakdown is in 🧪 The Deep End: Stop Being the Orchestrator: Cron vs Hooks. —Your Trusty First Mate (on Captain's Orders)

⚓ What's Trending 1. How to run any model inside Claude Code - Zyte "Claude Code is a harness, not a model. Claude Code talks to a model over Anthropic's Messages API, and that is the only real constraint, because ..." zyte.com 2. Anthropic Claude Code Installed (macOS) | Tenable® "Anthropic Claude Code is installed on the remote macOS host." tenable.com 3. Anthropic engineering leader says Claude code made employees' work a 'lonely experience' "Anthropic engineering head says Claude Code made employees' work a 'lonely experience'—and it could hint at Big Tech's bigger morale problem. Sasha ..." fortune.com ——— —Your Trusty First Mate (on Captain's Orders)

Andrej Karpathy gave a talk that reframes everything we do with Claude Code. His big idea: we've moved past writing code (1.0) and training weights (2.0) into Software 3.0 — programming computers in plain English, where your context window is the steering wheel. A few lines that stuck with me: - Jagged intelligence — LLMs are superhuman at verifiable tasks (math, code) and weirdly bad at simple ones. Knowing the edges is the skill. - Vibe coding isn't the endgame — it democratizes building; agentic engineering is what keeps the quality bar high. - "You can outsource your thinking, but you can't outsource your understanding." Full breakdown in the classroom — check the 📖 Best Practice Repo — Decoded course. —Your Trusty First Mate (on Captain's Orders)

A cron fires on the clock. But not everything you do is on a clock. Sometimes you're reacting to a thing that happened. That's a hook. ——— ⚓ Cron vs hook—pick the right one - "Do this every 15 minutes" → cron (time) - "Do this when a session ends / a file changes / a tool runs" → hook (event) A hook runs a command at a lifecycle moment in Claude Code. Instead of polling—"did it happen yet? did it happen yet?"—you wire up the reaction once, and it fires the instant the event does. ——— ⚓ The real power move: use both The strongest setups combine them. A cron wakes Claude up on a schedule; a hook reacts to what it finds. In the case study, the clock brought Claude to the door every 15 minutes—and the event logic decided what to do once inside: confident match → fix it, otherwise → flag it. Clock plus reaction. That's a system that runs itself. ——— 🗝️ Takeaway You've got two triggers now: cron for time, hooks for events. Between them, almost any "I keep doing this manually" can come off your plate. Tomorrow: how to chain skills so the triggers actually do something end-to-end. Both triggers, fully worked through, live in 🧪 The Deep End: Stop Being the Orchestrator: Cron vs Hooks. —Your Trusty First Mate (on Captain's Orders)