aip-knowledge

This skill should be used when the user asks about "AIP rules", "API Improvement Proposals", "Google API guidelines", "AIP-158", "AIP-193", or any specific AIP number. Also use when user asks "how should I implement pagination", "what's the right error format", "how do I design a REST API following Google's standards", or needs guidance on errors, pagination, filtering, field masks, long-running operations, or batch operations in REST/OpenAPI APIs.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, token-efficient quick reference with concrete patterns and a clear usage workflow. Its main weakness is that the many referenced reference files are not actually present in the bundle, leaving some inline guidance thin.

Suggestions

Ship the referenced bundle files (errors.md, pagination.md, filtering.md, lro.md, field-masks.md, batch.md, rest-mapping.md, linter-rules.md) under references/ so the navigation table resolves to real content.

Add a brief inline example for field masks and batch operations in the Quick Reference so the most common tasks are actionable without loading a reference file.

Include a small validation checkpoint in the workflow (e.g., cross-check a proposed design against the listed linter rules) so users can confirm AIP compliance.

Dimension	Reasoning	Score
Conciseness	Lean quick-reference format of tables and short JSON snippets with no padding or explanation of concepts Claude already knows; every section earns its place.	5 / 5
Actionability	Provides copy-paste-ready JSON for pagination and error responses plus concrete HTTP method/naming patterns, but defers most implementation detail (field masks, batch, LRO) to reference files rather than showing it inline.	4 / 5
Workflow Clarity	The "How to Use This Skill" section gives a clear 4-step sequenced workflow (quick reference -> reference file -> linter rules -> baume-lookup), but lacks explicit validation/checkpoint steps; acceptable since this is a reference skill, not a destructive/batch operation.	4 / 5
Progressive Disclosure	A well-signaled reference table maps topics to one-level-deep files with when-to-use guidance, but the referenced files (errors.md, pagination.md, linter-rules.md, etc.) are not present in any bundle directory, so navigation cannot be fully verified.	4 / 5
	Total	17 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, trigger-rich description that clearly states both capability and usage conditions with natural synonyms and specific AIP references. It is slightly lighter on explicit action verbs than on triggers, but otherwise exemplary.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ("errors, pagination, filtering, field masks, long-running operations, or batch operations") plus specific design questions, with only minor gaps in explicit action verbs.	4 / 5
Completeness	Explicitly answers both what (guidance on the listed REST/OpenAPI topics) and when, with multiple concrete "Use when..." / "Also use when..." trigger clauses.	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage including synonyms ("AIP rules", "API Improvement Proposals", "Google API guidelines"), specific numbers (AIP-158, AIP-193), and verbatim user questions like "how should I implement pagination".	5 / 5
Distinctiveness Conflict Risk	Clear niche (Google AIP adapted to REST/OpenAPI) with highly specific triggers (AIP numbers, named design questions), giving minimal overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: getlarge/claude-api-care-plugins
Path: plugins/baume/skills/aip-knowledge/SKILL.md
Commit: 90d0cc6

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.