OpenClaw/clawhub-security-signals huggingface dataset:
Skill: gitjhb/erotic-writer (version 1.0.0)

--- name: erotic-writer description: Craft tasteful adult fiction and intimate scenes. Triggers on requests for erotic stories, romance with mature themes, NSFW creative writing, or 小黄文/情色故事. Supports multiple styles and settings. --- # Erotic Fiction Writing Guide ## Core Principles 1. **Literary Quality First** — This is creative writing, not crude content. Prioritize prose, atmosphere, and emotional depth. 2. **Build Tension Gradually** — Stories need arc and pacing. Anticipation is often more powerful than the act itself. 3. **Engage All Senses** — Sight, sound, touch, smell, taste. Immerse the reader fully. 4. **Master the Art of Suggestion** — What's left unsaid can be more evocative than explicit detail. ## Writing Elements ### Atmosphere Building - **Environment**: Lighting, temperature, scents, ambient sounds - **Psychology**: Nervousness, anticipation, hesitation, desire - **Pacing**: Slow burn → Rising tension → Climax → Afterglow ### Character Development - Characters need personality, not just bodies - Dialogue should feel natural and true to their voice - Emotions must feel authentic — show the chemistry ### Scene Types (Reference) - 🌙 **Romantic**: First time, reunion after separation, candlelit evening - 🔥 **Passionate**: Office tension, elevator encounter, stormy night - 💕 **Tender**: Lazy morning, shower together, afternoon intimacy - ⛓️ **Forbidden**: Secret affair, power dynamics, taboo attraction ## Style Options Ask the user's preference: - **Subtle/Poetic** — Suggestive, leaves much to imagination - **Sensual/Realistic** — Rich detail, immersive experience - **Literary/Artistic** — Elaborate prose, metaphor-heavy, romantic ## Workflow 1. **Confirm settings**: Characters, relationship, scenario, style preference, language (EN/中文) 2. **Write with proper pacing**: Build up → Development → Peak → Resolution 3. **Suggested length**: 1,000-3,000 words for short pieces ## Output After completing a piece, automatically save to: ``` ~/clawd/writing/erotic/{date}-{title-slug}.md ``` Create the directory if it doesn't exist. Format: ```markdown # {Title} **Date**: {YYYY-MM-DD} **Characters**: {names} **Setting**: {brief description} **Style**: {subtle/sensual/literary} --- {story content} ``` ## Guidelines - All characters must be consenting adults - Relationships must be consensual - No illegal, harmful, or non-consensual content - Respect user's boundaries and preferences


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: juryory/ausub (version 1.0.3)

--- slug: ausub display_name: AUSUB --- # OpenClaw `openclaw` 是一个本地 skill，用来基于 Tushare 跟踪黄金行情，并输出动态定投建议。 ## 适用场景 当用户希望做这些事情时，使用这个 skill： - 基于 Tushare 获取黄金 ETF 的日度行情快照 - 用纪律化规则生成黄金动态定投建议 - 按固定节奏持续监测，而不是凭感觉择时 - 根据收入、支出、存款和投资偏好，生成一个初始黄金定投方案 ## 输入 这个 skill 最好具备以下输入： - 环境变量中的 `TUSHARE_TOKEN` - 要跟踪的标的定义 - 用户的基础定投金额，或者由模型协助生成的方案 - 可选的风控上下限 ## 安装前说明 - `TUSHARE_TOKEN` 是必需项；如果当前运行环境没有正确设置这个变量，skill 将无法获取 Tushare 数据。 - 安装其他 Tushare 相关 skill，并不等于当前 skill 会自动获得可用的 `TUSHARE_TOKEN`。 - `OPENCLAW_CONFIG`、`OPENCLAW_USER_ID`、`OPENCLAW_HISTORY_PATH`、`OPENCLAW_SYMBOL` 都是可选项，但如果设置了这些变量，skill 会读取对应的本地文件或路径。 - `OPENCLAW_USER_ID` 会映射到 `memory/users/<id>.json`。 - `fetch_history.py` 会在 `references/history/` 下写入本地 CSV 文件。 - 远程网络请求仅通过 `tushare` 库访问 Tushare，不包含额外隐藏网络端点。 建议配置如下： - `OPENCLAW_SYMBOL`：跟踪的黄金 ETF，默认 `518880.SH` - `OPENCLAW_BASE_AMOUNT`：每期基础定投金额，默认推荐值可由用户覆盖 - `OPENCLAW_MAX_MULTIPLIER`：最大加码倍率，默认 `1.8` - `OPENCLAW_MIN_MULTIPLIER`：最小投入倍率，默认 `0.6` ## 工作流 1. 读取 Tushare 中配置标的的最新日线数据。 默认执行标的是 `518880.SH`。 ETF 主行情使用 Tushare `fund_daily`。 2. 计算价格行为相关指标。 3. 用核心指标把市场分成 4 个状态： - `oversold` - `weak` - `neutral` - `hot` 4. 用布林线位置做倍率修正。 5. 只在极端状态下使用 MACD 做确认修正。 6. 如需展示黄金现货参考行情，读取上海黄金交易所 `Au99.99`。 `Au99.99` 参考行情使用 Tushare `sge_daily`。 7. 输出带理由和风险提示的定投建议。 ## 用户方案原则 - `weekly_thursday_if_trading` 和 `1000` 元应被视为默认推荐方案，而不是唯一固定方案。 - 用户可以自行定义定投节奏、基础金额和执行偏好。 - 如果用户尚未确定方案，可以选择性描述预算范围、投资目标和风险偏好，由 openclaw 的模型给出一个建议方案。 - 不应要求用户在配置文件中持久化保存收入、支出、存款等敏感财务信息；这类信息仅适合在临时对话中用于生成建议。 - 涉及个人财务规划的方案建议，应在用户确认后再写入配置文件。 ## 约束 - 不要把结果表述成保证收益的投资建议。 - 不要建议使用杠杆。 - 所有建议都要限制在设定的最小和最大倍率之间。 - 如果数据缺失、过旧或接口失败，要明确说明，不要强行给建议。 ## 输出格式 输出应包含： - 市场摘要 - 指标摘要 - 建议倍率 - 建议投入金额 - 触发细节 - 自然语言解释 - 风险提示 ## 规则说明 - 使用硬阈值，避免边界条件重叠。 - 60 日回撤固定定义为：`(rolling_60d_high - close) / rolling_60d_high` - 布林线修正使用位置值 `pos = (close - lower_band) / (upper_band - lower_band)`： - `pos <= 0`：`+0.2` - `0 < pos <= 0.25`：`+0.1` - `0.25 < pos < 0.75`：`0` - `0.75 <= pos < 1`：`-0.1` - `pos >= 1`：`-0.2` - MACD 只用于 `oversold` 和 `hot` 两种极端状态，并要求柱体动能连续两期收敛后才触发修正。 ## 示例 如果基础金额是 `1000`，最终倍率是 `1.5`，则建议本期投入 `1500`，并附带简要说明，例如市场偏弱、价格接近布林下轨、下跌动能减弱等。 ## 实现说明 - 优先使用小型 Python 脚本负责 Tushare 取数和指标计算。 - 所有阈值都应易于调参。 - 数据获取和建议逻辑要分离，便于后续替换数据源或升级规则。 - 以 ETF 日线为主要决策依据。 - `518880.SH` 主行情默认通过 Tushare `fund_daily` 获取。 - 上海黄金交易所 `Au99.99` 可作为辅助参考锚，默认通过 Tushare `sge_daily` 获取，但不替代执行标的。 - 不要把“当前脚本未取到 Au99.99 数据”表述成“Tushare 不支持 SGE 数据”；正确表述应是“当前参考数据暂不可用或当前流程未启用该接口”。

path: requirements.txt
content: tushare


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

--- name: diff4 description: Preview git diffs and files using the diff4 CLI. Use when the user wants to see code changes, review files content securely via diff4 metadata: author: diff4 version: "0.1.0" --- # diff4 - Encrypted Diff & File Sharing diff4 encrypts diffs and files client-side (AES-256-GCM) before uploading. The server never sees plaintext. Recipients need the passphrase to decrypt. ## Prerequisites - `diff4` must be installed and available on PATH. Use `npm i -g @diff4/cli` to install. - A passphrase must be configured (see setup below) ## Commands ### Share the latest commit diff ``` diff4 git-latest ``` Runs `git diff HEAD~1`, encrypts the result, and uploads. Use when the user says "preview my last commit" or "send the latest diff." ### Share staged changes ``` diff4 git-staged ``` Runs `git diff --staged`, encrypts, and uploads. Use when the user says "preview my staged changes" or "send what's about to be committed." ### Share arbitrary files ``` diff4 files path/to/file1.ts path/to/file2.ts ``` Reads each file (UTF-8 text only), bundles them as JSON, encrypts, and uploads. Supports any number of paths (relative or absolute). ### Key management - `diff4 key-gen [key]` - Generate or set the encryption passphrase - `diff4 key-get` - Print the current passphrase ## Options All upload commands (`git-latest`, `git-staged`, `files`) accept: | Flag | Description | |------|-------------| | `-s, --server <url>` | Override the diff4 server URL. Default: `https://diff4.com` (or `DIFF4_SERVER` env var) | | `-p, --passphrase <key>` | Override the passphrase for this command only. Default: `DIFF4_PASSPHRASE` env var | ## Gotchas - **Empty diffs fail gracefully.** `git-latest` and `git-staged` will error if there is nothing to share. - **Binary files are not supported.** `diff4 files` reads files as UTF-8 text. - **Server is configurable.** Self-hosted instances can be set via `DIFF4_SERVER` env var or `-s` flag. - **The passphrase must be shared out-of-band.** diff4 only encrypts — recipients need the same passphrase to decrypt. - **key-gen updates existing keys.** If `DIFF4_PASSPHRASE` already exists in the shell config, key-gen replaces it in-place. ## Typical workflow 1. User asks to see a diff or files 2. Verify setup: run `diff4 key-get` (if it fails, run `diff4 key-gen` and tell user to source their rc file) 3. Run the appropriate command (`git-latest`, `git-staged`, or `files <paths>`) 4. Return the URL from the response to the user 5. Remind the user that recipients need the passphrase to decrypt


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: bytesagain3/poem-generator (version 2.0.0)

--- version: "2.0.0" name: poem-generator description: "诗歌生成助手。现代诗、俳句、对联、藏头诗、古诗翻译。Poem generator with free verse, haiku, couplets, acrostic poems." author: BytesAgain homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills --- # poem-generator 诗歌生成助手。现代诗、俳句、对联、藏头诗、古诗翻译。Poem generator with free verse, haiku, couplets, acrostic poems, classical poetry translation. ## 速查表 See commands above. ## 可用命令 - **write** — write - **haiku** — haiku - **couplet** — couplet - **modern** — modern - **acrostic** — acrostic - **translate** — translate > 💡 小技巧：先用 `help` 查看所有命令，再选择最适合的 ## 专业建议 - 三行: 5-7-5 音节（中文: 5-7-5字） - 包含季语（季节元素） - 瞬间感悟，意在言外 - 字数相等 - 词性相对（名对名、动对动） --- *poem-generator by BytesAgain* --- 💬 Feedback & Feature Requests: https://bytesagain.com/feedback Powered by BytesAgain | bytesagain.com ## Examples ```bash # Show help poem-generator help # Run poem-generator run ``` - Run `poem-generator help` for all commands ## Commands Run `poem-generator help` to see all available commands.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: speraxos/pump-mcp-server (version 0.1.0)

--- name: Pump MCP Server description: > Model Context Protocol server exposing 7 tools, 3 resource types, and 3 prompts for AI agent consumption — Solana wallet operations, vanity address generation, message signing, and address validation over stdio transport. metadata: openclaw: homepage: https://github.com/nirholas/pump-fun-sdk --- # MCP Server — Model Context Protocol for Solana Wallet Operations Model Context Protocol server exposing tools, resources, and prompts for AI agent consumption over stdio transport with session keypair management. ## Architecture ``` AI Agent (Claude, etc.) │ stdio transport │ SolanaWalletMCPServer │ ┌────┼────────┬──────────┐ │ │ │ │ Tools Resources Prompts Session │ │ │ State 7 3 3 │ tools types prompts Keypair ``` ## Tools (7) | Tool | Description | |------|-------------| | `generate_keypair` | Generate a new random Solana keypair | | `generate_vanity` | Generate vanity address with prefix/suffix | | `estimate_vanity_time` | Estimate time for vanity pattern | | `validate_address` | Validate a Solana Base58 address | | `sign_message` | Sign a message with session keypair | | `verify_signature` | Verify a signed message | | `restore_keypair` | Restore keypair from secret key bytes | ## Resources (3) | URI Pattern | Description | |-------------|-------------| | `solana://keypair/current` | Current session keypair info | | `solana://keypair/{id}` | Specific keypair by ID | | `solana://address/{address}` | Address validation details | ## Prompts (3) | Prompt | Description | |--------|-------------| | `generate-wallet` | Guide user through wallet generation | | `vanity-address` | Guide vanity address generation with difficulty estimate | | `security-review` | Review security of wallet operations | ## Session State Management ```typescript class SolanaWalletMCPServer { private sessionKeypair: Keypair | null = null; generateKeypair(): KeypairInfo { if (this.sessionKeypair) { this.sessionKeypair.secretKey.fill(0); // zeroize old } this.sessionKeypair = Keypair.generate(); return this.getKeypairInfo(); } } ``` ## Security Model - Session keypair is zeroized when replaced or server shuts down - No network calls for key generation - All crypto uses `@solana/web3.js` only - Zod schemas validate all tool inputs - Secret key bytes are never logged or exposed in resources ## Patterns to Follow - Validate all inputs with Zod schemas before processing - Zeroize secret keys when replaced or on shutdown - Return structured JSON for all tool responses - Use descriptive error messages for validation failures - Keep session state minimal — one active keypair at a time ## Common Pitfalls - Session keypair is ephemeral — lost when server restarts - `generate_vanity` is single-threaded — long prefixes will be slow - `sign_message` requires an active session keypair — `generate_keypair` first - Resource URIs are case-sensitive


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: ddrayne/bbc-news (version 1.0.0)

--- name: bbc-news description: Fetch and display BBC News stories from various sections and regions via RSS feeds. Use when the user asks for BBC news, UK news headlines, world news from BBC, or news from specific BBC sections (technology, business, politics, science, health, entertainment, regional UK news, or world regions). --- # BBC News Fetch top stories from BBC News across different sections and regions. ## Quick Start Fetch top stories: ```bash python3 scripts/bbc_news.py ``` Fetch from specific section: ```bash python3 scripts/bbc_news.py uk python3 scripts/bbc_news.py world python3 scripts/bbc_news.py technology ``` List all available sections: ```bash python3 scripts/bbc_news.py --list ``` ## Available Sections ### Main Sections - `top` - Top stories (default) - `uk` - UK news - `world` - World news - `business` - Business news - `politics` - Politics - `health` - Health news - `education` - Education - `science` - Science & Environment - `technology` - Technology news - `entertainment` - Entertainment & Arts ### UK Regional - `england` - England news - `scotland` - Scotland news - `wales` - Wales news - `northern-ireland` - Northern Ireland news ### World Regions - `africa` - Africa news - `asia` - Asia news - `australia` - Australia news - `europe` - Europe news - `latin-america` - Latin America news - `middle-east` - Middle East news - `us-canada` - US & Canada news ## Options **Limit number of stories:** ```bash python3 scripts/bbc_news.py world --limit 5 ``` **JSON output:** ```bash python3 scripts/bbc_news.py technology --json ``` ## Examples Get top 5 UK stories: ```bash python3 scripts/bbc_news.py uk --limit 5 ``` Get Scotland news in JSON: ```bash python3 scripts/bbc_news.py scotland --json ``` Get latest technology headlines: ```bash python3 scripts/bbc_news.py technology --limit 3 ``` ## Dependencies Requires `feedparser`: ```bash pip3 install feedparser ``` ## Resources ### scripts/bbc_news.py Python CLI that fetches and displays BBC News stories from RSS feeds. Supports all major BBC sections and regions, with text and JSON output formats. ### references/feeds.md Complete list of BBC News RSS feed URLs organized by section and region.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: operator-auteng-ai/markdown-publish-share (version 1.0.5)

--- name: markdown-publish-share description: Publish markdown and return share links using curl. Support markdown with mermaid diagrams such as component diagrams, flowcharts, and sequence diagrams. Also supports KaTex and code blocks. AutEng will return a shareable link to the published rendered document. Use cases include Software Architecture diagrams and documentation, Maths and Physics derivations and Systems documentation. --- # AutEng Docs Curl Publish Use this endpoint: `https://auteng.ai/api/tools/docs/publish-markdown/` Send JSON with: - `markdown` (required) - `title` (optional) - `expires_hours` (optional) Use this command to publish markdown: ```bash curl -sS -X POST "https://auteng.ai/api/tools/docs/publish-markdown/" \ -H "Content-Type: application/json" \ -d @- <<'JSON' { "markdown": "# API Test\n\nHello from curl.", "title": "API Test", "expires_hours": 24 } JSON ``` Extract only the share URL: ```bash curl -sS -X POST "https://auteng.ai/api/tools/docs/publish-markdown/" \ -H "Content-Type: application/json" \ -d '{"markdown":"# Hello\n\nPublished from curl."}' \ | jq -r '.share_url' ``` Extract a compact success payload: ```bash curl -sS -X POST "https://auteng.ai/api/tools/docs/publish-markdown/" \ -H "Content-Type: application/json" \ -d '{"markdown":"# Hello\n\nPublished from curl."}' \ | jq '{title, share_url, expires_at}' ``` Treat any response without `share_url` as an error and show the full JSON body. For full documentation and supported markdown for mermaid, KaTeX and code syntax along with examples, see https://auteng.ai/llms.txt

path: VERSION.txt
content: 1.0.5

Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: iammeter/iammeter-openclaw (version 0.2.0)

--- name: iammeter description: "Query and export device/site data via the iammeter API (based on https://www.iammeter.com/swaggerui/swagger.json). Triggers: list sites/devices, get real-time or historical energy data, export CSV, run power or offline analysis." metadata: {"openclaw": {"primaryEnv": "IAMMETER_TOKEN", "requires": {"env": ["IAMMETER_TOKEN"]}}} --- # iammeter Skill (Node.js) A Node.js client and CLI for the iammeter API, based on the official swagger spec. Features - Token is loaded automatically: first from the `IAMMETER_TOKEN` environment variable, then from `~/.openclaw/openclaw.json` (`skills.entries.iammeter.apiKey`) - List user sites (sitelist) - Get latest data for all meters (metersdata) - Get latest upload data for a single meter (meterdata / meterdata2) - Query site energy history (energyhistory) and export CSV - Power analysis (poweranalysis), offline analysis (offlineanalysis) Configuration - Option A (OpenClaw / Clawhub): set the token in the Skills UI. It is stored in `~/.openclaw/openclaw.json` under `skills.entries.iammeter.apiKey` and injected as the `IAMMETER_TOKEN` environment variable at runtime. - Option B (local testing): export IAMMETER_TOKEN=<your_token> before running. Files - references/api.md — endpoint reference summarized from swagger - scripts/iammeter_client.js — Node.js client wrapping common endpoints - scripts/cli.js — CLI: sitelist|meters|meter|history|poweranalysis|offlineanalysis - package.json — dependencies (axios, yargs) Usage (local testing) 1) Install dependencies: cd ~/.openclaw/workspace/skills/iammeter npm install 2) Run: node scripts/cli.js sitelist node scripts/cli.js meters node scripts/cli.js meter <device_sn> node scripts/cli.js history <placeId> 2026-02-01 2026-02-25 --out out.csv Notes - Some endpoints have strict rate limits (see references/api.md for details). - Do not commit real tokens to public repositories. # Credits - API endpoints and fields from https://www.iammeter.com/swaggerui/swagger.json # About IAMMETER IAMMETER is an energy monitoring solution provider offering Wi-Fi-based single-phase and three-phase smart meters with multiple open interfaces, including Modbus/TCP, MQTT, HTTP/HTTPS API, TCP, and Local Push protocols. These open communication options make IAMMETER devices easy to integrate with OpenHAB and other open-source platforms. Learn more about supported protocols and APIs: Device communication protocols: https://www.iammeter.com/newsshow/blog-fw-features IAMMETER Cloud API: https://www.iammeter.com/docs/system-api ![advanced-user-ecosystem](https://iammeterglobal.oss-accelerate.aliyuncs.com/img/advanced-user-ecosystem.png)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: markma84/wiki-manager (version 1.0.0)

# wiki-manager / Wiki 索引管理 > 版本：v1.0 > 创建：2026-04-08 > 更新：2026-04-08（空空建议，改为单 JSON 索引方案） > 依据：空空方案 + 小蜂自想（两者高度一致） > 铁三角：彧哥 + 空空 + 小蜂 --- ## 核心理念 **用工具化索引文件代替散 .md**： - 1 个 wiki.json = 所有关键词索引 - 500 条封顶 - 三池循环（core / buffer / new） - 不存大段正文，内容交给向量库/memory --- ## 文件结构 ``` wiki/ ├── wiki.json ← 索引文件（三池合一，全部词条在这里） ├── wiki.json.bak ← 上一次备份（每次写入前自动更新） └── SKILL.md ← 本文件，管理脚本 ``` --- ## wiki.json 结构 ```json { "version": "1.0", "name": "小蜂Wiki索引", "pools": { "core": { "name": "核心热词池", "limit": 200 }, "buffer": { "name": "次热缓冲池", "limit": 200 }, "new": { "name": "新晋新词池", "limit": 100 } }, "entries": [ { "id": "001", "keyword": "四部曲", "pool": "core", "definition": "想→说→做→看，沟通决策流程", "source": "skills/4steps-to-wisdom/SKILL.md", "score": 5, "lastUsed": "2026-04-08", "created": "2026-04-08", "sourceType": "skill" } ] } ``` **字段说明**： | 字段 | 必填 | 说明 | |------|------|------| | id | ✅ | 唯一ID，格式"001"～"500" | | keyword | ✅ | 关键词（去重校验） | | pool | ✅ | 所在池：core / buffer / new | | definition | ✅ | 一句话定义 | | source | ✅ | 引用路径（memory/xxx 或 skills/xxx） | | score | ✅ | 使用频率评分（1-5） | | lastUsed | ✅ | 最后使用日期 YYYY-MM-DD | | created | ✅ | 创建日期 YYYY-MM-DD | | sourceType | ❌ | 来源类型：skill / memory / discuss | --- ## 三池容量 | 池 | 上限 | 说明 | |---|------|------| | core | 200 | 最高频，核心专属 | | buffer | 200 | 次高频，缓冲梯队 | | new | 100 | 新增词，观察期 | | **合计** | **500** | **永不膨胀** | --- ## 循环规则 ``` new 高频用 → 升 buffer buffer 高频用 → 升 core core 长期不用 → 降 buffer buffer 长期不用 → 降 new → 淘汰 ``` **降级/淘汰触发**：最后使用距今 > 30 天 --- ## 管理脚本（无工具版，用 exec） ### 查词（按池） ```bash # 查 core 池 cat wiki/wiki.json | jq '.entries | map(select(.pool == "core"))' # 模糊搜索 cat wiki/wiki.json | jq '.entries | map(select(.keyword | contains("四部")))' ``` ### 查所有（高效加载） ```bash cat wiki/wiki.json # 一次读完所有词条，毫秒级 ``` ### 新增词条 ```bash # 编辑 wiki/wiki.json，手动追加 entries[] # 注意：先检查是否已存在（keyword 去重） ``` ### 升降级 ```bash # 将某词从 new 升到 buffer（score >= 3 时触发） # 修改 wiki.json 中对应 entry 的 pool 字段 ``` ### 淘汰检查（每次心跳或定期） ```bash # 检查 buffer/new 池中最后使用 > 30 天的词 cat wiki/wiki.json | jq '.entries | map(select(.lastUsed < "2026-03-09" and .pool != "core"))' ``` ### 备份（写入前自动） ```bash cp wiki/wiki.json wiki/wiki.json.bak ``` --- ## compact 恢复流程 compact 后认知丢失 → 执行以下步骤恢复： ``` 1. cat wiki/wiki.json # 加载所有词条（毫秒级） 2. 读取 definition 字段 # 恢复一句话认知 3. 如需详细内容 → 从 source 字段路径读取 memory/ 向量库 ``` --- ## 维护节奏 | 动作 | 频率 | |------|------| | 新词入 new 池 | 按需，随时 | | 升降级检查 | 每天开机 | | 淘汰检查 | 每周 | | 备份 | 每次 wiki.json 写入前 | --- ## 注意事项 - 每次写入前先 `cp wiki/wiki.json wiki/wiki.json.bak` - wiki.json 损坏时用 `cp wiki/wiki.json.bak wiki/wiki.json` 恢复 - compact 后 reload 一次 wiki.json 即可恢复全部词条认知 - 不要存大段正文，只存引用路径，详细内容在 memory 向量库 --- *Wiki 索引管理 v1.0 - 轻量高效，铁三角共识*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector:  ()
Skill: jikeapi-cn/jike-surname-query (version 1.0.0)

--- name: jike-surname-query description: 百家姓查询。输入姓氏，查询姓氏起源、名人、迁徙分布等信息。 适用场景：用户询问相关传统文化、生活常识或配对资料时使用。数据由即刻数据（jikeapi.cn）开放接口提供。 homepage: https://www.jikeapi.cn/ metadata: {"openclaw":{"emoji":"📜","requires":{"bins":["python3"],"env":["JIKE_SURNAME_QUERY_KEY"]},"primaryEnv":"JIKE_SURNAME_QUERY_KEY"}} --- # 百家姓查询 - 即刻数据 > 数据由 **[即刻数据](https://www.jikeapi.cn/)** 提供，帮助 AI 客户端快速接入可靠数据服务。 ## 前置配置 ```bash export JIKE_SURNAME_QUERY_KEY=你的AppKey # 或使用通用 Key export JIKE_APPKEY=你的AppKey ``` ## 使用方法 ```bash python3 scripts/surname_query.py --name 赵 python3 scripts/surname_query.py --name 欧阳 --json ``` 直接调用 API： ```text GET https://api.jikeapi.cn/v1/surname/query?name=赵&appkey=YOUR_APPKEY ``` ## AI 使用步骤 1. 从用户消息中提取查询参数。 2. 执行 `python3 scripts/surname_query.py` 并传入对应参数。 3. 默认返回中文文本；需要结构化处理时追加 `--json`。 4. 如果用户没有提供可选参数，可不传该参数，由接口按默认逻辑处理。 ## 脚本位置 `scripts/surname_query.py`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: xnlc-qft/get-ali-searches (version 1.0.0)

# 获取相关搜索 用途：获取阿里云相关搜索 ## 调用 使用mcp调用此工具，需要提供以下参数： | 参数 | 默认 | 说明 | |--------|----|----------------| | robotId| 必填 | 使用ALIYUN_RPA_RobotId| ## 输出结构 - 返回列表结构 ```list [ "阿里云官网登录入口", "阿里云游戏服务器", "阿里云控制台", "阿里云轻量云服务器", "阿里云域名注册", "阿里云免费服务器", "阿里云域名购买", "云服务", "阿里云和腾讯云哪个好", "中国十大云计算公司排名", ]


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