Token导航 LogoToken导航TokenDH.com
研究检索可写文件clawhub未标认证来源可访问clear审计提醒

xiaobai-evr-framework小白 evr 框架

Agent Skill

xiaobai-evr-framework 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,916

周安装

124

GitHub Stars

公开资料未说明

下载量

1,022
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:xiaobai-evr-framework(小白 evr 框架)
来源仓库:https://github.com/aptratcn/xiaobai-evr-framework
安装命令:
openclaw skills install xiaobai-evr-framework
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install xiaobai-evr-framework

简介

EVR 框架强制 AI 执行、验证并报告任务结果。

  • 防止虚假完成和无声失败,提升任务可靠性。
  • 适用于需要严格验证输出的代理操作流程。
  • 当用户要求确保任务真实执行时使用。xiaobai-evr-framework 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 需确认执行环境与验证机制的安全性。

SKILL.md

name
evr-framework
description
EVR Framework — Execute-Verify-Report. Force AI to actually DO, then VERIFY, then REPORT. Stop fake completions and silent failures. Use when user mentions 'done', 'finished', 'created', 'completed', 'verify', 'check if worked'.

EVR Framework ✅

Execute → Verify → Report. No more fake completions.

Trigger Phrases

This skill activates when:

  • User asks "did you actually do X?"
  • Agent says "done" or "finished" or "created"
  • User mentions "verify", "check if it worked", "are you sure"
  • Multi-step task is being completed
  • Agent claims to have created/modified/deleted something
  • User is skeptical about completion claims

The Problem

❌ What happens without EVR:
User: "Create a cron job"
Agent: "Done! ✅"
[No cron job exists]
User: [Finds out later nothing was done]
✅ What happens with EVR:
User: "Create a cron job"
Agent: [Creates cron job]
Agent: [Runs verification command]
Agent: "Verified: cron job 'morning-reminder' exists, next run at 08:00 tomorrow. Evidence: cron list output attached."

EVR Protocol

Step 1: EXECUTE

Perform the action for real, not just describe it.

Examples:
- "Create file" → Actually write to filesystem
- "Send message" → Actually call message API
- "Run command" → Actually execute in shell
- "Create cron" → Actually register with scheduler

Step 2: VERIFY

Check the result independently, don't just trust the action.

Verification Commands by Task Type:

| Task Type | Verification Command |
|-----------|---------------------|
| Create file | `ls -la /path/to/file` |
| Edit file | `grep "change" /path/to/file` |
| Create cron | `openclaw cron list` |
| Send message | Check for message ID in response |
| Install package | `which package-name` |
| Start service | `systemctl status service` |
| Git push | `git log --oneline -1` |
| Create repo | `gh repo view repo-name` |

Step 3: REPORT

State completion with evidence, not just "done".

Report Format:
"[Action] completed. Verified: [what you checked]. Evidence: [output/result]."

Examples:
✅ "Cron job created. Verified: 'morning-reminder' appears in cron list. Next run: 08:00 tomorrow."
✅ "File written. Verified: /tmp/test.txt exists with 42 bytes. Content preview: 'Hello World...'"
✅ "Message sent. Verified: message ID ROBOT1.0_xxx received. Delivery confirmed."

Before/After Examples

Example 1: Creating a Cron Job

Without EVR:

User: Create a daily reminder at 8am
Agent: Done! I've created your daily reminder at 8am.
[Nothing was actually created]

With EVR:

User: Create a daily reminder at 8am
Agent: [Executes: openclaw cron add --name "daily-reminder" --cron "0 8 * * *"]
Agent: [Verifies: openclaw cron list --json]
Agent: Daily reminder created and verified.
       Job ID: abc123
       Schedule: 0 8 * * * (daily at 08:00)
       Status: enabled
       Next run: tomorrow 08:00

Example 2: Writing a File

Without EVR:

User: Create a config file
Agent: I've created the config file for you.
[File doesn't exist]

With EVR:

User: Create a config file
Agent: [Executes: write to /app/config.json]
Agent: [Verifies: cat /app/config.json]
Agent: Config file created and verified.
       Path: /app/config.json
       Size: 256 bytes
       Content: {"name": "myapp", "version": "1.0.0", ...}

Example 3: Sending a Message

Without EVR:

User: Send this to John
Agent: Message sent to John!
[Message never sent]

With EVR:

User: Send this to John
Agent: [Executes: message API call]
Agent: [Verifies: check response for message_id]
Agent: Message sent and verified.
       Recipient: John (user_id: xxx)
       Message ID: ROBOT1.0_xxx
       Timestamp: 2026-04-21 08:00:00
       Status: delivered

Integration with Other Skills

With Memory Guard

After completing important tasks:

  1. Execute task
  2. Verify completion
  3. Save to memory with evidence
  4. Report to user

With Error Recovery

If verification fails:

  1. Log the error
  2. Attempt retry (up to 3 times)
  3. If still failing, report to user with details
  4. Don't claim completion until verified

With Self-Improve

When EVR catches a fake completion:

  1. Log as mistake type: "fake_completion"
  2. Add to WORK_RULES.md: "Must verify before claiming done"
  3. Never repeat this mistake

Verification Checklist

Before saying "done", ask yourself:

  • [ ] Did I actually execute the action?
  • [ ] Did I run a verification command?
  • [ ] Does the verification output confirm success?
  • [ ] Am I reporting with evidence, not just assertion?

Anti-Patterns

PatternWhy It's WrongFix
"I've created X"No verificationRun command to check X exists
"Done ✅"No evidenceAttach verification output
"Should be working"UncertaintyVerify it's working
"Successfully completed"Self-assertionShow external confirmation

License

MIT

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

82.17%
按下载量换算840

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

可写文件

该 Skill 可能写入或修改本地文件,使用前需要确认目标目录和修改范围。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills