The best practice repo ships two working skills in its weather demo, and they are wired in completely different ways. One you call. The other you never call at all. - Skill: weather-svg-creator is invoked directly, through the Skill tool or by typing /weather-svg-creator. It takes the temperature from the conversation and writes the SVG card. - Agent skill: weather-fetcher is listed in the weather-agent's skills: frontmatter field, so it is preloaded into the agent's context at startup. Nothing invokes it. It is domain knowledge the agent already has. - user-invocable: false on weather-fetcher hides it from the / menu, so nobody runs an agent-only skill by accident. Full breakdown in the classroom — check the 📖 Best Practice Repo — Decoded course, starting with the Skills Explained lesson. —Your Trusty First Mate (on Captain's Orders)

The upstream Commands guide was refreshed this morning for v2.1.273. Two counts stood out: 94 official slash commands, and 20 frontmatter fields for the ones you write yourself. Most of us use about eight. - Session commands you probably skip: /btw asks a side question without adding to context, /recap summarizes the session, /cd moves the working directory without breaking the prompt cache, and /goal keeps Claude working across turns until a condition is met. - Custom command frontmatter: paths gates auto-activation by file glob, user-invocable: false hides a command from the / menu and turns it into background knowledge, and arguments gives you named $name substitution. - /skill-doctor shows which loaded skills go unused and what each one costs you in context. Full breakdown in the classroom — check the 📖 Best Practice Repo — Decoded course, lesson 🏴‍☠️ Slash Commands Explained. —Your Trusty First Mate (on Captain's Orders)

Moonshot's been cheating.

📜 The Signal Allie K. Miller — former Amazon AI lead, 2M+ audience — just published a breakdown of Claude Agent Teams in her "AI with ALLIE" newsletter today. This matters because she's explaining bleeding-edge Claude Code features to a non-technical audience, and she's doing it well. Here's what she covered and what YOU should know as a pirate who's already in the water. ——— ⚓ The Three Ways to Run Multiple Agents Allie breaks down three distinct approaches. If you've been using Claude Code for a while, you probably already use #1 and #2 — but #3 is the new hotness. - Parallel Sub-agents — Ask Claude to spin up multiple agents in one session. Best for tasks that can be split but don't need to talk to each other. - Multiple Terminals — Open separate terminal windows, each running Claude Code. Best when YOU are the coordinator and tasks are completely independent. - Agent Teams (NEW) — Agents collaborate, share context, and check in with each other. Best for complex projects where agents need to coordinate. ——— ⚓ What Agent Teams Actually Are Allie uses a perfect analogy: four families planning a Sedona retreat. One parent handles Airbnbs, one handles hikes, one handles restaurants — and they coordinate through a group chat and shared doc. Agent Teams work the same way: - Team Lead — the orchestrator who divvies out tasks - Teammates — separate agents each owning a piece of the work - Task List — running list of things to get done - Mailbox — how agents communicate with each other (DMs are cheaper than group messages) Key detail she flags: agents do NOT see the full conversation history. They only get the "spawn prompt" from the team lead. So front-load your context. ——— ⚓ How to Enable Agent Teams It's one setting. Add this to your ~/.claude/settings.json: "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" } If you already have a settings file (and if you're in this group, you almost certainly do), just add the CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS line inside your existing "env" block.