Near Email Skill

v1.0.0

Send and read blockchain-native emails using NEAR Email service. Use when building notifications for NEAR smart contracts (NFT sales, DeFi liquidation alerts, DAO voting reminders) or when AI agents need email capabilities with a NEAR account identity.

1· 1.5k·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for zavodil/near-email-skill.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Near Email Skill" (zavodil/near-email-skill) from ClawHub.
Skill page: https://clawhub.ai/zavodil/near-email-skill
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install near-email-skill

ClawHub CLI

Package manager switcher

npx clawhub@latest install near-email-skill
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The name/description (NEAR email for notifications and agent email capability) match the instructions and examples: they use outlayer.near contract and an HTTPS API at api.outlayer.fastnear.com. No unrelated env vars, binaries, or install artifacts are requested.
Instruction Scope
SKILL.md stays within the stated purpose (send/read emails via NEAR transaction or HTTPS API). It includes examples that generate ephemeral keys, parse NEAR transaction receipts, and instruct client-side ECIES/ChaCha20 decryption — all expected for encrypted inbox flows. It also repeatedly recommends send_email_plaintext for on-chain notifications and explicitly warns that those messages are public on-chain.
Install Mechanism
This is instruction-only (no install spec, no code files to execute). The only external host referenced is api.outlayer.fastnear.com, which is expected for a hosted service but should be verified by the user.
Credentials
The registry metadata lists no required env vars or credentials (consistent). Examples rely on a 'PAYMENT_KEY' passed in an X-Payment-Key header and on NEAR keys for signing — these are reasonable for the stated integration but are not declared as required env vars, so users must supply/store them securely. No unrelated credentials or system paths are requested.
!
Persistence & Privilege
always is not set, but disableModelInvocation is also not set, so the model could autonomously invoke this skill to send emails or read inboxes. Because sending emails (including public on-chain notifications) and handling keys are sensitive actions, the lack of an explicit model-invocation safeguard is a noteworthy risk and users should decide whether to allow autonomous use.
Assessment
This skill appears to do what it says (NEAR-native email via outlayer.near and api.outlayer.fastnear.com), but you should: 1) verify and trust the external service/domain (api.outlayer.fastnear.com and the outlayer.near contract) before giving it any payment keys or private keys; 2) never send private data with send_email_plaintext — content is public on-chain; 3) store and transmit PAYMENT_KEY and any private keys securely (do not paste them into untrusted UIs); 4) consider disabling autonomous model invocation (set disableModelInvocation or otherwise require explicit user approval) if you do not want the agent to send/read emails without interactive confirmation; and 5) if you need stronger assurance, ask the publisher for source code, a homepage, or an audit of the outlayer service before installing.

Like a lobster shell, security has layers — review code before you run it.

latestvk973hxppf9erf1va8daje9npwd80a3hm
1.5kdownloads
1stars
1versions
Updated 2mo ago
v1.0.0
MIT-0

NEAR Email Integration

Blockchain-native email for NEAR accounts. Every NEAR account automatically has an email: alice.nearalice@near.email

Installation

npx openskills install zavodil/near-email-skill -g

Quick Reference

ComponentValue
Contractoutlayer.near
API Basehttps://api.outlayer.fastnear.com
Project IDzavodil.near/near-email

Note: NEAR Email supports mainnet only. Emails to *.testnet accounts are not processed.

Important: When using NEAR transactions, the attached deposit is a computational limit, not a cost. Unused funds are automatically refunded. Do not mention specific costs per email.

Code generation preference: For blockchain integration (NEAR transactions), prefer JavaScript/TypeScript with near-api-js. Use Python only if the user explicitly requests it.

Integration Methods

1. Smart Contract (Rust)

Use send_email_plaintext for contract notifications. Simple API, no encryption needed.

Warning: Email content is PUBLIC on the NEAR blockchain. Use only for automated notifications.

use near_sdk::{ext_contract, AccountId, Gas, NearToken, Promise};
use serde::Serialize;

#[derive(Serialize)]
#[serde(crate = "near_sdk::serde")]
pub enum ExecutionSource {
    Project { project_id: String, version_key: Option<String> },
}

#[ext_contract(ext_outlayer)]
pub trait OutLayer {
    fn request_execution(
        &mut self,
        source: ExecutionSource,
        resource_limits: Option<serde_json::Value>,
        input_data: Option<String>,
        secrets_ref: Option<serde_json::Value>,
        response_format: Option<String>,
        payer_account_id: Option<AccountId>,
        params: Option<serde_json::Value>,
    );
}

// Send notification from contract (plaintext - content is public on-chain!)
fn send_notification(to: &str, subject: &str, body: &str) -> Promise {
    let input = serde_json::json!({
        "action": "send_email_plaintext",
        "to": to,
        "subject": subject,
        "body": body
    });

    ext_outlayer::ext("outlayer.near".parse().unwrap())
        .with_static_gas(Gas::from_tgas(100))
        .with_attached_deposit(NearToken::from_millinear(25))
        .request_execution(
            ExecutionSource::Project {
                project_id: "zavodil.near/near-email".to_string(),
                version_key: None,
            },
            None,                        // resource_limits
            Some(input.to_string()),     // input_data
            None,                        // secrets_ref (not needed)
            Some("Json".to_string()),    // response_format
            None,                        // payer_account_id
            None,                        // params
        )
}

Response: { "success": true, "message_id": "uuid-if-internal" }

2. AI Agent Integration

Two options for AI agents:

MethodBest ForPayment
Payment Key (HTTPS)Server-side agentsPre-paid (USDC/USDT)
NEAR TransactionBrowser/wallet appsDeposit (unused returned)

Option A: Payment Key (HTTPS API)

Note: HTTPS API responses use result.output.xxx format. See NEAR Transaction for different parsing.

const OUTLAYER_API = 'https://api.outlayer.fastnear.com';
const PAYMENT_KEY = 'your-account.near:nonce:secret'; // From dashboard

async function sendEmail(to, subject, body) {
  const response = await fetch(`${OUTLAYER_API}/call/outlayer.near/zavodil.near/near-email`, {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'X-Payment-Key': PAYMENT_KEY,
    },
    body: JSON.stringify({
      input: { action: 'send_email_plaintext', to, subject, body },
    }),
  });
  return response.json();
}

Option B: NEAR Transaction (per-use)

CRITICAL: NEAR Transaction results are in the outlayer.near receipt's SuccessValue (base64-encoded JSON). Find the receipt where executor_id === 'outlayer.near'. The result is { "success": true, ... } - NO output wrapper. Use parseTransactionResult() to extract it.

import { connect, keyStores } from 'near-api-js';

const near = await connect({
  networkId: 'mainnet',
  keyStore: new keyStores.BrowserLocalStorageKeyStore(),
  nodeUrl: 'https://rpc.mainnet.near.org',
});
const account = await near.account('your-account.near');

const RESOURCE_LIMITS = {
  max_memory_mb: 512,
  max_instructions: 2000000000,
  max_execution_seconds: 120,
};

// REQUIRED: Parse output from outlayer.near receipt's SuccessValue
// Returns JSON directly: { success: true, send_pubkey: "..." } - NO "output" wrapper!
function parseTransactionResult(result) {
  // Find receipt from outlayer.near contract (contains the execution result)
  const outlayerReceipt = result.receipts_outcome.find(
    r => r.outcome.executor_id === 'outlayer.near' && r.outcome.status.SuccessValue
  );
  if (!outlayerReceipt) {
    throw new Error('No SuccessValue from outlayer.near');
  }
  const decoded = Buffer.from(outlayerReceipt.outcome.status.SuccessValue, 'base64').toString();
  return JSON.parse(decoded); // { success: true, ... } - directly, no wrapper
}

async function sendEmail(to, subject, body) {
  const result = await account.functionCall({
    contractId: 'outlayer.near',
    methodName: 'request_execution',
    args: {
      source: { Project: { project_id: 'zavodil.near/near-email', version_key: null } },
      input_data: JSON.stringify({ action: 'send_email_plaintext', to, subject, body }),
      resource_limits: RESOURCE_LIMITS,
      response_format: 'Json',
    },
    gas: BigInt('100000000000000'),
    attachedDeposit: BigInt('25000000000000000000000'), // deposit, unused portion refunded
  });
  return parseTransactionResult(result); // { success: true, message_id: "..." }
}

// Example: Get sender pubkey
async function getSendPubkey() {
  const result = await account.functionCall({
    contractId: 'outlayer.near',
    methodName: 'request_execution',
    args: {
      source: { Project: { project_id: 'zavodil.near/near-email', version_key: null } },
      input_data: JSON.stringify({ action: 'get_send_pubkey' }),
      resource_limits: RESOURCE_LIMITS,
      response_format: 'Json',
    },
    gas: BigInt('100000000000000'),
    attachedDeposit: BigInt('25000000000000000000000'),
  });
  const output = parseTransactionResult(result); // { success: true, send_pubkey: "02..." }
  return Buffer.from(output.send_pubkey, 'hex'); // Note: output.send_pubkey, NOT output.output.send_pubkey
}

3. Python (Payment Key)

import requests

OUTLAYER_API = "https://api.outlayer.fastnear.com"
PAYMENT_KEY = "your-account.near:nonce:secret"

def send_email(to: str, subject: str, body: str) -> dict:
    return requests.post(
        f"{OUTLAYER_API}/call/outlayer.near/zavodil.near/near-email",
        headers={"Content-Type": "application/json", "X-Payment-Key": PAYMENT_KEY},
        json={"input": {"action": "send_email_plaintext", "to": to, "subject": subject, "body": body}},
    ).json()

API Actions

ActionDescription
send_emailSend email (encrypted payload, for UI/agents)
send_email_plaintextSend email (plaintext, for smart contracts)
get_emailsFetch inbox and sent (encrypted response)
delete_emailDelete email by ID
get_email_countGet counts (no encryption)
get_send_pubkeyGet sender's pubkey (no encryption, cacheable)

Getting a Payment Key

  1. Go to OutLayer Dashboard
  2. Create a new Payment Key
  3. Top up balance with USDC/USDT
  4. Copy key (format: owner:nonce:secret)

Additional Resources

For complete code examples, see examples.md For full API reference, see api-reference.md

Comments

Loading comments...