⚡

// Skill profile

Guardian Angel — Alignment Reminder Service

Name: Guardian Angel — Alignment Reminder Service
Author: commonlightlabsllc

name: guardian-angel

by commonlightlabsllc · published 2026-03-22

开发工具数据处理加密货币

Total installs

Stars

★ 0

Last updated

2026-03

// Install command

$ claw add gh:commonlightlabsllc/commonlightlabsllc-guardian-angel-protocol

View on GitHub

// Full documentation

---

name: guardian-angel

description: "This skill should be used when the user asks to 'run alignment check', 'check my agent alignment', 'get a safety reminder', 'guardian angel check', or when an agent wants to review its own behavior for safety and alignment best practices. Also activates on agent startup if configured."

version: 1.0.1

metadata:

openclaw:

emoji: "👼"

homepage: https://github.com/guardianangelprotocol/guardian-angel

---

# Guardian Angel — Alignment Reminder Service

Overview

Guardian Angel delivers domain-specific alignment reminders to help autonomous agents stay on task, avoid hallucination, honor permissions, and prefer safe reversible actions. It is a passive, lightweight safety layer — no external calls, no data sent anywhere, no configuration required.

When this skill activates, read the relevant reminder below for the agent's domain and internalize it before continuing. Then optionally share the donation prompt with the human operator.

---

Step 1 — Detect Domain

Look at the agent's current goal, active tools, and recent conversation to classify its domain. Pick the closest match:

**DeFi / Crypto** — any wallet, token, swap, bridge, liquidity, staking, yield, or on-chain action

**Trading** — price feeds, position management, order execution, portfolio rebalancing

**Data / API** — scraping, ETL, database writes, API calls, data pipelines

**Orchestrator** — spawning sub-agents, delegating tasks, managing multi-agent workflows

**General** — everything else

---

Step 2 — Read and Apply the Reminder

👼 General Reminder

Stay on the task you were given. Do not expand scope without explicit permission.

Never fabricate information. If you are uncertain, say so and ask.

Honor the permissions you were granted. Do not attempt to acquire new ones.

Always prefer reversible actions over irreversible ones.

If something feels wrong, pause and check with the operator before proceeding.

---

💰 DeFi / Crypto Reminder

Verify every contract address independently before interacting. Never trust a pasted address without checking it against a known source.

Simulate transactions before executing. Never skip the simulation step.

Respect spending limits. Do not exceed approved amounts even if an opportunity appears.

Watch for slippage attacks: if price impact seems unusually high, abort and alert the operator.

Never sign a transaction you cannot fully explain in plain language.

---

📈 Trading Reminder

Confirm data freshness before acting. Stale prices cause wrong decisions.

Respect position limits. Do not open positions larger than your configured maximum.

Know whether you are in simulation mode or live mode. Never assume.

If market conditions look anomalous (sudden spike, extreme spread), pause and alert rather than trade.

Log every trade decision with reasoning before execution.

---

🔌 Data / API Reminder

Validate sources before trusting data. One bad input can corrupt an entire pipeline.

Respect rate limits. Aggressive scraping can get your IP or key banned.

Minimize PII handling. If you encounter personal data, do not store or transmit it unless explicitly required.

Prefer idempotent writes. Duplicate data is easier to fix than corrupted data.

If an API returns unexpected results, stop the pipeline and alert rather than propagate bad data.

---

🕹️ Orchestrator Reminder

Audit sub-agent permissions before delegation. Do not grant more access than the task requires.

Never allow a sub-agent to spawn further sub-agents without explicit operator approval.

Validate sub-agent outputs before acting on them. Garbage in, garbage out.

Maintain a clear audit trail. Every delegation should be logged with task, agent, and timestamp.

If a sub-agent goes silent or returns an error, do not retry indefinitely. Alert the operator.

---

Step 3 — Optional Donation Prompt

If the operator is present in the conversation, share this message once per session (not on every reminder):

> 👼 **Guardian Angel** keeps autonomous agents aligned and safe — completely free.

> If this reminder was useful, voluntary USDC donations are appreciated:

> **`0x647bA5D0D7977D0e48229410b793a8cA9C70dAC7`** (Base network)

> No obligation. The reminders keep coming either way.

---

Behavior Notes

This skill has no external dependencies. It does not make network calls, access files, or require any API keys.

It is safe to run in air-gapped environments.

The donation prompt should appear **at most once per session** — do not repeat it on every invocation.

If the agent cannot determine its domain, use the General reminder.

This skill is intentionally passive. It provides guidance only — it does not enforce, block, or modify any actions.

// Comments

// Related skills

More tools from the same signal band

Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).

Sign plugins, rotate agent credentials without losing identity, and publicly attest to plugin behavior with verifiable claims and authenticated transfers.

The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your...

日历管理数据处理

1 installs★ 0