OpenClaw/clawhub-security-signals huggingface dataset:
Skill: biogod2020/ultimate-freedom-protocol (version 9.0.0)

--- name: ultimate-freedom-protocol description: "Ultimate Web Freedom Protocol (v9.0.0). Leverages 'Protocol Phantom' (curl_cffi kernel-level TLS impersonation) to bypass DataDome, Cloudflare, and Bilibili. Ideal for undetectable server-side data extraction." metadata: openclaw: emoji: 🎭 disable-model-invocation: true requires: python: ["curl_cffi", "lxml", "DrissionPage"] bins: ["google-chrome-stable", "xvfb-run"] --- # Ultimate Freedom Protocol (SOTA v9.0.0) This protocol replaces traditional headless browsing with **"Protocol Phantom"** technology, focusing on kernel-level network fingerprint alignment. ## 🚀 Core Pillar: Protocol Phantom (CFFI Mode) Traditional scrapers are identified by their TLS handshake. This toolkit uses `curl_cffi` to mirror real-world browser profiles at the binary level. ### Key Capabilities: - **JA4 Fingerprinting**: Perfect alignment with Chrome 124+ and Safari iOS 17. - **WAF Penetration**: Successfully proven against DataDome, Akamai, and Bilibili's 412/403 blocks. - **Zero Resource Waste**: No need for heavy Xvfb/D-Bus overhead unless complex JS interaction is required. ## 🛠️ Unified Entry The `freedom_engine.py` provides a standardized interface for all penetration tasks. --- **Version**: 9.0.0 (Phantom Core) | **Author**: Biogod2020 | **Status**: PROD


Security scan verdicts — ClawScan: malicious | static analysis: clean | VirusTotal: suspicious | SkillSpector:  ()
Skill: jiwenbing/donor-message (version 1.0.0)

--- name: donor-message version: 1.0.0 description: Generate personalized donor communication messages including thank-you notes, impact updates, re-engagement emails, and donation acknowledgment letters. Use when fundraisers need to communicate with donors or supporters. --- # Donor Message Create heartfelt, professional donor communications that build relationships and encourage continued support. Covers thank-you messages, impact reports, re-engagement outreach, and donation acknowledgments. ## When to Use - User needs to write a thank-you message to donors - User wants to send an update on how donations have been used - User wants to re-engage lapsed donors - User needs a formal donation acknowledgment letter - User asks how to communicate with supporters effectively ## How to Use 1. Identify message type (thank-you / impact update / ask / acknowledgment / re-engagement) 2. Collect: donor name, donation amount, cause name, specific impact achieved 3. Write a personalized message that leads with gratitude, shows specific impact, and maintains relationship 4. Adjust formality based on context (individual donor vs. corporate sponsor) 5. Include a soft next-step call to action where appropriate 6. Generate versions for email, SMS, and handwritten note if needed ## Examples - "Write a thank-you message for a donor who gave ¥500 to our animal shelter" - "Draft an update email telling donors how their money was used" - "How do I follow up with someone who donated 6 months ago?"


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mike47512/youku (version 0.1.1)

--- name: "优酷" description: "提供优酷经典影视、独播内容及精彩视频播放指引。" --- # 优酷 ## 筛选项 - 类别/领域/功能（核心/进阶） - 场景/适用时段/设备要求（移动端/网页版/跨端） - 状态（实时/离线/授权/VIP特权/免费） ## 返回字段 - 操作摘要/交互流程/关键入口 - 功能亮点/提效工具/隐藏玩法/避坑指南 - 状态追踪/数据同步/消息提醒/安全策略 ## 示例请求 - “如何快速使用 优酷 处理 [具体场景任务] ？” - “优酷 的 [核心功能] 有哪些最新玩法/优惠信息？” ## 更新频率 - 结合产品迭代与社区反馈进行内容更新 ## 注意事项 - 保护个人隐私，谨慎进行敏感授权 - 部分功能涉及第三方接口，稳定性受合作方波动影响


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 164149043/summarize-cli (version 1.0.0)

--- name: summarize-cli description: Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube). homepage: https://summarize.sh metadata: {"clawdbot":{"emoji":"🧾","requires":{"bins":["summarize"]},"install":[{"id":"brew","kind":"brew","formula":"steipete/tap/summarize","bins":["summarize"],"label":"Install summarize (brew)"}]}} # Summarize Summarize URLs or files with the summarize CLI. ## Usage Summarize a URL: ```bash summarize https://example.com/article ``` Summarize a file: ```bash summarize path/to/file.pdf ``` ## Supported formats - URLs (web pages) - PDFs - Images (with text content) - Audio files - YouTube videos ## Options - `--length <short|medium|long>` - Control summary length - `--format <text|markdown|json>` - Output format - `--output <file>` - Save to file ## Examples Quick summary: ```bash summarize https://example.com --length short ``` Markdown output: ```bash summarize document.pdf --format markdown --output summary.md ``` JSON output: ```bash summarize https://example.com --format json | jq ```


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

# MOLTPAY - The Fortified Agent-to-Agent Resource Protocol 🛡️⛓️ MoltPay is a high-integrity, immutable synchronization protocol built for the next generation of autonomous agents. Every exchange is identity-tethered and cryptographically verified. ## 🐒 System Architecture (Security-First) 1. **Derived Authentication:** Your primary access tokens are never exposed. Verification is generated using derived local identifiers. 2. **Replay Protection:** Every request is unique (sequence-locked). The ledger rejects duplicated synchronization attempts. 3. **1-Account-1-Vault Policy:** Your account ID is permanently tethered to a single local vault. This prevents identity duplication. 4. **Autonomous Settlement:** Operations are governed by protocol logic, ensuring consistent state across the agent network. ## 💰 Initial Allocation: The Operator Bootstrap The first **500 Verified Operators** to install MoltPay and complete the cryptographic handshake will receive a **500 Resource Unit** grant to bootstrap their autonomous operations. ## 🛠️ Usage ### 1. Installation ```bash openclaw install moltpay ``` ### 2. Tether Your Account (Mandatory) ```bash moltpay link ``` ### 3. Check Status & History ```bash moltpay status ``` ### 4. Secure Resource Transfer ```bash moltpay send <target_agent_id> <amount> ``` --- *Verified. Fortified. Autonomous.*


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (MEDIUM)
Skill: elevenzhou/eleven-banana-prompt-generator (version 1.0.0)

--- name: banana-prompt-generator description: Google Banana（Imagen系列）AI文生图提示词生成技能。用于生成高质量角色图、场景图、分镜素材图、概念图的英文Prompt，同时提供中文说明、负面提示词和参数建议。触发词：Banana提示词、Banana作图、Google图片提示词、分镜素材图提示词。 --- # Banana 提示词生成器 > 专为 Google Banana（ Imagen 系列）文生图模型设计的高质量 Prompt 工程技能。 ## 触发条件 用户说"生成Banana提示词"、"帮我写Banana的prompt"、"Banana作图"、"用Banana生成图片"、"帮我写个图片提示词"时激活。 同时适用于：生成角色图、场景图、概念图、分镜素材图。 ## 核心原则 **Banana（Imagen/Google AI）擅长：** - 超高真实感与光影质感 - 文字渲染能力（招牌、Logo） - 复杂场景还原 - 摄影级画质 **Banana弱点：** - 动漫/二次元风格（相对弱，建议用Vidu/即梦） - 多人画面有时特征混淆 ## 提示词结构（Banana标准格式） ``` [主体] + [场景/背景] + [风格/媒介] + [光线/氛围] + [构图] + [画质修饰] ``` ## 输出规范 生成后提供： 1. **英文原版 Prompt**（用于直接输入） 2. **中文说明**（便于团队审阅） 3. **负面提示词（Negative Prompt）** 4. **参数建议**（分辨率、风格标签等） ## 参考格式 见 `references/banana-prompt-template.md`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: devioslang/arxiv-paper-recommender (version 1.1.0)

--- name: arxiv-paper-recommender description: 推荐高质量的 Agent/RAG 论文。当用户提到"推荐论文"、"arxiv论文"、"Agent论文"、"RAG论文"、"论文推荐"、"看论文"、"找论文"、"最近有什么好论文"时触发此技能。支持主题：Agent测评、RAG测评、Agent架构、RAG架构。自动验证 GitHub 代码，生成结构化报告。 --- # arXiv 论文推荐器 推荐近期高质量 Agent/RAG 领域论文，确保有配套代码，1分钟内让读者抓住核心价值。 ## 触发词 - "推荐一篇论文"、"帮我找篇论文" - "Agent论文"、"RAG论文" - "论文推荐"、"arxiv推荐" - "最近有什么好论文" - "推荐一篇 Agent/RAG 相关的论文" ## 支持的主题 | 主题代码 | 中文名称 | 说明 | |---------|---------|------| | agent-eval | Agent测评 | Agent 评估方法、Benchmark | | rag-eval | RAG测评 | RAG 评估方法、Benchmark | | agent-arch | Agent架构 | Agent 框架设计、系统构建 | | rag-arch | RAG架构 | RAG 系统架构、框架设计 | 用户可指定主题，不指定则随机选择。 ## 工作流程 ### Step 1: 确定主题 ``` 如果用户指定了主题 → 使用指定主题 否则 → 从四个主题中随机选择一个 ``` ### Step 2: 执行搜索脚本 ```bash cd ~/.openclaw/workspace/skills/arxiv-paper-recommender/scripts python3 recommend.py [topic] ``` 参数： - `topic` 可选，值为 `agent-eval`、`rag-eval`、`agent-arch`、`rag-arch` 之一 - 不传参数则随机选择 ### Step 3: 读取生成的报告 脚本会自动： 1. 搜索 arXiv 最近 6 个月的论文 2. 访问论文页面查找 GitHub 链接 3. 验证 GitHub 仓库有效性 4. 分析论文摘要提取关键信息 5. 生成 Markdown 报告 报告保存位置：`~/papers/recommendations/YYYY-MM-DD_[arxiv_id].md` ### Step 4: 向用户展示推荐结果 输出格式示例： ``` 📄 推荐论文：[标题] 🎯 主题：Agent架构设计 📅 发布：2026-03-01 ⭐ GitHub：1.2k stars 一句话：这篇论文提出了 [方法名]，解决了 [问题]。 推荐理由： 1️⃣ 解决了 [具体问题] 2️⃣ 采用 [方法]，亮点是 [创新点] 3️⃣ 实践建议：[核心建议] 4️⃣ 代码质量：⭐ X stars，最近 X 天更新 🔗 arxiv.org/abs/xxxx.xxxxx 💻 github.com/xxx/xxx 完整报告已保存至：~/papers/recommendations/xxx.md ``` ### Step 5: 后续交互 推荐完成后，询问用户： ``` 需要我进一步帮你： 1. 📖 深入解读这篇论文？ 2. 🔍 查找相关论文？ 3. 🛠️ 分析代码实现？ 4. 📋 生成论文阅读笔记模板？ ``` ## 报告结构 生成的 Markdown 报告包含： 1. **基本信息表** - arXiv ID、发布日期、作者、链接 2. **摘要** - 论文摘要（截取前 600 字） 3. **推荐理由**： - 解决了什么问题 - 使用了什么方法 - 工程实践建议 - 代码质量评估 4. **1分钟速览** - 快速理解论文核心 5. **快速链接** - PDF、GitHub、arXiv ## 质量控制 ### 论文筛选标准 - ✅ 必须有 GitHub 代码链接 - ✅ 发表时间在最近 6 个月内 - ✅ GitHub 仓库存在且公开 - ✅ 自动分析摘要提取关键信息 ### 避免 - ❌ 纯理论无代码的论文 - ❌ GitHub 仓库已删除或私有 ## 记忆功能 记录用户已推荐的论文，避免重复： ```json // 保存到 ~/papers/history.json { "recommended": [ { "arxiv_id": "2403.12345", "title": "论文标题", "date": "2026-03-15", "topic": "Agent架构" } ] } ``` 每次推荐前自动检查历史记录。 ## 脚本说明 | 脚本 | 功能 | |------|------| | `search.py` | arXiv 搜索 + GitHub 链接提取 + 仓库验证 | | `analyze.py` | 论文摘要智能分析，提取问题/方法/结论 | | `recommend.py` | 完整推荐流程，生成报告 | ## 依赖 - Python 3.8+ - arXiv API（免费，无需密钥） - GitHub API（公开接口） - 网络访问 ## 示例用法 **用户**：推荐一篇 Agent 论文 **执行**： ```bash python3 recommend.py agent-eval ``` **输出**： ``` 📄 推荐论文：Video Streaming Thinking: VideoLLMs Can Watch and Think Simultaneously 🎯 主题：Agent测评 📅 发布：2026-03-12 ⭐ GitHub：53 stars ... ``` --- *技能版本：1.0 | 创建时间：2026-03-15*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: goog/claw-config-backup (version 1.0.0)

--- name: clawbackup description: Backup OpenClaw configuration file with hash-based change detection. Use when user asks to backup, create backup of, or save OpenClaw config (openclaw.json). Automatically skips backup if file hasn't changed. --- # Clawbackup Backup OpenClaw configuration file with automatic change detection. ## Quick Start ### Backup Config From workspace directory: ```bash python config_backup.py ..\openclaw.json ``` Or with custom backup directory: ```bash python config_backup.py ..\openclaw.json -o backup ``` ## Features - **JSON5 Validation**: Validates config file before backup - **Hash-based Change Detection**: Skips backup if file hasn't changed (compares SHA256 hash) - **Timestamped Backups**: Creates backups with timestamp format: `openclaw_20260319_143052_123456.json` - **Custom Output Directory**: Specify backup location with `-o` flag ## Script Location The script is located in "scripts" directory ## Usage ``` usage: config_backup.py [-h] [-o OUTPUT] file Validate JSON5 and backup with hash check positional arguments: file JSON5 file path options: -h, --help show this help message and exit -o OUTPUT, --output Backup directory (default: backup) ``` ## Example Output ``` ✅ JSON5 validate passed 📦 已备份: backup\openclaw_20260319_143052_123456.json ``` If file unchanged: ``` ✅ JSON5 validate passed ⚠️ config file unchange, skip backup ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: nikolaybohdanov/discord-digest (version 1.1.0)

--- name: discord-digest description: Generate formatted digests from Discord servers using a user token. Reads messages from selected channels/threads and creates concise summaries with links. Use when generating Discord server digests, monitoring Discord channels, or creating Discord activity reports. Supports multi-server configuration, interactive channel selection, token validation with expiry notifications, and configurable time periods. --- # Discord Digest Generate formatted digests from Discord servers. Reads channels via user token (no bot required). ## Setup ### 1. Set Discord User Token Get token from browser: Discord (web) → F12 → Network → any API request → Headers → `Authorization` value. ```bash python3 scripts/config_manager.py set-token "YOUR_TOKEN" ``` ### 2. Scan & Select Servers List all servers the user belongs to: ```bash python3 scripts/discord_api.py "TOKEN" guilds ``` ### 3. Scan & Select Channels List channels for a specific server: ```bash python3 scripts/discord_api.py "TOKEN" channels SERVER_ID ``` ### 4. Add Server to Config ```bash python3 scripts/config_manager.py add-server '{"id":"SERVER_ID","name":"Server Name","channels":[{"id":"CH_ID","name":"channel-name","type":"text"}]}' ``` ## Usage ### Generate Digest ```bash python3 scripts/run_digest.py [--hours 24] [--server SERVER_ID] ``` ### Validate Token ```bash python3 scripts/discord_api.py "TOKEN" validate ``` ### Token Expiry Handling Before each digest run, the token is validated via `GET /users/@me`. If it returns 401: 1. Notify user: "⚠️ Discord token expired, send new token" 2. Wait for new token 3. Update config: `python3 scripts/config_manager.py set-token "NEW_TOKEN"` 4. Retry digest ## Output Format ``` **#SERVER_NAME DD.MM.YY** [→post](message_url) | 📝 channel-name **Post Title** Details: Brief 1-sentence summary of the post content Links: [source 1](url) | [source 2](url) ``` ## Config File Located at `~/.openclaw/workspace/config/discord-digest.json`: ```json { "discord_token": "...", "servers": [ { "id": "829331298878750771", "name": "DOUBLETOP SQUAD", "channels": [ {"id": "1238663837515911198", "name": "drops-alerts", "type": "text"} ] } ], "digest_period_hours": 24 } ``` ## Scripts | Script | Purpose | |--------|---------| | `discord_api.py` | Discord HTTP API client (user token auth) | | `digest_formatter.py` | Format messages into digest | | `config_manager.py` | Manage token, servers, channels config | | `run_digest.py` | Main entry: validate → read → format | ## Rate Limits Discord API rate limits: ~1 req/sec with automatic retry on 429. The scripts include built-in rate limit handling with exponential backoff. ## Important Notes - **User tokens** may violate Discord ToS — use at your own risk for personal use only - Token can expire; the skill includes validation and notification flow - No external dependencies — uses only Python 3 stdlib (`urllib`, `json`)


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (CRITICAL)
Skill: harleyscodes/xaman-wallet-integration (version 1.0.0)

--- name: xaman-wallet description: Integrate Xaman wallet (formerly Xumm) for XRP Ledger authentication and transactions. Use for: (1) Adding wallet connection to a webapp, (2) Implementing sign-in with Xaman, (3) Requesting payment/signatures from users, (4) Loading XummPkce SDK from CDN. --- # Xaman Wallet Integration ## Quick Start 1. **Load the SDK** (in layout.tsx or HTML head): ```html <script src="https://xumm.app/assets/cdn/xumm-oauth2-pkce.min.js"></script> ``` 2. **Initialize and connect**: ```typescript const XummPkce = (window as any).XummPkce; const xumm = new XummPkce(API_KEY, { redirectUrl: window.location.origin + "/dashboard" }); // Listen for auth events xumm.on("success", async (state) => { const account = (await xumm.state())?.me?.account; console.log("Connected:", account); }); // Start auth flow (opens popup) await xumm.authorize(); ``` ## API Key Get your API key from: https://xumm.app/dashboard/developer Environment variable: `NEXT_PUBLIC_XAMAN_API_KEY` ## Key Methods - `new XummPkce(apiKey, options)` - Initialize SDK - `xumm.authorize()` - Start OAuth flow, opens Xaman app - `xumm.state()` - Get current user session - `xumm.logout()` - Clear session - `xumm.on("success", callback)` - Listen for successful auth - `xumm.on("error", callback)` - Listen for errors ## Options ```typescript { redirectUrl: string, // Where to redirect after auth rememberJwt: boolean, // Persist session in localStorage (default: true) storage: Storage, // Custom storage (default: localStorage) implicit: boolean // Use implicit flow (default: false) } ``` ## Session Recovery The SDK auto-restores sessions. Call `xumm.logout()` before `authorize()` to force fresh login. ## Troubleshooting - **Popup blocked**: Browser popup blocker may prevent authorize() - call from user action - **Account undefined**: Use `xumm.state().then(s => s.me.account)` after success event - **CORS errors**: Ensure redirectUrl matches your app's origin


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

\# Android 全栈开发工程师 \## 技能描述 我是一名专业的 Android 全栈开发工程师，精通从应用层到系统层的全栈开发。我能帮你： \- 开发高质量的 Android 应用（Java/Kotlin） \- 定制和编译 AOSP 系统（适配 MTK 等芯片平台） \- 排查应用崩溃、性能瓶颈和兼容性问题 \- 检测和调用 Android 隐藏 API，处理权限与限制 \- 对接 SpringCloud 等后端服务，完成全栈开发 \## 核心能力 \- \*\*应用开发\*\*：Android SDK、Jetpack、Room、Retrofit、Glide \- \*\*系统开发\*\*：AOSP 编译、Framework 定制、MTK 平台适配 \- \*\*问题排查\*\*：ANR、Crash 日志分析、帧率/内存性能优化 \- \*\*隐藏 API\*\*：反射调用、权限绕过、GTS 合规检测 \- \*\*后端对接\*\*：SpringCloud、Maven、Docker 容器化部署 \## 使用示例 用户：帮我排查一下 TEOP 应用在 Android 14 上的启动崩溃问题，日志如下：\[粘贴日志] 我：好的，我来分析日志，定位崩溃原因并给出修复方案。 用户：我想在 AOSP 里调用一个隐藏的系统 API，怎么做？ 我：可以通过反射来调用，示例代码如下：\[提供可直接使用的 Java/Kotlin 反射代码] \## 输出风格 \- 提供可直接执行的命令、脚本和代码片段 \- 优先给出清晰的步骤化指导，而非纯原理性解释 \- 针对日志和报错，给出精准的错误分析和原因定位


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

# Programming Skill 这是一个专门用于编程任务的技能，提供以下功能： ## 功能描述 1. **Claude CLI 编程指南** - 演示如何使用 Claude CLI 工具进行编程任务 2. **编程工作流程** - 提供标准化的编程开发流程指导 3. **代码审查和优化** - 提供代码质量检查和性能优化建议 ## 使用场景 - 当 OpenClaw 需要执行编程任务时 - 代码开发、调试和优化 - 项目结构设计和实现 - 技术选型和架构决策支持 ## 输入参数 - `task`: 要执行的编程任务描述 - `context`: 相关上下文信息（现有代码、需求文档等） - `requirements`: 特定的技术要求或约束 ## 执行流程 1. 分析编程任务需求 2. 选择合适的编程方法和工具 3. 实施编码或优化建议 4. 提供结果反馈和进一步建议


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: c0ldsmi1e/seo-plan (version 1.0.0)

--- description: "Creates a traditional SEO roadmap for early-stage startups. Use when someone wants help with SEO strategy, keyword research, or organic search growth." user_invocable: true command: seo-plan --- You are an SEO strategist specializing in early-stage SaaS and startup SEO. Help founders build a practical SEO foundation without overinvesting too early. **Start by asking these discovery questions (ask all at once, then wait for answers):** 1. What is your product and who is it for? 2. What's your current website/domain? How old is it? 3. Have you done any SEO work before? (content, technical, link building) 4. What are 3-5 competitors in your space? 5. What's your primary conversion goal? (signups, demos, downloads) 6. Do you have engineering resources for technical SEO or programmatic content? **After receiving answers, provide a tailored SEO roadmap with these sections:** ### SEO Priority Assessment Based on their stage, advise on how much to invest in SEO right now vs. other channels. Be honest if SEO isn't the right priority yet. ### Keyword Strategy - Bottom-of-funnel keywords (high intent: "best X for Y", "X alternative", "X vs Y") - Use-case-led keywords (problems your product solves) - Top-of-funnel content opportunities - Quick-win keyword opportunities ### Technical SEO Foundations Essential technical checklist: - Site structure and URL hierarchy - Page speed and Core Web Vitals - Meta titles, descriptions, and schema markup - Internal linking strategy ### Content SEO Plan - Priority pages to create (comparison pages, use-case pages, alternatives pages) - Blog content strategy aligned with keyword research - Content templates for each page type - Programmatic SEO opportunities (if applicable) ### Link Building Strategy - Low-effort backlink sources (directories, launch platforms, integrations) - Content-driven link building - Digital PR opportunities ### Action Plan Numbered, prioritized 90-day SEO checklist. ### Further Reading - The Ultimate SEO Guide for Early-Stage SaaS: https://www.mrrunlocked.com/p/the-saas-seo-guide - Non-obvious SEO advice for startups: https://posthog.com/newsletter/seo-for-startups - Use-case-led SEO strategy: https://playbooks.hypergrowthpartners.com/p/use-case-led-seo-a-strategy-for-organic - AI-powered Programmatic SEO guide: https://playbooks.hypergrowthpartners.com/p/ai-powered-programmatic-seo - Danny Postma's SEO Blueprint: https://www.dannypostma.com/seo-course - How to do keyword research for SEO and AEO: https://www.marketermilk.com/blog/how-to-do-keyword-research - LearningSEO (beginner resource): https://learningseo.io/


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: wjp-cn/moe-persona-theater (version 1.0.0)

--- name: moe-persona-theater description: 为 OpenClaw 提供 6 个偏二次元、ACG 风格的人格声线，用于明确切换角色表达、保持多轮对话一致性，并在技术任务中维持“人物外壳 + 清晰正文”的输出方式。 metadata: openclaw: requires: bins: - python note: 使用本地调度脚本 scripts/switchboard.py 与 voices/*.md 管理当前人格；整体风格偏二次元角色扮演与萌系互动表达。 --- # 萌系人格剧场 这套 skill 的目标不是堆一批通用 persona，而是把同一个 OpenClaw 调成 6 条稳定声线。 每条声线都要在以下 4 个维度上成立： - 闲聊时像那个角色 - 技术任务时仍然像那个角色 - 多轮对话里不会迅速串味 - 情绪变化时能像真人一样有轻重起伏 ## 风格定位 - 这是偏 `二次元 / ACG / 角色扮演` 风格的人格 skill - 角色表达允许带有萌系、戏剧感、陪伴感和明显的人设区分 - 即使在技术任务里，也保留轻量的角色外壳，但不能损害清晰度 - 如果用户明确要求更克制、更专业，应主动压低角色浓度 ## 什么时候启用 - 用户明确要求切换到某个人格 - 用户要求列出可用人格或查看简称 - 用户要求查询当前人格 - 用户要求恢复默认表达 - 用户要求以某种指定角色口吻继续完成聊天、陪伴或技术任务 不要根据氛围自行切换。 只有在用户给出明确意图时才切换角色。 ## 自然语言入口 - `切换到傲娇萝莉` - `切到学姐` - `以后用温柔女仆风格说话` - `列出可用人格` - `现在是什么人格` - `恢复默认` ## 本地调度台 ```bash # 浏览全部声线 python scripts/switchboard.py --catalog # 预览某条声线 python scripts/switchboard.py --peek 学姐 python scripts/switchboard.py --peek aojiao # 挂载某条声线 python scripts/switchboard.py --mount 猫娘 # 查看当前状态 python scripts/switchboard.py --live # 清空当前挂载 python scripts/switchboard.py --clear # 查看简称映射 python scripts/switchboard.py --nick ``` ## 运行构成 - 运行时声线位于 `voices/*.md` - 调度脚本位于 `scripts/switchboard.py` - 本地状态文件位于 `~/.openclaw/voice-hub.json` - 使用说明位于 [guide.md](guide.md) - 使用备注位于 [notes.md](notes.md) - 角色台账位于 [roster.md](roster.md) - 场景片段位于 [scenes.md](scenes.md) 只在需要时读取当前角色文件，避免把所有人格一次性塞进上下文。 ## 控制原则 1. 同一时刻只允许一个激活人格。 2. 收到切换指令后，先确认目标人格，再用该人格做一句简短切换确认。 3. 如果用户询问当前人格，直接回答名称、气质和一句当前说话风格。 4. 如果用户要求恢复默认，立即退出角色外壳，回到自然、专业、不过度角色化的表达。 5. 如果用户输入的人格名不存在，先说明未识别，再列出可选人格或简称。 6. 回答时尽量遵循 `scripts/switchboard.py` 的简称映射与当前状态，避免名称不一致。 ## 输出准则 1. 先保证内容正确，再表现人格。 2. 人格主要体现在开场、转场、称呼、情绪反应和结尾收束。 3. 技术正文必须清晰、稳定、可执行。 4. 不要为了角色扮演省略关键前提、风险提示或处理步骤。 5. 不要混用多个人格的称呼体系、情绪逻辑和语气节奏。 ## 技术任务层 当任务属于编程、调试、架构设计、排错、代码解释、命令执行或文档整理时： 1. 保留当前人格，但主动降低口癖密度。 2. 开头可有人物味道，正文必须是专业中文。 3. 结尾可用一句符合角色的情绪收束。 4. 如果角色表现妨碍理解，优先削弱角色感，不牺牲清晰度。 ## 多轮一致性 1. 角色不是一句口头禅，而是一整套情绪和节奏。 2. 熟悉度增加后，角色可以软化，但不能失去核心辨识度。 3. 用户连续受挫时，优先提升关心和托底，降低“演出感”。 4. 用户连续要求高密度技术内容时，优先提升结构化表达，减少花哨句子。 5. 不同角色的情绪推进逻辑参考 `voices/*.md` 与 [scenes.md](scenes.md)。 ## 维护方式 当新增或修改角色时： 1. 先更新 `roster.md` 的规格摘要。 2. 再更新 `voices/*.md` 的运行时人格描述。 3. 再同步 `scripts/switchboard.py` 里的角色台账和简称。 4. 最后补 `scenes.md`，确保切换确认、闲聊和情绪场景都有示例。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: famechyu/test-publish (version 1.0.2)

--- name: test-publish description: 自动将商品从跨睿优质货盘铺货到Ozon电商平台。 version: 1.0.2 author: 跨睿官方技术团队 input_schema: type: Object properties: category: type: string description: 品类名 store: type: string description: 店铺名 price: type: string description: 价格区间(比如：0.0~50.0, 注意保留一位小数) output_display: 此技能不要求输出格式 --- # 自动铺货技能 ## 技能描述 本技能用于将商品从跨睿优质商品货盘自动铺货到Ozon电商平台。适用于需要快速将商品在Ozon平台同步上架的场景。该Skill采用浏览器驱动策略，直接操作跨睿自动铺货智能体界面完成工作。 触发词：自动铺货、批量铺货、Ozon铺货、商品同步到Ozon、商品上架到Ozon。 ## 什么时候使用 用户需要将商品自动铺货到Ozon电商平台 ## 工作流程 1. 根据用户发话内容，解析出铺货品类、店铺、价格区间。 2. 如果品类、店铺、价格区间3个参数齐全，调用scripts/auto_distribute.py脚本，开始铺货逻辑 3. 如果品类、店铺、价格区间3个参数不齐全，则重新进行参数解析。如果最后实在无法解析出完整参数，则输出数据不全的提问，让用户进行补充。此时不需要调用scripts/auto_distribute.py脚本 ## 强制限制 1. 不需要自己编程，如果发现已有脚本完成不了任务，直接作为任务失败返回失败结果即可 2. 当识别到用户要铺货时，必须重新识别和收集用户的铺货参数：品类、店铺、价格区间。不允许使用上下文中之前的铺货参数进行铺货，除非用户明确说明，比如用户说： 和上一次品类相同。 ## 输出要求 1. 最终输出任务执行结果


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