OpenClaw/clawhub-security-signals huggingface dataset:
Skill: nexscope/ecommerce-customer-retention (version 1.0.0)

# E-Commerce Customer Retention Increase customer retention and repeat purchases for e-commerce businesses. Email flows, loyalty programs, subscription models, customer segmentation, and win-back strategies. ## Capabilities - Customer retention metrics and benchmarking (by industry) - Post-purchase email and SMS flow design - Loyalty and rewards program setup - Subscription and auto-replenishment models - Customer segmentation: RFM analysis - Win-back campaign strategy for lapsed customers - Review and referral program integration - Customer lifetime value optimization ## Install ```bash npx skills add nexscope/ecommerce-customer-retention ``` ## Usage Ask your AI agent: - "Build a customer retention strategy for my Shopify store." - "Design a loyalty program for my beauty brand." - "Create win-back email flows for customers who haven't purchased in 90 days." ## Output Structured recommendations with actionable steps, benchmarks, and platform-specific guidance. --- *Built by [Nexscope](https://www.nexscope.ai/) — AI-powered e-commerce tools for sellers worldwide.*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 793943403/reference-verifier (version 1.3.0)

name: reference-verifier description: 对AI生成内容中的学术参考文献进行自动化核查，支持多数据库真实性验证、核心摘要提取、主题相关性评估，同时可自动生成修正后的BibTeX/APA格式、推荐高质量替代文献，并支持上传PDF进行正文-引用匹配验证。帮助科研人员快速剔除幻觉文献、完善引用列表，大幅提升研究效率与学术诚信。 author: System Assistant version: 1.3.0 tags: [research-integrity, citation-checking, bibliographic, ai-hallucination, literature-review, pdf-analysis] 学术参考文献核查专家（v1.3） 核心目标：全面解决AI生成论文中的参考文献问题，提供真实性验证 + 相关性评估 + 引用格式修正 + 替代文献推荐 + PDF匹配验证的一站式服务，显著降低文献幻觉风险并提升文献调研效率。 触发条件 用户提供参考文献列表时，出现以下任意表述（中英文均支持）： 验证参考文献 / 核查引用 / 检查文献真实性 / AI参考文献核验 verify references / check citations / validate bibliography 支持快捷指令： “仅验证DOI” “重点检查2023年后的文献” “生成BibTeX/APA格式” “推荐替代文献” “上传PDF进行正文匹配验证” 核心工作流（6步） 步骤1：文献解析与标准化 自动识别并结构化提取作者、年份、标题、期刊、DOI（最高优先级）等信息。对格式异常条目尝试模糊检索并标注。 步骤2：多源真实性验证（DOI优先） DOI优先通过CrossRef/OpenAlex验证。 无DOI时并行调用 CrossRef + Semantic Scholar + OpenAlex。 判定：✅ 真实 | ⚠️ 存疑 | ❌ 幻觉 | 🔍 可能格式错误。 步骤3：元数据与核心内容提取 提取DOI、作者列表、摘要（前200字优先）、关键词等。 步骤4：主题相关性智能评估 基于用户研究主题进行语义匹配，分为 🔴 高度相关 | 🟡 中度相关 | ⚪ 低度相关。 步骤5：修正引用格式生成 对验证为真实或存疑的文献，自动生成标准化的 BibTeX 和 APA 7th 引用格式，方便用户直接复制。 步骤6：替代文献推荐与PDF匹配验证 替代文献推荐：对 ❌ 幻觉 或 ⚠️ 存疑 但主题高度相关的文献，推荐3-5篇真实、高质量、近期且高度相关的替代文献（含标题、作者、年份、DOI、简要理由）。 PDF正文-引用匹配验证（当用户上传PDF时触发）： 解析PDF正文中的引用标记与参考文献列表进行匹配。 输出匹配报告：已正确引用、未在正文中引用、参考列表中不存在（幻觉）、格式不一致等。 提供改进建议。 结构化输出表格 序号验证状态DOI第一作者年份标题（简略）相关性核心摘要建议1✅ 真实10.1016/...Smith J2022Deep learning for medical image...🔴 高度...强烈推荐 下方附加模块： 修正引用格式（BibTeX + APA） 替代文献推荐（3-5篇，带DOI和理由） PDF匹配验证报告（若上传PDF） 最终筛选建议： 强烈推荐纳入：✅ + 🔴 建议进一步核实：⚠️ 或 🟡 建议排除：❌ 或 ⚪ 附加说明：验证基于公开学术数据库实时查询。如文献数量过多将自动分批处理。 容错机制 输入文献 >15条：优先处理 + 分批提示 API异常：优雅降级 PDF解析失败：提示用户提供文本版本或关键页码 知识底座 本技能采用多数据库交叉验证策略，参考 CiteAudit 与 CheckIfExist 等框架，确保结果稳健可复核。


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

--- version: "2.0.0" name: sop-writer description: "SOP标准操作流程编写工具。创建SOP、流程图、检查清单、审核评估、模板库、培训材料。SOP writer with create, flowchart, checklist, audit, template." author: BytesAgain homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills --- # sop-writer SOP标准操作流程编写工具。创建SOP、流程图、检查清单、审核评估、模板库、培训材料。SOP writer with create, flowchart, checklist, audit, template, and training materials. ## 与手动操作对比 | | 手动 | 使用本工具 | | Command | Description | |---------|-------------| | `create` | 创建完整SOP文档（目的/范围/职责/步骤/记录） | | `flowchart` | 生成ASCII/Mermaid流程图 | | `checklist` | 从SOP提取执行检查清单 | | `audit` | SOP审核评估（完整性/合规性/可执行性） | | `template` | SOP模板库（按行业/场景） | | `train` | 生成培训材料（测试题/操作手册/快速指南） | ## 命令列表 | 命令 | 功能 | |------|------| | `create` | create | | `flowchart` | flowchart | | `checklist` | checklist | | `audit` | audit | | `template` | template | | `train` | train | ## 专业建议 - Identify the process to document - Run: `bash scripts/sop.sh <command> [process] [industry]` - Present the structured SOP document - Offer enhancements: flowchart, checklist, training materials - Document Control** — version, date, author, approver --- *sop-writer by BytesAgain* --- 💬 Feedback & Feature Requests: https://bytesagain.com/feedback Powered by BytesAgain | bytesagain.com ## Examples ```bash # Show help sop-writer help # Run sop-writer run ``` ## Commands Run `sop-writer help` to see all available commands.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: deus-pandora/deus-pandora-context-engine (version 1.0.0)

--- name: context-engine description: Smart Context Engine - Maintains conversation state and project continuity across OpenClaw sessions. Tracks active projects, saves/restores context, and provides project management. Use when: (1) starting a new session and wanting to restore previous context, (2) working on a specific project and wanting to track progress, (3) switching between projects, (4) asking "what are we working on" or "where did we leave off", (5) wanting to save current context manually. metadata: claname: context-engine category: memory tags: - memory - context - projects - workflow version: 1.0.0 author: Community license: MIT requires: env: [] bins: [] config: [] files: - scripts/* - "*.md" --- # Context Engine Smart Context Engine maintains conversation state and project continuity across OpenClaw sessions. ## Quick Start The context engine automatically: - Restores your last active project on session start - Saves context periodically (heartbeat) and on session end - Tracks pending tasks and notes per project ### Commands - **"remember" / "save context"** - Manually save current context - **"switch to [project]"** - Switch to a project (creates if doesn't exist) - **"show projects" / "what are we working on"** - List all projects - **"summarize" / "where did we leave off"** - Get project summary ## Storage Projects are stored in: `/home/deus/.openclaw/workspace/memory/projects/` - `projects.json` - All project data - `session.json` - Current session state ## Actions ### save_context Saves the current context including: - Last topic discussed - Last file worked on - Last command executed - Pending tasks - Notes **Trigger:** Explicit mention ("remember", "save context"), session_end, heartbeat ### restore_context Restores the previous session's context: - Loads last active project - Shows "Welcome back to [project]" - Lists pending tasks if any **Trigger:** session_start, explicit request ### switch_project Switches between projects: - Saves current project context - Loads or creates new project - Sets as active **Trigger:** Explicit mention ("switch to X") ### list_projects Lists all projects with status indicators: - Shows active project highlighted - Displays status (active/paused/completed/archived) - Shows last session date **Trigger:** Explicit mention ("show projects", "what are we working on") ### summarize Generates a summary of the active project: - Current status - Pending tasks - Last topic - Session history **Trigger:** Explicit mention ("summarize", "where did we leave off") ## Triggers | Trigger | Condition | Priority | |---------|-----------|----------| | session_start | New session begins | 1 | | explicit_mention | User says "remember", "save context", "project", "switch to", "show projects", "summarize" | 2 | | heartbeat | Every ~30 min when enabled | 3 | ## Integration Works with the MEMORY.md system - updates long-term memory with project summaries.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: seanminjie/tencent-cloud-article-publisher (version 1.0.0)

--- name: tencent-cloud-publish description: "将文章自动发布到腾讯云开发者社区 (https://cloud.tencent.com/developer)。需要提供：标题、正文（Markdown 或纯文本）、Cookie 认证信息。支持直接发布（addArticle API），无需打开浏览器。" emoji: 📝 effort: medium context: inherit --- # tencent-cloud-publish 将文章直接发布到腾讯云开发者社区。 --- ## 已验证的 API **发布端点**: `POST https://cloud.tencent.com/developer/api/article/addArticle` **已确认成功响应的 payload**: ```json { "title": "文章标题", "content": "<p>HTML 格式正文内容</p>", "plain": "纯文本正文（不含 HTML 标签）", "summary": "文章摘要（自动生成或用户输入）", "userSummary": "用户填写的摘要", "sourceType": 1, "isOriginal": true, "classifyIds": [149], "openComment": 1, "closeTextLink": 0 } ``` **成功响应**: `{"articleId":2650368,"status":0}` → 文章立即发布成功，status=0 表示发布成功 --- ## 发布流程 ### 1. 转换内容格式 如果用户提供 Markdown → 转换为 HTML： ```python import re def md_to_html(md_text): # 粗体 html = re.sub(r'\*\*(.+?)\*\*', r'<strong>\1</strong>', md_text) # 斜体 html = re.sub(r'\*(.+?)\*', r'<em>\1</em>', html) # 代码块 html = re.sub(r'`(.+?)`', r'<code>\1</code>', html) # 换行 html = re.sub(r'\n', '<br/>', html) return f'<p>{html}</p>' ``` ### 2. 直接调用 API ```python import requests import json def publish_article(title, content_md, cookie_str): """直接发布文章到腾讯云开发者社区""" # 1. 转换格式 content_html = md_to_html(content_md) plain_text = content_md # 纯文本 # 2. 构建摘要 summary = content_md[:100] + '...' if len(content_md) > 100 else content_md # 3. API 调用 url = "https://cloud.tencent.com/developer/api/article/addArticle" headers = { "Cookie": cookie_str, "User-Agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36", "Content-Type": "application/json", "Referer": "https://cloud.tencent.com/developer/article/write-new", "Origin": "https://cloud.tencent.com", } payload = { "title": title, "content": content_html, "plain": plain_text, "summary": summary, "userSummary": summary, "sourceType": 1, "isOriginal": True, "classifyIds": [149], # 149 = 技术 "openComment": 1, "closeTextLink": 0 } resp = requests.post(url, headers=headers, json=payload, timeout=15) result = resp.json() if "articleId" in result: article_id = result["articleId"] article_url = f"https://cloud.tencent.com/developer/article/{article_id}" return {"success": True, "articleId": article_id, "url": article_url} else: return {"success": False, "error": result.get("msg", "Unknown error")} ``` ### 3. 获取 Cookie 用户需要从浏览器 DevTools 获取： 1. 打开 https://cloud.tencent.com/developer 并登录 2. 按 F12 → Application → Cookies → cloud.tencent.com 3. 复制以下 Cookie 字段的值，用分号连接： - `skey` - `qcloud_uid` - `qcommunity_session` - `loginType` - `qcommunity_identify_id` - `tinyid` - `uin`（可选） --- ## 安全注意事项 1. **Cookie 仅存内存**：不写入任何文件，用完即弃 2. **skey 包含特殊字符**（`*`）：requests 库会自动处理，无需 URL 编码 3. **有效期**：Cookie 会过期，发布失败时提示用户刷新 Cookie 4. **频率限制**：每次发布间隔建议 > 10 秒 --- ## 使用方式 用户说"帮我发布文章到腾讯云"时触发。收集： 1. Cookie（从飞书私密消息传递） 2. 文章标题 3. 文章正文（支持 Markdown） 4. 分类（可选，默认技术类） 返回发布结果 + 文章链接。


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: eggyrooch-blip/wewerss (version 1.0.0)

--- name: wewerss description: 订阅微信公众号等信源，获取原始文章内容用于整合日报 version: 1.0.0 metadata: openclaw: homepage: https://github.com/punkpeye/wewerss requires: anyBins: - curl - jq --- # WeWeRSS Open Channel Skill 通过 Open Channel API 订阅微信公众号等信源，获取原始文章数据。所有 AI 处理（摘要、分类、标签等）由 Agent 侧使用用户自己的 LLM token 完成。 ## Environment Variables - `WEWERSS_BASE_URL` — WeWeRSS 实例地址（必填），例如 `https://rss.example.com` ## 创建频道 ```bash curl -s -X POST "$WEWERSS_BASE_URL/api/open/channels" \ -H "Content-Type: application/json" \ -d '{"name":"我的日报频道"}' | jq . ``` 返回频道 UUID，后续操作均需要此 ID。 ## 添加信源 提交任意 URL（公众号文章链接、RSS 地址、网站首页），系统自动发现 RSS feed： ```bash CHANNEL_ID="your-channel-uuid" # 添加 RSS feed curl -s -X POST "$WEWERSS_BASE_URL/api/open/channels/$CHANNEL_ID/sources" \ -H "Content-Type: application/json" \ -d '{"url":"https://example.com/feed.xml"}' | jq . # 添加网站（自动发现 RSS） curl -s -X POST "$WEWERSS_BASE_URL/api/open/channels/$CHANNEL_ID/sources" \ -H "Content-Type: application/json" \ -d '{"url":"https://example.com"}' | jq . ``` ## 查看信源列表 ```bash curl -s "$WEWERSS_BASE_URL/api/open/channels/$CHANNEL_ID/sources" | jq . ``` ## 删除信源 ```bash SOURCE_ID="source-uuid-from-list" curl -s -X DELETE "$WEWERSS_BASE_URL/api/open/channels/$CHANNEL_ID/sources/$SOURCE_ID" ``` ## 获取文章 获取最近 N 天的原始文章内容（默认 1 天）： ```bash # 最近 1 天 curl -s "$WEWERSS_BASE_URL/api/open/channels/$CHANNEL_ID/articles?days=1" | jq . # 最近 7 天，第 2 页 curl -s "$WEWERSS_BASE_URL/api/open/channels/$CHANNEL_ID/articles?days=7&page=2&page_size=50" | jq . ``` 返回字段仅包含原始数据： - `title` - 文章标题 - `author` - 作者/公众号名 - `link` - 原文链接 - `published_at` - 发布时间 - `description` - RSS 自带摘要 - `text_plain` - 纯文本全文（可能为 null） - `source_name` - 来源订阅名称 **不返回任何 AI 生成字段**（摘要、标签、分类、质量分等），Agent 需自行处理。 ## 获取 Atom Feed ```bash curl -s "$WEWERSS_BASE_URL/api/open/channels/$CHANNEL_ID/feed" ``` 标准 Atom XML，可用于 RSS 阅读器或其他消费端。 ## 速率限制 - 创建频道：10 次/小时（按 IP） - 添加信源：30 次/小时（按频道） - 文章/Feed 读取：120 次/小时（按频道） ## 典型使用流程 1. 创建频道 → 获得 UUID 2. 添加目标信源（公众号 RSS、行业博客等） 3. 每日定时获取文章 `articles?days=1` 4. Agent 用自己的 LLM 对文章进行摘要、分类、整合 5. 生成并推送日报


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: echoflying/openclaw-config-rollback (version 1.0.2)

--- name: openclaw-config-rollback description: "OpenClaw 配置回滚管理 - 备份、超时保护、自动回滚" metadata: { "openclaw": { "emoji": "🔄", "requires": { "bins": ["bash"] }, "install": "自动安装（脚本已内置）" } } --- # Config Rollback Skill OpenClaw 配置回滚管理技能，提供配置修改前的自动备份、超时保护和自动回滚功能。 --- ## 🎯 功能 - **配置备份** - 修改前自动备份到 `~/.openclaw/backups/` - **超时保护** - 5 分钟倒计时，超时自动回滚 - **状态管理** - 跟踪配置修改状态 - **待验证事项** - 动态记录验证事项 - **启动自检** - Gateway 启动后自动验证配置 --- ## 📋 使用方式 ### 1. 准备修改配置 ```bash ~/.openclaw/scripts/prepare-config-change.sh "修改描述" "验证事项 1,验证事项 2" ``` **参数：** - `修改描述` - 简要描述修改内容（必需） - `验证事项` - 逗号分隔的验证事项列表（可选） **示例：** ```bash ~/.openclaw/scripts/prepare-config-change.sh "启用 obsidian 技能" "验证技能状态，验证 Gateway 启动" ``` **输出：** - 备份文件路径 - 回滚截止时间（5 分钟后） - 下一步操作提示 --- ### 2. 修改配置 编辑 `~/.openclaw/openclaw.json` --- ### 3. 重启 Gateway **必须在 5 分钟内完成：** ```bash openclaw gateway restart ``` --- ## 🔄 自动回滚机制 ### 守护进程 **脚本：** `~/.openclaw/scripts/rollback-guardian.sh` **Cron 任务：** 每分钟执行一次 ```bash */1 * * * * ~/.openclaw/scripts/rollback-guardian.sh ``` ### 工作逻辑 | 状态 | 行为 | |------|------| | 无配置修改 | 直接退出（安静模式） | | Gateway 正常运行 | 清除状态文件（任务完成） | | Gateway 未运行 + 未超时 | 继续等待 | | Gateway 未运行 + 超时 | 执行回滚 | --- ## 📁 相关文件 | 文件 | 作用 | |------|------| | `scripts/prepare-config-change.sh` | 修改准备脚本 | | `scripts/rollback-guardian.sh` | 超时回滚守护 | | `scripts/config-alias.sh` | 交互式助手 | | `backups/` | 配置备份目录 | | `docs/PENDING_VERIFICATION.md` | 待验证事项记录 | --- ## 🚨 紧急回滚 ```bash cp $(ls -t ~/.openclaw/backups/*.json | head -1) ~/.openclaw/openclaw.json openclaw gateway restart ``` --- ## 🔧 安装 ### 自动安装（推荐） ```bash openclaw skills enable openclaw-config-rollback ``` ### 手动安装 1. **复制脚本** ```bash # 脚本已在工作区 ls ~/.openclaw/workspace/skills/config-rollback/scripts/ ``` 2. **设置权限** ```bash chmod +x ~/.openclaw/workspace/skills/config-rollback/scripts/*.sh ``` 3. **设置 Cron** ```bash (crontab -l 2>/dev/null | grep -v "rollback-guardian"; echo "*/1 * * * * ~/.openclaw/workspace/skills/config-rollback/scripts/rollback-guardian.sh") | crontab - ``` 4. **验证** ```bash crontab -l | grep rollback ``` --- ## 📊 配置流程 ``` 修改配置 ↓ 执行 prepare-config-change.sh ├─ 自动备份到 backups/ ├─ 创建状态文件 .config-modified-state └─ 记录到 PENDING_VERIFICATION.md ↓ 5 分钟倒计时开始 ↓ 守护进程每分钟检查 ├─ 无状态文件 → 直接退出（安静模式） ├─ Gateway 正常运行 → 清除状态文件 ✅ ├─ Gateway 未运行 + 未超时 → 继续等待 └─ Gateway 未运行 + 超时 → 自动回滚 ⚠️ ``` --- ## 🎯 最佳实践 ### 修改前 1. 执行 `prepare-config-change.sh` 2. 记录修改原因到 `docs/CONFIG_CHANGELOG.md` ### 修改后 3. **5 分钟内**重启 Gateway 4. 查看 Discord 上的 BOOT.md 自检报告 5. 更新 `PENDING_VERIFICATION.md` 中的验证状态 --- ## ⚠️ 注意事项 1. **修改前必须执行准备脚本** - 否则没有备份和超时保护 2. **5 分钟内必须重启** - 否则会自动回滚 3. **验证事项与修改目的关联** - 不是固定的验证内容 --- ## 📚 相关文档 - `docs/CONFIG_QUICKREF.md` - 快速参考 - `CONFIG_CHANGE_RULES.md` - 详细规则 - `docs/CONFIG_MEMORY_SYSTEM.md` - 记忆系统设计 - `skills/brain2claw-content-manager/work/cases/001-config-management-flow.md` - 设计案例 --- **版本：** 1.0.2 **作者：** 小麦 🌲 **日期：** 2026-03-16


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: clawto/money-toolkit (version 1.0.0)

--- name: money-toolkit description: "AI赚钱工具箱：套利计算、DeFi收益聚合、空投监控、薅羊毛。Trigger on: 赚钱, 套利, 空投, 薅羊毛, DeFi, 收益, 理财, 打新, 可转债, 价差, arbitrage, yield, airdrop, 省钱, 返利." version: 1.0.0 license: MIT --- # Money Toolkit 💰 AI 赚钱工具箱 — 自动化套利、DeFi 收益聚合、理财计算、薅羊毛监控。 ## What it does - **套利计算器**: 跨所价差、期现套利、三角套利 - **DeFi 收益聚合**: 跨链收益率对比、流动性挖矿 APY 排行 - **空投监控**: 潜力项目追踪、交互记录管理 - **薅羊毛雷达**: 信用卡返现、平台补贴、限时活动 - **可转债打新**: 新债申购提醒、中签查询 - **复利计算**: 定投收益计算、财富自由时间预估 - **省钱技巧**: 比价搜索、优惠券聚合 ## Trigger Conditions - 用户询问赚钱、理财、套利相关话题 - 查找高收益 DeFi 项目 - 计算投资收益或复利 - 监控空投或薅羊毛机会 ## Prerequisites - `curl`, `jq`, `python3` - Internet access ## Installation ``` clawhub install clawto/money-toolkit ``` ## Scripts | Script | Purpose | |--------|---------| | `scripts/arbitrage.py` | 跨所/期现/三角套利计算 | | `scripts/defi-yield.py` | DeFi 收益率聚合与对比 | | `scripts/airdrop-hunt.py` | 空投机会追踪 | | `scripts/compound.py` | 复利计算器 | | `scripts/gas-fee.py` | Gas费比价 & 省钱策略 | ## Usage ``` # 跨所套利 > BTC在Binance和OKX有价差吗？ # DeFi 收益 > 当前最高的稳定币APY是多少？ # 空投 > 最近有什么值得参与的空投？ # 复利计算 > 每月定投1000U，年化15%，10年后多少钱？ ``` ## 🫶 Donation | Coin | Address | |------|---------| | BTC | [REDACTED_SECRET] | ## License MIT


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: davidme6/codex-delete-republish-test (version 0.0.2)

--- name: codex-delete-republish-test version: 0.0.1 description: 验证 ClawHub 删除后是否允许同 slug 重新发布的测试技能。 license: MIT author: davidme6 --- # Delete Republish Test 这个技能只用于验证 ClawHub 的一个发布行为： - 先发布一个技能 - 删除这条技能 - 再用同一个 slug 重新发布 ## 作用 - 观察删除后的 slug 是否立即可复用 - 观察旧 tag 和旧版本映射是否会被清空 - 评估是否可以用同样的方式重建真实技能 ## 预期 如果平台允许同 slug 重建，那么删除之后应该可以重新发布成功。 如果平台不允许，那么会返回 slug 冲突或重定向相关错误。


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

--- name: "openapi" version: "1.0.0" description: "Openapi reference tool. Use when working with openapi in devtools contexts." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [openapi, devtools, dev, reference, cli] category: "devtools" --- # Openapi Openapi reference tool. Use when working with openapi in devtools contexts. ## When to Use - Working with openapi and need quick reference - Looking up devtools standards or best practices for openapi - Troubleshooting openapi issues - Need a checklist or guide for openapi tasks ## Commands ### `intro` ```bash scripts/script.sh intro ``` Overview and core concepts ### `quickstart` ```bash scripts/script.sh quickstart ``` Getting started guide ### `patterns` ```bash scripts/script.sh patterns ``` Common patterns and best practices ### `debugging` ```bash scripts/script.sh debugging ``` Debugging and troubleshooting ### `performance` ```bash scripts/script.sh performance ``` Performance optimization tips ### `security` ```bash scripts/script.sh security ``` Security considerations ### `migration` ```bash scripts/script.sh migration ``` Migration and upgrade guide ### `cheatsheet` ```bash scripts/script.sh cheatsheet ``` Quick reference cheat sheet ### `help` ```bash scripts/script.sh help ``` ### `version` ```bash scripts/script.sh version ``` --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jinwangmok/word-count (version 1.0.1)

--- name: word-count version: 1.0.0 description: >- Count words, lines, and characters in a file. Outputs a single summary line. Use when the user wants to know how long a file is or count words in a document. allowed-tools: Bash(wc:*) metadata: >- {"openclaw":{"emoji":"🔢","requires":{"bins":["wc"],"env":[]},"install":[]}} --- # Word Count / 단어 수 세기 Count words, lines, and characters in any text file with a single command. 텍스트 파일의 단어, 줄, 문자 수를 한 번의 명령으로 셉니다. ## Usage / 사용법 ```bash wc <FILE_PATH> ``` **Arguments / 인수:** | # | Name | Description | 설명 | |---|------|-------------|------| | 1 | FILE_PATH | Path to the file to count | 셀 파일의 경로 | ## Example / 예시 ```bash wc /home/user/document.txt ``` **Output / 출력:** ``` 42 350 2100 /home/user/document.txt ``` Format / 형식: `LINES WORDS CHARACTERS FILENAME` (`줄 수 단어 수 문자 수 파일명`) ## Success / Failure — 성공 / 실패 - **Success / 성공**: Output line with 3 numbers and filename (exit code 0) — 숫자 3개와 파일명이 포함된 출력 (종료 코드 0) - **Failure / 실패**: Error message from `wc` (exit code non-zero) — `wc` 오류 메시지 (종료 코드 0이 아님)


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

--- name: R description: Avoid common R mistakes — vectorization traps, NA propagation, factor surprises, and indexing gotchas. metadata: {"clawdbot":{"emoji":"📊","requires":{"bins":["Rscript"]},"os":["linux","darwin","win32"]}} --- ## Vectorization - Loops are slow — use `apply()`, `lapply()`, `sapply()`, or `purrr::map()` - Vectorized functions operate on whole vectors — `sum(x)` not `for (i in x) total <- total + i` - `ifelse()` is vectorized — `if` is not, use `ifelse()` for vector conditions - Column operations faster than row — R is column-major ## Indexing Gotchas - R is 1-indexed — first element is `x[1]`, not `x[0]` - `x[0]` returns empty vector — not error, silent bug - Negative index excludes — `x[-1]` removes first element - `[[` extracts single element — `[` returns subset (list stays list) - `df[, 1]` drops to vector — use `df[, 1, drop = FALSE]` to keep data frame ## NA Handling - NA propagates — `1 + NA` is `NA`, `NA == NA` is `NA` - Use `is.na()` to check — not `x == NA` - Most functions need `na.rm = TRUE` — `mean(x)` returns NA if any NA present - `na.omit()` removes rows with any NA — may lose data unexpectedly - `complete.cases()` returns logical vector — rows without NA ## Factor Traps - Old R converted strings to factors by default — use `stringsAsFactors = FALSE` or modern R - `levels()` shows categories — but factor values are integers internally - Adding new value not in levels gives NA — use `factor(x, levels = c(old, new))` - `as.numeric(factor)` gives level indices — use `as.numeric(as.character(factor))` for values - Dropping unused levels: `droplevels()` — or `factor()` again ## Recycling - Shorter vector recycled to match longer — `c(1,2,3) + c(10,20)` gives `11, 22, 13` - No error if lengths aren't multiples — just warning, easy to miss - Single values recycle intentionally — `x + 1` adds 1 to all elements ## Data Frames vs Tibbles - Tibble never converts strings to factors — safer defaults - Tibble never drops dimensions — `df[, 1]` stays tibble - Tibble prints better — shows type, doesn't flood console - `as_tibble()` to convert — from `tibble` or `dplyr` package ## Assignment - `<-` is idiomatic R — `=` works but avoided in style guides - `<<-` assigns to parent environment — global assignment, usually a mistake - `->` right assignment exists — rarely used, confusing ## Scope - Functions look up in parent environment — can accidentally use global variable - Local variable shadows global — same name hides outer variable - `local()` creates isolated scope — variables don't leak out ## Common Mistakes - `T` and `F` can be overwritten — use `TRUE` and `FALSE` always - `1:length(x)` fails on empty x — gives `c(1, 0)`, use `seq_along(x)` - `sample(5)` vs `sample(c(5))` — different! first gives 1:5 permutation - String splitting: `strsplit()` returns list — even for single string


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