near-email-reporter

What This Skill Does

The near-email-reporter skill serves as a dedicated communication layer for your NEAR Protocol activities. By integrating SMTP capabilities directly into your agent, it allows for automated oversight of your blockchain presence. Instead of manually querying blockchain explorers, you can rely on this skill to push status updates, balance alerts, and full transaction history summaries directly to your inbox. It acts as a bridge between the decentralized ledger and your personal notification infrastructure, ensuring you remain informed about your account health without constant manual intervention.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/shaiss/near-email-reporter

Once installed, you must perform an initial setup to authorize the agent to send mail on your behalf. Use the command near-email setup providing your SMTP server credentials (host, port, user, and password). For increased security, it is highly recommended to use App Passwords for services like Gmail, as this limits the scope of access provided to the agent.

Use Cases

• Automated Financial Reporting: Generate and email daily or weekly summaries of transaction activity for your NEAR wallets for accounting or tax purposes.
• Security Monitoring: Receive instant email alerts if your wallet balance drops below a specific threshold, helping you detect potential unauthorized drainage or unexpected contract interactions.
• Wallet Management: Keep team members or collaborators updated on treasury movements without sharing private keys, using the recipient parameters to direct specific reports to relevant stakeholders.

Example Prompts

1. "Send a transaction report for my account 'my-near-wallet.near' to my work email."
2. "Set up a recurring daily report for 'treasury.near' at 8 AM and send it to [email protected]."
3. "Configure a balance alert for 'personal.near' so I get an email if the balance falls below 50 NEAR."

Tips & Limitations

• Security: The configuration file is stored in your user directory. Ensure your host machine has restricted permissions on the ~/.near-email/ directory.
• SMTP Providers: Ensure your provider allows programmatic access. Some providers may block non-standard authentication attempts if you do not use app-specific passwords or if your IP address is not whitelisted.
• Cron Logic: When scheduling, ensure your system time is set correctly, as the cron engine relies on the host machine's system clock.
• Dependency: This skill requires an active internet connection to communicate with both the NEAR RPC API and your SMTP relay.