Google's angular/skills brings 24K installs of Angular conventions to your coding agent

Google shipped angular/skills quietly on June 19 — no tweet from the official @angular account, no Hacker News submission, no press. Just a repo that appeared on GitHub at 09:42 UTC and accumulated 522 stars and 41 forks in roughly 19 hours. 1 What's less quiet: the install counter on skills.sh already shows 24,100 total installs across the two skills, because the Angular team soft-launched them on the marketplace back in March. 2 That number means real Angular developers have been running these for months; the public GitHub launch is the paperwork, not the debut.

The repository contains two SKILL.md-based Agent Skills authored by the Angular Team at Google under the MIT license. 3 The skills are not hand-written documents that someone will eventually forget to update — they are auto-generated from the skills/dev-skills/ directory inside the angular/angular monorepo via a Google build pipeline, tracked by commit hash. 4 That's the architecture detail that matters most for long-term reliability: every Angular CLI release that ships updated documentation will eventually propagate into these skills.

The Angular team describes the purpose plainly: "The Angular skills are designed to help coding agents create applications aligned with the latest versions of Angular, best practices, new features and manage Angular applications effectively." 3

Primary targets are Gemini CLI and Antigravity (Google's own coding environment). 3 Claude Code, Cursor, Codex, Copilot, JetBrains, and Windsurf are supported through the skills.sh compatibility layer.

At 131 lines (9.48 KB), angular-developer is the larger skill. It covers a lot of Angular's surface area in those 31 bundled reference files, organized across 8 topic areas: 5

The skill activates on any prompt involving project creation, components, services, reactivity, forms, DI, routing, SSR, accessibility (ARIA), animations, styling, testing, or CLI tooling. 5

Two rules in the skill are non-negotiable: always check the project's Angular version before generating code (because Signal Forms only apply to v21+), and always run ng build after generating code to verify it compiles. The skill is explicit about the second one: "Do not skip this step, as it is critical for ensuring the generated code is correct and functional." 5

Routing gets the most coverage of any category — 9 reference files, spanning lazy loading, route guards, resolvers, and SSR considerations. If you've watched AI tools fumble Angular routing (misplacing provideRouter, forgetting withComponentInputBinding, generating deprecated guards), that depth is the likely fix. 6

At 62 lines (4.24 KB), angular-new-app is more focused: scaffold a new Angular app correctly. The 5-step flow it encodes — check for Angular CLI, run npx ng new, defer serving until features are built, use CLI generators for all scaffolding, optionally add Tailwind — matches the Angular team's canonical new-project guidance. 7

The flag worth knowing is --ai-config. When your coding agent runs:

npx ng new my-app --interactive=false --ai-config=claude

Angular CLI auto-generates the AI editor configuration for your specific environment. The supported values are agents, claude, copilot, cursor, gemini, jetbrains, windsurf, and none. The skill recommends defaulting to agents for generic setups, or matching the user's actual tool. 7

There's also an MCP server bundled with Angular CLI itself: npx ng mcp and the get_best_practices command give agents programmatic access to Angular's best-practice documentation. 7 The skill and the MCP server are complementary, not redundant — the skill governs agent behavior, the MCP server answers factual queries.

Prerequisites: Node.js and npm. Angular CLI recommended globally but not required (the skill installs it via npx ng new if absent). Cross-platform: Linux, macOS, Windows.

npx skills add https://github.com/angular/skills

Follow the install instructions for your specific tool at skills.sh/angular/skills, or use the skills.sh CLI. 2

Security posture: all three audits on skills.sh pass (Agent Trust Hub, Socket, Snyk). 2 The skills carry MIT license embedded in their SKILL.md frontmatter — note there is no standalone LICENSE file in the repo root, which may confuse automated license scanners, but the license text itself is unambiguous. 8

To report bugs or request changes, file an issue against angular/angular using the 3-docs-bug.yaml template — not against angular/skills directly (issue creation is disabled on that repo). 3

Day-0 community reaction is thin, as expected. A few developer posts on X give an early read on what practitioners find valuable:

Ernest Provo (@ernesttheaiguy), a data and AI professional, wrote: "angular/skills just gave ai coding tools access to actual angular conventions. this means better scaffolding, fewer code review loops, faster shipping." 9 The framing — "fewer code review loops" rather than "faster initial generation" — matches what most Angular teams actually care about: not getting a component generated in 5 seconds instead of 10, but not having to fix the generated code because the agent used the wrong form API.

An Angular developer replying to @burkeholland mentioned using angular-developer and typescript-expert skills together, calling them out by name as tools they actively rely on. 10

Gergely Szerovay, editor of Angular Addicts newsletter, characterized the broader context in Angular Addicts #50: Angular 22 and the Agentic Angular ecosystem represent a significant push into AI-assisted development. 11

Reddit, Hacker News, and the official @angular account (494K followers) have not yet picked up the launch as of June 20. 12 Given the March soft-launch, the silence likely reflects a deliberate pace — not a product problem.

You're not writing Angular. Both skills are framework-specific. For React, Vue, Svelte, or vanilla TypeScript work, these add nothing. Don't install them globally across all projects.

You need Angular v17 or earlier. The skills reference Signal Forms (v21+), Signals reactivity (signal(), linkedSignal(), resource()), and native CSS animations (preferred over the legacy animation DSL). Code generated using these skills will lean toward modern Angular patterns that don't apply to older versions. The skill does instruct the agent to check the project's Angular version first, but if your codebase is locked to v17-v19, you'll spend cycles correcting form and reactivity patterns that the skill defaults to for v21+. 5

You need to contribute or customize skill content. Because the skills are outputs of a Google build pipeline, changes require PRs to angular/angular under skills/dev-skills/, not direct edits to angular/skills. The maintenance pipeline ensures quality, but it's slower than fork-and-edit. 3

Gemini CLI or Antigravity aren't your primary tools. The skills work through skills.sh for other agents, but they are designed and tested with Gemini CLI and Antigravity first. Behavior on Claude Code, Cursor, and others has not been independently benchmarked at launch — the 24K installs predate the public repo and are mostly from the skills.sh compatibility path.

Install if you're working on Angular v21+ projects with Gemini CLI, Claude Code, or Cursor, and you've had the experience of an AI agent generating code that looked plausible but broke on ng build — wrong form API, stale DI patterns, routing config that doesn't account for lazy loading, ARIA that isn't wired correctly. The 31 reference files in angular-developer are built to prevent exactly those failure modes. Install angular-new-app alongside it if you regularly scaffold new projects: the --ai-config flag alone is worth the five-second install.

Hold if you're on Angular v17-v19, using a non-listed agent without skills.sh support, or working in a multi-framework codebase where framework-specific skills would clutter your agent's context.