sails-local-smoke

Validate Gear/Vara Sails applications against a local Vara node.

17|23|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/gear-foundation/vara-skills --skill sails-local-smoke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sails-local-smoke
Source: https://github.com/gear-foundation/vara-skills/tree/main/skills/sails-local-smoke
Command: npx skills add https://github.com/gear-foundation/vara-skills --skill sails-local-smoke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of untested remote deployments by providing a structured, repeatable workflow to validate that a completed Gear/Vara Sails application works correctly against a live local Vara node after all unit tests pass.

Core Features & Use Cases

  • Dual Deployment Paths: Supports both the user-friendly vara-wallet CLI for simplified account and program management, and the Rust gclient path for projects with existing Rust test harnesses.
  • Best Practice Enforcement: Mandates use of optimized .opt.wasm artifacts to avoid on-chain size limit errors, requires local dev accounts instead of Ethereum addresses, and enforces post-deploy initialization verification to catch uninitialized program states.
  • Use Case: For example, after your Sails app passes all gtest unit tests, use this Skill to deploy the optimized WASM to a local node, run a test command and query to confirm end-to-end integration works before moving to testnet or mainnet.

Quick Start

Use the sails-local-smoke skill to validate your Sails app with passing gtest coverage against a local Vara node by following the documented deployment and integration testing workflow.

Frequently Asked Questions about sails-local-smoke

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a Sails app on a local Vara node after gtest passes?

Use this workflow to deploy optimized .opt.wasm artifacts to a local Vara node, manage local dev accounts, verify program initialization, and confirm typed client wiring and message flow correctness.

What is the best way to smoke test Gear Sails applications before remote deployment?

The best way to smoke test Gear Sails applications is deploying optimized WASM to a local Vara node to verify deployed program behavior and message flow correctness prior to testnet or mainnet deployment.

Does the local Vara smoke test workflow support both vara-wallet CLI and gclient?

Yes, the local Vara smoke test workflow supports dual deployment paths, allowing you to use the vara-wallet CLI for simplified account management or the Rust gclient test harness for integration validation.

Why does my Sails WASM deployment fail on the Vara network with size limit errors?

Sails WASM deployment fails with size limit errors if you use non-optimized artifacts; you must deploy optimized .opt.wasm artifacts to avoid on-chain size limit errors during local node validation.

When do I need local node validation for my Gear Sails program?

You need local node validation for your Gear Sails program after completing gtest unit test coverage to verify uninitialized program states, typed client wiring, and deployed behavior before remote network deployment.