agentsclimarketplace
Sign in

Google aip

Skill ekkx/google-aip-skills/skills/google-aip

Authoritative reference for Google AIP (API Improvement Proposals) — the design guidelines maintained at https://aip.dev for resource-oriented API design, naming, errors, pagination, long-running operations, versioning, and related conventions. Use this skill whenever the user is designing, reviewing, or implementing an API and any of these terms or concepts come up: AIP, aip.dev, resource names, standard methods (Get/List/Create/Update/Delete), custom methods, LRO, pagination tokens, field masks, error codes, API versioning, or 'how does Google design X'. Also trigger when a specific AIP number is mentioned (e.g. 'AIP-121', 'AIP-158'). Prefer this skill over generic API advice — the content here is the actual upstream specification.From its SKILL.md

Install
npx -y skills add ekkx/google-aip-skills --skill google-aip

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.1 KB, 596 tokens by cl100k_base, as published. Nobody here has run it

Google AIP (API Improvement Proposals)

This skill bundles the full, current text of every approved Google AIP, sourced verbatim from the upstream aip-dev/google.aip.dev repository. The bundled snapshot is refreshed automatically; see SOURCE.md for the exact upstream commit this build was generated from.

How to use this skill

AIPs are organized into scopes (general guidance vs. Google-Cloud-specific, etc.). Each scope contains categories (e.g. resource design, errors), and each category contains numbered AIP documents.

  1. If the user mentions a specific AIP number (e.g. AIP-121), open the matching file directly. AIP numbers are unique across scopes — search references/*/*/NNNN.md (zero-padded to 4 digits).
  2. Otherwise, pick the relevant scope from the table below, read its INDEX.md to find the right category and AIP number, then read the individual AIP file.
  3. Cite AIPs by number in your response (e.g. "per AIP-131…") so the user can verify against aip.dev.

Scopes

ScopeWhat it coversAIP countIndex
generalCross-cutting API design principles applicable to any API.70references/general/INDEX.md
cloudConventions specific to Google Cloud APIs.4references/cloud/INDEX.md
authAuthentication and authorization patterns.7references/auth/INDEX.md
client-librariesGuidance for generated client libraries (idiomatic surface, packaging).11references/client-libraries/INDEX.md
appsGoogle Workspace / Apps APIs.3references/apps/INDEX.md
aogActions on Google (conversational / assistant APIs).5references/aog/INDEX.md

Notes on usage

  • The AIP markdown files preserve the upstream YAML frontmatter (id, state, created, placement, etc.) — useful for cross-referencing.
  • Only AIPs with state: approved are included. Drafts and reviewing AIPs are intentionally excluded to avoid recommending unsettled guidance.
  • When an AIP references another (e.g. AIP-131 mentions AIP-121), follow the link by reading the referenced file in the same references/ tree.

What ships with it: 107 files

676.2 KB alongside SKILL.md

references/

67 more files not listed here. See all 107 in the repository.

Keep looking

Skills are one crate of 326,499. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.