add-sdk-method
/add-sdk-method
Add a method across all five AerolVM SDKs (TypeScript, Python, Go, Rust, Java) in lockstep, plus the synced docs example. Use when the user asks to "expose this in the SDK", "add an SDK method", "wire this up in the clients", or whenever a new /v1 endpoint needs SDK coverage. Proactively suggest after a new /v1 endpoint lands to keep SDK parity.
- Author
- aerol-ai ↗
- Repository
- microvm ↗
- Licence
- MIT
- Last repository change
- 20.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 20.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Add a method across all five AerolVM SDKs (TypeScript, Python, Go, Rust, Java) in lockstep, plus the synced docs example. Use when the user asks to "expose this in the SDK", "add an SDK method", "wire this up in the clients", or whenever a new /v1 endpoint needs SDK coverage. Proactively suggest after a new /v1 endpoint lands to keep SDK parity.
Triggers from the description
Original author description
Add a method across all five AerolVM SDKs (TypeScript, Python, Go, Rust, Java) in lockstep, plus the synced docs example. Use when the user asks to "expose this in the SDK", "add an SDK method", "wire this up in the clients", or whenever a new /v1 endpoint needs SDK coverage. Proactively suggest after a new /v1 endpoint lands to keep SDK parity.
How it works
- Per-SDK file map
- Per-SDK steps (repeat 5×)
- Verify locally
- Style
SKILL.md preview
--- name: add-sdk-method description: Add a method across all five AerolVM SDKs (TypeScript, Python, Go, Rust, Java) in lockstep, plus the synced docs example. Use when the user asks to "expose this in the SDK", "add an SDK method", "wire this up in the clients", or whenever a new /v1 endpoint needs SDK coverage. Proactively suggest after a new /v1 endpoint lands to keep SDK parity. --- # Add a method to all five SDKs The SDKs are kept lockstep so the docs' five-tab examples stay accurate. Touching one SDK without the others should be rare and explained in the PR. ## Per-SDK file map | SDK | Public surface | Transport (versioned) | Tests | |---|---|---|---| | TypeScript | `sdk/typescript/src/Sandbox.ts`, `MicroVM.ts`, `types.ts` | `sdk/typescript/src/internal/api/v1/` | `sdk/typescript/src/*.test.ts` | | Python | `sdk/python/microvm/client.py`, `types.py` | `sdk/python/microvm/_internal/api/v1/` | `sdk/python/tests/` | | Go | `sdk/go/pkg/microvm/`, `sdk/go/pkg/types/` | `sdk/go/internal/apiclient/v1/` | `*_test.go` next to source | | Rust | `sdk/rust/src/lib.rs`, `types.rs` | `sdk/rust/src/` | inline `#[cfg(test)]` | | Java | `sdk/java/src/main/java/...` | same tree | `sdk/java/src/test/java/...` | ## Per-SDK steps (repeat 5×) 1. Add request/response types in that SDK's `types.*`. 2. Add the transport call in the `v1/` (or equivalent) versioned module. **Use the SDK's existing `versioned()` helper / `apiVersion` option — do not hand-build `/v1/...` URLs at the call site.** This is what lets `apiVersion` pin work without rewriting every method. 3. Surface the new method on the public client (`Sandbox` or `MicroVM`). 4. Add a test. 5. If this SDK is the canonical example for any docs page, update the example. ## Verify locally ``` (cd sdk/typescript && npm ci && npm run build && npm test) (cd sdk/python && python -m unittest discover -s tests -v) (cd sdk/go && go test ./...) (cd sdk/rust && cargo test) (cd sdk/java && mvn -B -ntp test) ``` CI is path-filtered (`.github/workflows/test.yml`) — only the SDKs whose folders changed will run on PR, so local verification of unchanged SDKs is the only way to catch parity drift before merge. ## Style - **One PR per method, all 5 SDKs.** Splitting drift across PRs has burned us — keep parity atomic. - **No version-leakage into the public surface.** Callers pick `apiVersion`; method signatures don't include `v1`. - **Match the existing argument style of nearby methods** in each SDK. Don't impose Go-isms on Python, etc.
Versions
The database has no other skills named add-sdk-method.
Database snapshot: 13.11.2026 · package version f3e73eaa431d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100add-docs-page
Add a new AerolVM docs page (.mdx) with synced five-language tabs and register it in the Starlight sidebar. Enforces the repo's hard rules — no raw curl, all five SDK languages, syncKey="lang" on every tab block. Use when the user asks to "add a docs page", "document this… - 100add-v1-endpoint
Add a new route under /v1/... to the AerolVM HTTP server. Walks through DTOs, handler, route registration, service-layer call, tests, and the idempotency check. Use when the user asks to "add a v1 endpoint", "add an API route", "add a new HTTP handler", or describes a new… - 96add-public-api
Add a public type, method, factory or error to this Java library with its Javadoc, example, tests, consumer call and API notes. Use when the user asks the library to expose something new, accept a new setting, or report a new kind of failure. - 96typescript-sdk
TypeScript SDK patterns for Opik. Use when working in sdks/typescript. - 100sui-sdks
Sui SDK landscape — which SDK to pick (TypeScript, Rust, or community-maintained Python/Go/Dart/Kotlin/Swift), how they map to each other, and how to install and wire each one up. Use when a user is starting a new Sui project in any language, migrating between languages,… - 90add-api-endpoint
Use when a ticket asks to add or extend an HTTP/API endpoint — a new route, handler, or RPC method — with request validation and a defined response. Invoke for "add a POST /things endpoint", "expose a list API", or "add a field to the X response".