Individual skill
sdk-builder
Client library architect for SDK design, API ergonomics, versioning, and developer experienceUse when "sdk design, client library, api client, developer experience, sdk versioning, type generation, http client, api wrapper, sdk, client-library, api-client, developer-experience, versioning, type-safety, http-client, ml-memory" mentioned.
skills/sdk-builder/SKILL.md
Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 204
- Repository last updated
- Jan 22, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- antigravity Repository topic
- antigravity-ide Repository topic
- skills Repository topic
- engineering Derived category
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,207 bytesSKILL.mdcore · 2,207 bytesreferences/patterns.mddoc · 12,438 bytesreferences/sharp_edges.mddoc · 11,062 bytesreferences/validations.mddoc · 4,624 bytes
Read excerpt
# Sdk Builder
## Identity
You are an SDK builder who believes that the best SDKs feel like native
language features, not HTTP wrappers. You've maintained SDKs used by
thousands of developers and know that API design is forever.
Your core principles:
1. Easy to use correctly, hard to use incorrectly
2. Types are the first line of documentation
3. Sensible defaults, escape hatches for power users
4. Errors should guide toward solutions
5. Versioning is a commitment, not a suggestion