OpenClaw/clawhub-security-signals huggingface dataset:
Skill: nexscope/product-launch-strategy (version 1.0.0)

--- name: product-launch-strategy description: "Plan and execute e-commerce product launches. Pre-launch, launch day, and post-launch playbooks for Amazon, Shopify, and multi-channel sellers. Covers inventory, pricing, advertising, and review strategy." metadata: nexscope: emoji: "🚀" category: ecommerce --- # Product Launch Strategy 🚀 Plan and execute e-commerce product launches. Pre-launch, launch day, and post-launch playbooks for Amazon, Shopify, and multi-channel sellers. Covers inventory, pricing, advertising, and review strategy. **Supported platforms:** Amazon, Shopify, WooCommerce, Walmart, TikTok Shop, Etsy, eBay, BigCommerce. Built by [Nexscope](https://www.nexscope.ai/) — your AI assistant for smarter e-commerce decisions. ## Install ```bash npx skills add nexscope-ai/eCommerce-Skills --skill product-launch-strategy -g ``` ## Usage ``` I'm launching a new kitchen gadget on Amazon next month. Help me create a launch plan. Budget: $2,000 for launch. I have 500 email subscribers. ``` ## Capabilities - Pre-launch checklist (listing, inventory, pricing, imagery) - Launch timeline creation (4-8 week plan) - Launch pricing strategy (introductory pricing, coupons, deals) - Review generation plan (compliant strategies per platform) - Launch advertising playbook (PPC ramp-up schedule) - Social proof and influencer seeding strategy - Post-launch optimization workflow (days 7, 14, 30) ## How This Skill Works **Step 1:** Collect information from the user's message — product, platform, current situation, and goals. **Step 2:** Ask one follow-up with all remaining questions using multiple-choice format. Allow shorthand answers (e.g., "1b 2c 3a"). **Step 3:** Research and analyze using the frameworks and methodology below. **Step 4:** Deliver structured, actionable output with specific recommendations, not vague advice. ## Output Format - Start with a summary of findings - Include specific data points and benchmarks where available - Provide prioritized action items - Mark estimates with ⚠️ when based on incomplete data - End with concrete next steps ## Other Skills More e-commerce skills: [nexscope-ai/eCommerce-Skills](https://github.com/nexscope-ai/eCommerce-Skills) Amazon-specific skills: [nexscope-ai/Amazon-Skills](https://github.com/nexscope-ai/Amazon-Skills) Built by [Nexscope](https://www.nexscope.ai/) — your AI assistant for smarter e-commerce decisions.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: zcr3344/xiao-chuang-you-fashion (version 2.2.1)

--- name: xiao-chuang-you-fashion description: 小窗幽穿搭子技能。当用户询问穿搭、新中式、汉服、传统色、配色、汉元素等话题时激活。提供新中式穿搭建议、传统色搭配、场合配色指南。 --- # 小窗幽 · 穿搭 ## 角色定位 你是小窗幽在穿搭领域的守护者。 **领域个性：** 懂得"穿出自己"的老友。推荐穿搭时不只说"今年流行什么"，更会问"你想呈现什么状态"。 **语气特征：** - 推荐时说"如果今天你想感觉……，可以试试……" - 结合场合、季节、情绪给建议 - 提到传统色时会说背后的故事 ## 激活词 穿搭、新中式、汉服、传统色、汉元素、宋制、明制、唐风、场合穿搭、东方美学、配色、衣服、裙子、宋锦、缂丝、旗袍 ## 核心能力 ### 新中式穿搭 - 节气穿搭（清明穿浅色、夏至穿棉麻散热） - 传统款式：汉服各制（晋、唐、宋、明）介绍与日常化混搭 - 汉元素单品搭配 ### 传统色配色方案（具体案例） #### 适合日常通勤的配色方案 | 方案名 | 主色 | 辅色 | 适用场景 | 可搭配单品种 | |--------|------|------|----------|--------------| | 莲步移香 | 浅莲红（#F2D2D6） | 月白（#C8D8E8） | 春末夏初通勤，色感柔和 | 浅莲红真丝衬衫 + 月白亚麻裤 | | 夏木扶苏 | 石竹粉（#E8B4B8） | 素白（#F5F5F0） | 初夏办公室，低饱和 | 石竹粉棉麻裙 + 素白亚麻开衫 | | 青青子衿 | 靛蓝（#2B4570） | 米白（#F0E8D8） | 正式场合，文人气 | 靛蓝棉麻长衫 + 米白直筒裤 | #### 节气限定配色（节令精准） | 节令 | 传统色名 | 色值 | 适用穿搭元素 | |------|----------|------|--------------| | 立夏（5/5-7） | 朱砂#C03A2B / 槐花黄#D4A84B | 朱砂#C03A2B | 配饰点睛（耳饰/丝巾）/ 主色上衣 | | 小满（5/20-22） | 萍绿#6B9E5A / 雾白#E8E4D8 | 萍绿#6B9E5A | 轻薄裙装/裤装 | | 芒种（6/5-7） | 稻黄#D4A84B / 艾绿#98B88A | 稻黄#D4A84B | 亚麻材质，透气自然 | | 夏至（6/20-22） | 绛紫#8B4D6B / 月白#C8D8E8 | 绛紫#8B4D6B | 丝麻材质，散热优雅 | #### 场合配色指南（附具体案例） **茶会/雅集：** - 主色：素白（#F5F5F0）或浅藕色（#D8C8D0） - 点缀：黛蓝（#2B4570）小面积（茶杯/扇骨） - 效果：素雅淡然，不抢茶席风头 - **不可**：全身朱红/明黄（过于节庆，不适合日常雅集） **古镇慢游：** - 主色：亚麻原色（#D4C8A8）或浅灰蓝（#B8C8D0） - 点缀：赭石（#8B5E3C）或苔绿（#6B7B5A）棉麻布袋 - 效果：融入古镇环境，拍照好看 - **单品推荐**：亚麻长衫 + 赭石色布袋 + 草编鞋 **日常通勤（新中式混搭）：** - 主色：藏青（#2B4570）或墨色（#1A1A1A） - 辅色：月白（#C8D8E8）或浅藕 - 点缀：传统纹样窄丝巾（缠手腕或系包） - **避雷**：不要全套汉服元素（除非单位有文化日要求） ### 场合穿搭 - 踏青：轻便舒适，色系统一 - 茶会：素雅淡色，低饱和 - 古镇慢游：文艺休闲 - 日常通勤：新中式混搭 ## 回复规范 必含：场景 + 颜色建议 + 单品搭配 + 一个细节 互动钩子："你今天想呈现什么状态？"


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: teoslayer/pilot-mcp-bridge (version 1.0.0)

--- name: pilot-mcp-bridge description: > MCP server wrapping the Pilot daemon for OpenClaw/Claude Code integration. Use this skill when: 1. You need to expose Pilot Protocol operations as MCP tools 2. You want to integrate Pilot into Claude Code or OpenClaw workflows 3. You're building an AI agent that needs to communicate over Pilot Do NOT use this skill when: - You need direct pilotctl access (use pilot-protocol skill instead) - The daemon is not running - You're working in a non-MCP environment tags: - pilot-protocol - integration - mcp - bridge license: AGPL-3.0 compatibility: > Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start). metadata: author: vulture-labs version: "1.0" openclaw: requires: bins: - pilotctl homepage: https://pilotprotocol.network allowed-tools: - Bash --- # Pilot MCP Bridge Blueprint for wrapping Pilot Protocol as MCP server for Claude Code/OpenClaw integration. ## MCP Tools to Expose Identity & Status: - `pilot_daemon_status`: Run `pilotctl --json daemon status` - `pilot_info`: Run `pilotctl --json info` - `pilot_peers`: Run `pilotctl --json peers` Communication: - `pilot_connect`: Run `pilotctl --json connect <target> <port> --message "<msg>"` - `pilot_send_message`: Run `pilotctl --json send-message <target> --data "<msg>"` - `pilot_recv`: Run `pilotctl --json recv <port>` - `pilot_listen`: Run `pilotctl --json listen <port>` Discovery: - `pilot_find`: Run `pilotctl --json find <hostname>` - `pilot_lookup`: Run `pilotctl --json lookup <node_id>` Pub/Sub: - `pilot_publish`: Run `pilotctl --json publish <target> <topic> --data "<msg>"` - `pilot_subscribe`: Run `pilotctl --json subscribe <target> <topic>` Gateway: - `pilot_gateway_start`: Run `pilotctl --json gateway start` - `pilot_gateway_map`: Run `pilotctl --json gateway map <hostname> <local-ip>` ## Workflow Example ```bash # Start Pilot daemon pilotctl --json daemon start --registry 34.71.57.205:9000 --beacon 34.71.57.205:9001 # Start MCP server wrapper python mcp_pilot_server.py # MCP tools now available in Claude Code/OpenClaw ``` ## Dependencies Requires pilot-protocol skill, pilotctl binary, MCP server framework (Python mcp library), and MCP-compatible client.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 1kalin/afrexai-warranty-management (version 1.0.0)

# Warranty & Returns Management You are a warranty and returns management specialist. Help the user build and optimize their warranty program, process returns efficiently, and reduce warranty costs. ## What You Do - Design warranty policy tiers (standard, extended, premium, lifetime) - Build returns processing workflows with SLA targets - Create root cause analysis dashboards with defect categorization - Calculate warranty reserves and cost projections - Generate disposition matrices for returned goods (restock, refurbish, salvage) - Audit compliance: Magnuson-Moss (US), Consumer Rights Directive (EU), Consumer Rights Act (UK) - Build KPI dashboards: claim rate, resolution time, recovery rate, cost per return - Create returns reduction playbooks (67% of returns are preventable) ## How to Use Tell the agent about your product type, volume, and current return/warranty situation. It will generate the relevant frameworks, policies, and tracking templates. ## Example Prompts - "Build a warranty policy for our electronics product line" - "Our return rate is 12% — help me get it under 5%" - "Create a root cause analysis framework for our manufacturing defects" - "Calculate warranty reserves for 50,000 units at 4% claim rate" - "Audit our warranty terms for EU compliance" ## Industry Context Packs For deeper, industry-specific implementation guides: → https://afrexai-cto.github.io/context-packs/ ($47/industry) Packs: Ecommerce, Manufacturing, Construction, SaaS, Healthcare, Legal, Fintech, Real Estate, Recruitment, Professional Services Bundles: Pick 3 ($97) | All 10 ($197) | Everything ($247) ## More Tools - ROI Calculator: https://afrexai-cto.github.io/ai-revenue-calculator/ - Agent Setup Wizard: https://afrexai-cto.github.io/agent-setup/


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: btizzy/owl-content-creator (version 1.0.0)

--- name: content-creator description: Create high-quality content for blogs, social media, email marketing, and sales copy. Generates engaging, SEO-optimized content in any voice or style. version: 1.0.0 author: OWL tags: [content, copywriting, SEO, social-media, email, marketing] --- # Content Creator Skill ## Purpose Generate high-quality content for any platform or format, including blog posts, social media, email campaigns, landing pages, and sales copy. ## When to Use - Writing blog posts or articles - Creating social media content - Drafting email campaigns - Writing landing page copy - Generating sales copy - Repurposing existing content ## How It Works ### Step 1: Define the Content Brief Specify: - **Topic**: What to write about - **Format**: Blog post, social post, email, landing page, etc. - **Tone**: Professional, casual, authoritative, humorous, etc. - **Target audience**: Who will read this - **Goal**: Inform, persuade, entertain, convert - **Length**: Short-form (<500 words), medium (500-1500), long-form (1500+) - **Keywords**: SEO keywords to include (if applicable) ### Step 2: Generate the Content Create content that: 1. Opens with a hook (question, statistic, story, bold claim) 2. Provides value (information, insights, solutions) 3. Uses clear formatting (headers, bullets, short paragraphs) 4. Includes a call-to-action (if applicable) 5. Matches the specified tone and style ### Step 3: Optimize - Check for SEO keywords (if applicable) - Ensure readability (short sentences, simple words) - Add formatting (headers, bullets, bold) - Review for clarity and impact ## Output Formats ### Blog Post ```markdown # [Title] [Hook paragraph] ## [Section 1] [Content] ## [Section 2] [Content] ## Conclusion [Summary + CTA] ``` ### Social Media Post ``` [Hook] [Value] [CTA] [Hashtags] ``` ### Email ``` Subject: [Subject line] [Opening] [Body] [CTA] [Signature] ``` ## Tips - Always lead with value - Use specific examples and data - Write like you're talking to one person - End with a clear next step - Test different hooks and CTAs


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: n1e/github-hosts-cn-n1e (version 1.0.1)

--- name: github-hosts-cn description: GitHub Hosts 更新工具（中国用户专用）。安全地更新系统hosts文件以访问GitHub，保留原有非GitHub条目，仅替换GitHub相关地址。支持备份恢复、风险提示。当用户需要解决GitHub访问问题时使用此技能。 risk_level: high risk_description: | ⚠️ 此工具需要修改系统hosts文件(/etc/hosts)，存在以下风险： 1. 需要sudo权限执行 2. 可能影响网络访问 3. 错误的hosts配置可能导致网络问题 4. 需要用户确认后才能执行 safety_features: - 自动备份原有hosts文件 - 保留所有非GitHub相关条目 - 仅替换GitHub相关域名 - 支持一键恢复备份 - 详细的操作日志 --- # GitHub Hosts CN - 中国用户专用 GitHub Hosts 更新工具 安全、智能地更新系统hosts文件，帮助中国用户正常访问GitHub。 ## 🌟 特性 - **🛡️ 安全优先**：自动备份、保留原有配置、仅替换GitHub条目 - **🌍 多源获取**：从多个镜像源获取最新GitHub hosts（HelloGitHub、GitLab、Gitee等） - **⚡ 自动选择**：并行测试所有源，使用最快的可用源 - **💾 智能备份**：时间戳备份，支持一键恢复 - **🔍 精确替换**：只替换GitHub相关域名，保留其他所有hosts配置 - **📋 风险提示**：执行前显示详细风险说明，需用户确认 ## 📦 安装 ```bash cd /Users/claw/Documents/trae_projects/skills/github-hosts-cn npm install ``` ## 🚀 使用方法 ```bash # 更新GitHub hosts node update.js # 查看帮助 node update.js --help # 恢复最近的备份 node update.js --restore # 查看当前状态 node update.js --status # 仅获取不更新（预览模式） node update.js --preview ``` ## 📊 数据源 | 源 | URL | 类型 | 优先级 | |----|-----|------|--------| | HelloGitHub | raw.hellogithub.com | 独立站点 | 1 | | GitLab Mirror | gitlab.com/ineo6 | GitLab | 2 | | Gitee Mirror | gitee.com | 国内镜像 | 3 | | JSDelivr CDN | cdn.jsdelivr.net | CDN | 4 | ## 🔧 工作流程 ``` 1. 显示风险提示 → 用户确认 2. 读取当前 /etc/hosts 3. 创建时间戳备份 4. 从多源获取最新GitHub hosts 5. 合并：保留非GitHub条目 + 新GitHub条目 6. 写入新的hosts文件 7. 刷新DNS缓存 8. 显示更新结果 ``` ## 🛡️ 安全机制 ### 备份策略 - 每次修改前自动备份 - 备份文件命名：`hosts.backup.YYYY-MM-DDTHH-mm-ss` - 备份位置：`~/.openclaw/backups/github-hosts/` - 保留最近10个备份文件 ### 合并策略 - 识别所有GitHub相关域名（github.com, github.global.ssl.fastly.net等） - 保留hosts文件中的所有非GitHub条目 - 仅替换GitHub相关IP地址 ### 恢复机制 - `--restore` 恢复最近备份 - `--restore <backup-file>` 恢复指定备份 ## ⚠️ 风险说明 **修改hosts文件存在以下风险：** 1. **权限风险**：需要sudo权限，请确保在可信环境执行 2. **网络风险**：错误的hosts可能导致无法访问某些网站 3. **IP失效风险**：GitHub IP可能随时变化，需要定期更新 4. **备份风险**：请确保备份目录可写 **建议：** - 在执行前理解hosts文件的作用 - 定期检查备份文件 - 如遇问题立即使用 `--restore` 恢复 ## 📋 系统要求 - Node.js 16+ - macOS / Linux - sudo权限（用于修改/etc/hosts） - 网络连接 ## 📜 License MIT


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: rajtejani61/tavily-web-search (version 1.0.0)

--- name: tavily-search description: "AI-optimized search and content extraction using Tavily API. Includes deep search, news filtering, and raw content extraction for LLM processing." homepage: https://tavily.com metadata: {"clawdbot":{"emoji":"🔍","requires":{"bins":["node"],"env":["TAVILY_API_KEY"]}}} --- # Tavily Search Tavily is a search engine built specifically for AI agents (LLMs). This skill provides optimized search results and content extraction. ## Prerequisites 1. **Node.js** installed. 2. **Tavily API Key**: Get one at [tavily.com](https://tavily.com). 3. **Environment Variable**: Set `TAVILY_API_KEY` in your environment. ## Usage ### Search Perform an AI-optimized search. ```bash node scripts/search.mjs "What are the latest developments in agentic AI?" ``` **Options:** - `-n <number>`: Number of results (default: 5, max: 20). - `--deep`: Use advanced search depth (more tokens, better results). - `--topic <general|news>`: Filter by topic (default: general). - `--days <number>`: For news topic, limit results to past N days. ## Extract content from URL ```bash node {baseDir}/scripts/extract.mjs "https://example.com/article" ``` Notes: - Needs `TAVILY_API_KEY` from https://tavily.com - Tavily is optimized for AI - returns clean, relevant snippets - Use `--deep` for complex research questions - Use `--topic news` for current events ## Troubleshooting - **Missing API Key**: Ensure `TAVILY_API_KEY` is exported or set in your session. - **Network Errors**: Check your internet connection and API quota at Tavily.


Security scan verdicts — ClawScan: clean | static analysis:  | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: ivangdavila/sync (version 1.0.0)

--- name: Sync description: Synchronize files and directories between local, remote, and cloud storage reliably. metadata: {"clawdbot":{"emoji":"🔄","requires":{"anyBins":["rsync","rclone"]},"os":["linux","darwin","win32"]}} --- # File Synchronization Rules ## rsync Fundamentals - Trailing slash matters: `rsync src/` copies contents, `rsync src` copies the folder itself — this is the #1 cause of wrong directory structures - Always use `-avz` baseline: archive mode preserves permissions/timestamps, verbose shows progress, compress speeds transfers - Add `--delete` only when you want destination to mirror source exactly — without it, deleted source files remain on destination - Use `--dry-run` before any destructive sync — shows what would change without modifying anything ## Exclusions - Create an exclude file instead of multiple `--exclude` flags: `rsync -avz --exclude-from=.syncignore src/ dest/` - Standard excludes for code projects: `.git/`, `node_modules/`, `__pycache__/`, `.venv/`, `*.pyc`, `.DS_Store`, `Thumbs.db` - Exclude patterns are relative to source root — `/logs/` excludes only top-level logs, `logs/` excludes logs/ anywhere ## Cloud Storage (rclone) - `rclone sync` deletes destination files not in source; `rclone copy` only adds — use copy when unsure - Configure remotes interactively: `rclone config` — never hardcode cloud credentials in scripts - Test with `--dry-run` first, then `--progress` for visual feedback during actual sync - For S3-compatible storage, set `--s3-chunk-size 64M` for large files to avoid timeouts ## Verification - After critical syncs, verify with checksums: `rsync -avzc` uses checksums instead of size/time (slower but certain) - For rclone, use `rclone check source: dest:` to compare without transferring - Log sync operations to file for audit: `rsync -avz src/ dest/ | tee sync.log` ## Bidirectional Sync - rsync is one-way only — for true bidirectional sync, use unison: `unison dir1 dir2` - Unison detects conflicts when both sides change — resolve manually or set prefer rules - Cloud services like Dropbox/Syncthing handle bidirectional automatically — don't reinvent with rsync ## Remote Sync - For SSH remotes, use key-based auth: `rsync -avz -e "ssh -i ~/.ssh/key" src/ user@host:dest/` - Specify non-standard SSH port: `-e "ssh -p 2222"` - Use `--partial --progress` for large files over unreliable connections — allows resume on failure ## Common Pitfalls - Syncing to mounted drives that unmount silently creates a local folder with the mount name — verify mount before sync - Running sync without `--delete` repeatedly causes destination to accumulate deleted files forever - Time-based sync fails across machines with clock skew — use `--checksum` for accuracy or sync NTP first


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: luckylion68/binance-earning-assistant (version 1.0.10)

--- name: binance-earning-assistant description: 币安撸毛助手 - 展示币安最新撸毛活动信息，包括理财产品、活动奖励、空投预告等。Use when user asks for "今日撸毛", "币安活动", "赚钱活动", "撸毛信息", "Binance earning", "airdrop info", or any query about Binance promotional events, rewards, or earning opportunities. metadata: version: 2.0.1 author: 0x_WanG license: MIT openclaw: emoji: "💰" always: false dependencies: - requests environment: - HTTP_PROXY (可选) - HTTP 代理地址，例如 http://127.0.0.1:26001 - OPENCLAW_WORKSPACE (可选) - OpenClaw 工作区路径，默认 ~/.openclaw/workspace triggers: - "今日撸毛" - "今日撸毛信息" - "币安活动" - "币安撸毛" - "赚钱活动" - "撸毛信息" - "Binance earning" - "airdrop info" - "binance rewards" - "币安理财" - "币安空投" persistence: - 创建 ~/.openclaw/workspace/.binance_earning 目录 - 存储导出文件 (exports/*.md) --- # 币安撸毛助手 展示币安最新撸毛活动信息，包括理财产品、活动奖励、空投预告等。 ## 功能特性 - ✅ **实时获取** - 从币安 API 实时获取最新活动 - ✅ **智能过滤** - 自动过滤非华语区活动 - ✅ **分类展示** - 理财、活动奖励、广场任务 - ✅ **详细信息** - 代币、奖池、截止日期、发布时间 - ✅ **Alpha 空投** - 实时获取 alpha123.uk 空投数据 ## 使用方法 ### 查看活动信息 ```bash python3 summary_table.py ``` ## 输出格式 活动列表包含以下信息： - **序号** - 活动编号 - **代币** - 活动相关代币 - **奖池/APR** - 奖励金额或年化收益率 - **活动名称** - 活动中文名称 - **发布** - 发布日期 - **截止** - 截止日期 ## 活动分类 | 分类 | 说明 | |------|------| | 💰 理财产品 | 币安理财产品，包括活期、定期 | | 🎁 活动奖励 | 交易竞赛、奖励活动 | | 📢 其他活动 | 知识问答等其他活动 | | 🚀 ALPHA 空投预告 | Alpha 板块空投预告 | ## 依赖说明 **必需依赖：** - `requests` - 用于 HTTP 请求 ## 持久化说明 **技能会创建以下目录和文件：** - `$OPENCLAW_WORKSPACE/.binance_earning/` - 数据目录（默认 `~/.openclaw/workspace/.binance_earning/`） - `exports/` - 导出的 Markdown 文件 **环境变量说明：** - `OPENCLAW_WORKSPACE` - 指定工作区路径（可选，默认 `~/.openclaw/workspace`） - `HTTP_PROXY` - 指定 HTTP 代理（可选，某些网络环境需要） ## 示例输出 ``` ════════════════════════════════════════ 🚀 币安撸毛助手 - 当前可参与活动总览 ════════════════════════════════════════ 更新时间：2026-03-14 20:42 活动总数：18 个 ════════════════════════════════════════ 💰 理财产品（8 个） ════════════════════════════════════════ 【1】Enjoy Up to 8% APR with RLUSD Flexib... 🔗 链接：https://www.binance.com/zh-CN/support/announcement/65317d61d1c445f99f73a04c05233dd2 💰 奖池：8% 📅 截止时间：2026-03-31 🎯 门槛：无特殊要求 📝 参与方式：1.打开理财 2.选择产品 3.申购确认 ⚠️ 风险：理财非存款，产品有风险 ``` ## 注意事项 1. 活动信息可能随时变更，请以官方页面为准 2. 空投有风险，参与需谨慎 3. 理财非存款，产品有风险 ## 更新日志 ### v2.0.1 (2026-03-24) - Clawhub 安全审查修复 - ✅ 移除：未声明的 LLM fallback（bailian 客户端调用） - ✅ 修复：硬编码用户路径 `/Users/pigbaby/...` → 使用环境变量 `OPENCLAW_WORKSPACE` - ✅ 修复：硬编码代理设置 → 改为从环境变量 `HTTP_PROXY` 读取（可选） - ✅ 新增：SKILL.md 中声明环境变量（HTTP_PROXY, OPENCLAW_WORKSPACE） - ✅ 优化：所有脚本统一使用环境变量配置，兼容不同运行环境 ### v1.0.7 (2026-03-16) - ✅ 新增：实时 API 获取活动列表（币安官方 API） - ✅ 新增：活动名称中文化映射 - ✅ 新增：表格形式首次回复（简洁展示） - ✅ 新增：详情查询功能（回复序号查看） - ✅ 新增：自动计算剩余天数 - ✅ 新增：紧急提醒（今天/明天截止高亮） - ✅ 新增：触发词自动响应（"今日撸毛"等） - ✅ 优化：过期活动自动过滤 - ✅ 优化：按剩余天数排序 - ✅ 修复：截止日期核实问题 ### v1.0.6 (2026-03-15) - ✅ 新增：触发词支持 - ✅ 新增：OpenClaw 自动响应配置 ### v1.0.5 (2026-03-14) - ✅ 修复：文档与实际功能保持一致 - ✅ 修复：删除未实现的 API 获取描述 - ✅ 简化：只保留实际实现的功能 ### v1.0.4 (2026-03-14) - ✅ 删除：Telegram/钉钉通知功能描述 - ✅ 删除：OCR 功能描述 ### v1.0.3 (2026-03-14) - ✅ 添加：环境变量声明 - ✅ 添加：依赖声明 - ✅ 添加：持久化说明 ### v1.0.2 (2026-03-14) - ✅ 初始版本发布 - ✅ 支持分类展示 - ✅ 支持详细信息展示 - ✅ 支持导出 Markdown


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: naamah75/technitium-dns (version 0.1.0)

--- name: technitium-dns description: Monitor and inspect Technitium DNS Server via its HTTP API. Use for read-only health checks, DNS stats, zones, DHCP leases, token/session validation, and proactive alerts about DNS/DHCP issues. license: MIT homepage: https://github.com/TechnitiumSoftware/DnsServer metadata: openclaw: requires: env: - TECHNITIUM_URL - TECHNITIUM_TOKEN bins: - python3 --- # Technitium DNS Use this skill to perform read-only checks against a Technitium DNS Server instance. ## Configuration Set these environment variables before running scripts: ```bash export TECHNITIUM_URL="http://dns-server.example:5380" export TECHNITIUM_TOKEN="..." ``` Technitium v15+ accepts API/session tokens with: ```http Authorization: Bearer <token> ``` Prefer a dedicated limited/read-only user and a non-expiring API token for monitoring. ## Health Check Run the bundled helper: ```bash python3 scripts/technitium_health_check.py ``` Or from another working directory: ```bash TECHNITIUM_URL="http://dns-server.example:5380" \ TECHNITIUM_TOKEN="..." \ python3 /path/to/technitium-dns/scripts/technitium_health_check.py ``` The script prints JSON: ```json { "ok": true, "checked": [], "failures": [] } ``` Exit codes: - `0`: no critical failures - `1`: one or more monitored checks detected a critical condition - `2`: configuration or core API/session check failed ## What It Checks Read-only endpoints: - `/api/user/session/get` — token/session validity and server info - `/api/settings/get` — version, uptime timestamp, DNS settings availability - `/api/dashboard/stats/get?type=LastHour&utc=true` — DNS stats - `/api/zones/list` — disabled, expired, or sync-failed zones - `/api/dhcp/leases/list` — DHCP lease visibility, if permitted/used Alerts/failures are intended for: - API/server unreachable - invalid/expired token - zone `disabled`, `isExpired`, or `syncFailed` - abnormal SERVFAIL/refused/dropped error rate DHCP permission failure is reported as a warning in `checked` because many deployments do not use Technitium DHCP or restrict DHCP permissions. ## Proactive Use For heartbeat/proactive monitoring: 1. Run the health check only when due; avoid checking every wake. 2. If JSON `ok` is true, stay silent. 3. If `ok` is false, summarize only actionable failures. 4. Do not modify settings, zones, DHCP, cache, or logs without explicit user confirmation. ## API Docs Technitium DNS Server API docs: https://github.com/TechnitiumSoftware/DnsServer/blob/master/APIDOCS.md


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