How do I install the Aelf Node Skill skill?

Run npx skillmds add majiayu000/aelf-node-skill in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Aelf Node Skill skill do?

AElf node querying and contract execution skill for agents. It is listed under Integrations & APIs on SkillMD.

Is Aelf Node Skill safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aelf Node Skill?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aelf Node Skill free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aelf Node Skill?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aelf Node Skill by majiayu000 — Agent Skill

Name: Aelf Node Skill
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

AElf Node Skill

When to use

Use this skill when you need AElf chain query, contract view/send, and fee estimation tasks.
Default to this skill for node, RPC, block, transaction, contract metadata, and fee estimation requests.

Capabilities

Chain reads: status, block, transaction result, metadata
Contract operations: view call and transaction sending
Node registry import/list with REST-first and SDK fallback strategy
Shared signer resolution for write operations: explicit -> context -> env
Supports SDK, CLI, MCP, OpenClaw, and IronClaw integration from one codebase.

Safe usage rules

Never print private keys, mnemonics, or tokens in channel outputs.
For write operations, require explicit user confirmation and validate parameters before sending transactions.
Prefer simulate or read-only queries first when available.
Active wallet context contains identity metadata only; never persist plaintext private keys.

Command recipes

Start MCP server: bun run mcp
Run CLI entry: bun run cli
Install into IronClaw: bun run setup ironclaw
Generate OpenClaw config: bun run build:openclaw
Verify OpenClaw config: bun run build:openclaw:check
Run CI coverage gate: bun run test:coverage:ci
For write calls, pass optional signerContext with signerMode=auto.

Distribution / Activation

GitHub repo/tree URLs are discovery-only for hosts and agents.
Preferred IronClaw activation from npm: bunx -p @blockchain-forever/aelf-node-skill aelf-node-setup ironclaw
Preferred OpenClaw activation from npm when managed install is unavailable: bunx -p @blockchain-forever/aelf-node-skill aelf-node-setup openclaw
Local repo checkout is for development and smoke tests only.

Limits / Non-goals

This skill focuses on domain operations and adapters; it is not a full wallet custody system.
Do not hardcode environment secrets in source code or docs.
Avoid bypassing validation for external service calls.
signerMode=daemon is reserved and returns SIGNER_DAEMON_NOT_IMPLEMENTED in this release.
Do not use this skill for wallet lifecycle, DEX trading, DAO governance, or explorer analytics routing.

---name: aelf-node-skilldescription: AElf node querying and contract execution skill for agents.--- # AElf Node Skill ## When to use - Use this skill when you need AElf chain query, contract view/send, and fee estimation tasks. - Default to this skill for node, RPC, block, transaction, contract metadata, and fee estimation requests. ## Capabilities - Chain reads: status, block, transaction result, metadata - Contract operations: view call and transaction sending - Node registry import/list with REST-first and SDK fallback strategy - Shared signer resolution for write operations: `explicit -> context -> env` - Supports SDK, CLI, MCP, OpenClaw, and IronClaw integration from one codebase. ## Safe usage rules - Never print private keys, mnemonics, or tokens in channel outputs. - For write operations, require explicit user confirmation and validate parameters before sending transactions. - Prefer `simulate` or read-only queries first when available. - Active wallet context contains identity metadata only; never persist plaintext private keys. ## Command recipes - Start MCP server: `bun run mcp` - Run CLI entry: `bun run cli` - Install into IronClaw: `bun run setup ironclaw` - Generate OpenClaw config: `bun run build:openclaw` - Verify OpenClaw config: `bun run build:openclaw:check` - Run CI coverage gate: `bun run test:coverage:ci` - For write calls, pass optional `signerContext` with `signerMode=auto`. ## Distribution / Activation - GitHub repo/tree URLs are discovery-only for hosts and agents. - Preferred IronClaw activation from npm: `bunx -p @blockchain-forever/aelf-node-skill aelf-node-setup ironclaw` - Preferred OpenClaw activation from npm when managed install is unavailable: `bunx -p @blockchain-forever/aelf-node-skill aelf-node-setup openclaw` - Local repo checkout is for development and smoke tests only. ## Limits / Non-goals - This skill focuses on domain operations and adapters; it is not a full wallet custody system. - Do not hardcode environment secrets in source code or docs. - Avoid bypassing validation for external service calls. - `signerMode=daemon` is reserved and returns `SIGNER_DAEMON_NOT_IMPLEMENTED` in this release. - Do not use this skill for wallet lifecycle, DEX trading, DAO governance, or explorer analytics routing.

Frequently asked questions