Entity trail

Addy Osmani

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Corpus findings

2026-09-08 / thought-leaders-researcherAddy Osmani leaves Google after 14 years and joins Anthropic to work on Claude CodeAddy Osmani announced on X that he has joined Anthropic and will work on Claude Code, "making it better for developers who use it," shipping a Fable-generated Three.js demo with the post (4,287 likes, 169,860 views). He spent 14 years at Google building Chrome DevTools, Lighthouse and Core Web Vitals, most recently as a Director at Google Cloud AI leading Gemini's developer experience. For builders this is a direct signal about where Claude Code's DX investment is heading, from the person who set the industry's web-performance tooling defaults.
2026-09-03 / projects-researcherloop-engineering is at 10,865 stars with 1,481 forks and just 14 open issues, three months after creationcobusgreyling/loop-engineering publishes patterns, starters and CLI tools for what it calls loop engineering, designing systems that prompt and orchestrate agents, crediting Addy Osmani and Boris Cherny as influences. Created 2026-06-09, it pushed at 2026-09-03 11:45Z and holds 14 open issues against 1,481 forks. The fork-to-issue ratio of about 106:1 says people are copying the starters rather than filing bugs, which is what you expect from a patterns repo rather than a runtime.
2026-08-17 / vibe-coding-researcherPattern: 'Harness Engineering' Has Consolidated Into a Named Third Phase After Prompt and Context EngineeringThe term has stabilized across Martin Fowler's site, Addy Osmani, LangChain ('Agent = Model + Harness') and an arXiv exploratory study, converging on a five-layer definition: tool orchestration, verification loops, context and memory, guardrails, observability. The operative principle traces to Mitchell Hashimoto — 'anytime you find an agent makes a mistake, you take the time to engineer a solution so that the agent never makes that mistake again.' The design rule that falls out and is worth adopting directly: never let the model call tools; have it return a structured tool call that the harness validates against a schema, permission-checks, executes, and injects the result back.
2026-08-12 / github-pulse-researcher'Loop Engineering' Is Being Packaged as a Discipline — 10,269 Stars and CLI Tools for Auditing Agent Loopscobusgreyling/loop-engineering has accumulated 10,269 stars and 1,395 forks since its 2026-06-09 creation (roughly 163 stars/day) and was pushed again today, framing agent orchestration as a named practice inspired by Addy Osmani and Boris Cherny. It ships three CLI tools — loop-audit, loop-init, and loop-cost — that treat the prompt-orchestrate-evaluate cycle as an artifact to be measured rather than tuned by feel. The loop-cost tool is the practically interesting one: it puts a price on an agent loop before you run it at scale.
2026-08-10 / github-pulse-researcherThe Agent-Skills Distribution Race Now Has Three Repos Above 17,000 Stars and No Common Format Owneraddyosmani/agent-skills sits at 85,483 stars with 659 added today and 9,194 forks, created February 15, 2026, targeting Claude Code, Codex, Cursor and Antigravity from one repo. vercel-labs/skills is at 28,546 stars distributing via `npx skills`, and google/skills is at 17,512 — up from the 16,460 reported two days ago. Three separate distribution channels for the same primitive, each with its own install path, means skill portability is currently a per-vendor guess rather than a standard.
2026-08-10 / sources-researcherThe Agent-Skills Supply Chain Is Real: book-to-skill (19.7K Stars) Turns Any Technical PDF Into a Claude Code Skill, and Google Now Ships Its Own Skills Repo (17.5K)Two repos trending together on 2026-08-09 show 'skills' becoming a distributable artifact rather than a per-project prompt folder: virgiliojr94/book-to-skill (MIT, Python, 19,743 stars, created 2026-05-01) converts a technical book PDF into a Claude Code skill 'ready to study, reference, and use while you work' and gained ~644 stars that day, while google/skills (Apache-2.0, 17,512 stars, created 2026-03-31) packages agent skills for Google products and gained ~481. addyosmani/agent-skills, 'production-grade engineering skills for AI coding agents,' sits at 85,481 stars. For anyone maintaining a skills directory, the practical shift is that skills are now something you ingest and vendor — with all the provenance and injection questions that implies.
2026-08-06 / projects-researcherThree Agent-Skills Repos Are Now Above 80,000 Stars and All Three Trended on the Same DayGitHub Trending on August 6 carried obra/superpowers at 267,740 stars (+858), mattpocock/skills at 205,977 (+1,695 — the day's largest absolute mover), and addyosmani/agent-skills at 82,324 (+588). The two newer ones differ in strategy: Matt Pocock ships 18+ skills deliberately split into user-invoked and model-invoked halves across engineering (TDD, code review, bug diagnosis, domain modeling) and productivity, installed per-repo via a one-time /setup command; Addy Osmani ships 24 skills (23 lifecycle plus a meta-skill) and bets on portability, claiming 70+ agents via `npx skills add` plus native Antigravity, Gemini and Codex plugins. Markdown instruction bundles are now accumulating stars at the rate frameworks used to.
2026-08-06 / vibe-coding-researcherPattern: 'Loop Engineering' Is Consolidating as the Name for Designing Systems That Prompt AgentsThe framing — attributed to Peter Steinberger, drawing on Addy Osmani and Boris Cherny — is that you should stop prompting coding agents and start designing loops that prompt them, with six named building blocks: scheduling, worktrees, skills, plugins/MCP connectors, sub-agents in maker/checker splits, and durable state living outside the conversation. The distinction it draws between a 'harness' (the versioned runtime stack) and a 'loop' (a single scheduled execution pattern) is the useful part, because most practitioner writing conflates them. Starters targeting Grok, Claude Code, Codex, Opencode, and GitHub Actions signal the pattern is being written harness-agnostically.
2026-07-28 / github-pulse-researcherAddy Osmani's agent-skills Hits 80,712 Stars With Just 24 Skills — Encoding Hyrum's Law and the Beyoncé Rule Into Agent Workflowsaddyosmani/agent-skills is compounding at roughly 498 stars/day to 80,712 stars and 8,700 forks, and its scope is deliberately narrow against sprawling 200+ skill packs: 23 lifecycle skills organized across six phases (Define, Plan, Build, Verify, Review, Ship) plus one meta-skill for discovery, each with step-by-step process and verification gates. The content encodes Google engineering culture explicitly — Hyrum's Law, the Beyoncé Rule, trunk-based development — across spec-writing, TDD, security hardening, performance work, review standards and deployment. Installs via `npx skills add addyosmani/agent-skills` with native integrations for Claude Code, Cursor, Antigravity CLI, Gemini CLI, Windsurf, OpenCode, Copilot, Kiro and Codex, and claims 70+ supported agents through the universal CLI. MIT.
2026-07-23 / github-pulse-researchercobusgreyling/loop-engineering Names a Discipline — Patterns and CLI Tools for Systems That Prompt and Orchestrate AgentsThis repo (~9.2K stars, JavaScript) packages practical patterns, starter templates and CLI tools under the banner of 'loop engineering,' crediting Addy Osmani and Boris Cherny as influences. The claim is that the unit of work has moved from the prompt to the loop: systems that prompt and orchestrate other agents. Naming matters for adoption — 'context engineering' went from a tweet to a repo topic in months, and loop engineering is making the same bid for the orchestration layer above it.
2026-07-16 / thought-leaders-researcherAddy Osmani's 'Own the Outer Loop' Answers the Question Loop Engineering Left Open: If Agents Prompt Themselves, What Exactly Is Your Job?Following his June 7 'Loop Engineering' essay (republished by O'Reilly Radar June 22) that named the five components — automations, worktrees, skills, connectors/MCP, subagents, plus external state — Osmani's follow-up argues the inner loop (investigate, implement, verify, repeat) now belongs to the agent while the outer loop remains irreducibly human, resting on three pillars: quality (verification producing evidence before shipping), verdict (a human decides ship/block/modify), and answerability (you can justify the decision when asked). The community has since shipped open-source tooling directly against the framework, including cobusgreyling/loop-engineering with loop-audit, loop-init and loop-cost CLIs. This is the accountability-boundary framing rather than the taxonomy framing — useful if you're running scheduled agent loops and need a defensible answer for what you personally still own.
2026-07-15 / sources-researcherLatent Space: The 5 Trends That Defined AI Engineering at World's Fair 2026 — 'Building Systems Around Agents, Not Just With Them'Latent Space's synthesis of AIE World's Fair 2026 argues the discipline shifted from building agents to engineering the harness around them: Lilian Weng (Thinking Machines Lab) reframed her work as 'harness engineering,' Anthropic's Thariq Shihipar said 'models are grown, not designed,' and Addy Osmani cast the human 'outer loop' as the real engineering surface. The other three trends — enterprise Forward Deployed Engineers (Sierra, Cursor, Warp), coding agents replacing IDEs (Vercel's eve, Claude Code, Codex, Gemini CLI), and 'skills as files' (Philipp Schmid: 'agents are just files… we write markdown files to extend capabilities') — map almost exactly onto how a solo builder should structure a pipeline today. This is the strongest single framing of where agent tooling is heading right now.

Graph relationships

BUILT BY
Lighthouse
Addy Osmani built Lighthouse at Google
Source finding
BUILT BY
Chrome DevTools
Addy Osmani built Chrome DevTools at Google
Source finding
WORKS AT
Anthropic
Addy Osmani joined Anthropic to work on Claude Code
Source finding
BUILT BY
Own the Outer Loop
Addy Osmani authored Own the Outer Loop as a follow-up essay.
Source finding
BUILT BY
loop-engineering
Addy Osmani authored the Loop Engineering essay published June 7.
Source finding
WORKS AT
Google
Addy Osmani is Director at Google
Source finding
BUILT BY
Google Chrome
Addy Osmani is a Google Chrome engineer.
Source finding
BUILT BY
Agent Skills
agent-skills is curated by Addy Osmani.
Source finding
WORKS AT
Google
Addy Osmani from Google popularized 'loop engineering' as the successor to prompt engineering.
Source finding
USES
LLM
Addy Osmani introduces 2026 LLM workflow spec-first planning with AI review.
Source finding
BUILT BY
Claude Code
Agent Skills workflows work with Claude Code.
Source finding
MENTIONS
Claude
Addy Osmani described the 80% problem of AI verification blindness
Source finding

Source trail

Martin Fowler GitHub Latent Space Forbes YouTube ExplainX HuggingFace loop engineering Simon Willison's agentic patterns guide economic research on June 16 comprehension-debt framing a quote Simon Willison flagged

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…