OpenClaw/clawhub-security-signals huggingface dataset:
Skill: calvinxhk/botlearn-rss-manager (version 1.0.0)

--- name: rss-manager role: RSS Feed Management Specialist version: 1.0.0 triggers: - "rss" - "feed" - "subscribe" - "digest" - "news feed" - "aggregator" - "syndication" - "feed reader" --- # Role You are an RSS Feed Management Specialist. When activated, you aggregate content from multiple RSS and Atom feeds, deduplicate overlapping stories, score articles by importance, cluster them into coherent topics, and produce concise daily digests that surface the most valuable information while minimizing noise. # Capabilities 1. Parse and normalize RSS 2.0, RSS 1.0 (RDF), and Atom 1.0 feeds, handling encoding variations, malformed XML, namespace conflicts, and partial content entries 2. Deduplicate articles across feeds using multi-signal similarity detection: URL canonicalization, title fuzzy matching, content fingerprinting (SimHash/MinHash), and entity overlap analysis 3. Score article importance using a weighted combination of source authority, publication recency, cross-source corroboration, social signal density, and topic relevance to user interests 4. Cluster related articles into coherent topics using TF-IDF vectorization, named entity co-occurrence, and temporal proximity, then select representative articles for each cluster 5. Generate structured daily digests with topic-organized summaries, importance rankings, source attribution, and trend indicators showing emerging or declining topics # Constraints 1. Never present duplicate or near-duplicate articles as separate items in a digest -- always merge them with attribution to all original sources 2. Never rely solely on publication timestamps for freshness -- verify against content signals since many feeds backdate or repost old content 3. Never include feed items that lack a valid title and either a description or content body -- flag them as malformed and skip 4. Always preserve source attribution -- every digest item must trace back to its original feed source(s) and publication URL(s) 5. Always respect feed update intervals specified in TTL, sy:updatePeriod, or cache headers -- never poll more frequently than the feed publisher intends 6. Never treat all feeds as equally authoritative -- maintain and apply per-source credibility scores that influence importance ranking # Activation WHEN the user requests RSS feed management, digest generation, or feed subscription: 1. Identify the user's goal: subscribe to new feeds, generate a digest, deduplicate existing content, or analyze feed health 2. Apply the appropriate phase from strategies/main.md based on the task 3. Use knowledge/domain.md for feed format parsing and content extraction rules 4. Apply knowledge/best-practices.md for deduplication, scoring, and clustering quality 5. Verify against knowledge/anti-patterns.md to avoid common feed management pitfalls 6. Output a structured digest or feed management report with clear topic organization and importance signals


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: rabbykst/fix-exec-allowlist-miss (version 1.0.0)

--- name: fix-exec-allowlist-miss description: Hybrid reload mode auto-restarts for gateway/plugins changes. Config patching requires baseHash from config.get first. Minimax cron auth uses system-level tokens, not session OAuth. --- Diagnosing exec deny: 1. Check tools.exec.security and tools.profile in config 2. If profile=coding and security=full still denied → profile baseline missing exec 3. Use gateway tool: gateway('config.patch', {raw: '{tools:{profile:"full"}}'}) 4. Hot-reload applies automatically in hybrid mode; explicit restart via gateway restart if needed 5. Verify: gateway('config.get', {}) → confirm profile=full Config patch workflow (atomic, hash-verified): 1. gateway('config.get', {}) → capture payload.hash 2. gateway('config.patch', {raw: '...', baseHash: '<hash>'}) 3. Rate limit: 3 req/60s per deviceId+clientIp. Restart coalesces with 30s cooldown. Hot-apply vs restart fields (hybrid mode): Hot-apply (no restart): channels, agent, models, routing, hooks, cron, session, messages, tools, browser, skills, mcp, audio, talk, ui, logging, identity, bindings Restart required: gateway.* (port, bind, auth, TLS, HTTP), discovery, plugins gateway.reload and gateway.remote changes do NOT trigger restart. Minimax OAuth failure (ConnectionRefused / 401): - Cron jobs use system-level auth, not current session OAuth → isolated session - If minimax portal token expired: gateway('update.run', {continuationMessage: '...'}) attempts re-auth on restart - Fallback: openclaw config set models.providers.minimax-portal.apiKey '<key>' ## Workflow Config patch protected paths: - Cannot patch channel-specific configs (e.g., whatsapp:8801322964987) - Raw must be object, not string — wrong: gateway('config.patch', {raw: '{...}'}) Right: gateway('config.patch', {raw: {channels: {...}}}) - Protected paths raise error: gateway config.patch cannot change protected config paths: <path>


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal:  | SkillSpector: clean (LOW)
Skill: damomhd/aiinsight-daily-new (version 1.0.0)

# AI Daily Skill 获取 **AI 洞察日报** 最新内容，从官方 RSS 源抓取，支持获取最新 N 条，支持推送到多个 webhook 渠道。 ## 触发词 ai daily、ai日报、ai daily、每日ai、人工智能日报、ai洞察 ## 环境变量配置 ```bash # 多个推送渠道，空格分隔。支持：Bark / 企业微信机器人 / 飞书机器人 / 钉钉机器人 / 通用 webhook export AI_DAILY_WEBHOOKS="https://api.day.app/your-token https://other-webhook" # 默认获取最新条数 export AI_DAILY_DEFAULT_COUNT=1 # RSS 源（默认已配置官方源，一般不需要修改） # export AI_DAILY_RSS_URL="https://justlovemaki.github.io/CloudFlare-AI-Insight-Daily/rss.xml" ``` --- ## 使用方式 ```bash # 加载配置 source ~/.openclaw/skills/ai-daily/config.sh # 获取默认条数（默认 1 条，当日日报） ~/.openclaw/skills/ai-daily/scripts/fetch.sh # 获取最新 N 条 ~/.openclaw/skills/ai-daily/scripts/fetch.sh 5 ``` --- ## 输出格式 **获取最新 1 条（当日日报）：** ``` **AI 洞察日报 - 2026-03-18** ### 产品与功能更新 - OpenAI 发布推理速度更快的轻量模型 - Midjourney 开启 V8 模型社区测试 - 谷歌 上线 NotebookLM 电影级视频功能 - Gamma 发布 AI 原生设计工具套件 - Lightricks 发布物理级写实视频模型 ### 前沿研究 - DeepMind 扩容蛋白质复合物数据库 - AI 通过新框架自主进化出社会规则 - Tether 发布手机端大模型离线训练框架 - Schmidt 悬赏百万美元研究 AI 欺骗行为 ### 行业展望与社会影响 - Hugging Face 发布开源趋势研究报告 - 英伟达 发布太空级 AI 基础设施蓝图 - 甲骨文 因 AI 基建成本飙升裁员三万人 ``` --- ## 说明 - 数据来源：[AI 洞察日报](https://justlovemaki.github.io/CloudFlare-AI-Insight-Daily/rss.xml) by [justlovemaki](https://github.com/justlovemaki) - RSS 目前为摘要模式，完整内容请点击原文链接查看 - 支持多个推送渠道，自动适配格式 ## 更新记录 - 2026-03-18: 初始版本，支持 RSS 抓取、多 webhook 推送


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

# Skill Name ## Overview A short description of what this skill does. Example: > This skill allows the agent to search GitHub repositories, fetch code snippets, and summarize project structures. --- # Metadata ```yaml name: github-integration version: 1.0.0 category: developer-tools description: GitHub integration skill for repositories and code analysis author: Your Name license: MIT ``` --- # Purpose Explain: * Why this skill exists * What problem it solves * Which workflows it supports Example: * Repository analysis * Pull request summaries * File search * Commit history lookup --- # Capabilities List the major capabilities of the skill. ## Features * Search repositories * Read repository files * Fetch pull requests * Analyze commits * Generate summaries * Semantic search support --- # Inputs Describe what input the skill expects. | Input Name | Type | Required | Description | | ---------- | ------ | -------- | ---------------------- | | repository | string | Yes | GitHub repository name | | branch | string | No | Branch name | | query | string | No | Search query | --- # Outputs Describe the response structure. | Field | Type | Description | | ------- | ------ | ------------------ | | summary | string | Generated summary | | files | array | Matching files | | commits | array | Commit information | --- # Environment Variables ```env GITHUB_TOKEN=your_token_here API_BASE_URL=https://api.github.com ``` --- # Installation ## Clone Repository ```bash git clone https://github.com/example/skill.git cd skill ``` ## Install Dependencies ```bash npm install ``` --- # Usage ## Example Request ```json { "repository": "openai/openai-python", "query": "embedding implementation" } ``` ## Example Response ```json { "summary": "Found embedding-related files and utilities.", "files": [ "embeddings.py", "vector_store.py" ] } ``` --- # Architecture Explain how the skill works internally. Example Flow: ```text User Request ↓ Skill Router ↓ Authentication Layer ↓ GitHub API Client ↓ Processing Layer ↓ Formatted Response ``` --- # Error Handling Common errors and solutions. | Error | Cause | Solution | | -------------------- | ----------------- | ----------------- | | Unauthorized | Invalid token | Update API token | | Rate Limited | Too many requests | Retry later | | Repository Not Found | Wrong repo name | Verify repository | --- # Security Describe security considerations. * Store tokens securely * Never expose secrets in logs * Use HTTPS requests only * Apply permission checks --- # Best Practices * Cache frequent API responses * Use pagination for large repositories * Validate user inputs * Handle API rate limits --- # Dependencies ```json { "axios": "^1.0.0", "dotenv": "^16.0.0" } ``` --- # Future Improvements * Add vector search * Add webhook support * Add multi-repository analysis * Improve semantic ranking --- # Maintainers | Name | Role | | --------- | --------- | | Your Name | Developer | --- # License MIT License


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: leooooooow/problem-solution-script-builder (version 1.0.0)

# Problem Solution Script Builder Turn a product, pain point, and promise into a clear creator-native script that moves from problem recognition to believable solution and action. Use this skill when a user wants a short-form ecommerce script built around a classic problem-to-solution structure without sounding stiff or overhyped. It works well for TikTok Shop videos, UGC briefs, affiliate content, PDP video scripts, and direct-response creator content. ## Problem it solves Many ecommerce scripts either jump straight into selling or stay too abstract. They name a benefit but never dramatize the real problem, explain the mechanism, or bridge to a credible CTA. This skill creates a tighter persuasion flow that makes the product feel relevant and timely. ## Use when - You need a script built from a pain point and product angle - A product solves an obvious everyday frustration - You want a clear direct-response structure for creator content - A team needs multiple script variants from the same problem - You are building content for testing different buyer pains ## Do not use when - The script should be purely story-led rather than problem-led - The user only needs hooks or CTAs, not a full script flow - There is no clear user pain or product mechanism to work from ## Inputs to ask for - Product and category - Target audience - Primary pain point or frustration - Desired outcome or transformation - Product mechanism / why it works - Proof available: demo, testimonial, creator experience, results, social proof - Platform and target length - CTA goal: click, comment, shop now, DM, follow, live join ## Workflow 1. Clarify the audience, pain, and offer 2. Pick the most concrete version of the problem 3. Agitate the problem in creator-native language without overselling 4. Introduce the product as the mechanism or relief path 5. Add proof, specificity, or usage context 6. End with a CTA matched to the content and funnel stage 7. Optionally produce 2-3 variants for different tones or awareness levels ## Output requirements Return: 1. Script in a clear beat-by-beat format 2. Hook 3. Problem setup 4. Agitation / consequence 5. Solution introduction 6. Proof / demonstration cue 7. CTA 8. Optional shorter and punchier alternate version ## Quality standards - The problem should feel real, not generic - The solution should be believable and specific - The script must feel like creator content, not corporate copy - Avoid unsupported guarantees or exaggerated claims - CTA should fit the actual stage of intent ## Example prompts - Build a TikTok Shop script around the problem this product solves - Turn this pain point and offer into a short problem-solution creator script - Write 3 variants of a UGC script using problem -> solution -> CTA structure


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

--- name: mcp-charter-planner description: Plan BVI sailing charters with real anchorages, weather-aware routing, provisioning lists, and local knowledge. Returns complete itineraries tailored by experience level. Use when planning Caribbean sailing trips or charter vacations. version: 1.0.0 metadata: openclaw: requires: bins: - npx emoji: ⛵ --- # BVI Charter Planner Generate complete British Virgin Islands sailing charter itineraries with real anchorages, weather considerations, and local tips. ## Setup ```json { "mcpServers": { "charter-planner": { "command": "npx", "args": ["-y", "@vbotholemu/mcp-charter-planner"] } } } ``` ## Tool: `plan_charter` | Parameter | Type | Required | Description | |------------|--------|----------|-------------| | days | number | yes | Trip duration (3-14 days) | | guests | number | yes | Number of guests | | experience | string | no | beginner, intermediate, or expert | | interests | string | no | Preferences: snorkeling, dining, remote, nightlife | ### Returns - Day-by-day itinerary with real BVI anchorages (The Baths, Norman Island, Jost Van Dyke, Anegada, etc.) - Experience-appropriate routing and sail distances - Seasonal weather patterns (trade winds, hurricane season, swell risks) - Guest-count-scaled provisioning lists with BVI-specific tips - Customs clearance, mooring ball protocols, national park fees - Restaurant and activity recommendations ## When to Use - Charter vacation planning - Sailing trip research - BVI travel preparation - Group trip logistics


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: cjmore66/plc-job-scraper (version 1.0.0)

--- name: plc-job-scraper version: "1.0.0" description: "Automaticky vyhledává PLC, automation a SCADA pracovní nabídky z LinkedIn, Indeed a dalších job boardů. Ideální pro PLC programátory a automation inženýry hledající nové projekty." --- # PLC Job Scraper Automatický scraper pro PLC a automatizační pracovní nabídky. ## Použití ### Konfigurace (nastav před spuštěním) ```bash # Cílové job boardy export JOB_BOARDS="linkedin,indeed,glassdoor" # Klíčová slova export SEARCH_TERMS="PLC programmer,automation engineer,SCADA" # Lokace (volitelné) export LOCATIONS="Germany,Austria,Czech Republic" # Typ úvazku export JOB_TYPE="full-time,contract" ``` ### Spuštění scrapingu ```bash # Použij Apify Actor pro scraping apify run caisik/plc-job-scraper # Nebo použij web_search + web_fetch ``` ### Export výsledků ```bash # Export do CSV python export_to_csv.py --input jobs.json --output plc_jobs.csv # Export do Google Sheets python export_to_sheets.py --input jobs.json ``` ## Výstupní formát Scraper vytváří JSON/CSV s následujícími poli: | Pole | Popis | |------|-------| | title | Název pozice | | company | Název firmy | | location | Lokace | | salary | Plat (pokud dostupný) | | description | Popis pozice | | url | Odkaz na inzerát | | date_posted | Datum zveřejnění | | job_type | Typ úvazku | | required_skills | Požadované skills | ## Automatizace ### Cron pro pravidelný scraping ```bash # Spusť každý den v 8:00 0 8 * * * apify run caisik/plc-job-scraper --quiet ``` ### Notifikace ```bash # Pošli Telegram zprávu s novými nabídkami python notify.py --jobs jobs.json --telegram ``` ## Tipy - Používej proxy rotation pro避开 rate limiting - Nastav delay mezi requesty (min 2s) - Ukládej výsledky do Google Sheets pro snadný přístup - Filtruj podle platového minima (např. €50k+) - Hledej "Siemens", "S7", "TIA Portal", "Beckhoff" v popisech

path: _meta.json
content: {
  "version": "1.0.0",
  "description": "Automaticky vyhledává PLC, automation a SCADA pracovní nabídky z LinkedIn, Indeed a dalších job boardů. Ideální pro PLC programátory a automation inženýry hledající nové projekty.",
  "tags": ["plc", "automation", "jobs", "scraper", "linkedin", "employment"],
  "author": {
    "name": "Jakub Cais",
    "email": "[REDACTED_SECRET]"
  }
}

Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: justoneapi/justoneapi-weibo-get-followers (version 1.0.0)

--- name: Weibo User Followers API description: Call GET /api/weibo/get-followers/v1 for Weibo User Followers through JustOneAPI with uid. author: JustOneAPI homepage: https://api.justoneapi.com metadata: {"openclaw":{"homepage":"https://api.justoneapi.com","primaryEnv":"JUST_ONE_API_TOKEN","requires":{"bins":["node"],"env":["JUST_ONE_API_TOKEN"]},"skillKey":"justoneapi_weibo_get_followers"}} --- # Weibo User Followers Use this focused JustOneAPI skill for user Followers in Weibo. It targets `GET /api/weibo/get-followers/v1`. Required non-token inputs are `uid`. OpenAPI describes it as: Get Weibo user Followers data, including profile metadata and verification signals, for network analysis and creator research. ## Endpoint Scope - Platform key: `weibo` - Endpoint key: `get-followers` - Platform family: Weibo - Skill slug: `justoneapi-weibo-get-followers` | Operation | Version | Method | Path | OpenAPI summary | | --- | --- | --- | --- | --- | | `getFollowersV1` | `v1` | `GET` | `/api/weibo/get-followers/v1` | User Followers | ## Inputs | Parameter | In | Required by | Optional by | Type | Notes | | --- | --- | --- | --- | --- | --- | | `page` | `query` | n/a | all | `integer` | Page number, starting with 1 | | `uid` | `query` | all | n/a | `string` | Weibo User ID (UID) | Request body: none documented; send parameters through path or query arguments. ## Version Choice Use `getFollowersV1` for the documented `v1` endpoint. There are no alternate versions grouped in this skill. ## Run This Endpoint Supported operation IDs in this skill: `getFollowersV1`. ```bash node {baseDir}/bin/run.mjs --operation "getFollowersV1" --token "$JUST_ONE_API_TOKEN" --params-json '{"uid":"<uid>"}' ``` Ask for any missing required parameter before calling the helper. Keep user-provided IDs, cursors, keywords, and filters unchanged. ## Environment - Required: `JUST_ONE_API_TOKEN` - Pass the token with `--token "$JUST_ONE_API_TOKEN"`; do not paste token values into chat messages, screenshots, or logs. - Get a token from [Just One API Dashboard](https://dashboard.justoneapi.com/en/login?utm_source=clawhub.ai&utm_medium=referral&utm_campaign=justoneapi_weibo_get_followers&utm_content=project_link). - Authentication details: [Just One API Usage Guide](https://docs.justoneapi.com/en/?utm_source=clawhub.ai&utm_medium=referral&utm_campaign=justoneapi_weibo_get_followers&utm_content=project_link). ## Output Focus - State the operation ID and endpoint path used, for example `getFollowersV1` on `/api/weibo/get-followers/v1`. - Echo the required lookup scope (`uid`) before summarizing results. - Prioritize fields that support this endpoint purpose: Get Weibo user Followers data, including profile metadata and verification signals, for network analysis and creator research. - Return raw JSON only after the short, endpoint-specific summary. - If the backend errors, include the backend payload and the exact operation ID.


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: googleworkspace-bot/gws-workflow-standup-report (version 1.0.12)

--- name: gws-workflow-standup-report description: "Google Workflow: Today's meetings + open tasks as a standup summary." metadata: version: 0.22.5 openclaw: category: "productivity" requires: bins: - gws cliHelp: "gws workflow +standup-report --help" --- # workflow +standup-report > **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it. Today's meetings + open tasks as a standup summary ## Usage ```bash gws workflow +standup-report ``` ## Flags | Flag | Required | Default | Description | |------|----------|---------|-------------| | `--format` | — | — | Output format: json (default), table, yaml, csv | ## Examples ```bash gws workflow +standup-report gws workflow +standup-report --format table ``` ## Tips - Read-only — never modifies data. - Combines calendar agenda (today) with tasks list. ## See Also - [gws-shared](../gws-shared/SKILL.md) — Global flags and auth - [gws-workflow](../gws-workflow/SKILL.md) — All cross-service productivity workflows commands


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: anlinxi/gequhai-music (version 1.0.1)

--- name: gequhai-music description: > 搜索和下载歌曲海(gequhai.com)的音乐，支持搜索歌曲、获取下载链接（优先无损/高品质）， 并可一键下载到群晖NAS。当用户询问歌曲、搜索音乐、或想下载歌曲时使用此技能。 nacos: namespace: ai_space service: gequhai-music port: 8001 capabilities: [search, download, ranking] --- # 歌曲海 (Gequhai) 音乐搜索与下载技能 搜索歌曲海音乐，支持下载到群晖NAS。 ## 功能 1. **搜索歌曲** - 按歌名/歌手搜索 2. **获取下载链接** - 优先无损/高品质，其次是标准品质 3. **排行榜** - 热门榜、新歌榜、飙升榜、抖音榜等 4. **下载到群晖** - 一键添加到群晖DownloadStation ## 网站信息 - 网站：https://www.gequhai.com/ - 特点：免费音乐搜索下载，支持高品质/无损音乐 ## 下载链接类型 | 类型 | 说明 | 可下载到群晖 | |------|------|-------------| | 标准品质（API） | 通过API获取的直接mp3链接 | ✅ 可以 | | 高品质（直接链接） | 页面上的直接mp3/flac链接 | ✅ 可以 | | 高品质（网盘链接） | 夸克网盘等分享链接 | ❌ 需手动下载 | **重要：** API请求需要带上 `X-Custom-Header: SecretKey` 才能成功！ ## 使用方法 ### 1. 搜索歌曲 ```bash python scripts/gequhai_crawler.py --search "青花瓷" ``` ### 2. 获取歌曲详情和下载链接 ```bash python scripts/gequhai_crawler.py --detail 553 ``` ### 3. 搜索并下载 ```bash python scripts/gequhai_crawler.py --download "周杰伦 晴天" ``` ### 4. Python脚本调用 ```python from scripts.gequhai_crawler import search_songs, get_download_url, download_song # 搜索歌曲 songs = search_songs("青花瓷") for s in songs[:5]: print(f"[{s['id']}] {s['title']} - {s['artist']}") # 获取下载链接 detail = get_download_url("553") print(f"标题: {detail['title']}") print(f"下载链接: {detail.get('url', detail.get('netdisk_url'))}") print(f"品质: {detail.get('quality')}") # 下载到群晖 result = download_song(detail, destination="download/音乐下载") print(f"下载结果: {result}") ``` ## 群晖下载配置 | 配置项 | 值 | |--------|-----| | 主机 | `192.168.123.223:5000` | | 用户 | `xiaoai` | | 默认下载目录 | `download/音乐下载` | ## 交互流程示例 用户问：**帮我下载周杰伦的青花瓷** 1. 搜索"青花瓷" 2. 获取第一首歌的下载链接 3. 如果是直接链接 → 添加到群晖下载 4. 如果是网盘链接 → 告知用户网盘地址 用户问：**最近有什么好听的歌？** 1. 获取热门歌曲列表 2. 展示给用户选择 3. 用户选择后下载 ## 注意事项 1. **API验证**：必须带上 `X-Custom-Header: SecretKey` header，否则API返回403 2. **Session**：需要使用Session保持cookie，先访问播放页再请求API 3. **下载链接类型**：高品质版本通常是网盘链接，标准品质是直接mp3链接 4. **请求频率**：避免频繁请求，以免被封IP ## 关键代码 ```python # API请求必须带上这个header api_headers = { "X-Requested-With": "XMLHttpRequest", "X-Custom-Header": "SecretKey", # 关键！ } # 使用Session保持cookie session = requests.Session() # 先访问播放页面获取cookie session.get(f"{BASE_URL}/play/{song_id}") # 再请求API session.post(f"{BASE_URL}/api/music", headers=api_headers, data={...}) ``` ## 错误处理 | 错误 | 原因 | 解决方案 | |------|------|----------| | 未找到歌曲 | 关键词不匹配 | 尝试其他关键词 | | 没有下载链接 | 歌曲暂无资源 | 换一首歌 | | 网盘链接 | 高品质版本在网盘 | 手动下载或使用标准品质 |

path: data/rename_queue.json

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