Ingest Claude blog post on marketing operations automation


<context timezone="America/Chicago" />
<task from="telegram-mg-17796" time="Jul 8, 2026, 5:00 PM">Script output:
{
  "newPosts": [
    {
      "slug": "how-anthropics-marketing-operations-team-uses-claude-cowork-to-automate-reporting-and-campaign-builds",
      "url": "https://claude.com/blog/how-anthropics-marketing-operations-team-uses-claude-cowork-to-automate-reporting-and-campaign-builds"
    }
  ]
}

Instructions:
New posts were detected on the Claude blog. The script output is in `data.newPosts` — an array of {slug, url} objects.

For each new post:
1. Evaluate relevance — prioritize: Claude Code features, agent SDKs, workflows, plugins, founder/engineering org content, security. Skip: customer case studies for specific industries (finance team, sales leader), compliance/partner announcements unless they introduce new capabilities.
2. For relevant posts: fetch the content using WebFetch and create a wiki source page in /workspace/extra/second-brain/wiki/sources/ following the naming pattern "Claude Blog - [Short Title].md". Also create a concept page in /workspace/extra/second-brain/wiki/concepts/ if the post introduces a significant new concept.
3. Update existing wiki tool pages if a post adds capabilities to an already-documented tool (e.g., Managed Agents updates).
4. Update /workspace/extra/second-brain/wiki/Home.md — add entries to the Sources section for new source pages and to Concepts for new concept pages.
5. Update /workspace/extra/second-brain/wiki/Wiki Ingest Log.md with a dated entry noting what was ingested.
6. Update CLAUDE.local.md if any new monitoring tasks or sources should be noted there.
7. Message James (telegram-mg-17796) with a concise bullet list of what was new and what was ingested. If nothing was relevant, send a brief note saying the blog was checked and nothing worth ingesting was found.</task>


- update-config: Use this skill to configure the Claude Code harness via settings.json. Automated behaviors ("from now on when X", "each time X", "whenever X", "before/after X") require hooks configured in settings.json - the harness executes these, not Claude, so memory/preferences cannot fulfill them. Also use for: permissions ("allow X", "add permission", "move permission to"), env vars ("set X=Y"), hook troubleshooting, or any changes to settings.json/settings.local.json files. Examples: "allow npm commands", "add bq permission to global settings", "move permission to user settings", "set DEBUG=true", "when claude stops show X". For simple settings like theme/model, suggest the /config command.
- keybindings-help: Use when the user wants to customize keyboard shortcuts, rebind keys, add chord bindings, or modify ~/.claude/keybindings.json. Examples: "rebind ctrl+s", "add a chord shortcut", "change the submit key", "customize keybindings".
- simplify: Review changed code for reuse, quality, and efficiency, then fix any issues found.
- fewer-permission-prompts: Scan your transcripts for common read-only Bash and MCP tool calls, then add a prioritized allowlist to project .claude/settings.json to reduce permission prompts.
- loop: Run a prompt or slash command on a recurring interval (e.g. /loop 5m /foo, defaults to 10m) - When the user wants to set up a recurring task, poll for status, or run something repeatedly on an interval (e.g. "check the deploy every 5 minutes", "keep running /babysit-prs"). Do NOT invoke for one-off tasks.
- schedule: Create, update, list, or run scheduled remote agents (routines) that execute on a cron schedule. - When the user wants to schedule a recurring remote agent, set up automated tasks, create a cron job for Claude Code, or manage their scheduled agents/routines. Also use when the user wants a one-time scheduled run ("run this once at 3pm", "remind me to check X tomorrow").
- claude-api: Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements).
TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`; user asks for the Claude API, Anthropic SDK, or Managed Agents; user adds/modifies/tunes a Claude feature (caching, thinking, compaction, tool use, batch, files, citations, memory) or model (Opus/Sonnet/Haiku) in a file; questions about prompt caching / cache hit rate in an Anthropic SDK project.
SKIP: file imports `openai`/other-provider SDK, filename like `*-openai.py`/`*-generic.py`, provider-neutral code, general programming/ML.
- agent-browser: Browse the web for any task — research topics, read articles, interact with web apps, fill forms, take screenshots, extract data, and test web pages. Use whenever a browser would be useful, not just when the user explicitly asks.
- frontend-engineer: Pro frontend engineering discipline. Enforces build-test-verify workflow for every web project. Never declare done until the site is built, tested, responsive, accessible, and visually verified in a real browser. Use alongside vercel-cli for production-quality deployments.
- whatsapp-formatting: Format messages for WhatsApp, including mentions that render as real WhatsApp tags. Use when responding in a WhatsApp conversation (platform_id / chatJid ends with @s.whatsapp.net or @g.us).
- vercel-cli: Deploy apps to Vercel. Use when asked to deploy, ship, or publish a web application, or manage Vercel projects, domains, and environment variables.
- slack-formatting: Format messages for Slack using mrkdwn syntax. Use when responding to Slack channels (folder starts with "slack_" or JID contains slack identifiers).
- welcome: Introduce yourself to a newly connected channel. Triggered automatically when a channel is first wired. Send a friendly greeting and brief overview of what you can do.
- self-customize: Customize your own agent — add capabilities, install packages, add MCP servers, edit code or CLAUDE.md. Use when the user asks you to add a feature, install a tool, or modify how you work. For non-trivial code changes, delegate to a builder agent via create_agent.
- onecli-gateway: OneCLI Gateway: transparent HTTPS proxy that injects stored credentials into outbound calls. You MUST use this skill when the user asks you to read emails, check calendar, access GitHub repos, create issues, check Stripe payments, or interact with ANY external service or API. Do NOT use browser extensions or OAuth CLI tools. Make HTTP requests directly; the gateway injects credentials automatically.
- consult-codex: Get a second opinion from OpenAI Codex on a plan, a problem you're stuck on, or any task that benefits from a fresh perspective or higher reasoning effort. Use when the user says "ask Codex", "red-team this with Codex", "get Codex's take", "I'm stuck - try Codex", "what would Codex say about this", or "run this by Codex".
- widget-install: Install widget build, bust caches, verify in gallery
- skill-review: Analyze the current session transcript to surface friction points — corrections made, clarifications added, questions Claude asked that a good skill or CLAUDE.md entry would have pre-answered. Use at the end of any working session when you say "skill review", "review this session", "what should I add to my skills", "what did the skill miss", "what kept needing prompting", "session debrief", "improve my setup from this session", or "what friction was there today".
- deploy-to-mini: Deploy a project's local git changes to the always-on Mac Mini (jamess-mac-mini, where long-running services like nanoclaw, the pool monitor, and the congressional trading monitor run) over the LAN via SSH, then rebuild and restart that project's launchd service. Use when the user says "deploy to the mini", "push this to the mac mini", "get these changes running on the mini", "restart <service> on the mini", or after committing a change that needs to go live on the Mini.
- consult-agy: Get a second opinion from Google's Antigravity (agy/Gemini) on a plan, a problem you're stuck on, or any task that benefits from a fresh perspective, large context, or higher-capability model pass. Use when the user says "ask agy", "ask Gemini", "red-team this with agy", "get Gemini's take", "I'm stuck - try agy", "what would Gemini say about this", or "run this by agy".
- escalate: Escalate a stuck problem to an external agent (Codex, Claude, or agy/Gemini) and surface a structured summary of what was tried, what was observed, and alternative strategies. Invoked automatically when 3 approaches have failed without measurable progress, or manually when the user says "escalate this", "ask an outside agent", "try a higher effort model", or "I'm stuck, get help".
- consult-claude: Get a second opinion from Anthropic Claude Code on a plan, a stuck problem, or any task that benefits from a fresh perspective or higher reasoning effort. Use when the user says "ask Claude", "red-team this with Claude", "get Claude's take", "try Claude", "what would Claude say about this", or "run this by Claude".
- smell-fix: Read the current project's observations.md and propose (or apply) fixes for open code smell items. Use when the user says "/smell-fix", "fix smell observations", "address observations backlog", "work through observations", or when pace is low and there's idle time.
- init: Initialize a new CLAUDE.md file with codebase documentation
- review: Review a pull request
- security-review: Complete a security review of the pending changes on the current branch


Let me evaluate the new post detected on the Claude blog:

**Slug:** `how-anthropics-marketing-operations-team-uses-claude-cowork-to-automate-reporting-and-campaign-builds`

This seems to be about Anthropic's internal marketing team using Claude + Cowork. Let me think about relevance:
- It mentions "Cowork" which is an Anthropic product/tool
- It's about automating reporting and campaign builds
- It could contain information about Claude Cowork capabilities

The CLAUDE.local.md says to skip: "customer case studies for specific industries (finance team, sales leader), compliance/partner announcements without new capabilities."
However, this is about Anthropic's own marketing operations team using Claude + Cowork, which is different from external customer case studies. Since it's internal use and mentions Cowork capabilities, I should fetch the post to evaluate whether it reveals new information about the product or just describes internal workflow automation.


ToolSearch

Question: select:mcp__nanoclaw__send_message,WebFetch


Question: select:mcp__nanoclaw__send_message,WebFetch


Let me fetch the blog post to evaluate its relevance and content.


On it — fetching and evaluating the new Claude blog post now.


Message sent to telegram-mg-17796 (id: 1453)


WebFetch

Prompt: Extract the full article content: title, date, author, main topics, all tools/products mentioned, key workflows described, technical capabilities shown, any new Claude or Cowork features introduced, and key takeaways.


# Article Extraction: Claude Cowork in Marketing Operations

**Title:** How Anthropic's marketing operations team uses Claude Cowork to automate reporting and campaign builds

**Date:** July 8, 2026

**Authors:** Ian Chan and Annabel Custer (Anthropic marketing operations team)

**Main Topics:**
- Automating weekly marketing metrics reporting
- Streamlining event and campaign setup across multiple platforms
- Reducing manual work through AI-driven workflows
- Quality improvements and consistency at scale

---

## Tools & Products Mentioned

**Marketing Platforms:** Salesforce, HubSpot, Swoogo, email tools, Asana, Gmail, Google Drive

**Claude Products:** Claude Cowork, connectors, skills

**Key Infrastructure:** Data warehouse, Slack, landing page builders

---

## Key Workflows Described

### Weekly Metrics Reporting (Ian Chan)
- **Automation:** Claude reads previous reports, meeting transcripts, and Slack messages; queries data warehouse
- **Process:** Scheduled Sunday evening task generates initial metrics with suggested focus areas
- **Skills used:** Prep skill, proofreading skill, action-items skill
- **Result:** Reduced 1-2 days of manual work to approximately 2 hours
- **Shift in work:** Ian now focuses on enablement, validation, and data layer refinement rather than data collection

### Event & Campaign Builds (Annabel Custer)
- **Intake system:** Dedicated Slack channel with form-based requests
- **Routing:** Dispatcher skill reads channel hourly and routes to appropriate specialist
- **Specialist skills:** Event-build, webinar landing page, audit, apply-to-attend, approval-support, data-import skills
- **Quality control:** Independent audit agent tests registrations and verifies outputs before completion
- **Result:** Consistency across builds and scalability; Annabel redirects efforts toward strategic projects

---

## Technical Capabilities Shown

- **Connectors:** Direct integration with marketing platforms
- **Skills system:** Modular, updatable instruction sets for specific tasks
- **Scheduled automation:** Recurring tasks that run without manual triggering
- **Multi-agent workflows:** Separate Claude instances for specialized functions (e.g., audit verification)
- **Data validation:** Flagging mismatches instead of guessing; tracing numbers to verified sources
- **Iterative refinement:** "Ask Claude to summarize what came up that should go back into the skills"

---

## New Features/Capabilities Introduced

- **Proofreading skill pattern:** Verification methodology for automated reporting
- **Dispatcher routing:** Workflow prioritization and task deduplication
- **Audit agent pattern:** Independent verification of automated outputs
- **Scheduled task execution:** Recurring automation without manual intervention
- **Manager agent:** Debugging and skill refinement mechanism

---

## Key Takeaways

1. **Automation enables strategic work:** As routine tasks automate, teams shift toward enablement, validation, and process improvement

2. **Human validation remains essential:** Both workflows emphasize review checkpoints—Ian validates reports; Annabel reviews audit results before shipping

3. **Skills are living systems:** Continuous updates based on corrections, edge cases, and process refinements strengthen automation over time

4. **Consistency at scale:** Centralized workflows eliminate quality variance from manual processes (e.g., wrong city names, broken landing pages)

5. **Practical implementation advice:**
   - "Turn repeated corrections into skills"
   - Start with proofreading skills for reports
   - Build scheduled tasks for recurring work
   - Use reflection prompts to improve instructions


Now I need to evaluate relevance. The post slug mentions "customer case studies" type content but this is actually about Anthropic's *own* marketing team using their product.

Relevance criteria from CLAUDE.local.md:
- Prioritize: Claude Code features, agent SDKs, workflows, plugins, founder/engineering org content, security
- Skip: customer case studies for specific industries (finance team, sales leader), compliance/partner announcements unless they introduce new capabilities

This is borderline. It's Anthropic's own team (not a customer), and it introduces several workflow patterns:
- Skills system / modular instruction sets
- Dispatcher routing pattern
- Audit agent pattern (independent verification)
- Scheduled task execution
- Multi-agent workflows

These patterns are genuinely useful for James given his interest in agentic workflows and his work with TradingBot25 and Cowork. The key distinction is that this isn't a random customer case study—it's Anthropic's internal team demonstrating concrete workflow patterns like dispatcher routing, audit agents, and skill iteration loops that directly apply to his projects.

Now I'm going to ingest this into the wiki. I'll check the existing structure to follow naming conventions, then create a source page for the Cowork patterns and a concept page for the multi-agent workflow patterns, updating the home page and ingest log accordingly.


Good content. This is Anthropic's own team showcasing Cowork workflow patterns — relevant given James's Cowork interest and nanoclaw parallels. Let me look at existing wiki structure before writing pages.


/workspace/extra/second-brain/wiki/sources/Claude Blog - Dynamic Workflows in Claude Code.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Running an AI-Native Engineering Org.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Founders Playbook.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Introducing Dynamic Workflows.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Managed Agents Self-Hosted Sandboxes.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Lessons from Building Claude Code How We Use Skills.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Best Practices for Claude Cowork.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Self-Service Data Analytics with Claude.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Claude Cowork Product Guide.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Claude for Foundation Models.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Connector Observability.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Whats New in Claude Managed Agents.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Building With Claude Managed Agents.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Field Guide to Claude Fable.md


/workspace/extra/second-brain/wiki/concepts/Human Sandwich Model.md
/workspace/extra/second-brain/wiki/concepts/3-Layer Context Engineering System.md
/workspace/extra/second-brain/wiki/concepts/Tokenmaxxing.md
/workspace/extra/second-brain/wiki/concepts/Saaspocalypse.md
/workspace/extra/second-brain/wiki/concepts/Claude Constitution.md
/workspace/extra/second-brain/wiki/concepts/Claude Code Drift Problem.md
/workspace/extra/second-brain/wiki/concepts/4 AI Digital Employees Framework.md
/workspace/extra/second-brain/wiki/concepts/Friction-First Development.md
/workspace/extra/second-brain/wiki/concepts/Screenshot-First Visual Verification.md
/workspace/extra/second-brain/wiki/concepts/Apple Widget Rendering Modes.md
/workspace/extra/second-brain/wiki/concepts/Agentic UI Impedance Mismatch.md
/workspace/extra/second-brain/wiki/concepts/Claude Code Subagents.md
/workspace/extra/second-brain/wiki/concepts/WebMCP.md
/workspace/extra/second-brain/wiki/concepts/WidgetKit Engineering Pitfalls.md
/workspace/extra/second-brain/wiki/concepts/But For Real Skill.md
/workspace/extra/second-brain/wiki/concepts/Claude Code Agent Teams.md
/workspace/extra/second-brain/wiki/concepts/Claude Code Dynamic Workflows.md
/workspace/extra/second-brain/wiki/concepts/AI-Native Engineering Org.md
/workspace/extra/second-brain/wiki/concepts/Claude Code Skills Best Practices.md
/workspace/extra/second-brain/wiki/concepts/Devin vs Claude Code.md
/workspace/extra/second-brain/wiki/concepts/Frontier Model Qualitative Step Change.md
/workspace/extra/second-brain/wiki/concepts/Builder-Verifier Loop Pattern.md
/workspace/extra/second-brain/wiki/concepts/Frontier Model Extraction Strategy.md
/workspace/extra/second-brain/wiki/concepts/Question-Led Selling Arc.md
/workspace/extra/second-brain/wiki/concepts/CLAUDE.md Progressive Disclosure.md
/workspace/extra/second-brain/wiki/concepts/Finding Your Unknowns Framework.md
/workspace/extra/second-brain/wiki/concepts/Orthogonal Visual Channels on Map Lines.md
/workspace/extra/second-brain/wiki/concepts/Error-Shaped Success Results in LLM SDKs.md
/workspace/extra/second-brain/wiki/concepts/NanoClaw Slack Mention-Sticky Session Bug.md
/workspace/extra/second-brain/wiki/concepts/NanoClaw REST Fallback Tool-Call Hallucination.md


Let me check existing Cowork-related pages and the Home.md and Wiki Ingest Log to understand the patterns.


Read

/workspace/extra/second-brain/wiki/sources/Claude Blog - Best Practices for Claude Cowork.md


1	# Claude Blog — Best Practices for Getting Started with Claude Cowork
2
3	**Source:** https://claude.com/blog/best-practices-for-getting-started-with-claude-cowork
4	**Author:** Austin Lau (Growth Marketing Lead, Anthropic)
5	**Date:** June 3, 2026
6	**Reading time:** 5 min
7
8	## Summary
9	Practical guide to Claude Cowork for non-technical knowledge workers. Key framing: Cowork brings Claude to your work (delegated autonomous execution), while Chat is you bringing questions to Claude.
10
11	## The tool selection matrix
12
13	| Tool | Use when |
14	|------|----------|
15	| **Chat** | Quick exchanges: questions, brainstorming, feedback — "a few exchanges" |
16	| **Claude Cowork** | Delegated work with file output: read 3 months of meeting notes → build QBR deck |
17	| **Claude Code** | Software developers building and shipping code |
18
19	Same underlying Claude models — different contexts and use cases.
20
21	## 5 ingredients of a Cowork-shaped task
22	1. Multiple inputs (files, folders, connected apps)
23	2. File output (document, deck, spreadsheet)
24	3. Recurring execution potential
25	4. Known quality standards
26	5. Tedious middle sections: extraction, compilation, reconciliation
27
28	## Real-world automation examples
29	- **Daily briefing** — 6am scan of Slack + email, categorize, flag incidents
30	- **Budget pacing** — live HTML dashboard from Google Ads + Meta Ads, auto run-rate calculations
31	- **Weekly reporting** — Google Search Console → reconcile dimensions → auto-generate report with comparisons
32
33	## The most important insight
34	> "The difference between mediocre and great Claude Cowork output is almost never your prompt, but whether you're providing enough rich context for Claude to work with."
35
36	## Getting started tip
37	Ask Claude to repeat the task back before executing: "Before we begin, repeat my ask back to me, then ask me as many clarifying questions as you have." Catches scope misalignment before it runs.
38
39	## Related
40	- [[Claude Blog - Founders Playbook]] — Chat/Cowork/Claude Code selection framework (complementary)
41	- [[Claude Code Dynamic Workflows]] — Claude Code's parallel to Cowork's delegated execution model
42

/workspace/extra/second-brain/wiki/sources/Claude Blog - Best Practices for Claude Cowork.md

# Claude Blog — Best Practices for Getting Started with Claude Cowork

**Source:** https://claude.com/blog/best-practices-for-getting-started-with-claude-cowork
**Author:** Austin Lau (Growth Marketing Lead, Anthropic)
**Date:** June 3, 2026
**Reading time:** 5 min

## Summary
Practical guide to Claude Cowork for non-technical knowledge workers. Key framing: Cowork brings Claude to your work (delegated autonomous execution), while Chat is you bringing questions to Claude.

## The tool selection matrix

| Tool | Use when |
|------|----------|
| **Chat** | Quick exchanges: questions, brainstorming, feedback — "a few exchanges" |
| **Claude Cowork** | Delegated work with file output: read 3 months of meeting notes → build QBR deck |
| **Claude Code** | Software developers building and shipping code |

Same underlying Claude models — different contexts and use cases.

## 5 ingredients of a Cowork-shaped task
1. Multiple inputs (files, folders, connected apps)
2. File output (document, deck, spreadsheet)
3. Recurring execution potential
4. Known quality standards
5. Tedious middle sections: extraction, compilation, reconciliation

## Real-world automation examples
- **Daily briefing** — 6am scan of Slack + email, categorize, flag incidents
- **Budget pacing** — live HTML dashboard from Google Ads + Meta Ads, auto run-rate calculations
- **Weekly reporting** — Google Search Console → reconcile dimensions → auto-generate report with comparisons

## The most important insight
> "The difference between mediocre and great Claude Cowork output is almost never your prompt, but whether you're providing enough rich context for Claude to work with."

## Getting started tip
Ask Claude to repeat the task back before executing: "Before we begin, repeat my ask back to me, then ask me as many clarifying questions as you have." Catches scope misalignment before it runs.

## Related
- [[Claude Blog - Founders Playbook]] — Chat/Cowork/Claude Code selection framework (complementary)
- [[Claude Code Dynamic Workflows]] — Claude Code's parallel to Cowork's delegated execution model


1	# Wiki Index
2
3	A catalog of everything in this knowledge base. Updated by Nano on every ingest.
4
5	## Tools & Software
6	*Guest-endorsed or actively used — not sponsors.*
7	- [[Agent Browser]] — Vercel Labs Rust CLI for AI-driven browser automation. Credential vault, accessibility-tree refs, React introspection, HAR recording.
8	- [[Devin]] — AI coding agent by Cognition. 15-thread code factory model.
9	- [[OpenClaw]] — Open-source AI executive assistant / chief of staff.
10	- [[ClawChief]] — Ryan Carson's open-sourced OpenClaw chief-of-staff config.
11	- [[Claude Code]] — Anthropic's coding agent. Ryan Carson's preferred coding tool.
12	- [[Codex]] — OpenAI's coding agent / browser testing tool.
13	- [[Sentry]] — Error monitoring. Used with Devin for automated bug triage.
14	- [[Tailscale]] — WireGuard mesh network. Used for remote access to Mac Mini services from phone. Includes full recipe for exposing any local port via `tailscale serve` + launchd.
15	- [[Figma]] — Design/wireframing. Visual context layer in Ravi Mehta's system.
16	- [[AgentsView]] — Agent token/cost accounting tool. Useful when new frontier-model pricing appears before dashboards and pricing databases catch up.
17	- [[Teach Skill]] — `/teach` by Matt Pocock. ZPD-based personalized tutor with persistent learning records. Trigger-based (no idle context cost). Claude Code only. Install: `npx skills add mattpocock/skills --skill teach`.
18
19	## Anthropic Official Repos & Resources
20	*Official Anthropic repositories — tools, SDKs, plugins, and reference implementations.*
21	- [[Anthropic Skills Repo]] — Reference implementations of the Claude Agent Skills system. Template for building custom skills.
22	- [[Claude Plugins Official]] — Anthropic's curated plugin marketplace for Claude Code. Install via `/plugin install`.
23	- [[Ralph Loop Plugin]] — Stop-hook-based autonomous iteration loop. Feeds Claude the same prompt until it outputs a completion promise. For well-defined tasks with clear success criteria and automatic verification.
24	- [[Hookify Plugin]] — Create Claude Code hooks from natural language. `/hookify warn me when I use rm -rf` → working hook instantly. No hooks.json editing required.
25	- [[Knowledge Work Plugins]] — 18 open-source role-specific plugins (sales, legal, finance, design, engineering, HR, ops, etc.) built on Claude Agent SDK.
26	- [[Claude for Legal]] — Deep legal workflow plugin suite (transactional + litigation + learning). Integrates with Westlaw, CourtListener.
27	- [[Claude for Life Sciences]] — Research marketplace: PubMed, BioRender, Synapse, Consensus + RNA-seq/Nextflow skills.
28	- [[Claude for Healthcare]] — Healthcare marketplace: FHIR developer, prior-auth review, clinical trial protocols + CMS/NPI servers.
29	- [[Claude for Financial Services]] — 10 named agents (Pitch Agent, GL Reconciler, Market Researcher, KYC Screener, etc.) + 9 vertical skill bundles (IB, ER, PE, WM, fund admin). Deployable as Cowork plugins or Managed Agent templates.
30	- [[Managed Agents]] — Anthropic's hosted agent orchestration platform. Self-hosted sandbox option (tool execution on your infra via outbound-polling worker), mid-session tool/MCP updates, large MCP output auto-offload. Scheduled deployments (cron, no custom infra). Env vars in vaults (credentials injected at network boundary). Opus 4.8 tool-description guidance included.
31	- [[Claude Agent SDK Demos]] — 8 local demo apps showcasing Claude Agent SDK patterns (multi-agent, streaming, email, docs).
32	- [[Claude Agent SDK TypeScript]] — `npm install @anthropic-ai/claude-agent-sdk`. Node.js 18+. Renamed from Claude Code SDK.
33	- [[Claude Agent SDK Python]] — `pip install claude-agent-sdk`. Python 3.10+. In-process MCP servers, hooks as Python functions, CLI bundled in wheel.
34	- [[Claude Cookbooks]] — Copy-paste code recipes and notebooks for Claude API (RAG, tool use, multimodal, agents).
35	- [[Claude Quickstarts]] — Production-ready starter projects: customer support, computer use, browser automation, coding agent.
36	- [[Anthropic Courses]] — 5-course official curriculum: API fundamentals → prompt engineering → real-world prompting → evals → tool use. Jupyter notebooks.
37	- [[Anthropic Prompt Engineering Tutorial]] — 9-chapter interactive prompt engineering course with exercise playgrounds. Available direct API and Amazon Bedrock variants.
38	- [[Claude Code Action]] — GitHub Action that brings Claude into PR review and CI/CD workflows.
39	- [[Defending Code Reference Harness]] — Reference impl for autonomous vuln discovery + human-reviewed patching. gVisor-sandboxed agents. Not actively maintained; Claude Security is the hosted version.
40	- [[Scone Bench]] — 417-task benchmark for evaluating LLM agents on smart-contract vuln discovery/exploitation. Historical DeFi incidents, MCP-based, Docker-sandboxed. From Anthropic Red Team.
41	- [[Claudes C Compiler]] — Claude Opus 4.6 wrote a dependency-free C compiler in Rust from scratch. Compiles PostgreSQL, SQLite, Linux kernel, FFmpeg. Capability showcase, not production-validated.
42	- [[Anthropic Performance Take-Home]] — Open version of Anthropic's original performance engineering take-home. Optimize a VLIW SIMD kernel; Claude Opus 4.5 scored 1,363 cycles vs 147,734 baseline (108× improvement).
43	- [[Claude Code Security Review]] — GitHub Action that auto-scans PRs for security vulnerabilities using Claude.
44	- [[Claude Desktop Buddy]] — ESP32 desk pet + Bluetooth API reference for makers integrating with Claude Desktop.
45	- [[HTML Effectiveness Examples]] — Anthropic's reference collection of single-file HTML artifacts (slide decks, dashboards, editing UIs, diagrams).
46	- [[Claude Code Setup Plugin]] — Official Anthropic plugin that scans your codebase and recommends tailored hooks, skills, MCP servers, subagents, and plugins. Read-only, 1-2 recs per category.
47	- [[Claude Code Monitoring Guide]] — Prometheus + OpenTelemetry toolkit for tracking Claude Code ROI, token spend, and team adoption.
48	- [[GitHub MCP Server]] — GitHub's official MCP server.
49	- [[PineForge MCP]] — Hosted MCP server for real Pine Script v6 backtests. `claude mcp add --transport http pineforge https://mcp.pineforge.dev/mcp`. No key/signup. 245/246 TradingView parity, 100 backtests/week, 13mo Binance data. Docker route for unlimited/custom data. 60+ tools: repos, issues, PRs, code search, security scanning.
50	- [[Devcontainer Features]] — One-line devcontainer.json feature that installs Claude Code CLI in any dev container.
51	- [[Claude Code Routines]] — Scheduled/triggered cloud automation. Runs on Anthropic infrastructure, not your machine. `/schedule` command, API + GitHub + time triggers. Research preview.
52	- [[Long-Running Agent Primitives]] — 3 core primitives (Default-FAIL, Fresh-context evaluator, Handoff) + 2 operator hooks (kill switch, STEER.md). From Anthropic's own patterns.
53	- [[Claude Plugins Community]] — Community plugin marketplace (security-reviewed). Submit at clau.de/plugin-directory-submission.
54	- [[Anthropic CLI]] — `ant` CLI for the Claude Developer Platform API. `brew install anthropics/tap/ant`.
55	- [[Anthropic CWC Workshops]] — 8 Code-with-Claude workshop curricula: Managed Agents, memory primitives (Dreaming Service), eval-driven dev, multi-agent decomposition, Deal Desk reference impl.
56	- [[Agent SDK Workshop]] — Hands-on workshop for Claude Agent SDK: 4-stage guided demo (chat → tools → subagents → memory) + breakout scenarios. Python 3.10+, flip switches in config.py.
57	- [[Long-Horizon Coding Agent Demo]] — Archived AWS re:Invent 2025 demo. GitHub issue → agent builds full-stack app → CloudFront preview → human approval gate. Bedrock AgentCore + Claude Agent SDK.
58	- [[Claude Foundation Models Swift Package]] — Swift package for hybrid Apple-platform apps: on-device model for fast/private tasks, Claude for reasoning + web search. iOS 27+, SPM install. Announced June 2026.
59	- [[Claude Tag Plugins]] — 19 SaaS integration plugins (Jira, Linear, Snowflake, Salesforce, Sentry, Datadog, etc.) via Claude Tag CLI. Credentials injected at runtime; install only what you need.
60	- [[Launch Your Agent]] — Claude Code skill that guides a founder from raw idea to live Claude Managed Agent: interview → scope → deploy → grade → schedule. One session, costs cents.
61	- [[Claude Fable 5 and Mythos 5]] — Anthropic's latest frontier models. Always-on adaptive thinking, new tokenizer (~30% more tokens), refusal stop reason + SDK fallback middleware, 30-day data-retention requirement. Fable 5 = GA; Mythos 5 = Preview.
62
63	## Third-Party Tools & Platforms
64	- [[Legora]] — AI-native operating system for legal teams. Autonomously plans, executes, reviews, and completes complex legal work end-to-end. Built on Claude. "Raises the tide" model: improves with each Claude release.
65
66	## Concepts & Reference Docs
67	- [[Orthogonal Visual Channels on Map Lines]] — Don't recolor a line to encode a boolean when color already carries a scalar; add a near-black dotted overlay (Mapbox: short dash + round cap, dasharray units are line-widths so zoom-scaling is free). Plus a puppeteer pattern for E2E-verifying map layers via the app's own custom events.
68	- [[CLAUDE.md Progressive Disclosure]] — Every-session context files hold only always-relevant rules; situational procedures move to `.claude/docs/` behind trigger-phrased pointers. Measure per-section cost first; add a size budget against regrowth.
69	- [[Claude Constitution]] — Anthropic's foundational values document. CC0 licensed. January 2026.
70	- [[Agentic UI Impedance Mismatch]] — Dario Amodei's framing: agents will complete tasks end-to-end most of the time, but humans need deep-dive inspection capability for the exceptions. No product solves this yet.
71	- [[Claude Code Subagents]] — Separate Claude instances with their own context windows. 5 copy-paste templates (reviewer, test-writer, doc-writer, security, pr-writer). Route to Sonnet for 5× cost savings.
72	- [[WebMCP]] — Chrome's proposed web standard for exposing structured tools to AI agents. Declarative HTML annotations + JS API replace fragile UI actuation. Origin trial in Chrome 149.
73	- [[But For Real Skill]] — Self-audit pattern: follow-up prompt that assumes bugs are present and bullies the AI into finding them. Simulates PR code review. From Josh Pigford's solo-founder skills stack.
74	- [[Claude Code Agent Teams]] — Native experimental feature: Team Lead + Teammates model with shared task list, dependency management, plan approval, and hooks. Enable via env flag. Claude Code only (no Codex/Aider).
75	- [[Claude Code Dynamic Workflows]] — Claude writes its own JS orchestration harness on the fly (`ultracode` keyword). 6 patterns: classify-and-act, fan-out-and-synthesize, adversarial verification, generate-and-filter, tournament, loop-until-done. Opus 4.8 era.
76	- [[Finding Your Unknowns Framework]] — Pre-flight protocol for agentic work. 4-quadrant unknowns model (Known/Unknown × Knowns/Unknowns) + 8 elicitation techniques (blind spot pass, interview mode, reference prompting, implementation plan, explainer artifact, quiz mode). Fable-era shift: user clarity is now the bottleneck, not model capability.
77	- [[AI-Native Engineering Org]] — Fiona Fung (Claude Code eng director): JIT planning, Claude reviews style/bugs/humans review domain, kill obsolete processes, track ramp time + PR cycle time + Claude-assisted commit rate.
78	- [[Claude Code Skills Best Practices]] — Thariq Shihipar: 9 skill categories, Gotchas sections, progressive disclosure via file system, trigger keywords, `${CLAUDE_PLUGIN_DATA}` memory, on-demand hooks. From Anthropic's own usage.
79	- [[X AI Signal Ingestion Source]] — Regular monitored X source for high-signal AI voices. Uses browser-visible/public pages only; no credential extraction or social-account side effects.
80	- [[NanoClaw Slack Mention-Sticky Session Bug]] — Two stacked router bugs made a documented `session_mode='shared'` config inert on threaded adapters (Slack/Discord): a forced per-thread coercion, plus a sticky-engagement check that always did an exact-thread lookup regardless of the wiring's actual session mode. Fix makes `mention-sticky` self-bootstrapping: first message creates the shared session, every message after keeps engaging.
81	- [[NanoClaw REST Fallback Tool-Call Hallucination]] — A toolless LM Studio/Codex fallback rung hallucinated fake tool-call tags (`<read_file .../>`) instead of admitting it had no tools, and the existing `<message>`-block validation only checked the wrapper, not the content, so raw tag soup reached the user. Fixed with an output-side allowlist check + corrective retry + honest fallback, deliberately without over-fitting the routing heuristic.
82
83	## 📢 Sponsor-only mentions
84	*Paid placements — not guest endorsements. Pages exist for reference.*
85	- [[Granola]] — AI meeting notes (Behind the Craft sponsor)
86	- [[Wispr Flow]] — Voice dictation (Behind the Craft sponsor)
87	- [[Linear]] — Project management / AI agent platform (Behind the Craft sponsor)
88
89	## Frameworks & Mental Models
90	- [[Apple Widget Rendering Modes]] — How to design SwiftUI widgets that work in both full-color and monochrome/accented modes (macOS, iOS, watchOS). Luminance zones, arc opacity, adaptive line colors, and `widgetAccentedRenderingMode`.
91	- [[WidgetKit Engineering Pitfalls]] — Infrastructure and data-layer pitfalls: intent-type orphaning, chronod descriptor caching, provider-data siloing, weekly-exhausted 5H row rules (0% + weekly reset + blank chart), and the early-cap reset pattern.
92	- [[Human Sandwich Model]] — Human frames → AI executes → Human judges. Dan Shipper's model for human-AI collaboration.
93	- [[Screenshot-First Visual Verification]] — Screenshots are the only ground truth for visual UI work; code correctness ≠ visual correctness.
94	- [[3-Layer Context Engineering System]] — Functional + Visual + Data layers for polished AI prototypes. Ravi Mehta's framework.
95	- [[Tokenmaxxing]] — Accusation that AI companies inflate token metrics; Boris Cherny's 250% productivity rebuttal.
96	- [[Saaspocalypse]] — Thesis that agents erode SaaS switching costs. Boris Cherny's nuanced take via Seven Powers.
97	- [[Claude Code Drift Problem]] — Config entropy at ~5 months: stale CLAUDE.md, bad folder structure, manual triggers that should be routines.
98	- [[4 AI Digital Employees Framework]] — 4 agent roles to "hire": Research Analyst, Strategic Advisor, Communication Specialist, Operations Manager.
99	- [[Friction-First Development]] — 6-principle philosophy for personal tool building: scratch your own itch, define the friction before the code, resist market-bias. Includes a pre-code Problem & Friction Analysis template.
100	- [[Devin vs Claude Code]] — Head-to-head comparison: philosophy, SWE-Bench (80.8% vs 13.86%), billing model, failure modes. Verdict: Claude Code wins for James's current stage.
101	- [[Frontier Model Qualitative Step Change]] — Pattern for treating credible practitioner reports as eval triggers when a model feels like a major-version jump on long tasks.
102	- [[Builder-Verifier Loop Pattern]] — Every code-writing loop needs a separate verifier running the real app. Builder makes the change; Verifier confirms feature correctness; you read the diff. Boris Cherny's core rule for avoiding confident-but-broken PRs.
103	- [[Question-Led Selling Arc]] — Synthesis of SPIN / Sandler / NEPQ / Oren Klaff / Chris Do into a four-step ask-don't-pitch arc (problem → change → cost → worth) plus a button-driven profiling block. Cross-project pattern for solution-selling sites' stage-2 discovery flow.
104	- [[Frontier Model Extraction Strategy]] — Frontier judgment required to *create*, ordinary intelligence sufficient to *use*. The irreversibility filter test: "Can a cheaper model redo this tomorrow?" Basis for the Learning Law in root CLAUDE.md.
105
106	## Reference
107	- [[Coding Agent Behavior Guide]] — INTJ-A derived instructions for coding agents working with James. Communication style, autonomy rules, pushback expectations, blindspot compensations.
108	- [[Ingestion Pipeline Patterns]] — 6 cost/quality optimization patterns for the wiki ingest pipeline: QFS, chapter chunking, map-reduce, tiered models, prompt caching, RAPTOR. Includes Phase 1–3 implementation order.
109	- [[Instagram Reel Transcription Pipeline]] — agent-browser + OpenAI Whisper pipeline for overnight reel-to-transcript processing. ~$0.003–$0.008/reel.
110	- [[Shared Vault Mount Guide]] — Step-by-step for mounting a shared host directory into multiple NanoClaw agent containers. `additionalMounts` config, allowlist setup, restart flow.
111	- [[Ryan Carson Tool Usage Notes]] — Detailed "how he actually uses it" notes for each tool from the May 24 episode (OpenClaw, Devin, Codex, Claude Code, Sentry, Tailscale, ClawChief).
112
113	## People
114	- [[James Lopez]] — Owner of this wiki. INTJ-A, mobile engineer (LinkedIn iOS), Austin TX. Full personality profile and background.
115	- [[Ramón Lopez]] — James's brother. Sr. Director Digital Manufacturing Architecture at Jabil. 25+ yrs medical device quality (FDA/ISO 13485). Domain expert persona for qip-qien.
116	- [[Ryan Carson]] — 5x founder, building Untangle solo with AI agents.
117	- [[Peter Yang]] — Host of Behind the Craft podcast.
118	- [[Dan Shipper]] — Co-founder of Every. Author of "After Automation."
119	- [[Andrej Karpathy]] — AI researcher and educator. High-signal source on frontier model capability and workflow ergonomics.
120	- [[Simon Willison]] — Developer and LLM tooling analyst. High-signal source on evals, sandboxing, cost accounting, and practical AI tools.
121	- [[Nathaniel Whittemore]] — Host of The AI Daily Brief.
122	- [[Ravi Mehta]] — AI instructor, ex-CPO Tinder. Created 3-layer context engineering system.
123	- [[Boris Cherny]] — Head of Claude Code at Anthropic.
124	- [[Alex Kantrowitz]] — Host of Big Technology Podcast.
125	- [[Gael Breton]] — Co-founder, Authority Hacker. Small biz AI automation practitioner.
126	- [[Mark Webster]] — Co-founder, Authority Hacker.
127	- [[Nufar Gaspar]] — Co-host, The AI Daily Brief.
128	- [[Delba de Oliveira]] — MTS Claude Code engineer at Anthropic. Created "Claude Code Patterns: Feedback loops" video — Cherny's cited breakdown of self-verification.
129	- [[Josh Pigford]] — Solo founder building 5 apps with AI agents. Creator of /but-for-real, /adversarial-code-review, /build, /learnings skills.
130	- [[Max Junestrand]] — Founder/CEO of Legora. Building AI-native OS for legal teams on Claude.
131
132	## Sources
133	- [[AI Daily Brief - The 4 AI Team Members Execs Should Hire Right Now]] — May 25, 2026. Framework for 4 agent roles leaders should implement.
134	- [[Instagram - hegetfunds - Claude Code Team of Developers]] — May 6, 2026. Using plugins/skills to assign specialist developer roles in Claude Code.
135	- [[Authority Hacker - Claude Code Setup Roast]] — May 21, 2026. 5-month setup audit: CLAUDE.md, folder structure, drift problem.
136	- [[Big Technology Podcast - Boris Cherny Claude Code]] — May 20, 2026. Claude Code growth, tokenmaxxing, agents beyond coding.
137	- [[Behind the Craft - Ryan Carson Episode]] — May 24, 2026. Tools for running a solo startup with AI agents.
138	- [[Behind the Craft - Ravi Mehta Context Engineering]] — May 3, 2026. 3-layer context engineering system with live demo.
139	- [[AI Daily Brief - Why Agents Still Need Humans]] — May 24, 2026. Covers Dan Shipper's After Automation essay.
140	- [[Dan Shipper - After Automation Essay]] — May 21, 2026. Why AI creates more expert human work, not less.
141	- [[Cheeky Pint - Dario Amodei Interview]] — Aug 6, 2025 (ingested May 30, 2026). Dario Amodei on Anthropic's business model, market structure, AGI-pilled products, the AI UI problem, regulation, and how he uses AI.
142	- [[Behind the Craft - Josh Pigford AI Skills Stack]] — May 31, 2026. Solo founder's exact AI skills: /build, /adversarial-code-review, /but-for-real (self-audit), /learnings. Transcript pending.
143	- [[CWC - Problem Solvers Max Junestrand Legora]] — June 2, 2026. Legora's bet on Claude as AI-native legal OS. "Raises the tide" model thesis.
144	- [[Authority Hacker - Claude Opus 4.8 Review]] — May 29, 2026. What changed: 4.7 regression fixed, more honest, 4x fewer logic errors in code. Full transcript pending.
145	- [[Claude Blog - Dynamic Workflows in Claude Code]] — June 2, 2026. Claude writes its own JS harness on the fly (`ultracode`). 6 patterns: classify-and-act, fan-out-and-synthesize, adversarial verification, generate-and-filter, tournament, loop-until-done.
146	- [[Claude Blog - Introducing Dynamic Workflows]] — May 28, 2026. Announcement post: availability, plan tiers, Bun Zig→Rust case study (750K lines, 11 days, 99.8% tests passing).
147	- [[Claude Blog - Managed Agents Self-Hosted Sandboxes]] — May 19, 2026. Sandbox providers: Cloudflare, Daytona, Modal, Vercel. MCP Tunnels for private-network MCP servers.
148	- [[Claude Blog - Founders Playbook]] — May 14, 2026. 4 AI-remapped startup stages + Chat/Cowork/Claude Code tool selection matrix. PDF download available.
149	- [[Claude Blog - Running an AI-Native Engineering Org]] — June 3, 2026. Fiona Fung on JIT planning, killing obsolete processes, metrics, and blurred roles.
150	- [[Claude Blog - Lessons from Building Claude Code How We Use Skills]] — June 3, 2026. Thariq Shihipar: 9 skill categories, best practices, distribution models, measurement via PreToolUse hooks.
151	- [[Claude Blog - Claude Cowork Product Guide]] — June 5, 2026. Official product guide: 7 workflow templates, permissions model, plugin usage, 3-tool selection matrix. eBook available.
152	- [[X AI Signal Sweep - 2026-06-09]] — Seed sweep for the regular X source. Captures Karpathy, Simon Willison, Dan Shipper, Ethan Mollick, and Claude Fable 5 / Mythos field reports.
153	- [[Claude Blog - Best Practices for Claude Cowork]] — June 3, 2026. Chat vs Cowork vs Claude Code matrix. 5 ingredients of a Cowork task. Context > prompt quality.
154	- [[Claude Blog - Self-Service Data Analytics with Claude]] — June 3, 2026. 3 failure modes + 4-layer architecture for agentic analytics. 95% query automation at 95% accuracy.
155	- [[0xchromium - Claude Workflows That Run Without You]] — June 4, 2026. 4-part workflow anatomy (Role/Tools/Trigger/Output), 12 workflow templates by role, 5-step build process, copy-paste morning briefing prompt.
156	- [[Andrej Karpathy - How I Use LLMs]] — Feb 27, 2025. 2h11m practical guide: zip-file mental model, LLM council approach, model selection matrix, tool integration hierarchy. Full chapter list.
157	- [[Claude Blog - Claude for Foundation Models]] — June 8, 2026. Swift package for hybrid Apple apps: on-device model + Claude handoff. iOS/macOS 27+, typed Swift inputs, streaming to SwiftUI.
158	- [[Claude Blog - Connector Observability]] — June 8, 2026. Performance dashboards (active users, tool calls, latency by tool) for published MCP connectors. In-app directory submission. Public beta.
159	- [[Reddit - Depureco MCP Case Study]] — June 2026. Depureco (Italian industrial vacuum manufacturer) connected product catalog to Claude via Remote MCP. Key insight: grounded AI becomes more humble and asks better questions — directly applicable to qip-qien and any regulated/safety-critical B2B tool.
160	- [[Mountain Movers - Boris Cherny Loop Definition]] — June 2026. Cherny's 3-stage engineer evolution + definition of a loop as a program that prompts, reads, evaluates, re-prompts. Hard stops, skills vs. plumbing distinction, cost reality (Uber $1,500/mo cap).
161	- [[Claude Blog - Building With Claude Managed Agents]] — June 10, 2026. Foundational engineering post: decoupled harness/sandbox architecture (p50 ~60% / p95 >90% latency reduction), Dreaming (scheduled memory refinement), Outcomes (agent self-grading), context anxiety history, three-phase evolution, when-to-use guidance.
162	- [[Claude Blog - Whats New in Claude Managed Agents]] — June 9, 2026. Two new public beta features: scheduled deployments (cron, no infra) and env vars in vaults (credential injection at network boundary). Customer examples: Rakuten, Notion, Browserbase, Milana.
163	- [[Alpha Batcher - Boris Cherny 5-Day Claude Code Setup]] — June 9, 2026. 5-day progressive setup ladder from Boris Cherny's loop philosophy. Includes embedded "Reflecting on a year of Claude Code" video (18 min) with Cherny & Cat Wu.
164	- [[Boris Cherny - Self-Verification Loops]] — June 9, 2026. Cherny's own statement: self-verification is the mechanism that enables longer autonomous runs. Cites ClaudeDevs video by Delba de Oliveira (839K views).
165	- [[DCBitMax - Bitcoin Power Law Out-of-Sample Test]] — June 10, 2026. Out-of-sample validation of Bitcoin Power Law using Claude Opus 4.8. Froze model at 2016 → 10-year mean residual −0.05σ. Same validation methodology applies to congressional-trading.
166	- [[AdiiX - Claude Trading Bot Architecture]] — June 9, 2026. 7.1M views. Claude Code writes trading logic; Claude Cowork sends 7am/9pm daily briefings. Multi-asset: SPX/NDX mean reversion (15m), crypto momentum (1h), commodities trend (4h). ATR sizing + correlation filter. No repo — marketing post. Architecture applicable to tradingbot25 and congressional-trading.
167	- [[Claude Blog - Field Guide to Claude Fable]] — July 6, 2026. Thariq Shihipar. 4-quadrant unknowns framework, 8 elicitation techniques (blind spot pass, interview mode, reference prompting, implementation plan, explainer, quiz). Core claim: with Fable, output quality is now bottlenecked by user clarity, not model capability.
168
169	[[Wiki Ingest Log]]
170

# Wiki Index

A catalog of everything in this knowledge base. Updated by Nano on every ingest.

## Tools & Software
*Guest-endorsed or actively used — not sponsors.*
- [[Agent Browser]] — Vercel Labs Rust CLI for AI-driven browser automation. Credential vault, accessibility-tree refs, React introspection, HAR recording.
- [[Devin]] — AI coding agent by Cognition. 15-thread code factory model.
- [[OpenClaw]] — Open-source AI executive assistant / chief of staff.
- [[ClawChief]] — Ryan Carson's open-sourced OpenClaw chief-of-staff config.
- [[Claude Code]] — Anthropic's coding agent. Ryan Carson's preferred coding tool.
- [[Codex]] — OpenAI's coding agent / browser testing tool.
- [[Sentry]] — Error monitoring. Used with Devin for automated bug triage.
- [[Tailscale]] — WireGuard mesh network. Used for remote access to Mac Mini services from phone. Includes full recipe for exposing any local port via `tailscale serve` + launchd.
- [[Figma]] — Design/wireframing. Visual context layer in Ravi Mehta's system.
- [[AgentsView]] — Agent token/cost accounting tool. Useful when new frontier-model pricing appears before dashboards and pricing databases catch up.
- [[Teach Skill]] — `/teach` by Matt Pocock. ZPD-based personalized tutor with persistent learning records. Trigger-based (no idle context cost). Claude Code only. Install: `npx skills add mattpocock/skills --skill teach`.

## Anthropic Official Repos & Resources
*Official Anthropic repositories — tools, SDKs, plugins, and reference implementations.*
- [[Anthropic Skills Repo]] — Reference implementations of the Claude Agent Skills system. Template for building custom skills.
- [[Claude Plugins Official]] — Anthropic's curated plugin marketplace for Claude Code. Install via `/plugin install`.
- [[Ralph Loop Plugin]] — Stop-hook-based autonomous iteration loop. Feeds Claude the same prompt until it outputs a completion promise. For well-defined tasks with clear success criteria and automatic verification.
- [[Hookify Plugin]] — Create Claude Code hooks from natural language. `/hookify warn me when I use rm -rf` → working hook instantly. No hooks.json editing required.
- [[Knowledge Work Plugins]] — 18 open-source role-specific plugins (sales, legal, finance, design, engineering, HR, ops, etc.) built on Claude Agent SDK.
- [[Claude for Legal]] — Deep legal workflow plugin suite (transactional + litigation + learning). Integrates with Westlaw, CourtListener.
- [[Claude for Life Sciences]] — Research marketplace: PubMed, BioRender, Synapse, Consensus + RNA-seq/Nextflow skills.
- [[Claude for Healthcare]] — Healthcare marketplace: FHIR developer, prior-auth review, clinical trial protocols + CMS/NPI servers.
- [[Claude for Financial Services]] — 10 named agents (Pitch Agent, GL Reconciler, Market Researcher, KYC Screener, etc.) + 9 vertical skill bundles (IB, ER, PE, WM, fund admin). Deployable as Cowork plugins or Managed Agent templates.
- [[Managed Agents]] — Anthropic's hosted agent orchestration platform. Self-hosted sandbox option (tool execution on your infra via outbound-polling worker), mid-session tool/MCP updates, large MCP output auto-offload. Scheduled deployments (cron, no custom infra). Env vars in vaults (credentials injected at network boundary). Opus 4.8 tool-description guidance included.
- [[Claude Agent SDK Demos]] — 8 local demo apps showcasing Claude Agent SDK patterns (multi-agent, streaming, email, docs).
- [[Claude Agent SDK TypeScript]] — `npm install @anthropic-ai/claude-agent-sdk`. Node.js 18+. Renamed from Claude Code SDK.
- [[Claude Agent SDK Python]] — `pip install claude-agent-sdk`. Python 3.10+. In-process MCP servers, hooks as Python functions, CLI bundled in wheel.
- [[Claude Cookbooks]] — Copy-paste code recipes and notebooks for Claude API (RAG, tool use, multimodal, agents).
- [[Claude Quickstarts]] — Production-ready starter projects: customer support, computer use, browser automation, coding agent.
- [[Anthropic Courses]] — 5-course official curriculum: API fundamentals → prompt engineering → real-world prompting → evals → tool use. Jupyter notebooks.
- [[Anthropic Prompt Engineering Tutorial]] — 9-chapter interactive prompt engineering course with exercise playgrounds. Available direct API and Amazon Bedrock variants.
- [[Claude Code Action]] — GitHub Action that brings Claude into PR review and CI/CD workflows.
- [[Defending Code Reference Harness]] — Reference impl for autonomous vuln discovery + human-reviewed patching. gVisor-sandboxed agents. Not actively maintained; Claude Security is the hosted version.
- [[Scone Bench]] — 417-task benchmark for evaluating LLM agents on smart-contract vuln discovery/exploitation. Historical DeFi incidents, MCP-based, Docker-sandboxed. From Anthropic Red Team.
- [[Claudes C Compiler]] — Claude Opus 4.6 wrote a dependency-free C compiler in Rust from scratch. Compiles PostgreSQL, SQLite, Linux kernel, FFmpeg. Capability showcase, not production-validated.
- [[Anthropic Performance Take-Home]] — Open version of Anthropic's original performance engineering take-home. Optimize a VLIW SIMD kernel; Claude Opus 4.5 scored 1,363 cycles vs 147,734 baseline (108× improvement).
- [[Claude Code Security Review]] — GitHub Action that auto-scans PRs for security vulnerabilities using Claude.
- [[Claude Desktop Buddy]] — ESP32 desk pet + Bluetooth API reference for makers integrating with Claude Desktop.
- [[HTML Effectiveness Examples]] — Anthropic's reference collection of single-file HTML artifacts (slide decks, dashboards, editing UIs, diagrams).
- [[Claude Code Setup Plugin]] — Official Anthropic plugin that scans your codebase and recommends tailored hooks, skills, MCP servers, subagents, and plugins. Read-only, 1-2 recs per category.
- [[Claude Code Monitoring Guide]] — Prometheus + OpenTelemetry toolkit for tracking Claude Code ROI, token spend, and team adoption.
- [[GitHub MCP Server]] — GitHub's official MCP server.
- [[PineForge MCP]] — Hosted MCP server for real Pine Script v6 backtests. `claude mcp add --transport http pineforge https://mcp.pineforge.dev/mcp`. No key/signup. 245/246 TradingView parity, 100 backtests/week, 13mo Binance data. Docker route for unlimited/custom data. 60+ tools: repos, issues, PRs, code search, security scanning.
- [[Devcontainer Features]] — One-line devcontainer.json feature that installs Claude Code CLI in any dev container.
- [[Claude Code Routines]] — Scheduled/triggered cloud automation. Runs on Anthropic infrastructure, not your machine. `/schedule` command, API + GitHub + time triggers. Research preview.
- [[Long-Running Agent Primitives]] — 3 core primitives (Default-FAIL, Fresh-context evaluator, Handoff) + 2 operator hooks (kill switch, STEER.md). From Anthropic's own patterns.
- [[Claude Plugins Community]] — Community plugin marketplace (security-reviewed). Submit at clau.de/plugin-directory-submission.
- [[Anthropic CLI]] — `ant` CLI for the Claude Developer Platform API. `brew install anthropics/tap/ant`.
- [[Anthropic CWC Workshops]] — 8 Code-with-Claude workshop curricula: Managed Agents, memory primitives (Dreaming Service), eval-driven dev, multi-agent decomposition, Deal Desk reference impl.
- [[Agent SDK Workshop]] — Hands-on workshop for Claude Agent SDK: 4-stage guided demo (chat → tools → subagents → memory) + breakout scenarios. Python 3.10+, flip switches in config.py.
- [[Long-Horizon Coding Agent Demo]] — Archived AWS re:Invent 2025 demo. GitHub issue → agent builds full-stack app → CloudFront preview → human approval gate. Bedrock AgentCore + Claude Agent SDK.
- [[Claude Foundation Models Swift Package]] — Swift package for hybrid Apple-platform apps: on-device model for fast/private tasks, Claude for reasoning + web search. iOS 27+, SPM install. Announced June 2026.
- [[Claude Tag Plugins]] — 19 SaaS integration plugins (Jira, Linear, Snowflake, Salesforce, Sentry, Datadog, etc.) via Claude Tag CLI. Credentials injected at runtime; install only what you need.
- [[Launch Your Agent]] — Claude Code skill that guides a founder from raw idea to live Claude Managed Agent: interview → scope → deploy → grade → schedule. One session, costs cents.
- [[Claude Fable 5 and Mythos 5]] — Anthropic's latest frontier models. Always-on adaptive thinking, new tokenizer (~30% more tokens), refusal stop reason + SDK fallback middleware, 30-day data-retention requirement. Fable 5 = GA; Mythos 5 = Preview.

## Third-Party Tools & Platforms
- [[Legora]] — AI-native operating system for legal teams. Autonomously plans, executes, reviews, and completes complex legal work end-to-end. Built on Claude. "Raises the tide" model: improves with each Claude release.

## Concepts & Reference Docs
- [[Orthogonal Visual Channels on Map Lines]] — Don't recolor a line to encode a boolean when color already carries a scalar; add a near-black dotted overlay (Mapbox: short dash + round cap, dasharray units are line-widths so zoom-scaling is free). Plus a puppeteer pattern for E2E-verifying map layers via the app's own custom events.
- [[CLAUDE.md Progressive Disclosure]] — Every-session context files hold only always-relevant rules; situational procedures move to `.claude/docs/` behind trigger-phrased pointers. Measure per-section cost first; add a size budget against regrowth.
- [[Claude Constitution]] — Anthropic's foundational values document. CC0 licensed. January 2026.
- [[Agentic UI Impedance Mismatch]] — Dario Amodei's framing: agents will complete tasks end-to-end most of the time, but humans need deep-dive inspection capability for the exceptions. No product solves this yet.
- [[Claude Code Subagents]] — Separate Claude instances with their own context windows. 5 copy-paste templates (reviewer, test-writer, doc-writer, security, pr-writer). Route to Sonnet for 5× cost savings.
- [[WebMCP]] — Chrome's proposed web standard for exposing structured tools to AI agents. Declarative HTML annotations + JS API replace fragile UI actuation. Origin trial in Chrome 149.
- [[But For Real Skill]] — Self-audit pattern: follow-up prompt that assumes bugs are present and bullies the AI into finding them. Simulates PR code review. From Josh Pigford's solo-founder skills stack.
- [[Claude Code Agent Teams]] — Native experimental feature: Team Lead + Teammates model with shared task list, dependency management, plan approval, and hooks. Enable via env flag. Claude Code only (no Codex/Aider).
- [[Claude Code Dynamic Workflows]] — Claude writes its own JS orchestration harness on the fly (`ultracode` keyword). 6 patterns: classify-and-act, fan-out-and-synthesize, adversarial verification, generate-and-filter, tournament, loop-until-done. Opus 4.8 era.
- [[Finding Your Unknowns Framework]] — Pre-flight protocol for agentic work. 4-quadrant unknowns model (Known/Unknown × Knowns/Unknowns) + 8 elicitation techniques (blind spot pass, interview mode, reference prompting, implementation plan, explainer artifact, quiz mode). Fable-era shift: user clarity is now the bottleneck, not model capability.
- [[AI-Native Engineering Org]] — Fiona Fung (Claude Code eng director): JIT planning, Claude reviews style/bugs/humans review domain, kill obsolete processes, track ramp time + PR cycle time + Claude-assisted commit rate.
- [[Claude Code Skills Best Practices]] — Thariq Shihipar: 9 skill categories, Gotchas sections, progressive disclosure via file system, trigger keywords, `${CLAUDE_PLUGIN_DATA}` memory, on-demand hooks. From Anthropic's own usage.
- [[X AI Signal Ingestion Source]] — Regular monitored X source for high-signal AI voices. Uses browser-visible/public pages only; no credential extraction or social-account side effects.
- [[NanoClaw Slack Mention-Sticky Session Bug]] — Two stacked router bugs made a documented `session_mode='shared'` config inert on threaded adapters (Slack/Discord): a forced per-thread coercion, plus a sticky-engagement check that always did an exact-thread lookup regardless of the wiring's actual session mode. Fix makes `mention-sticky` self-bootstrapping: first message creates the shared session, every message after keeps engaging.
- [[NanoClaw REST Fallback Tool-Call Hallucination]] — A toolless LM Studio/Codex fallback rung hallucinated fake tool-call tags (`<read_file .../>`) instead of admitting it had no tools, and the existing `<message>`-block validation only checked the wrapper, not the content, so raw tag soup reached the user. Fixed with an output-side allowlist check + corrective retry + honest fallback, deliberately without over-fitting the routing heuristic.

## 📢 Sponsor-only mentions
*Paid placements — not guest endorsements. Pages exist for reference.*
- [[Granola]] — AI meeting notes (Behind the Craft sponsor)
- [[Wispr Flow]] — Voice dictation (Behind the Craft sponsor)
- [[Linear]] — Project management / AI agent platform (Behind the Craft sponsor)

## Frameworks & Mental Models
- [[Apple Widget Rendering Modes]] — How to design SwiftUI widgets that work in both full-color and monochrome/accented modes (macOS, iOS, watchOS). Luminance zones, arc opacity, adaptive line colors, and `widgetAccentedRenderingMode`.
- [[WidgetKit Engineering Pitfalls]] — Infrastructure and data-layer pitfalls: intent-type orphaning, chronod descriptor caching, provider-data siloing, weekly-exhausted 5H row rules (0% + weekly reset + blank chart), and the early-cap reset pattern.
- [[Human Sandwich Model]] — Human frames → AI executes → Human judges. Dan Shipper's model for human-AI collaboration.
- [[Screenshot-First Visual Verification]] — Screenshots are the only ground truth for visual UI work; code correctness ≠ visual correctness.
- [[3-Layer Context Engineering System]] — Functional + Visual + Data layers for polished AI prototypes. Ravi Mehta's framework.
- [[Tokenmaxxing]] — Accusation that AI companies inflate token metrics; Boris Cherny's 250% productivity rebuttal.
- [[Saaspocalypse]] — Thesis that agents erode SaaS switching costs. Boris Cherny's nuanced take via Seven Powers.
- [[Claude Code Drift Problem]] — Config entropy at ~5 months: stale CLAUDE.md, bad folder structure, manual triggers that should be routines.
- [[4 AI Digital Employees Framework]] — 4 agent roles to "hire": Research Analyst, Strategic Advisor, Communication Specialist, Operations Manager.
- [[Friction-First Development]] — 6-principle philosophy for personal tool building: scratch your own itch, define the friction before the code, resist market-bias. Includes a pre-code Problem & Friction Analysis template.
- [[Devin vs Claude Code]] — Head-to-head comparison: philosophy, SWE-Bench (80.8% vs 13.86%), billing model, failure modes. Verdict: Claude Code wins for James's current stage.
- [[Frontier Model Qualitative Step Change]] — Pattern for treating credible practitioner reports as eval triggers when a model feels like a major-version jump on long tasks.
- [[Builder-Verifier Loop Pattern]] — Every code-writing loop needs a separate verifier running the real app. Builder makes the change; Verifier confirms feature correctness; you read the diff. Boris Cherny's core rule for avoiding confident-but-broken PRs.
- [[Question-Led Selling Arc]] — Synthesis of SPIN / Sandler / NEPQ / Oren Klaff / Chris Do into a four-step ask-don't-pitch arc (problem → change → cost → worth) plus a button-driven profiling block. Cross-project pattern for solution-selling sites' stage-2 discovery flow.
- [[Frontier Model Extraction Strategy]] — Frontier judgment required to *create*, ordinary intelligence sufficient to *use*. The irreversibility filter test: "Can a cheaper model redo this tomorrow?" Basis for the Learning Law in root CLAUDE.md.

## Reference
- [[Coding Agent Behavior Guide]] — INTJ-A derived instructions for coding agents working with James. Communication style, autonomy rules, pushback expectations, blindspot compensations.
- [[Ingestion Pipeline Patterns]] — 6 cost/quality optimization patterns for the wiki ingest pipeline: QFS, chapter chunking, map-reduce, tiered models, prompt caching, RAPTOR. Includes Phase 1–3 implementation order.
- [[Instagram Reel Transcription Pipeline]] — agent-browser + OpenAI Whisper pipeline for overnight reel-to-transcript processing. ~$0.003–$0.008/reel.
- [[Shared Vault Mount Guide]] — Step-by-step for mounting a shared host directory into multiple NanoClaw agent containers. `additionalMounts` config, allowlist setup, restart flow.
- [[Ryan Carson Tool Usage Notes]] — Detailed "how he actually uses it" notes for each tool from the May 24 episode (OpenClaw, Devin, Codex, Claude Code, Sentry, Tailscale, ClawChief).

## People
- [[James Lopez]] — Owner of this wiki. INTJ-A, mobile engineer (LinkedIn iOS), Austin TX. Full personality profile and background.
- [[Ramón Lopez]] — James's brother. Sr. Director Digital Manufacturing Architecture at Jabil. 25+ yrs medical device quality (FDA/ISO 13485). Domain expert persona for qip-qien.
- [[Ryan Carson]] — 5x founder, building Untangle solo with AI agents.
- [[Peter Yang]] — Host of Behind the Craft podcast.
- [[Dan Shipper]] — Co-founder of Every. Author of "After Automation."
- [[Andrej Karpathy]] — AI researcher and educator. High-signal source on frontier model capability and workflow ergonomics.
- [[Simon Willison]] — Developer and LLM tooling analyst. High-signal source on evals, sandboxing, cost accounting, and practical AI tools.
- [[Nathaniel Whittemore]] — Host of The AI Daily Brief.
- [[Ravi Mehta]] — AI instructor, ex-CPO Tinder. Created 3-layer context engineering system.
- [[Boris Cherny]] — Head of Claude Code at Anthropic.
- [[Alex Kantrowitz]] — Host of Big Technology Podcast.
- [[Gael Breton]] — Co-founder, Authority Hacker. Small biz AI automation practitioner.
- [[Mark Webster]] — Co-founder, Authority Hacker.
- [[Nufar Gaspar]] — Co-host, The AI Daily Brief.
- [[Delba de Oliveira]] — MTS Claude Code engineer at Anthropic. Created "Claude Code Patterns: Feedback loops" video — Cherny's cited breakdown of self-verification.
- [[Josh Pigford]] — Solo founder building 5 apps with AI agents. Creator of /but-for-real, /adversarial-code-review, /build, /learnings skills.
- [[Max Junestrand]] — Founder/CEO of Legora. Building AI-native OS for legal teams on Claude.

## Sources
- [[AI Daily Brief - The 4 AI Team Members Execs Should Hire Right Now]] — May 25, 2026. Framework for 4 agent roles leaders should implement.
- [[Instagram - hegetfunds - Claude Code Team of Developers]] — May 6, 2026. Using plugins/skills to assign specialist developer roles in Claude Code.
- [[Authority Hacker - Claude Code Setup Roast]] — May 21, 2026. 5-month setup audit: CLAUDE.md, folder structure, drift problem.
- [[Big Technology Podcast - Boris Cherny Claude Code]] — May 20, 2026. Claude Code growth, tokenmaxxing, agents beyond coding.
- [[Behind the Craft - Ryan Carson Episode]] — May 24, 2026. Tools for running a solo startup with AI agents.
- [[Behind the Craft - Ravi Mehta Context Engineering]] — May 3, 2026. 3-layer context engineering system with live demo.
- [[AI Daily Brief - Why Agents Still Need Humans]] — May 24, 2026. Covers Dan Shipper's After Automation essay.
- [[Dan Shipper - After Automation Essay]] — May 21, 2026. Why AI creates more expert human work, not less.
- [[Cheeky Pint - Dario Amodei Interview]] — Aug 6, 2025 (ingested May 30, 2026). Dario Amodei on Anthropic's business model, market structure, AGI-pilled products, the AI UI problem, regulation, and how he uses AI.
- [[Behind the Craft - Josh Pigford AI Skills Stack]] — May 31, 2026. Solo founder's exact AI skills: /build, /adversarial-code-review, /but-for-real (self-audit), /learnings. Transcript pending.
- [[CWC - Problem Solvers Max Junestrand Legora]] — June 2, 2026. Legora's bet on Claude as AI-native legal OS. "Raises the tide" model thesis.
- [[Authority Hacker - Claude Opus 4.8 Review]] — May 29, 2026. What changed: 4.7 regression fixed, more honest, 4x fewer logic errors in code. Full transcript pending.
- [[Claude Blog - Dynamic Workflows in Claude Code]] — June 2, 2026. Claude writes its own JS harness on the fly (`ultracode`). 6 patterns: classify-and-act, fan-out-and-synthesize, adversarial verification, generate-and-filter, tournament, loop-until-done.
- [[Claude Blog - Introducing Dynamic Workflows]] — May 28, 2026. Announcement post: availability, plan tiers, Bun Zig→Rust case study (750K lines, 11 days, 99.8% tests passing).
- [[Claude Blog - Managed Agents Self-Hosted Sandboxes]] — May 19, 2026. Sandbox providers: Cloudflare, Daytona, Modal, Vercel. MCP Tunnels for private-network MCP servers.
- [[Claude Blog - Founders Playbook]] — May 14, 2026. 4 AI-remapped startup stages + Chat/Cowork/Claude Code tool selection matrix. PDF download available.
- [[Claude Blog - Running an AI-Native Engineering Org]] — June 3, 2026. Fiona Fung on JIT planning, killing obsolete processes, metrics, and blurred roles.
- [[Claude Blog - Lessons from Building Claude Code How We Use Skills]] — June 3, 2026. Thariq Shihipar: 9 skill categories, best practices, distribution models, measurement via PreToolUse hooks.
- [[Claude Blog - Claude Cowork Product Guide]] — June 5, 2026. Official product guide: 7 workflow templates, permissions model, plugin usage, 3-tool selection matrix. eBook available.
- [[X AI Signal Sweep - 2026-06-09]] — Seed sweep for the regular X source. Captures Karpathy, Simon Willison, Dan Shipper, Ethan Mollick, and Claude Fable 5 / Mythos field reports.
- [[Claude Blog - Best Practices for Claude Cowork]] — June 3, 2026. Chat vs Cowork vs Claude Code matrix. 5 ingredients of a Cowork task. Context > prompt quality.
- [[Claude Blog - Self-Service Data Analytics with Claude]] — June 3, 2026. 3 failure modes + 4-layer architecture for agentic analytics. 95% query automation at 95% accuracy.
- [[0xchromium - Claude Workflows That Run Without You]] — June 4, 2026. 4-part workflow anatomy (Role/Tools/Trigger/Output), 12 workflow templates by role, 5-step build process, copy-paste morning briefing prompt.
- [[Andrej Karpathy - How I Use LLMs]] — Feb 27, 2025. 2h11m practical guide: zip-file mental model, LLM council approach, model selection matrix, tool integration hierarchy. Full chapter list.
- [[Claude Blog - Claude for Foundation Models]] — June 8, 2026. Swift package for hybrid Apple apps: on-device model + Claude handoff. iOS/macOS 27+, typed Swift inputs, streaming to SwiftUI.
- [[Claude Blog - Connector Observability]] — June 8, 2026. Performance dashboards (active users, tool calls, latency by tool) for published MCP connectors. In-app directory submission. Public beta.
- [[Reddit - Depureco MCP Case Study]] — June 2026. Depureco (Italian industrial vacuum manufacturer) connected product catalog to Claude via Remote MCP. Key insight: grounded AI becomes more humble and asks better questions — directly applicable to qip-qien and any regulated/safety-critical B2B tool.
- [[Mountain Movers - Boris Cherny Loop Definition]] — June 2026. Cherny's 3-stage engineer evolution + definition of a loop as a program that prompts, reads, evaluates, re-prompts. Hard stops, skills vs. plumbing distinction, cost reality (Uber $1,500/mo cap).
- [[Claude Blog - Building With Claude Managed Agents]] — June 10, 2026. Foundational engineering post: decoupled harness/sandbox architecture (p50 ~60% / p95 >90% latency reduction), Dreaming (scheduled memory refinement), Outcomes (agent self-grading), context anxiety history, three-phase evolution, when-to-use guidance.
- [[Claude Blog - Whats New in Claude Managed Agents]] — June 9, 2026. Two new public beta features: scheduled deployments (cron, no infra) and env vars in vaults (credential injection at network boundary). Customer examples: Rakuten, Notion, Browserbase, Milana.
- [[Alpha Batcher - Boris Cherny 5-Day Claude Code Setup]] — June 9, 2026. 5-day progressive setup ladder from Boris Cherny's loop philosophy. Includes embedded "Reflecting on a year of Claude Code" video (18 min) with Cherny & Cat Wu.
- [[Boris Cherny - Self-Verification Loops]] — June 9, 2026. Cherny's own statement: self-verification is the mechanism that enables longer autonomous runs. Cites ClaudeDevs video by Delba de Oliveira (839K views).
- [[DCBitMax - Bitcoin Power Law Out-of-Sample Test]] — June 10, 2026. Out-of-sample validation of Bitcoin Power Law using Claude Opus 4.8. Froze model at 2016 → 10-year mean residual −0.05σ. Same validation methodology applies to congressional-trading.
- [[AdiiX - Claude Trading Bot Architecture]] — June 9, 2026. 7.1M views. Claude Code writes trading logic; Claude Cowork sends 7am/9pm daily briefings. Multi-asset: SPX/NDX mean reversion (15m), crypto momentum (1h), commodities trend (4h). ATR sizing + correlation filter. No repo — marketing post. Architecture applicable to tradingbot25 and congressional-trading.
- [[Claude Blog - Field Guide to Claude Fable]] — July 6, 2026. Thariq Shihipar. 4-quadrant unknowns framework, 8 elicitation techniques (blind spot pass, interview mode, reference prompting, implementation plan, explainer, quiz). Core claim: with Fable, output quality is now bottlenecked by user clarity, not model capability.

[[Wiki Ingest Log]]


Now let me check the Wiki Ingest Log to understand the format.


1	# Ingest Log
2
3	Chronological record of everything added to this wiki.
4
5	---
6
7	## 2026-07-08 (NanoClaw provider fallback tool-hallucination fix)
8
9	- **[[NanoClaw REST Fallback Tool-Call Hallucination]]** (new concept, internal-origin) — From a `/goal` session fixing garbled non-English-looking Slack replies. Root cause: a generic "please follow up" message didn't match the `needsClaudeCode()` keyword heuristic, so it routed to the toolless LM Studio fallback rung, which hallucinated a fake `<read_file .../>` tool-call tag instead of admitting it had no tools — and the existing `<message>`-block validation only checked the wrapper, not the content, so the raw tag reached the user. Fixed with an output-side tag-allowlist check + corrective retry + honest fallback message, deliberately not by tightening the routing heuristic (which can never cover every phrasing). RED→GREEN tests replay the exact reported text in `gemini-openai-claude.test.ts`.
10
11	## 2026-07-08 (Claude blog check)
12
13	- **Thomson Reuters / Fiduciary-Grade AI** — customer case study for legal/professional services vertical. No new Claude capabilities or engineering insights. Skipped per policy.
14
15	## 2026-07-08 (NanoClaw Slack engagement fix)
16
17	- **[[NanoClaw Slack Mention-Sticky Session Bug]]** (new concept, internal-origin) — From a `/goal` session fixing NanoClaw's Slack bot only replying to explicit `@mentions`. Root cause was two stacked router bugs: `session_mode='shared'` was unconditionally coerced to `'per-thread'` for any threaded-adapter (Slack/Discord/…) group chat, and `mention-sticky`'s engagement check always did an exact-thread session lookup regardless of the wiring's actual `session_mode`. Combined with Slack's own per-message thread-id fallback (an un-threaded reply gets its own fresh thread id), a plain reply to the bot's own question could never be recognized as a continuation. Fixed by honoring `session_mode` as configured and adding a scope-aware session lookup; RED→GREEN regression test in `src/host-core.test.ts`.
18
19	## 2026-07-08 (Anthropic GitHub sweep #24)
20
21	- No new wiki pages needed — all 30 updated repos in the `anthropics` org were already covered by sweep #23 (2026-07-07) or are not relevant (buffa, model-cards, financial-services/life-sciences/legal verticals, courses).
22	- No new skill commits (`newSkillCommits: []`).
23	- Repos verified as current: `launch-your-agent`, `cwc-long-running-agents`, `claude-agent-sdk-typescript`, `claude-agent-sdk-python`, `claude-tag-plugins`, `knowledge-work-plugins`, `defending-code-reference-harness`, `claudes-c-compiler`, `claude-plugins-official`, `claude-plugins-community`, `claude-code-action`, `claude-code-security-review`.
24
25	## 2026-07-07 (RoadSense ridden-indicator fix)
26
27	- **[[Orthogonal Visual Channels on Map Lines]]** (new concept, internal-origin) — From the RoadSense ridden-roads fix: keep line color reserved for the score, encode the ridden boolean as a near-black dotted overlay (Mapbox `line-dasharray` short-dash + round-cap dots; dasharray units are line-widths so dot spacing zoom-scales for free; overlay goes topmost to avoid junction clipping). Includes the puppeteer E2E pattern of driving the map via the app's own CustomEvents and toggling state through the public API.
28
29	## 2026-07-07 (Anthropic GitHub sweep #23)
30

# Ingest Log

Chronological record of everything added to this wiki.

---

## 2026-07-08 (NanoClaw provider fallback tool-hallucination fix)

- **[[NanoClaw REST Fallback Tool-Call Hallucination]]** (new concept, internal-origin) — From a `/goal` session fixing garbled non-English-looking Slack replies. Root cause: a generic "please follow up" message didn't match the `needsClaudeCode()` keyword heuristic, so it routed to the toolless LM Studio fallback rung, which hallucinated a fake `<read_file .../>` tool-call tag instead of admitting it had no tools — and the existing `<message>`-block validation only checked the wrapper, not the content, so the raw tag reached the user. Fixed with an output-side tag-allowlist check + corrective retry + honest fallback message, deliberately not by tightening the routing heuristic (which can never cover every phrasing). RED→GREEN tests replay the exact reported text in `gemini-openai-claude.test.ts`.

## 2026-07-08 (Claude blog check)

- **Thomson Reuters / Fiduciary-Grade AI** — customer case study for legal/professional services vertical. No new Claude capabilities or engineering insights. Skipped per policy.

## 2026-07-08 (NanoClaw Slack engagement fix)

- **[[NanoClaw Slack Mention-Sticky Session Bug]]** (new concept, internal-origin) — From a `/goal` session fixing NanoClaw's Slack bot only replying to explicit `@mentions`. Root cause was two stacked router bugs: `session_mode='shared'` was unconditionally coerced to `'per-thread'` for any threaded-adapter (Slack/Discord/…) group chat, and `mention-sticky`'s engagement check always did an exact-thread session lookup regardless of the wiring's actual `session_mode`. Combined with Slack's own per-message thread-id fallback (an un-threaded reply gets its own fresh thread id), a plain reply to the bot's own question could never be recognized as a continuation. Fixed by honoring `session_mode` as configured and adding a scope-aware session lookup; RED→GREEN regression test in `src/host-core.test.ts`.

## 2026-07-08 (Anthropic GitHub sweep #24)

- No new wiki pages needed — all 30 updated repos in the `anthropics` org were already covered by sweep #23 (2026-07-07) or are not relevant (buffa, model-cards, financial-services/life-sciences/legal verticals, courses).
- No new skill commits (`newSkillCommits: []`).
- Repos verified as current: `launch-your-agent`, `cwc-long-running-agents`, `claude-agent-sdk-typescript`, `claude-agent-sdk-python`, `claude-tag-plugins`, `knowledge-work-plugins`, `defending-code-reference-harness`, `claudes-c-compiler`, `claude-plugins-official`, `claude-plugins-community`, `claude-code-action`, `claude-code-security-review`.

## 2026-07-07 (RoadSense ridden-indicator fix)

- **[[Orthogonal Visual Channels on Map Lines]]** (new concept, internal-origin) — From the RoadSense ridden-roads fix: keep line color reserved for the score, encode the ridden boolean as a near-black dotted overlay (Mapbox `line-dasharray` short-dash + round-cap dots; dasharray units are line-widths so dot spacing zoom-scales for free; overlay goes topmost to avoid junction clipping). Includes the puppeteer E2E pattern of driving the map via the app's own CustomEvents and toggling state through the public API.

## 2026-07-07 (Anthropic GitHub sweep #23)


Now I have enough context. Let me evaluate relevance more carefully:

This post is about Anthropic's own marketing operations team using Claude Cowork. The CLAUDE.local.md says to skip "customer case studies for specific industries (finance team, sales leader)." This is Anthropic's own internal team, not a customer. And the content reveals genuinely useful workflow patterns:
- Dispatcher routing pattern
- Audit agent pattern
- Skill refinement loops ("ask Claude to summarize what came up that should go back into the skills")
- Scheduled task automation patterns
- Multi-agent specialist architecture
This is different from a "marketing team at BigCorp uses Claude Cowork" case study—it's Anthropic showcasing their own internal usage with concrete workflow patterns. Looking at what concept pages already exist, I see there's "Claude Code Skills Best Practices" and "Builder-Verifier Loop Pattern," but the new patterns here are the dispatcher-specialist multi-agent routing approach and the independent audit agent verification model.

The main novel concept is the dispatcher routing to specialists with quality control, which is distinct enough to warrant its own concept page. I'll create a source page from the blog post and a corresponding concept page for the dispatcher-specialist pattern, then update the home index and ingest log.


Relevant — Anthropic's own team, not a customer, and it reveals concrete multi-agent workflow patterns (dispatcher, audit agent, skill refinement loops). I'll write the source and concept pages now.


Write

/workspace/extra/second-brain/wiki/sources/Claude Blog - Marketing Ops Cowork Automation.md

# Claude Blog — How Anthropic's Marketing Ops Team Uses Claude Cowork to Automate Reporting and Campaign Builds

**Source:** https://claude.com/blog/how-anthropics-marketing-operations-team-uses-claude-cowork-to-automate-reporting-and-campaign-builds
**Authors:** Ian Chan and Annabel Custer (Anthropic marketing operations)
**Date:** July 8, 2026
**Reading time:** ~6 min

## Summary

Anthropic's own marketing ops team shows two real Cowork deployments: automated weekly metrics reporting and event/campaign build orchestration. Useful for the concrete workflow patterns, not the domain (marketing).

---

## Workflow 1 — Weekly Metrics Reporting (Ian Chan)

**Before:** 1–2 days of manual data collection across Slack, meeting transcripts, and a data warehouse.
**After:** ~2 hours of validation. Report drafts arrive Sunday evening.

### How it runs
- Scheduled Cowork task fires Sunday evening
- Claude reads prior reports, meeting transcripts, Slack messages, queries data warehouse
- Uses a chain of **skills**: Prep → Proofreading → Action-items
- Returns a drafted report with suggested focus areas and flagged mismatches

### What changed for Ian
Work shifted from data collection to **enablement, validation, and data layer refinement** — maintaining the skill instructions and ensuring the data sources are clean.

---

## Workflow 2 — Event & Campaign Builds (Annabel Custer)

**Before:** Manual builds across Salesforce, HubSpot, Swoogo, email tools, Asana, Google Drive, landing page builders.
**After:** Request submitted via Slack form → Claude routes and executes → Annabel reviews audit output.

### How it runs
1. Requestors submit via a dedicated Slack channel form
2. **Dispatcher skill** reads the channel hourly and routes to the right specialist
3. Specialist skills: event-build, webinar landing page, audit, apply-to-attend, approval-support, data-import
4. **Audit agent** (independent Claude instance) tests registrations and verifies outputs before completion
5. Annabel reviews audit results; only ships if audit passes

### Key design decisions
- Hourly dispatcher prevents duplicate/conflicting runs
- Audit is a *separate* Claude instance — not the same agent self-checking
- Skills are modular and independently updatable

---

## Key Patterns

| Pattern | Description |
|---------|-------------|
| **Dispatcher routing** | One scheduled agent reads intake and routes to specialist agents by task type |
| **Audit agent** | Independent agent verifies outputs before they ship — avoids self-check blind spots |
| **Skills as living systems** | "Ask Claude to summarize what came up that should go back into the skills" — corrections flow back into instructions |
| **Proofreading skill** | Verification step for reports: catches errors before human review |
| **Scheduled automation** | Sunday-evening trigger for weekly work; hourly routing check |

---

## Practical advice from the article

- **Start with proofreading skills** for report workflows
- **Build scheduled tasks** for recurring work that currently requires manual triggering
- Use reflection prompts to improve skills: "Summarize corrections made this run → update skill instructions"
- Data validation rule: **flag mismatches, don't guess** — trace numbers to verified sources

---

## Related
- [[Claude Blog - Best Practices for Claude Cowork]] — 5-ingredient framework for Cowork-shaped tasks
- [[Claude Blog - Claude Cowork Product Guide]] — 7 workflow templates, permissions, plugin model
- [[Claude Blog - Self-Service Data Analytics with Claude]] — 4-layer agentic analytics architecture
- [[Cowork Dispatcher-Specialist Pattern]] — Concept page for the dispatcher/audit/skill-refinement architecture shown here
- [[Builder-Verifier Loop Pattern]] — Boris Cherny's framing of the same separation-of-concerns principle in code


File created successfully at: /workspace/extra/second-brain/wiki/sources/Claude Blog - Marketing Ops Cowork Automation.md (file state is current in your context — no need to Read it back)

# Claude Blog — How Anthropic's Marketing Ops Team Uses Claude Cowork to Automate Reporting and Campaign Builds

**Source:** https://claude.com/blog/how-anthropics-marketing-operations-team-uses-claude-cowork-to-automate-reporting-and-campaign-builds
**Authors:** Ian Chan and Annabel Custer (Anthropic marketing operations)
**Date:** July 8, 2026
**Reading time:** ~6 min

## Summary

Anthropic's own marketing ops team shows two real Cowork deployments: automated weekly metrics reporting and event/campaign build orchestration. Useful for the concrete workflow patterns, not the domain (marketing).

---

## Workflow 1 — Weekly Metrics Reporting (Ian Chan)

**Before:** 1–2 days of manual data collection across Slack, meeting transcripts, and a data warehouse.
**After:** ~2 hours of validation. Report drafts arrive Sunday evening.

### How it runs
- Scheduled Cowork task fires Sunday evening
- Claude reads prior reports, meeting transcripts, Slack messages, queries data warehouse
- Uses a chain of **skills**: Prep → Proofreading → Action-items
- Returns a drafted report with suggested focus areas and flagged mismatches

### What changed for Ian
Work shifted from data collection to **enablement, validation, and data layer refinement** — maintaining the skill instructions and ensuring the data sources are clean.

---

## Workflow 2 — Event & Campaign Builds (Annabel Custer)

**Before:** Manual builds across Salesforce, HubSpot, Swoogo, email tools, Asana, Google Drive, landing page builders.
**After:** Request submitted via Slack form → Claude routes and executes → Annabel reviews audit output.

### How it runs
1. Requestors submit via a dedicated Slack channel form
2. **Dispatcher skill** reads the channel hourly and routes to the right specialist
3. Specialist skills: event-build, webinar landing page, audit, apply-to-attend, approval-support, data-import
4. **Audit agent** (independent Claude instance) tests registrations and verifies outputs before completion
5. Annabel reviews audit results; only ships if audit passes

### Key design decisions
- Hourly dispatcher prevents duplicate/conflicting runs
- Audit is a *separate* Claude instance — not the same agent self-checking
- Skills are modular and independently updatable

---

## Key Patterns

| Pattern | Description |
|---------|-------------|
| **Dispatcher routing** | One scheduled agent reads intake and routes to specialist agents by task type |
| **Audit agent** | Independent agent verifies outputs before they ship — avoids self-check blind spots |
| **Skills as living systems** | "Ask Claude to summarize what came up that should go back into the skills" — corrections flow back into instructions |
| **Proofreading skill** | Verification step for reports: catches errors before human review |
| **Scheduled automation** | Sunday-evening trigger for weekly work; hourly routing check |

---

## Practical advice from the article

- **Start with proofreading skills** for report workflows
- **Build scheduled tasks** for recurring work that currently requires manual triggering
- Use reflection prompts to improve skills: "Summarize corrections made this run → update skill instructions"
- Data validation rule: **flag mismatches, don't guess** — trace numbers to verified sources

---

## Related
- [[Claude Blog - Best Practices for Claude Cowork]] — 5-ingredient framework for Cowork-shaped tasks
- [[Claude Blog - Claude Cowork Product Guide]] — 7 workflow templates, permissions, plugin model
- [[Claude Blog - Self-Service Data Analytics with Claude]] — 4-layer agentic analytics architecture
- [[Cowork Dispatcher-Specialist Pattern]] — Concept page for the dispatcher/audit/skill-refinement architecture shown here
- [[Builder-Verifier Loop Pattern]] — Boris Cherny's framing of the same separation-of-concerns principle in code


# Cowork Dispatcher-Specialist Pattern

**Origin:** [[Claude Blog - Marketing Ops Cowork Automation]] (Anthropic internal, July 8, 2026)

## What it is

A three-layer multi-agent architecture for high-volume intake workflows:

1. **Dispatcher** — Scheduled agent that reads an intake channel/queue and routes each request to the right specialist. Runs on a short cadence (e.g., hourly) to prevent duplicate runs and enforce ordering.
2. **Specialist agents** — Purpose-built skills or Claude instances for specific task types (e.g., event-build, webinar landing page, data-import). Each has focused instructions and narrow scope.
3. **Audit agent** — *Independent* Claude instance that verifies specialist output before it ships. Key: the same agent that built the output cannot reliably self-check it.

```
Intake channel
      │
[Dispatcher - runs hourly]
      │
      ├── event-build skill
      ├── webinar landing page skill
      ├── data-import skill
      └── ... other specialists
                    │
              [Audit agent]  ← separate Claude instance
                    │
             Human review → ship
```

## Why the audit agent is separate

Asking the same Claude instance that built something to check it introduces the same blind spots that caused the bug. A separate instance starts cold, runs the same checks without any continuity bias, and is more likely to catch mismatch or missing steps.

## Skills as living systems

Both workflows in the article emphasized that the system improves continuously:
- After each run, reflect: *"What corrections were made this run that should go back into the skill instructions?"*
- Pipe the answer into updated skill text
- Skills drift toward fewer edge cases over time

This is the Cowork analog to the self-verification loop principle from [[Builder-Verifier Loop Pattern]].

## When to use this pattern

- **High intake volume** with predictable request types (events, campaigns, reports, support tickets)
- **Consistency requirement** — manual processes introduce variance; centralized skills eliminate it
- **Recurring work** — the amortized skill-writing cost falls as the task repeats

## Difference from Builder-Verifier

| | Builder-Verifier | Dispatcher-Specialist |
|---|---|---|
| **Primary use** | Code writing | Intake + execution |
| **Verifier scope** | Tests, compilation, app smoke | Domain-specific audit (e.g., verify registration form, test link) |
| **Routing** | Single builder | Dispatcher routes to N specialists |
| **Skill update loop** | N/A | Explicit reflection → skill refinement |

## Applicability to James's projects

- **qip-qien** — The Dispatcher-Specialist pattern mirrors the triage pipeline: dispatcher reads intake, routes to domain expert (specialist), independent audit before delivering to Ramon
- **nanoclaw** — The `create_agent` + skill system can implement this pattern directly: one scheduled router agent + named specialist agents
- **TradingBot25 / congressional-trading** — Dispatcher can route different signal types to specialist scoring agents

## Related
- [[Builder-Verifier Loop Pattern]]
- [[Claude Blog - Best Practices for Claude Cowork]]
- [[Long-Running Agent Primitives]] — Default-FAIL, Fresh-context evaluator, Handoff primitives complement this pattern


File created successfully at: /workspace/extra/second-brain/wiki/concepts/Cowork Dispatcher-Specialist Pattern.md (file state is current in your context — no need to Read it back)

# Cowork Dispatcher-Specialist Pattern

**Origin:** [[Claude Blog - Marketing Ops Cowork Automation]] (Anthropic internal, July 8, 2026)

## What it is

A three-layer multi-agent architecture for high-volume intake workflows:

1. **Dispatcher** — Scheduled agent that reads an intake channel/queue and routes each request to the right specialist. Runs on a short cadence (e.g., hourly) to prevent duplicate runs and enforce ordering.
2. **Specialist agents** — Purpose-built skills or Claude instances for specific task types (e.g., event-build, webinar landing page, data-import). Each has focused instructions and narrow scope.
3. **Audit agent** — *Independent* Claude instance that verifies specialist output before it ships. Key: the same agent that built the output cannot reliably self-check it.

```
Intake channel
      │
[Dispatcher - runs hourly]
      │
      ├── event-build skill
      ├── webinar landing page skill
      ├── data-import skill
      └── ... other specialists
                    │
              [Audit agent]  ← separate Claude instance
                    │
             Human review → ship
```

## Why the audit agent is separate

Asking the same Claude instance that built something to check it introduces the same blind spots that caused the bug. A separate instance starts cold, runs the same checks without any continuity bias, and is more likely to catch mismatch or missing steps.

## Skills as living systems

Both workflows in the article emphasized that the system improves continuously:
- After each run, reflect: *"What corrections were made this run that should go back into the skill instructions?"*
- Pipe the answer into updated skill text
- Skills drift toward fewer edge cases over time

This is the Cowork analog to the self-verification loop principle from [[Builder-Verifier Loop Pattern]].

## When to use this pattern

- **High intake volume** with predictable request types (events, campaigns, reports, support tickets)
- **Consistency requirement** — manual processes introduce variance; centralized skills eliminate it
- **Recurring work** — the amortized skill-writing cost falls as the task repeats

## Difference from Builder-Verifier

| | Builder-Verifier | Dispatcher-Specialist |
|---|---|---|
| **Primary use** | Code writing | Intake + execution |
| **Verifier scope** | Tests, compilation, app smoke | Domain-specific audit (e.g., verify registration form, test link) |
| **Routing** | Single builder | Dispatcher routes to N specialists |
| **Skill update loop** | N/A | Explicit reflection → skill refinement |

## Applicability to James's projects

- **qip-qien** — The Dispatcher-Specialist pattern mirrors the triage pipeline: dispatcher reads intake, routes to domain expert (specialist), independent audit before delivering to Ramon
- **nanoclaw** — The `create_agent` + skill system can implement this pattern directly: one scheduled router agent + named specialist agents
- **TradingBot25 / congressional-trading** — Dispatcher can route different signal types to specialist scoring agents

## Related
- [[Builder-Verifier Loop Pattern]]
- [[Claude Blog - Best Practices for Claude Cowork]]
- [[Long-Running Agent Primitives]] — Default-FAIL, Fresh-context evaluator, Handoff primitives complement this pattern


Now update Home.md (Sources and Concepts sections) and the Ingest Log:


Edit

- [[Claude Blog - Field Guide to Claude Fable]] — July 6, 2026. Thariq Shihipar. 4-quadrant unknowns framework, 8 elicitation techniques (blind spot pass, interview mode, reference prompting, implementation plan, explainer, quiz). Core claim: with Fable, output quality is now bottlenecked by user clarity, not model capability.

[[Wiki Ingest Log]]

- [[Claude Blog - Field Guide to Claude Fable]] — July 6, 2026. Thariq Shihipar. 4-quadrant unknowns framework, 8 elicitation techniques (blind spot pass, interview mode, reference prompting, implementation plan, explainer, quiz). Core claim: with Fable, output quality is now bottlenecked by user clarity, not model capability.
- [[Claude Blog - Marketing Ops Cowork Automation]] — July 8, 2026. Anthropic's own marketing ops team. Dispatcher-specialist architecture, audit agent pattern, skill refinement loops. Concrete Cowork workflow patterns applicable to qip-qien and nanoclaw.

[[Wiki Ingest Log]]