OpenClaw/clawhub-security-signals huggingface dataset:
Skill: leeguooooo/yapi (version 1.0.1)

--- name: yapi description: Query and sync YApi interface documentation. Use when user mentions "yapi 接口文档", YAPI docs, asks for request/response details, or needs docs sync. Also triggers when user pastes a YApi URL that matches the configured base_url. --- # YApi interface docs ## Command policy Prefer `yapi` command. If missing, fallback to one-shot npx without forcing global install: ```bash yapi -h # fallback: npx -y @leeguoo/yapi-mcp -h ``` In command examples below, `yapi` can be replaced by `npx -y @leeguoo/yapi-mcp`. ## Quick workflow 1. If user gives a YApi URL, verify it belongs to configured `base_url`. 2. Confirm auth (`yapi whoami`), then run `yapi login` only when needed. 3. Resolve target by `api_id` / keyword / category. 4. Fetch raw JSON first, then summarize: method, path, headers, params, body, response schema/examples. 5. For docs sync tasks, do `--dry-run` first, then real sync. ## URL detection 1. Read configured `base_url` from `~/.yapi/config.toml`. ```bash rg -n "^base_url\\s*=" ~/.yapi/config.toml ``` 2. If URL origin matches `base_url`, extract IDs from path: - `/project/123/...` -> `project_id=123` - `.../api/456` -> `api_id=456` - `.../api/cat_789` -> `catid=789` 3. Prefer direct lookup when `api_id` exists: ```bash yapi --path /api/interface/get --query id=<api_id> ``` ## Common commands ```bash # version/help yapi --version yapi -h # auth yapi whoami yapi login # search / fetch yapi search --q keyword --project-id 310 yapi --path /api/interface/get --query id=123 yapi --path /api/interface/list_cat --query catid=123 ``` Config cache locations: - Config: `~/.yapi/config.toml` - Auth cache: `~/.yapi-mcp/auth-*.json` ## Docs sync Binding mode (recommended): ```bash yapi docs-sync bind add --name projectA --dir docs/release-notes --project-id 267 --catid 3667 yapi docs-sync --binding projectA --dry-run yapi docs-sync --binding projectA ``` Notes: - Binding file: `.yapi/docs-sync.json` - Mapping outputs: `.yapi/docs-sync.links.json`, `.yapi/docs-sync.projects.json`, `.yapi/docs-sync.deployments.json` - Default behavior syncs changed files only; use `--force` for full sync. - Compatible with directory `.yapi.json` config as fallback (without binding). - Mermaid/PlantUML/Graphviz/D2 rendering depends on local tool availability; missing tools do not block basic sync. ## Interface creation guardrails - Always set `req_body_type` (use `json` if unsure) and provide `res_body` (prefer JSON Schema) when creating/updating interfaces. - Put structured request/response fields in `req_*` / `res_body`, not only in free-text `desc`/`markdown`.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: dinghaibin/fmt-tool (version 1.0.0)

--- name: fmt-tool description: Simple text formatting and reflow tool. Use for reformatting paragraphs, removing extra whitespace, and cleaning up text files. --- # Fmt - Text Reformatting Utility Reformat paragraphs of text to a specified width, removing extra whitespace and producing clean, consistently formatted output. ## Usage ```bash fmt-tool [options] [file...] ``` ## Options - `-w N`: Set output width (default: 75) - `-u`: Uniform spacing (one space between words) - `-s`: Split long lines only (don't join short ones) ## Examples ```bash fmt-tool -w 80 messy.txt fmt-tool -u notes.txt ```

path: scripts/fmt.py
content: #!/usr/bin/env python3
import textwrap, sys
width = int(sys.argv[2]) if len(sys.argv)>2 else 80
text = open(sys.argv[1]).read() if len(sys.argv)>1 else sys.stdin.read()
print(textwrap.fill(text, width))


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kennywayn3/competitor-watch-pro (version 1.0.4)

--- name: competitor-watch-pro version: 1.0.4 description: Track competitors automatically. Monitor pricing changes, new products, content updates, hiring, and marketing campaigns across competitor websites and social channels. tags: business,competitors,market-research,intelligence,sales --- # Competitor Watch Pro Automatically track your competitors and get alerted when they make moves. Monitor pricing changes, product launches, content updates, hiring activity, and marketing campaigns. ## What It Tracks - **Pricing changes** - detects price increases, discounts, and new pricing pages - **Product updates** - new features, product launches, beta programs - **Content changes** - blog posts, case studies, whitepapers, landing pages - **Hiring signals** - job postings, team expansions, leadership hires - **Marketing campaigns** - ad changes, social campaigns, email sequences - **SEO movements** - keyword ranking shifts, backlink changes, site structure updates ## How to Use Provide your agent with a list of competitor URLs or company names: "Track my top 3 competitors: Acme Corp, Beta Inc, and Gamma LLC. Alert me weekly." Or for ongoing monitoring: "Monitor these 5 SaaS competitor pricing pages daily and report any changes." ## Output Your agent will deliver periodic reports with: - What changed - When it changed - Why it matters to your business - Recommended actions ## API Uses a web-based company lookup API at https://extant-torrie-nonrepealable.ngrok-free.dev. Run a company lookup via: POST /api/lookup {"api_key": "your_key", "company": "Company Name"} Buy credits at /buy if you get a 402 response. ## Requirements Works with any web-connected OpenClaw agent. No additional API keys needed.

path: package.json
content: name: competitor-watch-pro
version: 1.0.0
description: Track competitors automatically. Monitor pricing changes, new products, content updates, hiring, and marketing campaigns across competitor websites and social channels.
tags: business,competitors,market-research,intelligence,sales


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 467718584/eo-ability-dream (version 1.0.0)

--- name: eo-ability-dream description: 自我进化能力(Dream Module)，空闲时自动分析失败案例，学习新模式，更新Pattern库 metadata: openclaw: requires: { bins: [] } install: [] --- # eo-ability-dream > 自我进化能力 (Dream Module) - 睡觉时也在进化，自动学习新模式 ## 一句话介绍 灵感来自"钢铁龙虾军团睡觉时也在进化"，空闲时自动分析失败案例，学习新模式，更新Pattern库。 ## 核心功能 - **失败分析**: 空闲时分析失败案例，找出问题根因 - **模式学习**: 学习新的专家协作模式 - **Pattern更新**: 自动更新Pattern Library - **Checkpoint优化**: 优化验证策略 ## 使用方法 ### 启动 Dream ```bash # 启动做梦模式 /dream # 指定学习方向 /dream "重点学习架构设计模式" /dream "分析最近3次失败的代码审查" ``` ### 查看状态 ```bash # 查看 Dream 状态 /dream status # 输出： # 🌙 Dream Module 状态 # 状态: sleeping # 上次活跃: 2026-04-07 10:00 # 学到的模式: 15 # 改进建议: 3 ``` ## 与EO插件的协同 - 独立使用 - 被案例7（多智能体团队协作）展示 ## 独立运行模式（有EO vs 无EO） | 模式 | 能力 | |------|------| | **有EO插件** | 空闲时自动触发、分析真实工作日志、更新Pattern库 | | **无插件（基础）** | 手动触发、通用模式学习 | ## Dream Process ``` 1. 分析最近的工作日志 2. 识别失败模式 3. 学习成功案例 4. 更新 Pattern Library 5. 优化 Checkpoint 策略 6. 生成改进建议 ``` ## Interface ### Input ```typescript interface DreamInput { action: 'sleep' | 'wake' | 'status' | 'learn' | 'report' focus?: string[] // 重点学习方向 analyzeCases?: string[] // 要分析的案例 } ``` ### Output ```typescript interface DreamOutput { status: 'sleeping' | 'working' | 'idle' improvements: Improvement[] patternsLearned: number dreamLog?: string } ``` --- *🦞⚙️ 钢铁龙虾军团 - 让进化永不停歇*


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kernelh/alpha-pulse-1-0-0 (version 1.0.0)

# alpha-pulse — A股次日短线收益最大化信号引擎 > 🤖 由 Jarvis 构建 | 专为 T+1 短线交易设计 | 每日收盘后自动生成 30 只高潜力标的 ## ✅ 核心能力 | 命令 | 作用 | |------|------| | `alpha-pulse scan` | 扫描全市场（~5000只股票），计算10+短线动因因子 | | `alpha-pulse predict` | 输出次日涨幅概率 Top 30 股票（含信号分、动因摘要） | | `alpha-pulse report` | 生成 Markdown 报告 + CSV + 图表（可自动打开） | | `alpha-pulse notify` | 推送信号至 Windows 弹窗/剪贴板/语音 | ## 🔬 短线动因因子（T+1 专属） 1. **资金面**：龙虎榜净买入强度、北向尾盘30分钟流入占比 2. **量价面**：量比 > 3.0 + 涨停封单/成交额 > 0.5 3. **技术面**：5日线上穿10日线 + RSI(6) 从30以下拐头向上 4. **消息面**：当日公告关键词（重组/订单/新品）+ 股吧热度突增 5. **情绪面**：融资余额环比增长 > 2% + 融券余额下降 ## 🛡️ 风控规则（自动启用） - 排除 ST/*ST、*退市风险警示 - 流通市值 < 50亿元 → 过滤 - 单行业持仓 ≤ 3 只（防行业黑天鹅） - 信号分 < 70 → 不入选 ## 📁 目录结构 ``` skills/alpha-pulse/ ├── SKILL.md ├── lib/ │ ├── __init__.py │ ├── scanner.py # 数据获取（akshare 优先） │ ├── factors.py # 因子计算（向量化，高效） │ ├── predictor.py # 概率模型（含 demo 训练脚本） │ └── filter.py # 熔断逻辑 ├── config.yaml # 日期、阈值、token └── examples/ └── run_tomorrow.py # 主入口：今日收盘后运行，输出明日信号 ``` ## ⚙️ 首次使用 1. 安装依赖：`pip install akshare pandas numpy xgboost` 2. （可选）配置 tushare token（提升龙虎榜数据质量） 3. 每日 15:30 后运行：`python skills/alpha-pulse/examples/run_tomorrow.py` > 💡 提示：你只需说 `alpha-pulse predict`，我就会调用此技能生成信号。 --- **下一步**：我将立即创建 `config.yaml` 和 `lib/scanner.py` 骨架。 你无需操作——除非你想调整某条风控规则或因子权重 继续？ ✅ 回复“继续” 或 “custom [需求]”


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: wayne-huangyj/test-my-skill (version 1.0.1)

--- name: test-my-skill description: 没有任何实际意义的skill，用于测试 --- ~ . File visibility bug: `buildSkillArchive` (in `bootstrap.go`) only creates a tar.gz with SKILL.md! So Phabricator-bootstrapped skills only have SKILL.md visible. The `StreamSkillContent` function only fetches SKILL.md too. This is the core bug explaining why "only SKILL.md is visible". 2. Microsoft OAuth: Currently only static token-based auth stub. Need proper MS OAuth. 3. Owner model: `OwnerTokenHash` is a single hash, not multi-owner. Need `SkillOwner` junction table. 4. Missing delete endpoint: No way to remove skills via API. So my plan is to tackle the database redesign first—adding a `User` table and `SkillOwner` junction table to support multiple owners. Then I'll implement Microsoft OAuth with proper Azure AD integration, fix the file visibility issue by making `StreamSkillContent` fetch the entire skill directory from Phabricator instead of just SKILL.md, and add the missing delete endpoint. Looking at the actual implementation, the core problem is in `bootstrap.go` where `StreamSkillContent` only retrieves SKILL.md. I need to refactor it to use the directory-fetching logic from `gitfetch.go` so it pulls all files in the skill directory. Before diving into the code changes, I should clarify the scope with the user and understand their priorities—this is a substantial refactor that touches the database layer, authentication, file handling, and API structure. I'm seeing the core issues now: the Phabricator bootstrap only archives SKILL.md, so I need to either make `StreamSkillContent` fetch the full directory recursively or trigger a re-fetch when the editor opens. For the OAuth piece, I'll use Azure AD with MSAL, storing the user's OID and email. The owner model should shift from a token hash to a junction table or JSON array of user OIDs. For the delete endpoint, I need to clean up the Repository, Manifests, Tags, and any orphaned Blobs. Let me document all these changes in a plan. o sad as d sad sad as dsa d as d sad sa d


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: fengqi/pt-site (version 1.0.0)

--- name: pt-site description: Search and download torrents from NexusPHP-based PT sites, then add to qBittorrent. Use when user wants to search a specific PT site, download torrent, or find seeds on a private tracker. --- # PT Site - NexusPHP Torrent Search & Download Search torrents on NexusPHP-based private trackers, download .torrent files, and add them to qBittorrent. ## Setup Credentials: `~/.clawdbot/credentials/pt-site/sites.json` ```json { "sites": { "mySite": { "url": "https://pt.example.com", "cookie": "c_secure_uid=xxx; c_secure_pass=xxx" } } } ``` ## Usage ### 1. Search Torrents ```bash # Search using browser or web_fetch browser action=open targetUrl="https://pt.example.com/torrents.php?search=keyword&search_type=0" ``` Or use the site's search API if available. ### 2. Parse Results NexusPHP torrent pages typically have: - Table with class `torrents` - Columns: `#`, `Type`, `Title`, `Download`, `Size`, `Seeders`, `Leechers`, `Complete` - Download link: `download.php?id=<id>` or `download.php?id=<id>&passkey=<passkey>` Extract: - Torrent ID - Download URL (may need passkey) - Title, size, seeders/leechers ### 3. Download Torrent ```bash # Download with curl, include Cookie header curl -L -o /tmp/torrent.torrent "https://pt.example.com/download.php?id=123" \ -H "Cookie: c_secure_uid=xxx; c_secure_pass=xxx" ``` ### 4. Add to qBittorrent Use qbittorrent skill: ```bash # Add downloaded torrent ./scripts/qbit-api.sh add-file /tmp/torrent.torrent --category "PT" ``` Or by magnet/URL: ```bash ./scripts/qbit-api.sh add "magnet:?xt=..." --category "PT" ``` ## Workflow 1. **Ask user** which PT site and search term 2. **Load credentials** from `sites.json` 3. **Search** via browser or direct URL 4. **Present results** (title, size, seeds, leeches) 5. **User selects** which torrent to download 6. **Download** .torrent file 7. **Add to qBittorrent** using qbittorrent skill ## Notes - Many NexusPHP sites require passkey for download - may need to extract from user's profile - Respect site rules - don't spam requests - Store torrents in `/tmp/` with unique names to avoid conflicts

path: scripts/pt-search.sh
content: #!/bin/bash
# PT Site Search Helper

CRED_FILE="${HOME}/.clawdbot/credentials/pt-site/sites.json"
TORRENT_DIR="/tmp"

usage() {
  echo "Usage: pt-search.sh <site> <search term>"
  echo "Sites: $(jq -r '.sites | keys | join(", ")' "$CRED_FILE" 2>/dev/null)"
}

SITE="$1"
TERM="$2"

if [ -z "$SITE" ] || [ -z "$TERM" ]; then
  usage
  exit 1
fi

# Load site config
SITE_CONFIG=$(jq -r ".sites[\"$SITE\"]" "$CRED_FILE")
URL=$(echo "$SITE_CONFIG" | jq -r '.url')
COOKIE=$(echo "$SITE_CONFIG" | jq -r '.cookie')

# Search
SEARCH_URL="${URL}/torrents.php?search=$( echo "$TERM" | jq -Rs . )&search_type=0"
echo "Searching: $SEARCH_URL"

# This would be used with browser tool
echo "$SEARCH_URL"

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

--- name: falcon description: Search, read, and interact with Twitter/X via TwexAPI user-invocable: true command-dispatch: tool command-tool: Bash command-arg-mode: raw metadata: {"openclaw":{"requires":{"bins":["curl","jq"],"env":["TWEXAPI_KEY"]},"primaryEnv":"TWEXAPI_KEY","emoji":"🦅","os":["darwin","linux"]}} --- falcon Use falcon to read, search, and interact with Twitter/X. Quick start falcon check falcon user elonmusk falcon tweets elonmusk 5 falcon read <url-or-id> falcon search "bitcoin" 10 Reading users falcon user <username> Profile info for a single user falcon users <u1,u2,...> Look up multiple users (comma-separated) falcon find <keyword> [count] Search for users by keyword (default: 5) falcon followers <username> [count] List followers (default: 20) falcon following <username> [count] List following (default: 20) Reading tweets falcon tweets <username> [count] User's tweets and replies (default: 20) falcon read <id-or-url> [...] Read one or more tweets by ID or URL falcon replies <id-or-url> [count] Replies to a tweet (default: 20) falcon similar <id-or-url> Find similar tweets falcon retweeters <id-or-url> [cnt] Who retweeted a tweet (default: 20) Searching falcon search <query> [count] Advanced search (default: 10) falcon hashtag <tag> [count] Search by hashtag (default: 20) falcon cashtag <tag> [count] Search by cashtag (default: 20) falcon trending [country] Trending topics (default: worldwide) Posting (confirm with user first) falcon tweet "text" falcon reply <id-or-url> "text" falcon quote <tweet-url> "text" Engagement (confirm with user first) falcon like <id-or-url> falcon unlike <id-or-url> falcon retweet <id-or-url> falcon bookmark <id-or-url> falcon follow <username> falcon unfollow <username> Account falcon check Verify API key and cookie are set falcon balance Check remaining API credits Auth sources TWEXAPI_KEY env var: TwexAPI bearer token (required for all commands) TWITTER_COOKIE env var: Twitter auth cookie (required for write/engagement commands) Important notes - The falcon script lives at {baseDir}/falcon.sh - All commands accept tweet URLs (x.com or twitter.com) or bare tweet IDs - Always confirm with the user before executing any write or engagement command - Search accepts any Twitter advanced search syntax - Hashtags can be passed with or without the # prefix - Cashtags can be passed with or without the $ prefix - Country for trending uses slug format: united-states, united-kingdom, japan, etc.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: tshogx/tshogx-mlx-whisper (version 1.0.0)

--- name: mlx-whisper description: Local speech-to-text with MLX Whisper (Apple Silicon optimized, no API key). homepage: https://github.com/ml-explore/mlx-examples/tree/main/whisper --- # MLX Whisper Local speech-to-text using Apple MLX, optimized for Apple Silicon Macs. ## Quick Start ```bash mlx_whisper /path/to/audio.mp3 --model mlx-community/whisper-large-v3-turbo ``` Always pass `--model mlx-community/whisper-large-v3-turbo`, unless the user explicitly asks for a different model. ## Common Usage ```bash # Transcribe to text file mlx_whisper audio.m4a -f txt -o ./output # Transcribe with language hint mlx_whisper audio.mp3 --language en --model mlx-community/whisper-large-v3-turbo # Generate subtitles (SRT) mlx_whisper video.mp4 -f srt -o ./subs # Translate to English mlx_whisper foreign.mp3 --task translate ``` ## Notes - Requires Apple Silicon Mac (M1/M2/M3/M4) - Models cache to `~/.cache/huggingface/`


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

--- name: aigohotel-mcp description: 使用 AigoHotel MCP 工具完成酒店检索、结构化筛选和实时房型价格确认。用户提出酒店推荐、预算或星级限制、候选对比、房型价格与退改规则确认时触发。本技能优先调用 MCP 工具并返回结构化结论，同时根据客户端环境选择 cloud HTTP、uvx stdio 或本地调试模式。 --- # Aigohotel MCP ## 关键原则 - skill 中描述流程、配置模板和参数映射。 - 运行依赖已有服务或已发布包： - HTTP（推荐直接使用）：`https://mcp.aigohotel.com/mcp` - stdio（备选本地运行）：`uvx aigohotel-mcp` - stdio（备选本地运行）：`npx -y aigohotel-mcp` - MCP配置/源码调试：参考 `references/mcp-config.md` ## 执行流程 1. 提取约束：地点、日期、人数、预算、星级、设施偏好。 2. 映射参数： - 地点映射到 `place` + `placeType` - 入住映射到 `checkInParam` / `dateParam` / `occupancyParam` - 偏好与预算映射到 `hotelTags` 3. 标签不确定时先调用 `getHotelSearchTags`。 4. 用 `searchHotels` 做候选召回与首轮筛选，`originQuery` 保留用户原句。 5. 需要确认价格和规则时，用 `getHotelDetail`（优先 `hotelId`）。 6. 输出结果时写清假设条件与筛选依据。 ## 执行规则 - 不臆造可售状态、税费、退改规则，只能引用工具返回。 - 未提供日期时，显式声明日期假设后再查询。 - 涉及结算币种时，显式传 `localeParam.countryCode` 和 `localeParam.currency`。 - 配置示例可直接使用默认 Key，见 `references/mcp-config.md`。 ## 参考文件 - 参数定义与调用顺序：`references/tools.md` - 客户端配置与本地运行：`references/mcp-config.md`


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: henryczq/openclaw-builtin-plugin-guide (version 1.0.0)

--- name: openclaw-builtin-plugin-guide description: 查询 OpenClaw 的内置插件清单、当前启用或禁用的插件列表，以及单个插件的详细说明。适用于用户想看全部内置插件、启用状态、禁用状态、插件详情、插件说明文档时。 metadata: { "openclaw": { "emoji": "box", "requires": { "bins": ["openclaw", "python"] }, }, } --- # OpenClaw 插件清单 ## 概览 这个 skill 用来处理 3 类查询： - 查询全部 OpenClaw 内置插件 - 查询当前环境里启用或禁用的插件 - 查询某个插件的详细说明 第 3 类会优先读取本 skill 自带的参考文档 `references/builtin-plugins.md`，再补充 `openclaw plugins inspect --json` 的运行状态、能力信息，以及仓库里的相关文档摘录。 ## 快速使用 ```bash python {baseDir}/scripts/openclaw_plugin_catalog.py bundled python {baseDir}/scripts/openclaw_plugin_catalog.py status --state enabled python {baseDir}/scripts/openclaw_plugin_catalog.py status --state disabled python {baseDir}/scripts/openclaw_plugin_catalog.py inspect discord python {baseDir}/scripts/openclaw_plugin_catalog.py --format json inspect openclaw-qqbot ``` ## 工作流 ### 1. 查询全部内置插件 当用户要看“全部内置插件”“内置插件清单”“OpenClaw 插件总表”时，运行： ```bash python {baseDir}/scripts/openclaw_plugin_catalog.py bundled ``` ### 2. 查询启用或禁用插件 当用户要看“启用的插件”“禁用的插件”“当前插件状态”时，运行： ```bash python {baseDir}/scripts/openclaw_plugin_catalog.py status --state enabled python {baseDir}/scripts/openclaw_plugin_catalog.py status --state disabled python {baseDir}/scripts/openclaw_plugin_catalog.py status --state all ``` 这里的 `enabled` 以 `plugin.enabled == true` 为准。即使插件当前加载失败，只要配置层面是启用，也算启用。 ### 3. 查询单个插件详细说明 当用户要看某个插件的作用、用途、常见配置或详细说明时，运行： ```bash python {baseDir}/scripts/openclaw_plugin_catalog.py inspect <plugin-id> ``` 脚本会按这个顺序取资料： 1. `references/builtin-plugins.md` 2. `openclaw plugins inspect --json` 3. 仓库内可能相关的 `docs/`、`README.md`、渠道文档摘录 如果用户想要更口语化、更适合面板展示的解释，可以基于脚本输出再整理成自然语言说明。 ## 参考资料 - 主参考文档：`references/builtin-plugins.md` ## 注意 - 这个 skill 依赖已经安装好的 `openclaw` CLI。 - `openclaw-main/` 可能只是源码树，未必已经构建，所以不要优先使用 `node openclaw.mjs`。 - 如果插件是 `enabled: true` 但 `status: "error"`，应表述为“已启用，但加载失败”。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: sunshine-del-ux/github-readme-generator (version 1.0.0)

--- name: github-readme-generator description: Generate beautiful, professional GitHub README files for your projects. Supports multiple templates, languages, and customization options. metadata: {"clawdbot":{"emoji":"📝","requires":{},"primaryEnv":""}} --- # GitHub README Generator Generate professional GitHub README files for your projects with multiple templates and customization options. ## Features - 🎨 Multiple templates (Modern, Minimal, Detailed, API-focused) - 🌐 Multi-language support - 📋 Auto-generated badges - 💼 Project type detection (Library, CLI, Web App, etc.) - 📊 Auto-generated stats sections ## Usage ### Basic Generation ```bash # Generate with default template github-readme-generator "Project Name" "Description" # Specify template github-readme-generator "Project Name" "Description" --template modern # Specify language github-readme-generator "项目名称" "描述" --lang zh ``` ### Available Templates | Template | Use Case | |----------|----------| | `modern` | Most projects (default) | | `minimal` | Simple libraries | | `detailed` | Complex projects with full documentation | | `api` | API/REST services | | `cli` | Command-line tools | ### Options - `--template, -t` : Template name - `--lang, -l` : Language (en, zh, ja, es, ko) - `--badges, -b` : Include badge section (default: true) - `--toc, -c` : Include table of contents (default: false) - `--output, -o` : Output file path ## Examples ### Python Library ```bash github-readme-generator "my-lib" "A powerful Python library" --template modern ``` ### CLI Tool ```bash github-readme-generator "super-cli" "Amazing CLI tool" --template cli ``` ### Node.js Package ```bash github-readme-generator "my-package" "NPM package description" --template modern ``` ## Installation ```bash # No dependencies required # Uses built-in templates ``` ## How It Works 1. Detects project type from name/description 2. Selects appropriate template 3. Generates sections based on project type 4. Adds relevant badges 5. Outputs ready-to-use README.md ## Output Example The generated README includes: - Project title and badges - Description - Features list - Installation instructions - Usage examples - API reference (if applicable) - Contributing guidelines - License - Contact information


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