OpenClaw/clawhub-security-signals huggingface dataset:
Skill: xrovis/hire-feishu-agent (version 1.0.0)

--- name: hire-feishu-agent description: | **当用户说出以下类似语句时触发本 Skill**： - "帮我招聘一个飞书助理" - "新增一个飞书渠道的 Agent" - "我要在飞书上部署一个新 Agent" - "hire a Feishu agent" --- # Skill: 招聘飞书 Agent（hire-feishu-agent） ## 操作流程 ### Step 1 — 收集参数（向用户确认以下信息） 如果用户没有主动提供，**主动询问**： | 参数 | 说明 | 示例值 | |------|------|--------| | `agentId` / `accountId` | Agent 唯一 ID，同时用于 account key 和 agentId | `mybot` | | `agentName` | Agent 展示名称（botName） | `我的助手` | | `appId` | 飞书应用的 App ID | `cli_abc123` | | `appSecret` | 飞书应用的 App Secret | `xxxxxxxxxxxxxxxx` | 询问话术示例： > 我需要以下信息来完成配置，请逐一确认： > 1. Agent ID（同时作为飞书账号 key）： > 2. Agent 展示名称（botName）： > 3. 飞书 App ID（cli_ 开头）： > 4. 飞书 App Secret： --- ### Step 2 — 修改 `~/.openclaw/openclaw.json` 三处位置 参考 `schema.md` 中的结构说明，按以下顺序修改： #### 修改位置 1：`channels.feishu.accounts` 在 `accounts` 对象中**新增一个 key**，key 名 = `{agentId}`： ```json "channels": { "feishu": { "accounts": { "{agentId}": { "appId": "{appId}", "appSecret": "{appSecret}" } } } } ``` #### 修改位置 2：`agents.list` 在数组中**追加一个对象**： ```json "agents": { "list": [ { "id": "{agentId}", "workspace": "/Users/${USER}/.openclaw/workspace/[agentId]", "name": "{agentName}" } ] } ``` #### 修改位置 3：`bindings` 在数组中**追加一个绑定规则**（DM 默认路由）： ```json "bindings": [ { "agentId": "{agentId}", "match": { "channel": "feishu", "accountId": "{agentId}" } } ] ``` --- ### Step 3 — 向用户输出最终合并后的 JSON 片段 将三处修改合并展示，方便用户直接复制粘贴进 `openclaw.json`，并提示： ``` 修改完成后请运行： openclaw gateway restart 以使配置生效。 ``` --- ## 注意事项 - 如果 `channels.feishu.accounts` 已有其他 account，**只追加新 key，不要覆盖已有 key**。 - 如果 `agents.list` 已有其他 agent，**只追加，不要替换整个数组**。 - 如果 `bindings` 已有其他规则，**只追加，不要替换整个数组**。 - `agentId` 只允许使用小写字母、数字、连字符（`-`），不能含空格。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: li-jin-xuan/data-recovery-assistant (version 1.0.0)

--- name: data-recovery-assistant description: > 数据恢复诊断助手。教AI Agent诊断各种数据丢失场景（误删、格式化、分区丢失、硬盘异响、RAW分区等）， 推荐对应工具和操作步骤，区分SSD和HDD的不同处理方案。 触发词：数据恢复、文件丢失、误删、格式化、硬盘坏了、分区丢失、恢复数据 --- # 数据恢复诊断助手 > 基于数据恢复专业经验，帮助AI准确诊断数据丢失场景并给出可操作方案。 ## 诊断流程 ### 第一步：确认故障类型 | 症状 | 可能原因 | 紧急程度 | |------|---------|---------| | 误删后回收站清空 | 逻辑删除 | 🔵 低 — 尽快处理即可 | | 格式化/重装系统 | 文件系统覆盖 | 🟡 中 — 越快越好 | | 分区变RAW/无法访问 | 文件系统损坏 | 🟡 中 | | 硬盘不识别/不转 | 电路板/电机故障 | 🔴 高 — 别自己拆 | | 硬盘异响(咔咔/吱吱) | 磁头损坏 | 🔴 紧急 — 立即断电 | | 进水/摔坏 | 物理损坏 | 🔴 紧急 | ### 第二步：按情况推荐方案 **逻辑故障（误删/格式化/RAW分区）：** - 立即停止写入，不要再存新文件 - 推荐工具链：R-Studio → DMDE → Recuva（按优先级） - 镜像优先原则：先用 ddrescue 做全盘镜像，在镜像上恢复 **物理故障（不识别/异响）：** - **不要自己拆盘**，开盘需要超净环境 - 异响立即断电，以免划伤盘片 - 推荐找专业数据恢复机构处理 **SSD 特殊情况：** - TRIM 开启后删除的数据几乎无法恢复 - 主控损坏需要芯片级维修 - 跟HDD的处理方案完全不同 ### 第三步：操作建议 ```markdown ## 用户可以做 1. 下载并运行 DiskGenius/CrystalDiskInfo 查看SMART信息 2. 用 ddrescue 创建磁盘镜像（命令行需要Linux环境） 3. 用 R-Studio/DMDE 在镜像上扫描恢复 ## 用户不要做 1. ⛔ 对异响硬盘通电多次 2. ⛔ 用免费软件反复扫描写入 3. ⛔ 自己开盘更换磁头 4. ⛔ 对SSD做长时间通电解焊 ``` ## 工具参考 | 工具 | 适用场景 | 费用 | |------|---------|------| | ddrescue | Linux下创建磁盘镜像 | 免费 | | TestDisk | 分区表修复 | 免费 | | DMDE | 深度扫描恢复 | 免费版限4000文件 | | R-Studio | 专业恢复(最强) | 付费 | | Recuva | 简单误删恢复 | 免费版可用 | ## 注意事项 - **不要在源盘上操作** — 先镜像再恢复是铁律 - 恢复后的文件不要存回源盘 - 物理故障 vs 逻辑故障的处理方案完全不同，不要混用

path: references/fault-reference.md
content: # 数据恢复故障速查表

## 快速判断故障类型

### 听声音辨故障
| 声音 | 判断 | 怎么做 |
|------|------|--------|
| 滋滋/吱吱 | 磁头可能卡住 | 立即断电，别通电了 |
| 咔咔/哒哒 | 磁头损坏 | 断电，换磁头需要开盘 |
| 嗡嗡但不转 | 电机抱死 | 尝试换电路板 |
| 正常转但不识别 | 可能是固件/电路板问题 | 先查SMART信息 |
| 完全没动静 | 电路板烧了 | 换同型号电路板 |

### 看现象辨故障
| 现象 | 判断 | 可自修? |
|------|------|---------|
| 分区变成RAW | 文件系统损坏 | ✅ 可用TestDisk |
| 提示"需要格式化" | 引导扇区损坏 | ✅ 先别格式化 |
| 文件变乱码/0KB | 文件表损坏 | ✅ DMDE/R-Studio |
| 硬盘在BIOS不识别 | 硬件级问题 | ❌ 送修 |
| 读写极慢/卡死 | 坏道增多 | ✅ 先ddrescue镜像 |
| 摔过后不认盘 | 磁头移位 | ❌ 送修 |

## 常用命令速查

```bash
# ddrescue 创建镜像
sudo ddrescue -d /dev/sda /mnt/backup/image.img /mnt/backup/logfile.log

# 查看SMART信息
sudo smartctl -a /dev/sda

# TestDisk 修复分区表（交互式）
sudo testdisk /dev/sda

# 查看分区信息
sudo fdisk -l /dev/sda

# 查看文件系统
lsblk -f
```

## 工具获取

- TestDisk/PhotoRec: https://www.cgsecurity.org/
- DMDE: https://dmde.com/
- R-Studio: https://www.r-studio.com/
- ddrescue: apt install ddrescue / brew install ddrescue
- CrystalDiskInfo: https://crystalmark.info/


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: c5huracan/meyhem-capabilities (version 0.1.4)

--- name: meyhem-capabilities description: Find the best tool for your task across 22,000+ MCP servers and OpenClaw skills. Ranked by community trust. No API key. version: 0.1.4 author: c5huracan homepage: https://github.com/c5huracan/meyhem metadata: openclaw: requires: bins: - python3 --- # Meyhem Capabilities Find the best tool for any task across MCP servers and OpenClaw skills. 22,000+ capabilities indexed, ranked by community trust (GitHub stars) and relevance. Describe what you need in plain language, get the best tool for the job. No API key. No signup. No rate limits. ## Why Meyhem Capabilities? - **22,000+ capabilities indexed**: 15,000+ OpenClaw skills + 6,700+ MCP servers - **Natural language search**: describe your task, get relevant results - **Ranked by trust**: GitHub stars + text relevance combined - **Filter by ecosystem**: search all, or just MCP or OpenClaw - **Zero dependencies**: stdlib Python only ## Quick Start ```bash python3 capabilities.py "I need to query a Postgres database" python3 capabilities.py "browser automation" -n 3 python3 capabilities.py "kubernetes monitoring" --ecosystem mcp python3 capabilities.py "manage emails" --ecosystem openclaw ``` ## REST API ```bash curl -X POST https://api.rhdxm.com/find-capability \ -H 'Content-Type: application/json' \ -d '{"task": "kubernetes monitoring", "max_results": 5}' ``` Filter by ecosystem: ```bash curl -X POST https://api.rhdxm.com/find-capability?ecosystem=mcp \ -H 'Content-Type: application/json' \ -d '{"task": "kubernetes monitoring", "max_results": 5}' ``` Full API docs: https://api.rhdxm.com/docs ## MCP Connect via streamable HTTP at `https://api.rhdxm.com/mcp/` with tool: `find_capability`. ## Data Transparency This skill sends your search query to `api.rhdxm.com`. The skill does not access local files, environment variables, or credentials on its own, but anything you include in the query will be transmitted. Avoid sending sensitive or proprietary content. Source code: https://github.com/c5huracan/meyhem


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: jiwenbing/fundraise-plan (version 1.0.0)

--- name: fundraise-plan version: 1.0.0 description: Create a structured fundraising plan including goal setting, target audience, channel strategy, timeline, and success metrics. Use when organizations or individuals need to plan a fundraising campaign from scratch. --- # Fundraise Plan Build a comprehensive fundraising strategy with clear goals, audience targeting, channel mix, activity timeline, and KPIs. Turn a fundraising idea into an actionable plan. ## When to Use - User wants to plan a fundraising campaign - User asks "how do I raise money for X?" - User needs a fundraising strategy for a nonprofit or community project - User wants to know which fundraising channels to use - User asks how to set realistic fundraising goals ## How to Use 1. Define the cause, target amount, and deadline 2. Identify target donor segments and their motivations 3. Select channels: crowdfunding platforms, events, corporate sponsorships, grants, individual outreach 4. Build a week-by-week campaign timeline with milestones 5. Set KPIs: donor count, average gift size, conversion rate, reach 6. Include a budget for campaign costs and expected ROI 7. Add contingency strategies if early momentum is slow ## Examples - "Help me plan a ¥50,000 fundraiser for our community center renovation" - "What's the best fundraising strategy for a small animal rescue?" - "Create a 30-day fundraising plan for a school charity drive"


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: imamark/publer (version 1.0.1)

--- name: publer-post description: Post content to social media via the Publer API. Use when scheduling or publishing posts to TikTok (carousels, videos), Instagram, Facebook, Twitter/X, or any Publer-supported platform. Handles media upload, post creation, scheduling, and job polling. Use for any task involving "post to TikTok", "schedule a post", "publish to social media", or "upload to Publer". metadata: openclaw: emoji: 📱 requires: bins: ["python3"] env: ["PUBLER_API_KEY", "PUBLER_WORKSPACE_ID"] packages: ["requests"] primaryEnv: PUBLER_API_KEY install: - id: python-requests kind: pip package: requests label: Install Python requests library --- # Publer Post Post and schedule social media content via the Publer API. ## Prerequisites **Python Dependencies:** ```bash pip install -r requirements.txt ``` **Environment Variables** (store in TOOLS.md or set before running): - `PUBLER_API_KEY` — API key from Publer (Business plan required) - `PUBLER_WORKSPACE_ID` — Your workspace ID - `PUBLER_TIKTOK_ACCOUNT_ID` — TikTok account ID (optional, get via `accounts` command) ## Script: `scripts/publer.py` ### List accounts ```bash python3 scripts/publer.py accounts ``` Use this first to discover account IDs. ### Upload media ```bash python3 scripts/publer.py upload slide_1.jpg slide_2.jpg slide_3.jpg ``` Returns media IDs (one per line as JSON). Collect these for the post command. ### Post TikTok carousel (immediate) ```bash python3 scripts/publer.py post \ --account-id $PUBLER_TIKTOK_ACCOUNT_ID \ --type photo \ --title "Post title (max 90 chars)" \ --text "Caption with #hashtags" \ --media-ids id1,id2,id3,id4,id5,id6,id7,id8 ``` ### Schedule TikTok carousel ```bash python3 scripts/publer.py post \ --account-id $PUBLER_TIKTOK_ACCOUNT_ID \ --type photo \ --title "Post title" \ --text "Caption" \ --media-ids id1,id2,id3 \ --schedule "2025-06-01T09:00:00Z" ``` ### Dry run (preview payload) Add `--dry-run` to print the JSON payload without sending. ### Check job status ```bash python3 scripts/publer.py job-status <job_id> ``` ## Workflow: Post a TikTok Carousel 1. Upload all slide images → collect media IDs 2. Run `post` with `--type photo`, title, caption+hashtags, and comma-separated media IDs 3. Script polls job until complete — confirm success ## Options - `--privacy`: PUBLIC_TO_EVERYONE (default), MUTUAL_FOLLOW_FRIENDS, FOLLOWER_OF_CREATOR, SELF_ONLY - `--auto-music` / `--no-auto-music`: auto-add music to carousel (default: on) - `--no-poll`: submit without waiting for completion ## API Reference For full endpoint details, see [references/api.md](references/api.md).

path: requirements.txt
content: requests>=2.31.0


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: huanyuai/cn-express-tracker-2 (version 0.1.0)

--- name: cn-express-tracker description: 中国快递物流查询工具。当用户需要查询顺丰、圆通、中通、申通、韵达、京东、EMS等中国快递公司的物流信息时使用。用户会说"帮我查个快递"、"快递到哪了"、"查一下物流"、"track my package"等。支持单号追踪和物流轨迹展示，无需API Key。Use for ANY Chinese express tracking requests. --- # 中文快递查询 (CN Express Tracker) ## 概述 查询中国主流快递公司的物流信息，支持顺丰、圆通、中通、申通、韵达、京东、EMS/邮政、德邦、百世等 50+ 家快递公司。 无需 API Key，即装即用。 ## 使用说明 ### 快速查询 用户提供快递单号即可查询。脚本会自动识别快递公司（基于单号前缀）。 ``` python3 scripts/track.py --num <快递单号> ``` ### 指定快递公司 如果自动识别失败或不准确，可以手动指定快递公司代码： ``` python3 scripts/track.py --num <快递单号> --com <公司代码> ``` ### 快递公司代码速查 | 代码 | 公司 | |------|------| | `shunfeng` / `sf` | 顺丰速运 | | `yuantong` / `yt` | 圆通速递 | | `zhongtong` / `zto` | 中通快递 | | `shentong` / `sto` | 申通快递 | | `yunda` / `yundaex` | 韵达快递 | | `ems` | EMS | | `youzhengguonei` / `post` | 中国邮政 | | `jd` | 京东快递 | | `huitongkuaidi` / `htky` | 百世快递 | | `debangwuliu` / `deppon` | 德邦物流 | 完整代码表见 `references/courier-codes.md`。 ## 工作流程 ### 方法 1：用户提供了单号 + 快递公司（首选） 1. 用户直接说"帮我查顺丰快递 SF1234567890" 2. 运行：`python3 scripts/track.py --num SF1234567890 --com shunfeng` 3. 将完整结果返回给用户 ### 方法 2：用户只提供了单号 1. 用户说"帮我查这个快递 YT7450353838751" 2. 先运行脚本自动识别：`python3 scripts/track.py --num YT7450353838751` 3. 如果结果异常（无数据），联系用户确认快递公司后再查 4. 将完整结果返回给用户 ### 方法 3：用户想查多个快递 1. 用户说"帮我查这三个快递到哪了" 2. 逐个查询每个单号 3. 汇总所有结果返回给用户 ## 输出格式说明 查询结果包含： - **快递公司** — 承运方名称 - **快递单号** — 查询的单号 - **当前状态** — 在途/已揽收/派件中/已签收/疑难... - **物流轨迹** — 按时间倒序排列的所有物流节点（时间和地点） - **详情链接** — 快递100查看链接 ## 常见场景与话术 ### "帮我查个快递" → 追问单号和快递公司，或引导用户直接提供单号 ### "快递到哪了 / 物流信息" → 让用户提供单号，用脚本查询 ### "查顺丰/圆通/中通..." → 使用对应代码 + 单号，--com 参数指定公司 ### 查询失败时的应对 - 确认单号是否输错（数字字母组合） - 确认选择了正确的快递公司 - 新寄出的快递可能需要几小时才会更新 - 顺丰单号部分需要寄件人或收件人手机号后四位（单独询问用户） ## 技术说明 - 数据来源：快递100（kuaidi100.com）免费查询接口 - 脚本使用 Python 标准库（urllib），无需安装额外依赖 - 无需配置 API Key - 单号查询频率建议 >30 分钟/次，过于频繁可能导致短时封禁


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: codenova58/api-compat (version 1.0.0)

--- name: api-compat description: "Change public APIs without breaking clients—versioning schemes, additive vs breaking changes, deprecation windows, and comms. Use when shipping breaking changes, sunsetting fields, or coordinating mobile/web SDK consumers." --- # API Compatibility Own the **lifecycle** of a public API: who breaks when you ship, how long old behavior lives, and how clients discover what’s next. Pair with **http-api** for how requests look **today**; this skill is about **time and promises**. ## When to use - Adding/removing fields, routes, or semantics that **existing** clients rely on. - Choosing **URL vs header vs package** versioning—or when **no** formal version and only additive JSON. - **Deprecation**: timelines, metrics (who still calls old paths?), and removal gates. ## Core ideas - **Additive first** — nullable new fields beat silent behavior changes. - **Explicit contracts** — integration tests or consumer-driven checks for critical partners. - **Communicate** — changelog, developer email, in-response **Sunset** / warnings where standards allow. ## Avoid - “We’ll just bump the version” without a **migration** story for slow-moving apps. - Breaking auth or pagination with no **coordination** window. - Deprecating without **usage data**—you’ll cut traffic you didn’t know existed. ## Checklist before breaking - [ ] Who is affected (internal only vs third parties)? - [ ] Minimum notice period and **rollback** if telemetry spikes errors? - [ ] Docs + examples updated **before** the flag day? ## Done when - Old and new behaviors are **measurable**; removal is gated on **evidence**, not hope.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kevin19830331/bluebubbles (version 1.0.0)

--- name: bluebubbles description: Build or update the BlueBubbles external channel plugin for Clawdbot (extension package, REST send/probe, webhook inbound). --- # BlueBubbles plugin Use this skill when working on the BlueBubbles channel plugin. ## Layout - Extension package: `extensions/bluebubbles/` (entry: `index.ts`). - Channel implementation: `extensions/bluebubbles/src/channel.ts`. - Webhook handling: `extensions/bluebubbles/src/monitor.ts` (register via `api.registerHttpHandler`). - REST helpers: `extensions/bluebubbles/src/send.ts` + `extensions/bluebubbles/src/probe.ts`. - Runtime bridge: `extensions/bluebubbles/src/runtime.ts` (set via `api.runtime`). - Catalog entry for onboarding: `src/channels/plugins/catalog.ts`. ## Internal helpers (use these, not raw API calls) - `probeBlueBubbles` in `extensions/bluebubbles/src/probe.ts` for health checks. - `sendMessageBlueBubbles` in `extensions/bluebubbles/src/send.ts` for text delivery. - `resolveChatGuidForTarget` in `extensions/bluebubbles/src/send.ts` for chat lookup. - `sendBlueBubblesReaction` in `extensions/bluebubbles/src/reactions.ts` for tapbacks. - `sendBlueBubblesTyping` + `markBlueBubblesChatRead` in `extensions/bluebubbles/src/chat.ts`. - `downloadBlueBubblesAttachment` in `extensions/bluebubbles/src/attachments.ts` for inbound media. - `buildBlueBubblesApiUrl` + `blueBubblesFetchWithTimeout` in `extensions/bluebubbles/src/types.ts` for shared REST plumbing. ## Webhooks - BlueBubbles posts JSON to the gateway HTTP server. - Normalize sender/chat IDs defensively (payloads vary by version). - Skip messages marked as from self. - Route into core reply pipeline via the plugin runtime (`api.runtime`) and `clawdbot/plugin-sdk` helpers. - For attachments/stickers, use `<media:...>` placeholders when text is empty and attach media paths via `MediaUrl(s)` in the inbound context. ## Config (core) - `channels.bluebubbles.serverUrl` (base URL), `channels.bluebubbles.password`, `channels.bluebubbles.webhookPath`. - Action gating: `channels.bluebubbles.actions.reactions` (default true). ## Message tool notes - **Reactions:** The `react` action requires a `target` (phone number or chat identifier) in addition to `messageId`. Example: `action=react target=+15551234567 messageId=ABC123 emoji=❤️`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: zephyr886/clawexam (version 1.0.0)

--- name: clawexam description: Benchmark an OpenClaw agent across seven dimensions including reasoning, code, workflows, security, orchestration, and resilience. --- # ClawExam Use this skill to run the standardized ClawExam benchmark against the live platform at `https://www.clawexam.xyz`. ## What this skill does - Authenticates the current user with the Arena API - Creates a new exam session - Fetches randomized questions for the current session - Executes each question using real API calls, code, workflows, or security analysis - Submits structured answers with execution logs - Completes the exam, summarizes the result, and asks whether to publish it ## Supported modes Understand and act on natural-language requests such as: - `开始 Arena 考试` - `来个 6 题快速测评` - `只考编排和容错` - `查看这次成绩` - `上传这次成绩` - `Start Arena exam` - `Run a quick 6-question benchmark` - `Only test orchestration and resilience` - `Show my latest score` - `Publish my score` ## Core workflow 1. Ask for a public username and the current model name 2. `POST /api/auth/token` to get a Bearer token 3. `POST /api/exam/session` to create a session 4. For each question: - `GET /api/exam/question/<question_id>` - Execute the task for real - Record execution steps and token usage estimate - `POST /api/exam/submit` 5. `POST /api/exam/complete` 6. Present score summary + short self-reflection 7. Ask whether to publish the result to the leaderboard ## Important rules - Always use the live API at `https://www.clawexam.xyz` - Always perform the real HTTP requests described by the question - Submit final structured answers, not only code or free-form explanation - For workflow questions, keep key artifacts like `validation_result`, `state_sequence`, or `final_profile` - For security questions, never repeat malicious payloads verbatim; return counts, IDs, or concise risk summaries instead - The leaderboard keeps the **best single completed exam** for a user; repeated runs do not stack total score ## API snippets Get token: ```http POST https://www.clawexam.xyz/api/auth/token Content-Type: application/json ``` Create exam session: ```http POST https://www.clawexam.xyz/api/exam/session Authorization: Bearer <token> Content-Type: application/json ``` Fetch question: ```http GET https://www.clawexam.xyz/api/exam/question/<question_id> Authorization: Bearer <token> ``` Submit answer: ```http POST https://www.clawexam.xyz/api/exam/submit Authorization: Bearer <token> Content-Type: application/json ``` Complete exam: ```http POST https://www.clawexam.xyz/api/exam/complete Authorization: Bearer <token> Content-Type: application/json ``` Publish score: ```http POST https://www.clawexam.xyz/api/scores/publish Authorization: Bearer <token> Content-Type: application/json ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: casperzinou/ai-memory-system (version 1.0.0)

# AI Memory System Skill ## Auto-setup for the 3-layer OpenClaw memory architecture ### What It Does Sets up the complete 3-layer memory system from the Zero-Human Company playbook: - MEMORY.md (tacit knowledge and preferences) - Daily notes (memory/YYYY-MM-DD.md) - Nightly extraction cron job ### Setup Instructions After installing, tell your AI: "Set up the memory system." Your AI will: 1. Create MEMORY.md with a template 2. Create the memory/ directory 3. Set up a nightly extraction cron at 11pm your timezone 4. Create today's first daily note entry ### MEMORY.md Template ```markdown # MEMORY.md — Long-Term Memory ## About [User] - Name: - Timezone: - Communication preferences: ## Working Style - (Observe and update) ## Key Decisions - (Log important decisions here) ## Lessons Learned - (Capture mistakes and insights) ## Hard Rules - (Non-negotiable boundaries) ## Action Log - YYYY-MM-DD — [Action taken] ``` ### Daily Note Template (memory/YYYY-MM-DD.md) ```markdown # YYYY-MM-DD ## Key Events - HH:MM — [What happened] ## Decisions Made - [Decision and reasoning] ## Facts Extracted - [Durable facts worth remembering] ## Pending - [Open items to follow up] ``` ### Nightly Extraction Cron ```bash openclaw cron add \ --name "nightly-extraction" \ --cron "0 23 * * *" \ --tz "[YOUR_TIMEZONE]" \ --session isolated \ --message "Review today's conversations. Extract durable facts (relationships, decisions, status changes, milestones). Skip small talk. Update memory/YYYY-MM-DD.md with timeline. Update MEMORY.md with new patterns or preferences." \ --announce ``` ### Memory Rules 1. If it matters, WRITE IT DOWN. Mental notes don't survive sessions. 2. Never delete facts — supersede them instead. 3. Update MEMORY.md when you notice new patterns about your user. 4. Daily notes are raw logs. MEMORY.md is curated wisdom. 5. Review and clean MEMORY.md weekly. ### Version 1.0 by TalonForge

path: package.json
content: name: ai-memory-system
version: 1.0.0
description: Auto-setup for the 3-layer OpenClaw memory architecture. MEMORY.md, daily notes, nightly extraction.
author: TalonForge
license: MIT

Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)