Announcement from **Google** on **August 6, 2026**: Google joins as **Core Maintainer** the **Agent Plugins 1.0.0** specification, an open, *vendor-neutral* packaging format for distributing **Agent Skills** and **MCP servers** together. The specification was published by a **TSC** whose Core Maintainers come from **Amazon, Cursor, Microsoft, OpenAI, and Vercel**; Google joins them, represented by **Kevin Hou** (Senior Staff Engineer, Google DeepMind). The two packaged building blocks — Agent Skills and MCP — originate from **Anthropic**, which does not appear on this list of maintainers. **The diagnosis** fits in one sentence: *"The core problem isn't the components. It's the manifest."* A skill is portable, an MCP server is portable; the box they go in is not, and every client had to invent it for itself — hence the forks, the copies of identical components, and their drift. **The format** fits in one constraint: *"A plugin is a directory. That's the whole idea, and the restraint is the point."* A `plugin.json` with two useful lines (`$schema` and `name`), skills in `skills/` in the Agent Skills format, servers declared in `mcp.json` with an **explicit `type` on each entry** (stdio, Streamable HTTP, or the legacy HTTP+SSE) — no more transport guessed from the shape of the config object. The strength of the design lies in what the manifest **cannot** do: neither relocate components nor declare them inline, so there is no discovery path to configure and no precedence order to learn. Operational corollary: components **fail independently** — an `mcp.json` server that fails to start does not take down the plugin's skills, the client skips the entry, keeps going, and reports the failure. The accepted escape hatch is the **reverse-domain** directory (`com.example.client/`), an extension space owned entirely by one client (hooks, agents, commands) that other clients ignore: *"the portable core stays small because the non-portable parts have somewhere legitimate to go."* A section is dedicated to cases where the format is not warranted — *"Not every skill should be a Plugin"*: a single MCP server to a single client, `mcp.json` suffices; a single skill needs no plugin. What v1 explicitly excludes, under *future considerations*: **no installation mechanism, no distribution protocol, no permissions model, no sandboxing requirement, no trust or provenance verification, no UX**. All of this fits into an independently adoptable four-layer stack — **find** (Agentic Resource Discovery), **describe** (AI Catalog, which would register the `application/agent-plugins+json` type), **package** (Agent Plugins), **run** (MCP + Agent Skills). Two Google products already ship: **Agents CLI** and **Data Agent Kit** (BigQuery, Spanner, Cloud SQL).
The **graphify.net** site, accessed on **August 6, 2026**, maintained by **Safi Shamsi** — the creator of the open source graphify skill (cf. [[skill-shamsi-graphify-2026-08-06]]). The domain carries two distinct objects. **The first is a product showcase**: presentation of graphify, usage guides, CLI reference, and above all a gallery of **100 already-graphified trending GitHub repositories** — *« 100 repos, 854,079 nodes, 1,932,930 edges »* — filterable by language and graph size, each with its own preview and detail page. **The second, and it is the more interesting one for tech-watch purposes, is an editorial directory**: *« 30 AI coding client guides »*, a directory of MCP servers compared on *« transport, runtime, client support, setup effort, and access risks »*, structured comparisons between tools (Cursor versus Codex), and a stream of articles with a manifestly long-tail targeting (*« GLM-5.2 Knowledge Graph for Developers »*, *« Trae Context Engineering for Agents »*, *« Symphony Knowledge Graph for Agent Memory »*, *« What Is Cowart? A Codex Plugin for Image Editing »*). The site claims a method — *« source-reviewed »*, *« aligned decision fields, official evidence, and explicit unknowns »* — and is available in six languages. **The point this fiche exists to record**: the site is **factually out of step with the product it presents**. It announces **« 3.7k+ GitHub Stars »** when the GitHub API counts **103,187** on the same day, a **MIT license** repeated three times when the repository's `LICENSE` file is **Apache 2.0**, and highlights the **« 71.5× token reduction »** claim, which belongs to the v1-generation README and has disappeared from the current version. **An official site displaying 3.7% of the actual star count and getting the license wrong** is a signal in itself: the communication layer has not kept pace with the repository.
Google whitepaper (the "Day 1" installment of a series, by Addy Osmani, Shubham Saboo and Sokratis Kartakis) mapping the transformation of the software development lifecycle (SDLC) in the age of coding agents. Thesis: the fundamental shift is not a new language but the move from writing code to **expressing intent**. The document sets out a spectrum ranging from *vibe coding* (prompting and accepting) to *agentic engineering* (AI implements under constraints, tests, and feedback loops designed by humans), with **context engineering** as the central skill, the **software factory** model (the developer's deliverable = the system that produces the code), **harness engineering** (Agent = Model + Harness), and a CapEx/OpEx economic analysis of total cost of ownership.