Description

Send XCH to Twitter users via Go4Me address lookup. Use when sending Chia (XCH) to someone by their Twitter handle, looking up a Twitter user's XCH address, or tipping someone on Go4Me. Triggers on "send XCH to @user", "tip @user", "lookup @user on go4me", "what's @user's XCH address".

README (SKILL.md)

Go4Me Skill

Name: Go4Me
Author: koba42corp

Send XCH to Twitter users by resolving their Go4Me addresses.

Dependencies

sage-wallet — Required for XCH transactions

Commands

Command	Description
`/go4me lookup \x3Cuser>`	Get user's XCH address and profile
`/go4me send \x3Cuser> \x3Camount>`	Send XCH to user (amount in XCH or mojos)
`/go4me tip \x3Cuser>`	Send 1 mojo tip

Natural Language

"Send 1 XCH to @hoffmang"
"Tip @sage_wallet"
"What's @bramcohen's XCH address?"
"Look up DracattusDev on Go4Me"

Lookup Script

source scripts/go4me-lookup.sh
go4me_lookup "DracattusDev"  # Returns JSON or exits 1

Workflow

Lookup

Strip @ from username if present
Run go4me_lookup "\x3Cusername>"
Parse JSON response for xchAddress, fullName, username
If exit code 1: user not found on Go4Me

Send

Lookup user (as above)
If not found, report error

Display confirmation:

Send \x3Camount> to @\x3Cusername> (\x3CfullName>)?
Address: \x3CxchAddress>
[Yes] [No]

On confirm, call sage-wallet send_xch:

curl -s --cert $CERT --key $KEY -X POST https://127.0.0.1:9257/send_xch \
  -H "Content-Type: application/json" \
  -d '{"address":"\x3CxchAddress>","amount":"\x3Cmojos>","fee":"0","memos":[],"auto_submit":true}'

Report transaction result

Tip

Same as send with amount = 1 mojo.

Amount Conversion

Input	Mojos
`1` (no unit)	1 mojo
`1 mojo`	1
`0.001 XCH`	1000000000
`1 XCH`	1000000000000

Parse amount: if contains "XCH", multiply by 10^12. Default unit is mojos for small numbers, XCH for decimals.

Error Handling

Condition	Response
User not on Go4Me	"User @{username} not found on Go4Me"
Invalid address	"Invalid XCH address returned from Go4Me"
Insufficient balance	"Insufficient balance for this transaction"
Network error	"Failed to connect to Go4Me"

Data Available

Field	Example
`username`	DracattusDev
`fullName`	🌱Drac 🍊
`xchAddress`	xch1rvgc3naytvzhv4lxhzphrdr2fzj2ka340tdj8fflt4872t2wqveq9lwz7t
`description`	Bio text
`avatarUrl`	Profile image URL
`totalBadgeScore`	220

Usage Guidance

This skill appears to implement Go4Me lookups and to call a local sage-wallet RPC to send XCH — that behavior is consistent with its description. However, before installing or granting it use, check and do the following: (1) Understand that sending requires access to your local wallet TLS client certificate and key (the SKILL.md uses $CERT and $KEY). The skill metadata does not declare these env vars; do not provide them until the skill explicitly documents and justifies how they will be used and protected. (2) Confirm that the agent environment has curl and jq installed; the script depends on them. (3) Verify that the skill will always prompt for an explicit confirmation before submitting any transaction (the docs show a prompt, but verify actual behavior). (4) Audit the skill's behavior locally (source the script and run lookup-only commands) before enabling send capability. (5) Consider running lookups only — do not give wallet credentials to the skill until the author clarifies the required environment variables and how the private credentials are kept local and not exfiltrated. If the author can update the metadata to list required binaries and required env vars (CERT, KEY) and provide clearer info about transaction confirmation and failure modes, this would reduce concern.

Capability Analysis

Type: OpenClaw Skill Name: go4me Version: 1.0.0 The skill's primary purpose is to resolve Go4Me addresses for Twitter users and facilitate sending Chia (XCH) via a local wallet. The `scripts/go4me-lookup.sh` file makes an external `curl` request to `https://<username>.go4.me/` to retrieve user data, which is essential for its stated functionality. The `SKILL.md` instructs the agent to interact with a local wallet RPC at `https://127.0.0.1:9257/send_xch` using `curl` with `$CERT` and `$KEY` for secure communication, which is an expected and standard practice for cryptocurrency transactions within the OpenClaw environment. There is no evidence of data exfiltration, malicious execution, persistence, or prompt injection attempts beyond the skill's clearly defined and necessary operations.

Capability Assessment

ℹ Purpose & Capability

The skill's stated purpose (resolve Go4Me/Twitter handles and send XCH) matches the code and README. Expectation of a local wallet RPC (sage-wallet) is reasonable for sending transactions. However, the skill metadata declares no dependencies or credentials while README/SKILL.md explicitly reference sage-wallet and the send flow, so the declared requirements are incomplete.

⚠ Instruction Scope

Runtime instructions and the included script perform network fetches of https://<username>.go4.me/ and parse embedded JSON, which is appropriate for address lookup. The send workflow instructs the agent to POST to https://127.0.0.1:9257/send_xch using client TLS cert/key ($CERT and $KEY) — these environment variables are used in the instructions but are not declared in requires.env. The agent would need access to local wallet credentials to complete transactions; this capability is sensitive and not surfaced in the skill metadata.

✓ Install Mechanism

This is an instruction-only skill with one small shell script; there is no install step or external archive download. That lowers installation risk. Nevertheless, the script depends on system tools (curl, jq) which are not declared as required binaries in the metadata.

⚠ Credentials

The skill requires access to a local wallet RPC with client TLS cert and key (referenced as $CERT and $KEY in SKILL.md) to send funds, but the skill metadata lists no required environment variables or primary credential. Requiring wallet certs/keys to send funds would be proportionate to the purpose, but they must be explicitly declared and justified — the omission is a red flag. The script also implicitly requires curl and jq (not declared).

✓ Persistence & Privilege

The skill is not marked always:true and does not request modification of other skills or global agent settings. It can be invoked by the agent (default), which is expected for a send/lookup skill.

Version History

v1.0.0

Go4Me Skill v1.0.0 - Initial release: Send Chia (XCH) to Twitter users via Go4Me address lookup. - Natural language triggers like "send XCH to @user," "tip @user," and address lookup supported. - Integrates with sage-wallet for sending XCH. - Handles user lookups, sending, tipping (1 mojo), and error reporting. - Supports XCH/mojo amount parsing and conversion. - Provides profile details and transaction confirmation steps.

Metadata

Slug go4me

Version 1.0.0

License —

All-time Installs 0

Active Installs 0

Total Versions 1

Frequently Asked Questions

What is Go4Me?

Send XCH to Twitter users via Go4Me address lookup. Use when sending Chia (XCH) to someone by their Twitter handle, looking up a Twitter user's XCH address, or tipping someone on Go4Me. Triggers on "send XCH to @user", "tip @user", "lookup @user on go4me", "what's @user's XCH address". It is an AI Agent Skill for Claude Code / OpenClaw, with 1564 downloads so far.

How do I install Go4Me?

Run "/install go4me" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Go4Me free?

Yes, Go4Me is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Go4Me support?

Go4Me is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Go4Me?

It is built and maintained by Koba42Corp (@koba42corp); the current version is v1.0.0.

More Skills

Go4Me