gear-gstd-api-map
/gear-gstd-api-map
Use when a builder needs to choose the right gstd API for messaging, execution, reservations, async reply flows, or program creation, and trace that API to gcore or gsys when behavior must be confirmed. Do not use for Vara.eth or ethexe-first work, non-Gear repositories, or broad runtime-maintenance tasks.
- Author
- gear-foundation ↗
- Repository
- vara-skills ↗
- Licence
- MIT
- Last repository change
- 13.07.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.07.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
Use when a builder needs to choose the right gstd API for messaging, execution, reservations, async reply flows, or program creation, and trace that API to gcore or gsys when behavior must be confirmed. Do not use for Vara.eth or ethexe-first work, non-Gear repositories, or broad runtime-maintenance tasks.
Original author description
Use when a builder needs to choose the right gstd API for messaging, execution, reservations, async reply flows, or program creation, and trace that API to gcore or gsys when behavior must be confirmed. Do not use for Vara.eth or ethexe-first work, non-Gear repositories, or broad runtime-maintenance tasks.
How it works
- Goal
- Inputs
- Route Here When
- Working Model
- API Quick Reference
- Guardrails
SKILL.md preview
--- name: gear-gstd-api-map description: Use when a builder needs to choose the right gstd API for messaging, execution, reservations, async reply flows, or program creation, and trace that API to gcore or gsys when behavior must be confirmed. Do not use for Vara.eth or ethexe-first work, non-Gear repositories, or broad runtime-maintenance tasks. --- # Gear gstd API Map ## Goal Keep design work API-first: start from `gstd`, then drop to `gcore` or `gsys` only when you need to confirm limits, gas shape, or low-level behavior. ## Inputs - `../../references/gear-execution-model.md` — execution model and block lifecycle - `../../references/gear-messaging-and-replies.md` — message flow and reply semantics - `../../references/gear-gas-reservations-and-waitlist.md` — gas reservations and waitlist - `../../references/gear-gstd-api-and-syscalls.md` — full API surface and syscall mapping ## Route Here When - a spec or architecture note needs to know whether a Gear program can send, await replies, self-schedule, reserve gas, or create child programs - a builder is choosing between typed payloads, raw bytes, staged push-plus-commit, or input-forwarding APIs - a design depends on `#[gstd::async_main]`, `_for_reply` flows, delayed work, `ReservationId`, or `prog::*` - a debugging pass needs to confirm which `gr_*` syscall family a high-level API actually reaches - a `send_for_reply` targets a hardcoded non-program `ActorId` (staking, proxy, BLS12-381, ETH bridge); route to `gear-builtin-actors` for the per-actor request shape and reply decoding ## Working Model 1. Start from builder intent, not from raw syscalls. 2. Choose the `gstd` family: `msg`, `exec`, `prog`, reservations, or async helpers. 3. Prefer the highest-level API that preserves the contract: typed send and reply first, bytes only for intentional raw payload paths or codec debugging. 4. Check design constraints: block-delayed execution, reply deposit, reservation lifetime, waitlist exposure, gas budget, and Sails Header routing stability for Sails clients. 5. Drop to `gcore` to confirm wrapper behavior and to `gsys` only when you need exact syscall names, fallibility, or control-vs-get distinctions. ## API Quick Reference | Module | Key APIs | When to Use | |--------|----------|-------------| | `msg` | `send`, `reply`, `send_delayed`, `send_for_reply`, `send_bytes`, push-plus-commit | Sending messages, replying, delayed dispatch, awaiting replies | | `exec` | `gas_available`, `block_height`, `wait`, `wait_for`, `wake`, `reply_deposit`, `exit` | Reading execution context, parking in waitlist, waking actors | | `prog` | `create_program`, `create_program_bytes`, create-for-reply | Creating child programs with optional delay and gas limits | | reservations | `ReservationId::reserve`, `.unreserve`, reservation pools | Future-block work that must keep a gas budget alive | ## Guardrails - Prefer `gstd` as the default public API for standard Gear/Vara builders. - Treat raw `gsys::gr_*` names as confirmation tools, not the first design vocabulary. - Keep design notes phrased in message flow, replies, blocks, and contracts, not in syscall sequences. - If a Sails route depends on generated clients, preserve that route contract even for delayed or self-messaging paths. - Stop if the task is really about runtime benchmarking, syscall-maintenance coverage, or ethexe-only behavior.
Files in this package (4)
- SKILL.md 3 KB
- assets/pressure-scenarios.md 1 KB
- references/.gitkeep 1 KB
- scripts/.gitkeep 1 KB
Versions
The database has no other skills named gear-gstd-api-map.
Database snapshot: 13.11.2026 · package version 6da700d35e5f (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
- 90gear-message-execution
Use when a builder needs to design or debug Gear message flow, replies, delayed execution, reservations, or waitlist behavior inside a standard Gear/Vara Sails app. Do not use for Vara.eth or ethexe-first work, non-Sails repositories, or broad protocol research. - 100gear-builtin-actors
Use when a builder needs to design or debug calls from a standard Gear/Vara Sails program into runtime builtin actors such as BLS12-381, staking, proxy, or ETH bridge, including ActorId derivation, request encoding, reply decoding, and gas or ED budgeting. Do not use for regular… - 90gear-diagnosis
Gear fault diagnosis workflow using vibration analysis via the predictive-maintenance-mcp server. Use this skill when the user says "gear fault", "gear diagnosis", "gear mesh", "gearbox analysis", "gear vibration", "tooth damage", "gear defect", "diagnose gear", "gear mesh…