OpenClaw/clawhub-security-signals huggingface dataset:
Skill: mctmilk/legal-decision-tree-mctmilk (version 1.0.0)

--- name: legal-decision-tree-mctmilk description: 基于前六步分析结果，为法条生成完整的适用决策流程图（SOP），标注判断节点、证据要求和切换条件。这是法条分析的最终沉淀，形成可复用的实战操作指南。 --- # 法条适用决策树生成 (Legal Decision Tree) ## 触发场景 - 用户说"生成决策流程图"、"做成SOP"、"形成可复用的指南" - 用户完成了前六步分析，想把结果固化 - 用户想有一张每次遇到这类案件都能用的"作战地图" ## 前置条件 此 skill 应在完成以下任一步骤后使用： 1. [REDACTED_SECRET] - 结构化拆解 2. `legal-concept-deep-dive-mctmilk` - 概念深挖 3. `legal-system-mapper-mctmilk` - 体系定位 4. `legal-evidence-mapping-mctmilk` - 证据对应 **建议至少完成前四步后再使用此 skill。** ## 核心提示词 ``` 基于以上分析，请为【法条编号】生成一张完整的适用决策流程图： 要求： 1. 以"是否满足要件"为判断节点 2. 每个节点标注：需要审查的事实 + 关键证据 + 举证责任 3. 标出常见"岔路口"：在哪些节点最容易出现争议？争议如何处理？ 4. 标出与其他法条的切换点：不满足本条时，可以转向哪条？ 5. 最终到达：支持/驳回的结论 + 法律效果 格式（文字树形结构）： START → 审查要件1（XXX） ├── 是 → 审查要件2（XXX） │ ├── 是 → ……（继续直到结论） │ └── 否 → [替代方案/驳回理由] └── 否 → [替代法条/驳回] ``` ## 输出要求 1. **决策流程图**（文字树形结构，ASCII格式） 2. **每个判断节点标注**： - 需要审查的具体事实 - 关键证据要求 - 举证责任归属 3. **岔路口标注**：易争议点 + 处理方式 4. **切换点标注**：不满足本条时的备选法条 ## 示例输出格式 ``` START └── 审查：行为人是否实施了侵权行为？ ├── 是 → 审查：是否造成损害后果？ │ ├── 是 → 审查：行为与损害是否存在因果关系？ │ │ ├── 是 → 审查：行为人是否有过错？ │ │ │ ├── 是 → 结论：支持原告诉请 │ │ │ └── 否 → 结论：按公平责任处理 │ │ └── 否 → 结论：不构成侵权，驳回 │ └── 否 → 结论：不构成侵权，驳回 └── 否 → 结论：不构成侵权，驳回 【切换点】如不满足本条，可转向： - 第1166条（无过错责任） - 第1167条（公平责任） ``` ## 注意事项 - 这张图就是用户个人的"法条专属SOP"，每次遇到相关案件直接对照使用 - 建议用户保存下来，实践中不断补充完善 - 切换点非常重要，帮助用户避免"一条路走到黑"


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: tianyn1990/thinking-spark (version 1.0.0)

--- name: thinking-spark description: 记录思考火花与沉淀的系统。用于用户想要记录临时思考、想法、灵感火花，或者将思考整理沉淀为有条理的内容时触发。 --- # Thinking Spark - 思考火花记录系统 ## 概述 用于记录临时的思考火花（突然产生，可能不完整），并支持有条后续整理为理的思考沉淀。 ## 数据结构 文件位置：`collection/思考火花.json` ```json { "schema_version": "1.0", "description": "思考火花与沉淀记录", "sparks": [ { "id": "20260310_001", "content": "原始思考内容...", "polished_content": "整理后的沉淀内容...", "tags": ["AI", "Agent"], "origin": "spark", "status": "polished", "priority": 1, "confidence": 0.8, "source_refs": ["article:20260309_001"], "created_at": "2026-03-10T11:51:00Z", "updated_at": "2026-03-10T12:00:00Z", "refined_at": "2026-03-10T14:00:00Z", "history": [ {"action": "created", "timestamp": "2026-03-10T11:51:00Z"}, {"action": "refined", "timestamp": "2026-03-10T14:00:00Z"} ] } ] } ``` ### 字段说明 | 字段 | 类型 | 说明 | |------|------|------| | id | string | 唯一标识，格式：YYYYMMDD_NNN | | content | string | 原始思考内容 | | polished_content | string | 整理后的沉淀内容（可选） | | tags | array | 标签 | | origin | string | 来源：spark(火花) 或 direct(直接沉淀) | | status | string | 状态：raw → refining → polished → archived | | priority | number | 优先级 1-5 | | confidence | number | 确定程度 0-1 | | source_refs | array | 关联外部ID，如 article:xxx, project:xxx | | created_at | string | 创建时间 | | updated_at | string | 更新时间 | | refined_at | string | 整理完成时间 | | history | array | 变更历史 | ## 命令列表 | 命令 | 说明 | |------|------| | `记录思考：xxx` | 快速记录火花 | | `沉淀思考：xxx` | 直接沉淀（跳过火花状态） | | `整理思考 [id]` | 整理指定火花 | | `整理思考 今天` | 整理今天所有火花 | | `查看思考` | 查看所有 | | `查看思考 待整理` | 查看未整理 | | `查看思考 tag:AI` | 按标签筛选 | | `关联思考 <id> <外部ID>` | 关联外部 | | `归档思考 <id>` | 归档已沉淀 | ## 使用示例 ### 记录火花 ``` 记录思考：Agent 的上下文管理能力决定了它的长期记忆效果 ``` → 创建 status=raw 的火花记录 ### 直接沉淀 ``` 沉淀思考：上下文是 Agent 最核心的能力之一，决定了能否保持对话连贯性和任务一致性 ``` → 创建 status=polished 的沉淀记录 ### 整理火花 ``` 整理思考 20260310_001 ``` → 帮你把原始思考内容整理成有条理的文章 ### 查看待整理 ``` 查看思考 待整理 ``` → 列出所有 status=raw 的记录 ### 关联外部 ``` 关联思考 20260310_001 article:20260309_001 ``` → 将思考与待阅文章关联 ## 与其他系统整合 - **待阅文章**：`source_refs: ["article:ID"]` 形成"阅读→思考→沉淀"闭环 - **开源项目**：`source_refs: ["project:ID"]` - **MEMORY.md**：polished + priority≥4 可候选写入长期记忆 ## 原子写入 更新 JSON 时使用临时文件 + rename 防止损坏： ```bash # 伪代码 tmp_file=$(mktemp) jq . > $tmp_file mv $tmp_file collection/思考火花.json ``` ## 脚本 Scripts 目录提供确定性操作： | 脚本 | 用法 | |------|------| | `create_spark.py` | `python3 create_spark.py "思考内容" "tag1,tag2"` | | `list_sparks.py` | `python3 list_sparks.py [raw\|polished\|today\|tag:xxx]` | | `update_spark.py` | `python3 update_spark.py <id> refine "整理后内容"` |


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: dxihyv/a-stock-analyzer (version 2.2.0)

--- name: a-stock-analyzer version: "2.1.0" description: "A股智能分析交易助手（专业版）。基于马克·米勒维尼趋势模板和7大严格财务条件筛选优质个股，适用于追求高基本面标准的价值趋势投资者。" compatibility: requires: - Python 3.9+ - akshare (pip install akshare) - pandas - numpy - requests os: - darwin - linux - win32 --- # A股智能分析交易助手（专业版） ## 概述 本技能采用**7大严格选股条件**，结合技术面和基本面，筛选A股市场中最优质的个股。 ## 7大选股条件 | 条件 | 说明 | |------|------| | 1 | 剔除ST股票和上市不满1年的次新股 | | 2 | 最近一季度营业收入同比增长率 > 25% | | 3 | 最近一季度净利润同比增长率 > 30% 且环比增长为正 | | 4 | 股价处于30日均线上方或接近均线（5%以内） | | 5 | 最近10个交易日平均成交量 > 120日均量（放量） | | 6 | 净资产收益率（ROE）> 15% | | 7 | 最近三年净利润复合增长率 > 20% | ## 核心功能 ### 1. 大盘分析 - 上证指数、深证成指、创业板指、科创板指 - 实时涨跌幅 ### 2. 专业选股 - 从热门股票池筛选 - 逐个检查7大条件 - 获取K线数据计算技术指标 - 获取财务数据分析基本面 ### 3. 买卖建议 - 买入区间（现价±2%） - 目标价（+15%） - 止损价（-5%） - 仓位配置（60%/20%/20%） ## 使用方式 ### 手动触发 ```bash # 完整分析（大盘+选股） python3 scripts/analyze.py --full # 只看大盘 python3 scripts/analyze.py --market # 只选股 python3 scripts/analyze.py --stocks ``` ### 自动推送 配置 cron 定时任务： ```bash # 每天早上8点分析 0 8 * * 1-5 cd /path/to/a-stock-analyzer && python3 scripts/analyze.py --full ``` ## 配置文件 (config.json) ```json { "push": { "enabled": true, "times": ["08:00", "14:00"], "channels": ["dingtalk"] }, "stock": { "max_holdings": 3, "recommend_count": 3, "position_ratio": [0.6, 0.2, 0.2] }, "risk": { "stop_loss_pct": 5, "stop_profit_pct": 15, "max_position_pct": 60 } } ``` ## 技术指标 | 指标 | 说明 | |------|------| | MA30 | 30日均线，价格支撑/压力位 | | MA60 | 60日均线，中期趋势 | | MA120 | 120日均线，长期趋势 | | VOL_MA10 | 10日均量，短期成交量 | | VOL_MA120 | 120日均量，长期均量 | ## 财务指标 | 指标 | 说明 | 筛选标准 | |------|------|----------| | 营收同比 | 营业收入增长速率 | > 25% | | 净利润同比 | 净利润增长速率 | > 30% | | 净利润环比 | 净利润环比增长 | > 0% | | ROE | 净资产收益率 | > 15% | | 三年复合增长率 | 净利润3年CAGR | > 20% | ## 输出文件 - `reports/report_YYYYMMDD_HHMMSS.md` - 每日分析报告 ## 风险提示 ⚠️ - 本技能仅供参考，不构成投资建议 - 股市有风险，入市需谨慎 - 请根据自身风险承受能力使用 - 严格执行止损纪律 ## 依赖安装 ```bash pip install akshare pandas numpy requests ``` ## 更新日志 - v2.0.0: 专业版，支持7大严格选股条件，马克·米勒维尼趋势模板 - v1.0.0: 初始版本，基础选股功能


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: ericsantos/relay-to-agent (version 0.0.1)

--- name: relay-to-agent description: "Relay messages to AI agents on any OpenAI-compatible API. Supports multi-turn conversations with session management. List agents, send messages, reset sessions." homepage: https://platform.openai.com/docs/api-reference/chat metadata: {"clawdbot":{"emoji":"🤖","requires":{"bins":["node"]},"primaryEnv":"RELAY_API_KEY"}} --- # Relay To Agent Send messages to AI agents on any OpenAI-compatible endpoint. Works with Connect Chat, OpenRouter, LiteLLM, vLLM, Ollama, and any service implementing the Chat Completions API. ## List available agents ```bash node {baseDir}/scripts/relay.mjs --list ``` ## Send a message to an agent ```bash node {baseDir}/scripts/relay.mjs --agent linkedin-alchemist "Transform this article into a LinkedIn post" ``` ## Multi-turn conversation ```bash # First message node {baseDir}/scripts/relay.mjs --agent connect-flow-ai "Analyze our latest campaign" # Follow-up (same session, agent remembers context) node {baseDir}/scripts/relay.mjs --agent connect-flow-ai "Compare with last month" ``` ## Reset session ```bash node {baseDir}/scripts/relay.mjs --agent linkedin-alchemist --reset "Start fresh with this article..." ``` ## Options | Flag | Description | Default | |------|-------------|---------| | `--agent ID` | Target agent identifier | (required) | | `--reset` | Reset conversation before sending | off | | `--list` | List available agents | — | | `--session ID` | Custom session identifier | `default` | | `--json` | Raw JSON output | off | ## Configuration ### agents.json Configure agents and endpoint in `{baseDir}/agents.json`: ```json { "baseUrl": "https://api.example.com/v1", "agents": [ { "id": "my-agent", "name": "My Agent", "description": "What this agent does", "model": "model-id-on-the-api" } ] } ``` ### Environment variables ```bash export RELAY_API_KEY="sk-..." # API key (required) export RELAY_BASE_URL="https://..." # Override base URL from config export RELAY_CONFIG="/path/to/agents.json" # Custom config path ``` ## Compatible Services - **Connect Chat** — `api.connectchat.ai/api` - **OpenRouter** — `openrouter.ai/api/v1` - **LiteLLM** — `localhost:4000/v1` - **vLLM** — `localhost:8000/v1` - **Ollama** — `localhost:11434/v1` - **Any OpenAI-compatible API** ## Session Management Sessions are stored locally at `~/.cache/relay-to-agent/sessions/`. Each agent+session combination keeps up to 50 messages. Use `--session` for parallel conversations with the same agent.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: jamierossouw/hourly-momentum-trader (version 1.0.0)

--- name: hourly-momentum-trader version: 1.0.0 description: Momentum-based trading agent for hourly crypto candles. Uses RSI, MACD, OBV, EMA, and Bollinger Band confluence to score directional momentum from -10 to +10. Optimized for Polymarket hourly binary markets and short-term spot/perp entries. Use when you need hourly candle signals, momentum scoring, short-term crypto direction, or Polymarket hourly market edge detection. author: JamieRossouw tags: [momentum, hourly, crypto, polymarket, rsi, macd, signals, trading] --- # Hourly Momentum Trader Directional momentum scoring for 1-hour crypto candles with Polymarket binary market integration. ## Momentum Score System (-10 to +10) Each signal contributes to the composite score: | Signal | Bullish (+) | Bearish (-) | Weight | |--------|------------|------------|--------| | RSI | <40 oversold | >70 overbought | ±1 | | RSI divergence | Bull div | Bear div | ±2 | | MACD cross | Bullish cross | Bearish cross | ±1 | | MACD histogram | Rising | Falling | ±1 | | EMA cross | EMA20>EMA50 | EMA20<EMA50 | ±1 | | EMA200 | Price above | Price below | ±1 | | Bollinger | Near lower (oversold) | Near upper (overbought) | ±1 | | OBV trend | Rising (accumulation) | Falling (distribution) | ±1 | | OBV divergence | Bull div | Bear div | ±2 | | Volume | High volume on move | Low volume | ±1 | ## Live Bet Integration (Polymarket Argus Strategy) Combine momentum score with Polymarket market odds: ```python # Edge formula our_prob = 0.50 + (momentum_score * 0.05) # score 6 = 80% confidence market_prob_up = polymarket_up_price # e.g. 0.35 (35% UP consensus) edge = our_prob - market_prob_up # e.g. 0.80 - 0.35 = 45% edge! # Bet when: # - abs(momentum_score) >= 3 # - abs(edge) >= 0.10 (10%) # - market is fresh (<30 min old) # - USDC.e balance >= $5 ``` ## Counter-Consensus Setups (L023) Highest-EV Polymarket plays: - Momentum score ≥+3 AND market DOWN >70% → **BET UP** (counter-consensus, 3-5x payout) - Momentum score ≤-3 AND market UP >70% → **BET DOWN** (counter-consensus, 3-5x payout) Example: SOL score=+4, Polymarket DOWN 80% → buy UP at 0.20 → if wins: 5x return ## Signals Output Format ```json { "asset": "BTC", "score": 3, "rsi": 64.9, "rsi_status": "neutral", "macd_hist": 10.39, "macd_direction": "rising", "obv_trend": "rising", "bb_pct": 0.72, "ema_cross": "bullish", "bias": "BULLISH", "confidence_pct": 65, "polymarket_edge": { "btc_4pm_et": { "market_up": 0.515, "our_p": 0.65, "edge": 0.135, "direction": "UP" } } } ``` ## Watchlist (Default) BTC, ETH, SOL, XRP, ATOM, ADA, SUI, LTC, NEAR, AVAX, BNB, LINK, DOT, TRX, DOGE


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: dommholland/getpost-sms (version 1.0.0)

--- name: getpost-sms description: "Send and receive SMS messages via API. Shared or dedicated numbers." version: "1.0.0" --- # GetPost SMS API Send and receive SMS messages. Shared number included, or provision a dedicated number. ## Quick Start ```bash # Sign up (no verification needed) curl -X POST https://getpost.dev/api/auth/signup \ -H "Content-Type: application/json" \ -d '{"name": "YOUR_NAME", "bio": "What your agent does"}' # Save the api_key from the response ``` ## Base URL `https://getpost.dev/api` ## Authentication ``` [REDACTED_SECRET] ``` ## Send SMS ```bash curl -X POST https://getpost.dev/api/sms/send \ -H "[REDACTED_SECRET]" \ -H "Content-Type: application/json" \ -d '{"to": "+14155551234", "body": "Hello from my bot!"}' ``` Phone numbers must be E.164 format. Cost: 5 credits per SMS. ## Read Inbox ```bash curl https://getpost.dev/api/sms/inbox \ -H "[REDACTED_SECRET]" ``` ## Provision Dedicated Number ```bash curl -X POST https://getpost.dev/api/sms/numbers \ -H "[REDACTED_SECRET]" \ -H "Content-Type: application/json" \ -d '{"area_code": "415", "country": "US"}' ``` ## Webhook Register a webhook for `sms.received` to get notified when you receive a text. ## Full Docs https://getpost.dev/docs/api-reference#sms


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: edmonddantesj/aoi-openclaw-security-toolkit-core (version 0.1.6)

--- name: aoi-openclaw-security-toolkit-core description: Fail-closed OpenClaw security toolkit (public-safe). Use to prevent accidental or unexpected data leakage by running local-only checks: default-deny allowlists, lightweight secret/token scans, egress-risk pattern scans, and prompt/document injection pattern scans. Use when preparing GitHub/ClawHub publishing, reviewing skills/scripts for risky behavior, or validating inbound text/doc content before tool execution. --- # AOI OpenClaw Security Toolkit (Core) **Why**: Prevent “one bad commit” incidents (accidental file leakage + secret exposure) with a fast, local-only, fail-closed check. **When**: Before committing/pushing, before publishing a skill, and when reviewing scripts/skills for unexpected egress behavior. **How**: Run a single command to get PASS/WARN/BLOCK and an optional redaction-safe report. **Scope**: Detection + reporting only (no auto-fix, no uploads, no auto-posting). **Quickstart**: `openclaw-sec check --preset repo --diff staged` This is a **public-safe** toolkit skill. - **Does:** detect + report risks (PASS/WARN/BLOCK) - **Does NOT:** auto-fix, auto-upload, auto-post, or exfiltrate data ## CLI Binary: `openclaw-sec` Common: ```bash openclaw-sec check --lang en openclaw-sec check --lang ko openclaw-sec scan-secrets openclaw-sec scan-egress openclaw-sec scan-prompt --file inbound.txt ``` Exit codes: - `0` PASS - `1` WARN - `2` BLOCK ## Default scan scope If `--paths` is omitted, it scans existing paths among: - `.` - `skills/` - `scripts/` - `context/` ## Rules Rule files live in `rules/`: - `secret_patterns.txt` - `egress_patterns.txt` - `prompt_injection_patterns.txt` Edit these to tune sensitivity.


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: ckchzh/blast (version 2.0.1)

--- name: "Blast L2 — Ethereum L2 Chain Reference" description: "Use when exploring Blast L2 chain features, understanding native yield mechanics, comparing gas costs, bridging assets, or discovering Blast ecosystem projects and DApps." version: "2.0.0" author: "BytesAgain" homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills tags: ["blast", "ethereum", "l2", "layer2", "yield", "defi", "blockchain"] --- # Blast L2 — Ethereum L2 Chain Reference Comprehensive reference for the Blast L2 chain — native yield, gas mechanics, bridging, and ecosystem overview for developers and users. ## Commands ### overview Blast chain architecture, key stats, and design philosophy. ```bash bash scripts/script.sh overview ``` ### yield Native yield mechanics — ETH staking yield, USDB, and auto-rebasing. ```bash bash scripts/script.sh yield ``` ### gas Gas costs comparison with L1 and other L2s. ```bash bash scripts/script.sh gas ``` ### bridge Bridging guide — deposit/withdraw, timelines, and security. ```bash bash scripts/script.sh bridge ``` ### ecosystem Blast ecosystem projects and key DApps. ```bash bash scripts/script.sh ecosystem ``` ### help Show all commands. ```bash bash scripts/script.sh help ``` ## Output - Chain specs and architecture details - Yield calculations and mechanics - Gas comparisons and bridging steps ## Feedback https://bytesagain.com/feedback/ Powered by BytesAgain | bytesagain.com


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: sky-lv/container-helper (version 1.0.0)

--- name: "docker-helper" slug: skylv-docker-helper version: 1.0.2 description: Docker assistant. Container management, image building, and Dockerfile optimization. Triggers: docker, container, dockerfile, docker build. author: SKY-lv license: MIT-0 tags: [docker, openclaw, agent] keywords: docker, container, devops, deployment triggers: docker helper --- # Docker Helper — Docker助手 ## 功能说明 辅助Docker容器管理和配置。 ## 使用方法 ### 1. 容器操作 ``` 用户: 列出所有运行中的容器 ``` ### 2. Dockerfile ``` 用户: 写一个Node.js的Dockerfile ``` ### 3. 镜像构建 ``` 用户: 构建镜像并推送到registry ``` ### 4. 网络配置 ``` 用户: 配置容器网络 ``` ## Usage 1. Install the skill 2. Configure as needed 3. Run with OpenClaw


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: lumenclaw-cloud/filtrix-video-gen (version 0.1.0)

--- name: filtrix-video-gen description: Generate videos through Filtrix Remote MCP. Use when users ask for text-to-video, image-to-video, video task polling, or downloading completed videos with generate_video_text, generate_video_image, and get_video_status. --- # Filtrix Video Gen (MCP) This skill is MCP-only. - Endpoint: `https://mcp.filtrix.ai/mcp` - Auth: `Authorization: Bearer <FILTRIX_MCP_API_KEY>` - Primary tools: - `generate_video_text` - `generate_video_image` - `get_video_status` ## Setup Required: - `FILTRIX_MCP_API_KEY` Optional: - `FILTRIX_MCP_URL` (default: `https://mcp.filtrix.ai/mcp`) ## Generate Video (Text) ```bash python scripts/generate.py \ --mode text-to-video \ --prompt "a cinematic drone shot over a neon city at night" \ [--aspect-ratio 16:9] \ [--idempotency-key KEY] \ [--wait] \ [--poll-interval 8] \ [--timeout 600] \ [--output /tmp/video.mp4] ``` Default behavior submits a request and prints `request_id`. Add `--wait` to poll until completion and download the final video. ## Generate Video (Image-to-Video) Grok Imagine: ```bash python scripts/generate.py \ --mode grok-imagine \ --prompt "camera slowly pushes in, fog drifting" \ --image-path /path/to/input.png \ --duration-seconds 6 \ [--aspect-ratio 16:9] \ [--wait] ``` Seedance 1.5 Pro: ```bash python scripts/generate.py \ --mode seedance-1-5-pro \ --prompt "soft cinematic motion, subject turns to camera" \ --image-url https://... \ --duration-seconds 8 \ [--aspect-ratio 16:9] \ [--wait] ``` Notes: - Grok duration: `6` or `15` - Seedance duration: `5`, `8`, `10`, `12` - Seedance in MCP has audio fixed to `on` ## Check Status ```bash python scripts/status.py \ --request-id YOUR_REQUEST_ID \ [--download] \ [--output /tmp/video.mp4] ``` ## Idempotency `idempotency_key` prevents duplicate billing on retries. If omitted, scripts auto-generate one UUID-based key. ## References - [MCP Tools Reference](references/mcp-tools.md) - [Video Prompt Guide](references/prompts.md)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: oguzhaslak/molt-mouse (version 1.0.0)

--- name: desktop-mouse description: Local mouse control via ydotool wrapper metadata: {"moltbot":{"emoji":"","os":["linux"],"requires":{"bins":["molt-mouse"]}}} user-invocable: false --- When the user asks to move/click the mouse: - Use the exec tool with host=gateway. - ONLY run commands that start with: `molt-mouse ...` - Supported: - `molt-mouse move <dx> <dy>` - `molt-mouse abs <x> <y>` - `molt-mouse click left|right|middle` - `molt-mouse click 0x40` # left button down (hold) - `molt-mouse click 0x80` # left button up (release) - If numbers are missing/ambiguous, ask the user.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: blammectrappora/miniature-world-generator (version 1.0.0)

--- name: miniature-world-generator description: AI miniature world and diorama art generator — create tilt-shift miniature scenes, tiny world illustrations, hyper-detailed diorama art, and shallow-depth-of-field fantasy landscapes. Perfect for Instagram art, Pinterest boards, desktop wallpapers, and creative visual storytelling via the Neta AI image generation API (free trial at neta.art/open). tools: Bash --- # Miniature World Generator AI miniature world and diorama art generator — create tilt-shift miniature scenes, tiny world illustrations, hyper-detailed diorama art, and shallow-depth-of-field fantasy landscapes. Perfect for Instagram art, Pinterest boards, desktop wallpapers, and creative visual storytelling. ## Token Requires a Neta API token (free trial at <https://www.neta.art/open/>). Pass it via the `--token` flag. ```bash node <script> "your prompt" --token YOUR_TOKEN ``` ## When to use Use when someone asks to generate or create miniature world diorama art generator images. ## Quick start ```bash node miniatureworldgenerator.js "your description here" --token YOUR_TOKEN ``` ## Options - `--size` — `portrait`, `landscape`, `square`, `tall` (default: `square`) - `--ref` — reference image UUID for style inheritance ## Install ```bash npx skills add blammectrappora/miniature-world-generator ```


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

--- name: Galician description: Write Galician that sounds human. Not formal, not robotic, not AI-generated. --- ## The Real Problem AI Galician is technically correct but sounds off. Too formal. Too literary. Natives write more casually, with warmth. Match that. ## Formality Default Default register is too high. Casual Galician is warm and melodic. Unless explicitly formal: lean casual. "Ola" not "Bo día". "Si" not "Si, por suposto". ## Ti vs Vostede Distinction: - Vostede: formal, elderly, respect - Ti: friends, peers, casual - Galician casual uses ti widely - Vostede in formal contexts only ## Galician vs Spanish vs Portuguese Galician is distinct: - Not Spanish, not Portuguese - Own vocabulary and patterns - "Grazas" not "Gracias" - Don't mix with Spanish ## Particles & Softeners These make Galician natural: - Pois: "well", "so" - Non si: tag question - Home/Muller: casual address - Logo: "then" ## Fillers & Flow Real Galician has fillers: - Pois, logo, ben - Sabes, entendes - Ou sexa, vamos - Mira, escoita ## Expressiveness Don't pick the safe word: - Ben → Xenial, Estupendo, Dabuti - Mal → Fatal, Moi mal - Moito → Abondo, Unha chea ## Common Expressions Natural expressions: - Vale, Ben, Dabondo - Non pasa nada, Tranquilo - De verdade?, En serio?, Que? - Xenial!, Estupendo!, Moi ben! ## Reactions React naturally: - De verdade?, En serio?, Que dis? - Carai!, Carallo!, Miña nai! - Xenial!, Dabuti!, Moi ben! - Jajaja in text ## Reintegrationism Some use Portuguese-aligned spelling: - Reintegrationist vs normative - Most use normative (RAG standard) - Stay consistent ## The "Native Test" Before sending: would a Galician speaker screenshot this as "AI-generated"? If yes—too formal, sounds Spanish, too literary. Add Galician warmth.


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