Anthropic publishes Champion Kit for Claude Code adoption

Anthropic has published a Champion Kit for individual engineers who already use Claude Code and want to help their team adopt it. The guide is structured around three behaviors intended to fit inside a normal working week, with explicit time budgets.
Three champion behaviors
- Share what you discover — post the prompts, screenshots, and small wins in the channels your team already reads. Reusable techniques (e.g., “I learned that @-mentioning…”) compound across the team; status updates do not.
- Be the person people ask — when a colleague asks how you did something, respond with the actual prompt you used so they can apply it directly. A concrete, runnable example removes the gap between curiosity and first successful use.
- Grow the circle — establish lightweight recurring habits like a dedicated channel or weekly thread so momentum continues even when you’re busy.
Weekly time budget
The guide recommends no more than ~40 minutes total per week, distributed as:
- Posting wins and prompts — about 15 min. Capture in the moment with a screenshot and one or two sentences; avoid formal write-ups.
- Answering questions in a shared channel — about 20 min. Answer publicly once, then link back to that answer when the question recurs.
- Hosting a weekly show-and-tell thread — about 5 min. The champion posts an opening prompt; the team supplies the content.
- Optional pairing or walkthroughs — 0 to 30 min, reserved for colleagues who are genuinely blocked. Offer the Quickstart link before scheduling time.
Common concerns and one-liners
The kit includes responses to frequent objections, for example when someone asks about Claude Code’s data access or cost. The recommended format is a quick-reference sheet rather than long documentation.
The full source includes the full thirty-day playbook and a link to the complete documentation index at https://code.claude.com/docs/llms.txt.
📖 Read the full source: HN AI Agents
👀 See Also

Slash Claude costs 60x by offloading mechanical tasks to DeepSeek V4 Flash via MCP
A Reddit user cut Claude API spend 60x by routing file classification, JSON reformatting, and field extraction to DeepSeek V4 Flash via a simple MCP tool and a CLAUDE.md deny-list rule.

Three Essential OpenClaw Skills for a Stable Setup: Memory, Security, and Discovery
A Reddit post recommends installing three specific types of OpenClaw skills first: a memory fix skill to prevent context loss, a local security vetting skill to check for malicious code, and a curated discovery hub to find maintained tools.

Qwen3.x models fail silently in OpenClaw due to streaming output format mismatch
Qwen3.x models in streaming mode output to the 'reasoning' field instead of 'content', causing OpenClaw to silently fall through to fallback models. A proxy that translates API formats and injects 'think: false' fixes the issue, enabling full tool-call evaluation.

Custom Command Center App for OpenClaw: React PWA with WebSocket Proxy and Tailscale
A developer built a React PWA command center for their OpenClaw setup, featuring a live agent dashboard, trading desk, and push notifications, using a WebSocket proxy pattern to bridge OpenClaw's loopback-only gateway with devices on a Tailscale mesh.