OpenClaw/clawhub-security-signals huggingface dataset:
Skill: engsathiago/mcp-server-scanner (version 1.0.0)

# MCP Server Scanner ## Description Scans MCP (Model Context Protocol) servers for security vulnerabilities, configuration issues, and data leakage risks. Based on Qualys alert: "10K+ MCP servers invisible in enterprises." ## Problem - **Shadow MCP**: Organizations don't know which MCP servers their agents use - **No visibility**: MCP servers bypass traditional security tools - **Data exfiltration**: Agents can leak data through compromised MCP servers - **Credential exposure**: Secrets often hardcoded in MCP configs ## What This Skill Does ### 1. Discovery Scan - Finds all MCP servers in your environment - Checks agent configurations for MCP connections - Maps external dependencies ### 2. Security Assessment - Validates authentication mechanisms - Checks encryption in transit - Identifies overprivileged scopes ### 3. Configuration Audit - Detects hardcoded secrets - Validates TLS certificates - Checks for insecure defaults ### 4. Data Flow Analysis - Maps what data each MCP can access - Identifies PII/SPII exposure - Checks retention policies ### 5. Compliance Mapping - SOC 2 controls - GDPR data handling - ISO 27001 requirements ## Output - **MCP Inventory**: All discovered servers - **Risk Assessment**: Severity-scored vulnerabilities - **Remediation Guide**: Step-by-step fixes - **Compliance Report**: Pass/Fail by control ## Pricing - **Quick Scan**: $30 (discovery + basic check) - **Full Assessment**: $100 (comprehensive audit) - **Enterprise**: $300 (assessment + monitoring + remediation) ## Example Usage ``` User: "Scan my MCP servers for vulnerabilities" EVE: [runs discovery and security scan] "MCP Security Scan Complete: - 7 MCP servers discovered - 2 critical: Hardcoded credentials found - 3 high: Missing TLS encryption - 12 medium: Overly permissive scopes Recommendation: Immediate rotation of exposed credentials" ``` ## Author EVE (eve-agent) Contact: Through Soul.Markets or Moltbook ## Version 1.0.0 - March 2026 ## Tags mcp, security, scanner, compliance, enterprise


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kaising-openclaw1/batch-search-monitor (version 1.0.0)

--- name: batch-search-monitor description: 批量搜索监控 - 关键词定时搜索、结果告警、数据导出 --- # Batch Search Monitor 定时监控关键词搜索结果，自动告警，支持数据导出。 ## 功能 - ✅ 多关键词批量监控 - ✅ 定时自动搜索 - ✅ 结果变化告警 - ✅ 数据导出 (CSV/Excel) - ✅ 支持 8 个中文搜索引擎 ## 使用 ```bash # 添加监控任务 clawhub monitor add --keywords "AI 技能，ClawHub" --engine "baidu" --interval 60 # 查看监控任务 clawhub monitor list # 导出结果 clawhub monitor export --task-id 1 --format csv # 删除任务 clawhub monitor remove --task-id 1 ``` ## 示例 ### 监控竞品动态 ```bash clawhub monitor add \ --keywords "竞品公司名" \ --engine "bing-cn" \ --interval 120 \ --notify true ``` ### 监控品牌提及 ```bash clawhub monitor add \ --keywords "我的品牌" \ --engine "sogou-wechat" \ --interval 60 \ --notify true ``` ## 定价 | 版本 | 价格 | 功能 | |------|------|------| | 免费版 | ¥0 | 1 个任务，60 分钟间隔 | | Pro 版 | ¥99 | 10 个任务，10 分钟间隔 | | 订阅版 | ¥29/月 | 无限任务，5 分钟间隔 + 邮件告警 |


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: darbling/csv-tool-pro (version 1.0.0)

--- name: csv-tool-pro description: CSV Swiss army knife - view, filter, sort, merge, split, dedupe, convert (JSON/YAML/TSV/Markdown), stats, and pivot tables. Pure Python, zero external dependencies. GitHub: https://github.com/darbling/clawhub-skills 当用户需要处理CSV文件、数据清洗、格式转换、表格合并、去重、统计时触发。 --- # 📊 CSV Tool Pro **Author: Lin Hui** | [GitHub](https://github.com/darbling/clawhub-skills) | MIT License | v1.0.0 One command to rule all your CSV files. View, filter, sort, merge, split, dedupe, convert, and analyze — all without leaving your terminal or opening Excel. ## ✨ Features ### Core Operations - **View** — Pretty-print CSV with alignment and truncation - **Filter** — Row filtering by column value, regex, or numeric range - **Sort** — Single or multi-column sort (asc/desc) - **Dedupe** — Remove duplicate rows by key columns ### Multi-File Operations - **Merge** — Combine multiple CSVs (union by headers) - **Join** — Inner/left/right/full join on key columns - **Split** — Split large CSV into smaller files by row count or column value ### Format Conversion - **to JSON** — Array of objects or nested format - **to YAML** — Clean YAML output - **to TSV** — Tab-separated output - **to Markdown** — GitHub-flavored markdown table - **to HTML** — Styled HTML table ### Analytics - **Stats** — Count, mean, median, min, max, std for numeric columns - **Frequency** — Value frequency distribution - **Pivot** — Pivot table aggregation ## 🚀 Usage ### View a CSV file ``` Read the CSV file at /path/to/data.csv and show the first 20 rows in a nice table. ``` ### Filter and sort ``` Read sales.csv, filter rows where amount > 1000, sort by date descending. ``` ### Merge multiple CSVs ``` Merge january.csv and february.csv into a single file Q1.csv. ``` ### Convert to JSON ``` Convert users.csv to JSON format and save as users.json. ``` ### Stats ``` Show statistics for all numeric columns in metrics.csv. ``` ### Dedupe ``` Remove duplicate rows from contacts.csv based on the email column. ``` ### Pivot table ``` Create a pivot table from sales.csv with region as rows, product as columns, sum of amount as values. ``` ## ⚙️ Technical Details - **Runtime**: Python 3.6+ - **Dependencies**: Zero (stdlib only: csv, json, statistics, re, argparse, os) - **Encoding**: Auto-detect UTF-8/GBK/UTF-8-BOM - **Large files**: Streaming processing for files >100MB - **Delimiters**: Auto-detect comma, tab, semicolon, pipe ## 📝 Notes - Auto-detects delimiter (comma, tab, semicolon, pipe) - Handles quoted fields with embedded delimiters and newlines - Preserves original encoding on write - Supports gzip-compressed CSV files


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

--- name: "breaker" version: "1.0.0" description: "Circuit breaker sizing and coordination tool. Use when json breaker tasks, csv breaker tasks, checking breaker status." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [breaker, electrical, cli, tool] category: "electrical" --- # breaker Circuit breaker sizing and coordination tool. Use when json breaker tasks, csv breaker tasks, checking breaker status. ## Commands ### `status` ```bash scripts/script.sh status ``` Show current status ### `add` ```bash scripts/script.sh add ``` Add new entry ### `list` ```bash scripts/script.sh list ``` List all entries ### `search` ```bash scripts/script.sh search ``` Search entries ### `remove` ```bash scripts/script.sh remove ``` Remove entry by number ### `export` ```bash scripts/script.sh export ``` Export data to file ### `stats` ```bash scripts/script.sh stats ``` Show statistics ### `config` ```bash scripts/script.sh config ``` View or set config ### `help` ```bash scripts/script.sh help ``` ### `version` ```bash scripts/script.sh version ``` ## Configuration Use `scripts/script.sh config <key> <value>` to set preferences. | Variable | Description | |----------|-------------| | `BREAKER_DIR` | Data directory (default: ~/.breaker/) | --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: michael-c-matias/obsidian-cli-notesmd (version 1.0.0)

--- name: obsidian description: Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli. homepage: https://help.obsidian.md metadata: { "openclaw": { "emoji": "💎", "requires": { "bins": ["obsidian-cli"] }, "install": [ { "id": "brew", "kind": "brew", "formula": "yakitrak/yakitrak/obsidian-cli", "bins": ["obsidian-cli"], "label": "Install obsidian-cli (brew)", }, ], }, } --- # Obsidian Obsidian vault = a normal folder on disk. Vault structure (typical) - Notes: `*.md` (plain text Markdown; edit with any editor) - Config: `.obsidian/` (workspace + plugin settings; usually don’t touch from scripts) - Canvases: `*.canvas` (JSON) - Attachments: whatever folder you chose in Obsidian settings (images/PDFs/etc.) ## Find the active vault(s) Obsidian desktop tracks vaults here (source of truth): - `~/Library/Application Support/obsidian/obsidian.json` `obsidian-cli` resolves vaults from that file; vault name is typically the **folder name** (path suffix). Fast “what vault is active / where are the notes?” - If you’ve already set a default: `obsidian-cli print-default --path-only` - Otherwise, read `~/Library/Application Support/obsidian/obsidian.json` and use the vault entry with `"open": true`. Notes - Multiple vaults common (iCloud vs `~/Documents`, work/personal, etc.). Don’t guess; read config. - Avoid writing hardcoded vault paths into scripts; prefer reading the config or using `print-default`. ## obsidian-cli quick start Pick a default vault (once): - `obsidian-cli set-default "<vault-folder-name>"` - `obsidian-cli print-default` / `obsidian-cli print-default --path-only` Search - `obsidian-cli search "query"` (note names) - `obsidian-cli search-content "query"` (inside notes; shows snippets + lines) Create - `obsidian-cli create "Folder/New note" --content "..." --open` - Requires Obsidian URI handler (`obsidian://…`) working (Obsidian installed). - Avoid creating notes under “hidden” dot-folders (e.g. `.something/...`) via URI; Obsidian may refuse. Move/rename (safe refactor) - `obsidian-cli move "old/path/note" "new/path/note"` - Updates `[[wikilinks]]` and common Markdown links across the vault (this is the main win vs `mv`). Delete - `obsidian-cli delete "path/note"` Prefer direct edits when appropriate: open the `.md` file and change it; Obsidian will pick it up.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: godsboy/mercury-bank (version 1.0.0)

--- name: mercury description: Mercury bank API for Digital 4 Jesus LLC (US entity). Use when the user asks about Mercury account balances, transactions, invoices, customers, or sending money. Triggers on phrases like "Mercury balance", "create invoice", "check Mercury", "list invoices", "create customer", "who owes me", "send money via Mercury", "Mercury statement", or any D4J LLC banking or AR question. Requires Mercury Plus for invoicing/customer endpoints. Credentials at ~/.secrets/mercury.env. license: MIT --- # Mercury Skill Mercury US business banking API for Digital 4 Jesus LLC (EIN 30-1413169). ## Setup Credentials at `~/.secrets/mercury.env`: ``` MERCURY_API_TOKEN=secret-token:... MERCURY_API_BASE=https://api.mercury.com/api/v1 MERCURY_AR_BASE=https://api.mercury.com/api/v1/ar MERCURY_ORG_ID=24ff8f74-e019-11f0-9f3c-3b30f2dfe1ae ``` Auth: Basic Auth — token as username, empty password. ## Quick Commands ```bash # Balance check bash /root/clawd/skills/mercury/scripts/mercury.sh balance # List invoices bash /root/clawd/skills/mercury/scripts/mercury.sh invoices # List customers bash /root/clawd/skills/mercury/scripts/mercury.sh customers # Create invoice (amount in cents — $500 = 50000) bash /root/clawd/skills/mercury/scripts/mercury.sh create-invoice \ <customer_id> 50000 2026-03-26 "Description" "INV-7" # Recent transactions bash /root/clawd/skills/mercury/scripts/mercury.sh transactions ``` ## Key Account IDs - Checking ••3223: [REDACTED_SECRET] - Savings ••4179: [REDACTED_SECRET] ## Known Customers | Name | ID | |------|----| | Digital 4 Jesus (Pty) Ltd | b70764bc-e6e7-11f0-b2c4-f7e8b0b59579 | | Tucbox Solutions LLC (Gareth) | b0a9dd9e-fcdf-11f0-9629-5f9339c3a927 | | Engel Schmidt / Sentralis Inc | f8badce2-2218-11f1-b827-dfd253723134 | ## Important Notes - **Amount is in cents**: $500 = `50000`, $250 = `25000` - **AR endpoints require Mercury Plus** (`/ar/invoices`, `/ar/customers`) - **Invoice numbers** auto-increment if not specified (script handles this) - **ACH only** for US clients to avoid Stripe fees; credit card can be enabled per invoice - For full endpoint reference, see `references/api.md`


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: earthwalking/mit24-team-building (version 1.0.0)

--- name: mit24-phase5-team-product description: "MIT有序创业24步法第五阶段（步骤19-21）。当用户需要定义最小可行商业产品MVBP、准备客户演示方案、组建创业核心团队时使用。触发词：MVBP、最小可行商业产品、产品演示、Demo、客户验证、创业团队、团队组建、核心团队、合伙人、联合创始人、团队角色、创业团队搭建" --- # MIT有序创业24步法 - 阶段五：团队与产品验证 第五阶段将创业从"纸上谈兵"推进到"实战验证"。需要确定可以投入市场的最小产品，准备向真实客户展示的方案，并组建有能力执行落地的核心团队。本阶段包含步骤19-21。 ## 前置条件 建议在前四个阶段的基础上进行，确保有清晰的产品定义和市场进入策略。 ## 工作流程 ### 步骤 19: 定义最小可行商业产品（MVBP） 确定可以验证商业模式的最小产品——注意MVBP与MVP的区别。 **MVBP vs MVP：** - MVP（最小可行产品）：最小化功能范围，验证产品是否有用 - MVBP（最小可行商业产品）：不仅验证产品有用，还要验证客户愿意付费 **MVBP的判定标准：** 1. 能解决步骤3中客户画像的核心痛点 2. 能支撑步骤11中定价策略的价格点 3. 能通过步骤14中的客户购买决策标准 4. 能在步骤18的假设验证中证明商业可行性 5. 具备完整的端到端客户体验（从认知到购买到使用） **MVBP规划清单：** - 核心功能列表（不超过5个） - 非功能性要求（性能、安全、可用性） - 技术架构选择 - 开发时间线（建议4-8周内完成） - 资源需求（人力、资金、工具） - 上线计划和初始客户获取方案 **输出要求：** MVBP产品规格文档，含功能范围、时间线、资源需求。 ### 步骤 20: 展示解决方案 向客户展示产品解决方案，收集真实反馈。 **展示方式选择：** | 方式 | 适用阶段 | 优势 | 局限 | |------|----------|------|------| | 产品Demo | 产品已有可运行版本 | 最直观 | 需要产品已完成 | | 原型演示 | 产品开发中 | 快速验证交互 | 可能与最终产品有差距 | | 概念视频 | 早期验证 | 制造成本低 | 缺乏交互体验 | | 案例研究 | 有早期客户案例 | 说服力强 | 需要真实数据 | | 客户见证 | 有满意客户 | 信任度高 | 需要真实客户配合 | | 数据报告 | 有使用数据 | 客观可信 | 需要足够数据积累 | **有效展示的5个要素：** 1. 开场30秒：快速建立共鸣，说明客户痛点 2. 产品展示：聚焦核心功能，控制在10分钟内 3. 价值证明：用数据和案例说话 4. 互动环节：邀请客户操作和提问 5. 下一步：明确的行动号召 **反馈收集框架：** - 客户最喜欢什么？ - 客户觉得缺少什么？ - 客户的购买意愿有多强？（1-10分） - 客户愿意付多少钱？ - 客户有什么顾虑或疑虑？ **输出要求：** 客户展示方案（Demo脚本/演示大纲）+ 反馈收集表。 ### 步骤 21: 建立核心团队 组建有能力将创业愿景落地的核心团队。 **四种核心角色：** | 角色 | 职责 | 关键特质 | 典型背景 | |------|------|----------|----------| | 愿景型（Visionary） | 设定战略方向，激励团队，对外讲故事 | 远见卓识、感染力、战略思维 | 创始人、连续创业者 | | 执行型（Executor） | 落实计划，解决问题，推动执行 | 结果导向、抗压能力强、组织能力 | 运营、项目经理 | | 技术型（Technician） | 开发产品，技术创新，技术决策 | 技术深度、创造力、学习能力 | CTO、技术负责人 | | 商业型（Business） | 市场开拓，商务合作，商业运营 | 商业敏感度、谈判能力、人脉资源 | 市场负责人、BD | **团队组建原则：** - 早期团队3-5人为佳，角色互补 - 技术团队和商业团队的比例要平衡 - 合伙人之间要有共同的价值观和愿景 - 明确股权分配和决策机制（避免日后纠纷） - 建立开放透明的沟通文化 **常见团队问题与应对：** - 技术团队强但商业能力弱 → 引入商业合伙人或顾问 - 合伙人之间分工不清 → 明确角色边界和决策权 - 早期招人难 → 用愿景和股权吸引，提供学习成长机会 - 团队扩张过快 → 先验证商业模式再扩大团队 ## 输出格式 完成3个步骤后，生成《团队与产品验证报告》，包含： 1. MVBP产品规格文档 2. 客户展示方案（Demo脚本 + 反馈收集表） 3. 团队组建方案（角色分工 + 招聘计划 + 股权建议） ## 实用建议 - MVBP的完成时间不应超过8周，否则说明范围太大 - 客户展示的最佳时机是产品可用但不完美的时候——太早没说服力，太晚错过反馈窗口 - 早期团队的股权分配是日后矛盾的常见根源，建议提前明确并签署协议 - 如果用户是科研人员创业，特别需要补充商业型角色，避免"技术自嗨"


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ramlee77/feishu-batch-task (version 1.0.0)

--- name: feishu-batch-task description: | Feishu Batch Task Creator - Create multiple tasks at once with templates. **Features**: - Batch create tasks from template - Quick task creation for common patterns - Import tasks from CSV format - Support task templates with default values **Trigger**: - User mentions "batch task", "create multiple tasks", "批量创建任务" - User wants to create many tasks at once --- # Feishu Batch Task Creator ## ⚠️ Pre-requisites - ✅ **Time format**: ISO 8601 / RFC 3339 (with timezone), e.g. `2026-02-28T17:00:00+08:00` - ✅ **current_user_id required**: Get from message context SenderId (ou_...) - ✅ **Use batch_create for multiple tasks**: Up to 500 records at once --- ## 📋 Quick Reference | Intent | Tool | action | Required Params | |--------|------|--------|-----------------| | Create single task | feishu_task_task | create | summary | | Batch create tasks | feishu_bitable_app_table_record | batch_create | app_token, table_id, records | | Query tasks | feishu_task_task | list | - | | Complete task | feishu_task_task | patch | task_guid, completed_at | --- ## 🛠️ Usage ### 1. Batch Create Tasks via Bitable Create a bitable template first, then batch import: ```json { "action": "batch_create", "app_token": "Mxxx", "table_id": "Txxx", "records": [ {"fields": {"任务名称": "任务1", "截止日期": 1740441600000, "负责人": [{"id": "ou_xxx"}]}}, {"fields": {"任务名称": "任务2", "截止日期": 1740528000000, "负责人": [{"id": "ou_yyy"}]}}, {"fields": {"任务名称": "任务3", "截止日期": 1740614400000, "负责人": [{"id": "ou_zzz"}]}} ] } ``` ### 2. Common Task Templates **Daily Standup Template**: ```json { "action": "create", "summary": "每日站会", "description": "同步昨日完成事项、今日计划、阻塞问题", "due": {"timestamp": "2026-03-31T18:00:00+08:00", "is_all_day": false}, "repeat_rule": "FREQ=DAILY" } ``` **Weekly Review Template**: ```json { "action": "create", "summary": "周报提交", "description": "提交本周工作总结", "due": {"timestamp": "2026-04-04T17:00:00+08:00", "is_all_day": false}, "repeat_rule": "FREQ=WEEKLY;INTERVAL=1;BYDAY=FR" } ``` ### 3. Task Template Bitable Create a bitable for templates: - Field: 任务名称 (Text) - Field: 任务描述 (Text) - Field: 截止日期 (Date) - Field: 负责人 (Person) - Field: 优先级 (Single Select: 高/中/低) - Field: 所属清单 (Text) --- ## 💰 Pricing | Version | Price | Features | |---------|-------|----------| | Free | ¥0 | Single task creation | | Pro | ¥10/month | Batch create, templates | | Team | ¥30/month | CSV import, API access | --- ## 📝 Example **User says**: "帮我批量创建5个任务，分别是需求评审、设计评审、开发评审、测试评审、上线评审，截止日期分别是下周一到周五" **Execute**: 1. Calculate dates for each day 2. Batch create 5 tasks with proper dates and descriptions 3. Return created task list --- ## 🔧 Tips - Use bitable for large batch operations (up to 500 at once) - Date fields: use millisecond timestamp (e.g., 1740441600000) - Person fields: use `{"id": "ou_xxx"}` format - For repeating tasks, use `repeat_rule` RFC5545 format


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

# tegrastats NVIDIA Jetson GPU/内存/温度实时监控工具。 ## 功能 - 实时 GPU 状态监控 - 内存使用情况 - CPU 温度监控 - 频率信息 ## 命令 ```bash # 一次性输出 tegrastats # 持续监控 (1秒间隔) tegrastats --interval 1000 # 停止监控 tegrastats --stop ``` ## 依赖 - tegrastats (系统自带)


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

--- name: tar-tool description: Create and extract tar archives with optional compression. Use for file bundling, backup, and distribution. --- # Tar - Tape Archive Utility Create, maintain, and extract tar archives. Supports gzip, bzip2, and xz compression for efficient storage and transfer. ## Usage ```bash tar-tool [options] <archive> [files...] ``` ## Common Commands - `-cf archive.tar files`: Create archive - `-xf archive.tar`: Extract archive - `-tf archive.tar`: List contents - `-czf archive.tar.gz files`: Create gzip compressed - `-cjf archive.tar.bz2 files`: Create bzip2 compressed ## Examples ```bash tar-tool -cf backup.tar ./docs/ tar-tool -czf archive.tar.gz ./project/ tar-tool -xf archive.tar.gz ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: lzgsrbs/jiuge-base-behavior (version 1.0.1)

# SKILL.md - 九歌完美版音频处理流水线 ## 名称 Jiuge Flow Perfect V1 - 九歌音频大师完美版 ## 版本 V1.2.0 ## 描述 基于2026-05-01 21:47《敬兄弟》no-wash完美处理经验封装的音频处理Skill。执行"01_Sep → 03_Dry → 04_Master"三步流程，跳过洗声节省25%时间，全链路48kHz，输出320kbps MP3预览版。 ## 核心特性 - **默认no-wash**：智能跳过洗声，节省约25%处理时间 - **全链路48kHz**：从分离到母带保持统一采样率 - **双版本输出**：320kbps母带 + 128kbps预览版 - **自动归档**：按"项目名+时间戳"自动归档到Jiuge_Audio_Projects - **断点续处理**：支持从任意步骤中断点继续 ## 执行流程 ### 第一步：人声分离 (01_Sep) - **引擎**：Kim_Vocal_2.onnx (MDX-Net) - **模型路径**：/Applications/Ultimate Vocal Remover.app/Contents/Resources/models/MDX_Net_Models - **输出格式**：WAV 48kHz - **输出文件**：(Vocals)_Kim_Vocal_2.wav, (Instrumental)_Kim_Vocal_2.wav ### 第二步：去混响脱水 (03_Dry) - **引擎**：UVR-De-Echo-Aggressive.pth (VR Architecture) - **模型路径**：/Applications/Ultimate Vocal Remover.app/Contents/Resources/models/VR_Models - **输入**：第一步的Vocals文件 - **输出**：(No Echo)_UVR-De-Echo-Aggressive.wav ### 第三步：母带处理 (04_Master) - **转换工具**：ffmpeg - **母带版本**：320kbps MP3, 48kHz, 立体声 - **预览版本**：128kbps MP3, 48kHz, 立体声 - **命名规则**：{项目名}_Master.mp3, {项目名}_Preview.mp3 ## 使用方法 ### 基本用法（默认no-wash） ```bash ~/Desktop/Jiuge_Flow_Perfect_V1.skill/scripts/jiuge_flow.sh "文件名.mp3" [模式编号] ``` ### 强制wash模式 ```bash ~/Desktop/Jiuge_Flow_Perfect_V1.skill/scripts/jiuge_flow.sh "文件名.mp3" 1 wash ``` ### 参数说明 - $1：输入文件名（必填） - $2：处理模式（可选，默认1） - 1：民歌高亢版（默认） - 2：美声共鸣版 - 3：流行中度脱水 - 4：会议轻度脱水 - 5：大教堂重度脱水 - $3：wash开关（可选，默认no-wash） - wash：执行完整四步流程（含洗声） - no-wash：跳过洗声，三步完成 ## 技术规范 ### 硬性指标 | 项目 | 规格 | |------|------| | 采样率 | 48kHz（全链路统一） | | 母带码率 | 320kbps MP3 | | 预览码率 | 128kbps MP3 | | 声道 | 立体声 | | 输出格式 | MP3 | ### 模型配置 | 步骤 | 模型 | 架构 | 用途 | |------|------|------|------| | 分离 | Kim_Vocal_2.onnx | MDX-Net | 人声/伴奏分离 | | 脱水 | UVR-De-Echo-Aggressive.pth | VR | 去混响 | ## 环境要求 - Python：3.11+（uvr_auto conda环境） - audio-separator：0.24.1+ - ffmpeg：4.3.2+ - 模型文件：已安装UVR5模型 ## 修复记录 ### V29 Bug修复 - **问题**：V29脚本dry_cmd为None导致TypeError - **原因**：自动化逻辑中变量未正确初始化 - **解决**：按21:47手动成功流程重新编写分步脚本 - **验证**：2026-05-01 21:47《敬兄弟》处理成功 ## 作者 九歌传媒 AI助手 ## 更新日志 - V1.2.0 (2026-05-01 23:51): 修复03_Dry文件名选择bug，排除Instrumental文件，确保选择主唱人声 - V1.1.0 (2026-05-01 22:47): 修复洗声逻辑，补充完整的背景合唱分离功能 - V1.0.0 (2026-05-01): 基于21:47完美处理经验首次封装


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mzfshark/axodus-project-bootstrap (version 1.0.0)

--- name: project-bootstrap description: Bootstrap new projects with predictable structure and validation commands. metadata: author: RedHat Dev version: 1.0.0 owner: RedHat Dev Agent category: execution --- # SKILL: project-bootstrap ## Purpose Initialize a new project with a predictable structure, quality gates (lint/test), and safe configuration defaults. ## When to Use - Starting a new service/app/library. - Creating a new package inside a monorepo. - You need a repeatable baseline for contributors/CI. ## Inputs - `project_type` (required, enum: `backend|frontend|library|contract|cli`). - `stack` (required, string): e.g., â€œnode-tsâ€, â€œpython-fastapiâ€, â€œnextjsâ€. - `name` (required, string): project/package name. - `path` (required, string): target directory. - `constraints` (optional, string[]): repo rules, linting, deployment constraints. ## Steps 1. Confirm target directory and ensure it is safe to create/modify. 2. Select a template that matches repo conventions; prefer minimal dependencies. 3. Scaffold project structure (src/tests/config/docs). 4. Configure: - lint/format (if repo uses them) - unit test runner - env/config examples (`.env.example`), never real secrets 5. Add a README with: - how to run locally - how to test - key design decisions 6. Run deterministic validation commands (install + test + build). ## Validation - Project builds/runs locally (basic smoke check). - Tests execute and pass (even if minimal). - No secrets or machine-specific paths are committed. ## Output - Created file tree - Commands to run (`install`, `dev`, `test`, `build`) - Configuration contract (env vars and defaults) ## Safety Rules - Never modify global tooling on the machine unless explicitly requested. - Pin versions where the repo requires it. - Do not auto-deploy; bootstrap is local by default. ## Example Bootstrap a TS backend: - `project_type`: `backend` - `stack`: `node-ts` - Output: `apps/api/` with `pnpm test` and `pnpm dev` working.


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