sails-ethexe-implementer
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.
What this skill does
# Sails Ethexe Implementer
## Overview
Implement approved tasks in Sails ethexe workspaces where the `ethexe` feature is enabled and methods may be exported via ethabi transport, accept value (payable), or emit Ethereum-style events.
If the task does NOT need the ethexe feature, use `../sails-rust-implementer/SKILL.md` instead.
## Inputs
- `../../references/sails-ethexe-patterns.md` — ethexe diff table, type requirements, transport rules, event patterns
- `../../references/sails-syscall-mapping.md` — `Syscall::*` API (note gated syscalls)
- `../../references/sails-cheatsheet.md` — core Sails patterns
- `../../references/sails-rs-imports.md` — import paths
- `../../references/sails-idl-v2-syntax.md` — IDL v2 annotations
- `../../references/sails-header-wire-format.md` — Sails Header routing
Consume the approved `spec`, `architecture`, and `tasks` artifacts before changing code.
## Workflow
1. Confirm the task is specified and architecture-approved.
2. Confirm the crate has `sails-rs` with `features = ["ethexe"]` in `Cargo.toml`.
3. Identify the smallest code change that satisfies the task.
4. Use `#[sails_type]` for all custom types. Types used in ethabi-exported methods must also be ABI-encodable as Solidity tuples (`SolValue`).
5. Choose the correct transport per method:
- `#[export]` — both scale + ethabi (default with ethexe)
- `#[export(scale)]` — scale only, no ethabi
- `#[export(ethabi)]` — ethabi only
- `#[export(ethabi, payable)]` — ethabi with value acceptance
6. Use `emit_eth_event()` for Ethereum-style events, `emit_event()` for standard Gear events. Do not mix them on the same event type without explicit architecture guidance.
7. Mark `#[indexed]` on up to 3 event fields per variant for Ethereum topic indexing.
8. Use `Syscall::*` for runtime accessors. Three syscalls are unavailable: `signal_from`, `signal_code`, `system_reserve_gas`.
9. Hand verification to the gtest loop before claiming done.
## Transport Decision Guide
| Scenario | Attribute |
|----------|-----------|
| Standard method, both transports | `#[export]` |
| Method only callable from Gear programs (no EVM) | `#[export(scale)]` |
| Method only callable from EVM | `#[export(ethabi)]` |
| Method that accepts value from EVM | `#[export(ethabi, payable)]` or `#[export(scale, ethabi, payable)]` |
| Query (read-only) | `#[export]` (transport flags orthogonal to query semantics) |
## Payable Methods
Non-payable methods panic at runtime if `msg::value() > 0`. To accept value:
```rust
#[export(payable)]
pub fn deposit(&mut self) -> u64 {
let value = Syscall::message_value();
// handle deposit...
value as u64
}
```
Constructors can also be payable: `#[export(payable)] pub fn create() -> Self { ... }`
## Eth Events
```rust
#[event]
pub enum MyEvent {
Transfer {
#[indexed]
from: ActorId,
#[indexed]
to: ActorId,
value: u64,
},
Paused,
}
// In service method:
self.emit_eth_event(MyEvent::Transfer { from, to, value });
```
- Max 3 `#[indexed]` fields per variant
- Forbidden variant names: ExecutableBalanceTopUpRequested, Message, MessageQueueingRequested, Reply, ReplyQueueingRequested, StateChanged, ValueClaimed, ValueClaimingRequested
## Guardrails
- Do not use `signal_from()`, `signal_code()`, or `system_reserve_gas()` — they are gated out under ethexe.
- Do not use raw `gcore::*`, `msg::*`, or `exec::*` calls — use `Syscall::*`.
- Do not mark more than 3 fields as `#[indexed]` per event variant.
- Do not use reserved event variant names.
- Do not assume `payable` works with scale-only transport — it requires ethabi.
- Service names must be PascalCase and must not collide with Solidity reserved keywords.
- Preserve released routes, reply shapes, and events unless the task explicitly changes them.
- Use `Syscall::message_source() == Syscall::program_id()` for self-message guards.
- Hand verification to the gtest loop before claiming done.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.