gear-foundation/gear-gstd-api-map
skills/gear-gstd-api-map/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add gear-foundation/vara-skills gear-gstd-api-mapInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 23, 2026, 2:39 AM20.2s2 files scanned
SKILL.md
- 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_replyflows, delayed work,ReservationId, orprog::* - a debugging pass needs to confirm which
gr_*syscall family a high-level API actually reaches - a
send_for_replytargets a hardcoded non-programActorId(staking, proxy, BLS12-381, ETH bridge); route togear-builtin-actorsfor the per-actor request shape and reply decoding
Working Model
- Start from builder intent, not from raw syscalls.
- Choose the
gstdfamily:msg,exec,prog, reservations, or async helpers. - Prefer the highest-level API that preserves the contract: typed send and reply first, bytes only for intentional raw payload paths or codec debugging.
- Check design constraints: block-delayed execution, reply deposit, reservation lifetime, waitlist exposure, gas budget, and Sails Header routing stability for Sails clients.
- Drop to
gcoreto confirm wrapper behavior and togsysonly 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
gstdas 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.
Related Skills
gear-foundation/sails-ethexe-implementer
development
VerifiedTrustedCommunity
Use when approved tasks require Rust code changes in a Sails ethexe workspace with the ethexe feature enabled. Do not use for standard Gear/Vara Sails apps without ethexe, or when the spec or architecture is still unsettled.
17SKILL.mdUpdated May 23, 2026
gear-foundation/sails-ethexe-architecture
development
VerifiedTrustedCommunity
Use when a builder needs to design or review architecture for a Sails ethexe app with dual-transport, payable methods, Solidity interface generation, or Ethereum-style events. Do not use for standard Gear/Vara Sails apps without ethexe.
17SKILL.mdUpdated May 23, 2026
gear-foundation/gear-builtin-actors
development
VerifiedTrustedCommunity
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 program-to-program messaging, Vara.eth or ethexe-only work, non-Sails repositories, or runtime-maintenance tasks inside the Gear repo.
17SKILL.mdUpdated May 16, 2026
gear-foundation/sails-indexer
development
VerifiedTrustedCommunity
Use when a builder needs a read-side indexer and query API for a standard Gear/Vara Sails app using program events, IDL-driven decoding, projected read models, and optional on-chain query enrichment. Do not use for command-side backends, generic Node APIs, non-Sails repositories, Vara.eth or ethexe-first work.
17SKILL.mdUpdated May 13, 2026