near-email-reporter

Communication
v1.0.0
Benign

Send NEAR reports and alerts via email with SMTP configuration, scheduling, and automatic reporting.

793 downloads793 installsby @shaiss

Setup & Installation

Install command

clawhub install shaiss/near-email-reporter

If the CLI is not installed:

Install command

npx clawhub@latest install shaiss/near-email-reporter

Or install with OpenClaw CLI:

Install command

openclaw skills install shaiss/near-email-reporter

or paste the repo link into your assistant's chat

Install command

https://github.com/openclaw/skills/tree/main/skills/shaiss/near-email-reporter

What This Skill Does

Sends NEAR blockchain transaction reports and balance alerts to email addresses via SMTP. Supports cron-based scheduling and configurable alert thresholds. Email settings are stored locally in a config file.

Automates NEAR account monitoring through email without requiring manual checks on blockchain explorers or custom notification infrastructure.

When to Use It

  • Scheduling daily NEAR account balance summaries
  • Receiving alerts when a NEAR account balance drops below a set amount
  • Emailing transaction reports to a team inbox
  • Automating weekly NEAR activity digests
  • Monitoring a NEAR account with periodic scheduled reports
View original SKILL.md file
# NEAR Email Reporter Skill

Send NEAR transaction reports via email with scheduling.

## Description

This skill allows you to configure email settings, send NEAR transaction reports, set up alerts, and schedule periodic email reports. Uses standard SMTP with secure configuration storage.

## Features

- Configure SMTP email settings
- Send transaction reports via email
- Set up alerts for specific events
- Schedule periodic reports
- Secure configuration storage

## Commands

### `near-email setup [options]`
Configure email settings.

**Options:**
- `--host <host>` - SMTP server host
- `--port <port>` - SMTP server port (default: 587)
- `--user <user>` - SMTP username
- `--pass <pass>` - SMTP password
- `--from <email>` - From email address
- `--secure` - Use SSL/TLS (default: false)

**Example:**
```bash
near-email setup --host smtp.gmail.com --port 587 --user myemail@gmail.com --pass mypassword --from myemail@gmail.com
```

### `near-email report <account_id> [recipient]`
Send a transaction report for an account.

**Parameters:**
- `account_id` - NEAR account to report on
- `recipient` - Email recipient (optional, uses default)

### `near-email alert <account_id> <threshold> [recipient]`
Set up balance alert for an account.

**Parameters:**
- `account_id` - NEAR account to monitor
- `threshold` - Balance threshold (in NEAR)
- `recipient` - Email recipient (optional)

### `near-email schedule <account_id> <cron_expr> [recipient]`
Schedule periodic email reports.

**Parameters:**
- `account_id` - NEAR account to report on
- `cron_expr` - Cron expression (e.g., "0 9 * * *" for daily at 9am)
- `recipient` - Email recipient (optional)

## Configuration

Email settings are stored in `~/.near-email/config.json` with secure permissions.

## Requirements

- SMTP email account (Gmail, SendGrid, etc.)
- Node.js for running the scripts

## Notes

- For Gmail, use App Passwords: https://myaccount.google.com/apppasswords
- Configuration file is stored securely with limited permissions

## References

- Nodemailer: https://nodemailer.com/
- NEAR RPC API: https://docs.near.org/api/rpc

Example Workflow

Here's how your AI assistant might use this skill in practice.

INPUT

User asks: Scheduling daily NEAR account balance summaries

AGENT
  1. 1Scheduling daily NEAR account balance summaries
  2. 2Receiving alerts when a NEAR account balance drops below a set amount
  3. 3Emailing transaction reports to a team inbox
  4. 4Automating weekly NEAR activity digests
  5. 5Monitoring a NEAR account with periodic scheduled reports
OUTPUT
Send NEAR reports and alerts via email with SMTP configuration, scheduling, and automatic reporting.

Share this skill

Security Audits

VirusTotalBenign
OpenClawBenign
View full report

These signals reflect official OpenClaw status values. A Suspicious status means the skill should be used with extra caution.

Details

LanguageMarkdown
Last updatedFeb 28, 2026