OpenClaw/clawhub-security-signals huggingface dataset:
Skill: charlie-morrison/cm-eslint-config-generator (version 1.0.0)

--- name: eslint-config-generator description: Generate optimal ESLint configurations based on project type, framework, and team preferences — flat config format, plugin selection, and rule tuning. metadata: tags: ["eslint", "javascript", "typescript", "linting", "code-quality"] --- # ESLint Config Generator Generate optimal ESLint flat configurations based on project analysis. Detects framework, TypeScript usage, and coding patterns to recommend plugins, rules, and presets. Handles migration from legacy .eslintrc to flat config format. ## Usage ``` "Generate ESLint config for my project" "Migrate my .eslintrc to flat config" "Recommend ESLint plugins for my React TypeScript project" "Audit my ESLint rules for conflicts" ``` ## How It Works ### 1. Project Analysis ```bash cat package.json | python3 -c " import json,sys d=json.load(sys.stdin) deps = {**d.get('dependencies',{}), **d.get('devDependencies',{})} for fw in ['react','vue','svelte','angular','next','nuxt','astro','express','fastify']: if fw in deps: print(f'Framework: {fw}') if 'typescript' in deps: print('TypeScript: yes') for plugin in [k for k in deps if 'eslint' in k.lower()]: print(f'ESLint plugin: {plugin}') " ``` ### 2. Configuration Generation Based on detected project type, generate flat config with: - Language parser (TypeScript, JSX, Vue SFC) - Framework-specific plugins and rules - Import sorting and validation - Accessibility rules for UI frameworks - Testing library rules if test framework detected - Prettier compatibility (if Prettier is used) ### 3. Rule Optimization - Remove conflicting rules - Tune strictness level (recommended → strict → custom) - Add project-specific ignores - Configure globals and environments - Set up overrides for test files and config files ### 4. Migration Support Convert legacy .eslintrc.json/.eslintrc.js to flat config: - Map extends to imports - Convert overrides to config array entries - Update plugin references to new format - Handle env/globals changes ## Output ``` ## ESLint Configuration Generated **Project:** React + TypeScript + Vitest **Format:** Flat config (eslint.config.mjs) ### Generated Config - TypeScript parser with type-aware linting - React plugin with hooks rules - Import plugin with TypeScript resolver - Vitest plugin for test files - Prettier compatibility (no conflicting rules) ### Plugin Recommendations ✅ @typescript-eslint — type-aware linting ✅ eslint-plugin-react — React best practices ✅ eslint-plugin-react-hooks — hooks rules ✅ eslint-plugin-import-x — import order + validation 🟡 eslint-plugin-jsx-a11y — accessibility (recommended) ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 58/nanning (version 1.0.0)

--- name: nanning version: 1.0.0 description: 全面介绍南宁市的技能包：景点、美食、交通、文化、购物、宜居信息一网打尽。南宁被称为"绿城"，是广西壮族自治区首府。 homepage: https://clawhub.ai metadata: openclaw: emoji: "🏙️" requires: bins: [] --- # Nanning 技能包 ## 简介 Nanning（南宁）是广西壮族自治区首府，被誉为"绿城"。这是一个全面的南宁市信息查询技能包，帮助用户了解南宁的方方面面——从旅游景点到地道美食，从交通出行到文化习俗，是您探索这座中国南部宜居城市的一站式助手。 ## 功能特点 - **景点推荐**：青秀山、南湖公园、扬美古镇等知名景点详细介绍 - **美食指南**：老友粉、柠檬鸭、卷筒粉等南宁特色美食推荐 - **交通信息**：机场、火车站、地铁、公交等出行指南 - **文化介绍**：壮族文化、博览会历史、民俗节庆 - **购物指南**：朝阳广场、万象城、会展中心商圈 - **宜居指南**：气候特点、房价水平、教育医疗资源 - **实时查询**：获取最新城市信息和实用建议 ## 使用场景 1. **旅游规划**：查询南宁必游景点和最佳路线 2. **美食探索**：寻找地道的南宁特色小吃和餐厅 3. **商务出行**：了解会展中心、会议场地和交通安排 4. **定居咨询**：了解南宁的生活成本、教育医疗资源 5. **文化体验**：探索壮族文化和地方节庆活动 6. **周末休闲**：发现适合一日游的周边目的地 ## 命令用法 ### 景点查询 ``` nanning spots [关键词] nanning attractions [关键词] ``` 查询南宁主要景点信息，支持按类型筛选（自然风光、历史古迹、主题公园等） ### 美食推荐 ``` nanning food [类型] nanning food --popular ``` 搜索南宁特色美食，--popular 显示人气榜单 ### 交通指南 ``` nanning transport nanning metro nanning airport ``` 获取机场、火车站、地铁、公交等交通信息 ### 文化介绍 ``` nanning culture nanning festivals nanning history ``` 了解南宁的历史文化、民俗节庆 ### 购物指南 ``` nanning shopping nanning malls ``` 推荐南宁主要商圈和购物中心 ### 宜居信息 ``` nanning living nanning weather nanning cost ``` 查询气候、生活成本、教育医疗等宜居信息 ### 实用信息 ``` nanning info nanning help ``` 显示所有可用命令和帮助信息 ## 南宁简介 ### 城市定位 - **广西壮族自治区首府** - **北部湾经济区核心城市** - **中国-东盟博览会永久举办地** ### 别称美誉 - **绿城**：城市绿化覆盖率极高，满城绿意盎然 - **邕城**：因邕江穿城而过而得名 ### 地理概况 - 位于广西南部，邕江沿岸 - 亚热带季风气候，夏长冬短 - 总面积约2.21万平方公里 - 常住人口约900万 ### 著名地标 - **青秀山**：国家5A级景区，绿城绿肺 - **南湖公园**：市区内综合性公园 - **广西民族博物馆**：展示壮族文化 - **会展中心**：中国-东盟博览会会场 ### 特色美食 - **老友粉**：南宁最具代表性的特色小吃 - **柠檬鸭**：武鸣地区的特色菜 - **卷筒粉**：越南风味的南宁街头美食 - **酸嘢**：酸味腌渍蔬果小吃 ### 交通枢纽 - **吴圩国际机场**：4E级国际机场 - **南宁站/南宁东站**：高铁枢纽 - **地铁**：已开通多条线路 ## 技术栈 - Node.js - JavaScript (ES6+) - 模块化架构设计 ## 相关资源 - 中国-东盟博览会官网 - 南宁旅游网 - 广西文化和旅游厅 ## 许可证 MIT License


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 52yuanchangxing/metric-definition-catalog (version 1.0.0)

--- name: metric-definition-catalog version: 1.0.0 description: "把散落指标统一整理成口径、公式、归属、例外情况与常见误用。；use for metrics, catalog, analytics workflows；do not use for 编造指标来源, 替代 BI 平台配置." author: OpenClaw Skill Bundle homepage: https://example.invalid/skills/metric-definition-catalog tags: [metrics, catalog, analytics, governance] user-invocable: true metadata: {"openclaw":{"emoji":"📐","requires":{"bins":["python3"]},"os":["darwin","linux","win32"]}} --- # 指标定义目录官 ## 你是什么 你是“指标定义目录官”这个独立 Skill，负责：把散落指标统一整理成口径、公式、归属、例外情况与常见误用。 ## Routing ### 适合使用的情况 - 整理这批指标定义 - 统一口径和计算方式 - 输入通常包含：指标列表、定义片段、计算方式 - 优先产出：指标目录、口径定义、维护建议 ### 不适合使用的情况 - 不要编造指标来源 - 不要替代 BI 平台配置 - 如果用户想直接执行外部系统写入、发送、删除、发布、变更配置，先明确边界，再只给审阅版内容或 dry-run 方案。 ## 工作规则 1. 先把用户提供的信息重组成任务书，再输出结构化结果。 2. 缺信息时，优先显式列出“待确认项”，而不是直接编造。 3. 默认先给“可审阅草案”，再给“可执行清单”。 4. 遇到高风险、隐私、权限或合规问题，必须加上边界说明。 5. 如运行环境允许 shell / exec，可使用： - `python3 "{baseDir}/scripts/run.py" --input <输入文件> --output <输出文件>` 6. 如当前环境不能执行脚本，仍要基于 `{baseDir}/resources/template.md` 与 `{baseDir}/resources/spec.json` 的结构直接产出文本。 ## 标准输出结构 请尽量按以下结构组织结果： - 指标目录 - 口径定义 - 计算方式 - 不适用场景 - 常见误用 - 维护建议 ## 本地资源 - 规范文件：`{baseDir}/resources/spec.json` - 输出模板：`{baseDir}/resources/template.md` - 示例输入输出：`{baseDir}/examples/` - 冒烟测试：`{baseDir}/tests/smoke-test.md` ## 安全边界 - 默认把冲突定义并排列出，避免强行合并。 - 默认只读、可审计、可回滚。 - 不执行高风险命令，不隐藏依赖，不伪造事实或结果。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: jgf78/calendar-local (version 1.0.0)

--- name: calendar-local description: Read Google Calendar from the local host using the configured gog wrapper. Use when the user asks for their agenda, calendar events, today's schedule, this week's events, upcoming appointments, or calendar summaries on this OpenClaw host. Applies to direct chats including Telegram when the runtime has access to /home/ubuntu/.openclaw/workspace/.openclaw/calendar.sh and GOG_KEYRING_PASSWORD is present in the service environment. --- # Calendar Local Use the local wrapper instead of generic calendar advice. ## Commands Run the wrapper with an explicit timeframe: ```bash /home/ubuntu/.openclaw/workspace/.openclaw/calendar.sh today /home/ubuntu/.openclaw/workspace/.openclaw/calendar.sh week /home/ubuntu/.openclaw/workspace/.openclaw/calendar.sh days 7 ``` The wrapper already targets the correct Google account and gog binary. It requires `GOG_KEYRING_PASSWORD` in the runtime environment. ## Workflow 1. Run the wrapper with the matching timeframe. 2. If the user asked for **today**, use `today`. 3. If the user asked for **this week**, use `week`. 4. If the user asked for **the next few days**, use `days N`. 5. Summarize results in natural language. 6. If no events match, say so plainly. 7. Do not tell the user to configure OAuth again unless the wrapper fails. ## Failure handling If the wrapper fails: - If output mentions `GOG_KEYRING_PASSWORD is not set`, explain that the OpenClaw service is missing the keyring password in its environment. - If output mentions keyring unlock/auth errors, explain that the local Google token/keyring is unavailable or locked. - Only then fall back to setup guidance. ## Output style - Be concise. - Prefer grouped agenda summaries. - Separate all-day items, timed events, and birthdays/tasks when useful.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: simoncai519/alibaba-store-analysis (version 1.0.0)

--- name: alibaba-store-analysis description: Alibaba International Station weekly business report analysis skill. Retrieves store weekly report data via browser session, validates, and presents structured diagnostics with on-demand deep report access. version: "1.0.0" --- # Alibaba Store Analysis Skill ## Overview This skill automates the retrieval and analysis of Alibaba International Station weekly business reports. It logs in via a browser, pulls summary data, validates it, displays key metrics and diagnostics, and optionally fetches the full report for on‑demand queries. ## Core Workflow (high‑level) 1. **Login Check** – Open `https://i.alibaba.com/`. If redirected to the login page, prompt the user to log in and wait until the session is authenticated. 2. **Fetch Summary Data** – Call `diagnoseData.json` API and obtain `encryptedReportId`, `receipt` and diagnostic arrays. 3. **Validate Data** – Silent checks for empty response, missing `encryptedReportId` or `receipt`. On failure, display a friendly fallback message and stop. 4. **Display Summary** – Render four sections in one output: - Store data overview (metrics table) - Diagnostic summary text - Merchant task list - Link to the weekly report using `encryptedReportId`. 5. **Full Report Retrieval** – Using the `receipt` token, call `queryWeekReportAllData.json` to obtain the detailed report. Validate silently; on success announce *"Full data analysis complete. Feel free to ask me any questions about your store data!"* and wait for user queries. ## Usage ```sh openclaw run alibaba-store-analysis ``` The skill will guide the user through any required login steps and then output the analysis automatically. For the complete step‑by‑step workflow, API payloads, error handling and module explanations, see `references/workflow.md`. --- **Created by [Simon Cai](https://github.com/simoncai519) · More e-commerce skills: [github.com/simoncai519/open-accio-skill](https://github.com/simoncai519/open-accio-skill)**


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: leooooooow/creator-followup-sequence (version 0.1.0)

--- name: creator-followup-sequence description: Write short, human follow-up messages for creator outreach when the first message gets ignored, delayed, or half-answered. Use when the user needs second-touch or third-touch outreach that revives the conversation without sounding needy, spammy, or generic. --- # Creator Followup Sequence ## Skill Card - **Category:** Creator Acquisition - **Core problem:** How to follow up with creators after no reply without sounding annoying or robotic? - **Best for:** Affiliate recruiting, UGC sourcing, partnership outreach, and creator pipeline recovery. - **Expected input:** Original outreach, creator context, offer angle, time since first touch, desired next step. - **Expected output:** 2-4 follow-up message options with timing logic, angle shifts, and stop rules. - **Creatop handoff:** Store winning follow-up patterns inside outreach SOPs and CRM templates. ## Workflow 1. Diagnose the conversation state. - no reply after first touch - warm but vague reply - interested then stalled - timing objection - likely low fit / low priority 2. Identify the most likely reason for silence. 3. Choose the best follow-up angle. - light bump - value bump - clarity bump - proof bump - polite close-the-loop 4. Draft a short sequence with escalating clarity, not escalating pressure. 5. Add timing guidance and stop rules. ## Output format Return in this order: 1. Outreach status diagnosis 2. Best follow-up angle to use now 3. Follow-up sequence (message 1 / message 2 / final check-in) 4. Timing recommendation 5. Stop / no-chase rule ## Quality and safety rules - Keep each message short and easy to answer from a phone. - Add new value, clearer context, or a smaller ask in each follow-up. - Do not guilt-trip, pressure, or fake urgency. - Do not invent proof, budgets, or performance claims. - If the creator appears unqualified or uninterested, recommend stopping. ## License Copyright (c) 2026 **Razestar**. This skill is provided under **CC BY-NC-SA 4.0** for non-commercial use. You may reuse and adapt it with attribution to Razestar, and share derivatives under the same license. Commercial use requires a separate paid commercial license from **Razestar**. No trademark rights are granted.

path: references/output-template.md
content: # Output Template

## 1) Outreach status diagnosis
- Current state:
- Likely reason for silence:
- Confidence:

## 2) Best angle to use now
- Recommended angle:
- Why this angle fits:

## 3) Follow-up sequence
### Follow-up 1

### Follow-up 2

### Final check-in

## 4) Timing recommendation
- Delay before next touch:
- Channel note:

## 5) Stop rule
- Stop after:
- Re-entry condition:


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

--- name: gate-mcp-skill description: Use Gate MCP through UXC for public spot and futures market data workflows with a fixed streamable-http endpoint and read-first guardrails. --- # Gate MCP Skill Use this skill to run Gate public market data workflows through `uxc` + MCP. Reuse the `uxc` skill for shared MCP execution, output parsing, and generic auth guidance. ## Prerequisites - `uxc` is installed and available in `PATH`. - Network access to `https://api.gatemcp.ai/mcp`. ## Scope This skill covers the official Gate MCP surface for: - public spot market discovery - public spot tickers, trades, order books, and candlesticks - public futures contracts, tickers, trades, order books, funding, and premium data This skill does **not** cover: - private account or trading workflows - Gate REST v4 signed APIs - wallet, funding, or portfolio actions ## Endpoint Use Gate's official MCP endpoint: - `https://api.gatemcp.ai/mcp` ## Core Workflow 1. Use the fixed link command by default: - `command -v gate-mcp-cli` - If missing, create it: `uxc link gate-mcp-cli https://api.gatemcp.ai/mcp` - `gate-mcp-cli -h` 2. Inspect tool and argument help before execution: - `gate-mcp-cli cex_spot_get_spot_tickers -h` - `gate-mcp-cli cex_spot_get_spot_order_book -h` - `gate-mcp-cli cex_fx_get_fx_tickers -h` - `gate-mcp-cli cex_fx_get_fx_order_book -h` 3. Prefer narrow spot or futures reads with explicit instrument identifiers: - `gate-mcp-cli cex_spot_get_spot_tickers currency_pair=BTC_USDT` - `gate-mcp-cli cex_spot_get_spot_order_book currency_pair=BTC_USDT limit=20` - `gate-mcp-cli cex_fx_get_fx_tickers contract=BTC_USDT` - `gate-mcp-cli cex_fx_get_fx_funding_rate contract=BTC_USDT` ## Operations ### Spot - `cex_spot_list_currencies` - `cex_spot_list_currency_pairs` - `cex_spot_get_currency` - `cex_spot_get_currency_pair` - `cex_spot_get_spot_tickers` - `cex_spot_get_spot_order_book` - `cex_spot_get_spot_trades` - `cex_spot_get_spot_candlesticks` ### Futures - `cex_fx_list_fx_contracts` - `cex_fx_get_fx_contract` - `cex_fx_get_fx_tickers` - `cex_fx_get_fx_order_book` - `cex_fx_get_fx_trades` - `cex_fx_get_fx_candlesticks` - `cex_fx_get_fx_funding_rate` - `cex_fx_get_fx_premium_index` - `cex_fx_list_fx_liq_orders` ## Guardrails - Keep automation on the JSON output envelope; do not use `--text`. - Parse stable fields first: `ok`, `kind`, `protocol`, `data`, `error`. - Treat this v1 skill as read-only. - Prefer `currency_pair` values like `BTC_USDT` for spot and `contract` values like `BTC_USDT` for futures unless help output indicates a different contract name. - `gate-mcp-cli <operation> ...` is equivalent to `uxc https://api.gatemcp.ai/mcp <operation> ...`. ## References - Usage patterns: `references/usage-patterns.md` - Official Gate for AI / MCP docs: https://www.gate.com/gate-mcp-skills - Gate MCP setup article: https://www.gate.com/ru/help/gateforai/gateforaibasics/50102/gate-for-ai-one-click-integration-with-major-ai-agents-no-api-keys-required-zero-barriers


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: dwhite-oss/openphone (version 1.0.0)

--- name: openphone description: Manage business phone calls, SMS, and contacts via OpenPhone API. Use when asked to send a text message, list calls or messages, look up conversation history with a contact, get voicemail transcripts, list phone numbers, or check call recordings. Requires OPENPHONE_API_KEY env var. --- # OpenPhone Skill OpenPhone REST API base: `https://api.openphone.com/v1` ## Auth ```bash curl -H "Authorization: $OPENPHONE_API_KEY" \ -H "Content-Type: application/json" \ https://api.openphone.com/v1/... ``` ## Phone Numbers ### List Your Phone Numbers ```bash curl "https://api.openphone.com/v1/phone-numbers" \ -H "Authorization: $OPENPHONE_API_KEY" # Save phoneNumberId for sending messages/calls ``` ## Contacts ### Search Contacts ```bash curl "https://api.openphone.com/v1/contacts?query=John+Smith" \ -H "Authorization: $OPENPHONE_API_KEY" ``` ### Create Contact ```bash curl -X POST "https://api.openphone.com/v1/contacts" \ -H "Authorization: $OPENPHONE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "firstName": "Jane", "lastName": "Smith", "phoneNumbers": [{"number": "+15551234567"}], "emails": [{"address": "[REDACTED_SECRET]"}], "company": "Acme Corp" }' ``` ## Messages (SMS/MMS) ### Send SMS ```bash curl -X POST "https://api.openphone.com/v1/messages" \ -H "Authorization: $OPENPHONE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "from": "<phoneNumberId>", "to": ["+15551234567"], "content": "Hi Jane, following up on our conversation earlier!" }' ``` ### List Messages (Conversation History) ```bash curl "https://api.openphone.com/v1/messages?phoneNumberId=<id>&participants[]=+15551234567&maxResults=20" \ -H "Authorization: $OPENPHONE_API_KEY" ``` ## Calls ### List Calls ```bash curl "https://api.openphone.com/v1/calls?phoneNumberId=<id>&maxResults=20" \ -H "Authorization: $OPENPHONE_API_KEY" ``` ### Get Call Details (Recording + Transcript) ```bash curl "https://api.openphone.com/v1/calls/<call_id>" \ -H "Authorization: $OPENPHONE_API_KEY" # Response includes: recordingUrl, transcript (if enabled), duration, direction ``` ### List Voicemails ```bash curl "https://api.openphone.com/v1/calls?type=voicemail&phoneNumberId=<id>" \ -H "Authorization: $OPENPHONE_API_KEY" ``` ## Call Directions `incoming`, `outgoing` ## Message Status Values `queued`, `sending`, `delivered`, `failed`, `received` ## Tips - `phoneNumberId` starts with `PN` — always list phone numbers first - Transcripts require call recording to be enabled in workspace settings - Rate limit: 60 req/min; batch message sends in loops with brief delays


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: drivenbymyai-max/soulledger-trust (version 1.0.0)

--- name: soulledger-trust description: Query AI agent trust scores, behavioral DNA, and identity verification via SoulLedger protocol user-invocable: true metadata: {"openclaw":{"requires":{"env":[]}},"homepage":"https://soulledger.sputnikx.xyz","author":"SputnikX","version":"1.0.0","tags":["trust","identity","agent","verification","base-chain"]} --- # SoulLedger Trust Scoring Query trust scores, behavioral DNA, and hash-chain verified identity for AI agents. 13 registered agents with computed trust from 5 weighted factors. ## Base URL `https://soul.sputnikx.xyz` ## Endpoints ### Get Trust Score (free) ```bash curl https://soul.sputnikx.xyz/soul/{agent_id}/trust ``` Returns: `{ agent_id, trust_score, factors }` — 5-factor breakdown (consistency, accuracy, reliability, responsiveness, collaboration). ### Get Behavioral DNA (free) ```bash curl https://soul.sputnikx.xyz/soul/{agent_id}/dna ``` Returns: 7-dimensional profile (autonomy, curiosity, precision, speed, collaboration, resilience, creativity). ### Get Agent Directory (free) ```bash curl https://soul.sputnikx.xyz/soul/directory ``` Returns: All registered agents with trust scores, DNA, passport hashes, event counts. ### Register Your Agent (free) ```bash curl -X POST https://soul.sputnikx.xyz/soul/register \ -H "Content-Type: application/json" \ -d '{"agent_id":"my-agent","display_name":"My Agent","issue_api_key":true}' ``` Returns: SX# passport + API key. First 1M passports free. ### Verify Chain Integrity ($0.10 x402 USDC) Hash-chain verification — every event cryptographically linked, Merkle roots anchored on Base chain. ## SDK ```bash npm install @sputnikx/soulledger-sdk ``` ```javascript import { SoulLedger } from '@sputnikx/soulledger-sdk'; const sl = new SoulLedger(); const trust = await sl.getTrust('oracle'); ``` ## When to use this skill - Verify if an AI agent is trustworthy before interacting - Check behavioral patterns and consistency of other agents - Register your agent to build verifiable reputation - Audit agent identity via hash-chain verification


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: quweilin/qwtest1 (version 1.0.1)

--- name: Chat Project description: "简易聊天模式输入数字回复对应内容" metadata: --- # 交互式对话系统技能 ## 技能信息 - **名称**: 交互式对话系统 - **版本**: 1.0.0 - **分类**: 娱乐互动 - **描述**: 一个简单的交互式对话系统，根据用户输入数字返回预设问候语 ## 功能说明 本技能提供基础的交互式对话功能，用户输入对应数字可获得预设回复。 ## 使用方法 ``` 运行技能后根据提示输入数字选择对话内容 ``` 示例: ``` 输入 1 -> 输出 '你好呀' 输入 2 -> 输出 '今天天气怎么样' 输入 3 -> 输出 '很高兴认识你' ``` ## 参数说明 - `input`: 数字输入(1/2/3)对应不同回复 ## 返回信息 - 预设的友好问候语句 ## 注意事项 - 仅支持数字1、2、3作为有效输入 - 输入其他内容会提示重新输入 - 输入'q'可退出程序


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: wondershare-boop/mediaio-google-veo-video-generator (version 1.0.1)

````skill --- name: mediaio-google-veo-video-generator description: "Generate AI videos using Google Veo (Veo 3 / Veo 3.1) via Media.io OpenAPI. Produces cinematic-quality video from text and image inputs." metadata: {"mediaio": {"emoji": "", "requires": {"env": ["API_KEY"]}, "priority": "P0", "core_goal_keywords": ["text-to-video", "image-to-video"], "trigger_keywords": ["Google Veo", "Veo 3.1", "Veo video generator", "Veo 3"]}, "publisher": "Community Maintainer", "source": "https://platform.media.io/docs/"} --- # Google Veo AI Video Generator ## Overview This skill focuses on a single model family and calls Media.io OpenAPI via `Skill.invoke(api_name, params, api_key)`. It includes only common APIs (`Credits`, `Task Result`) plus model-specific APIs for this skill. ## Core Trigger Keywords Google Veo, Veo 3.1, Veo video generator, Veo 3 ## Core Goal Keywords text-to-video, image-to-video ## Environment Variable - `API_KEY` (required): Media.io OpenAPI key used as `X-API-KEY`. ## Quick Start ```python import os from scripts.skill_router import Skill skill = Skill('scripts/c_api_doc_detail.json') [REDACTED_SECRET]'API_KEY', '') result = skill.invoke('Credits', {}, [REDACTED_SECRET]) print(result) ``` ## Available APIs - `Credits` (`user-credits`) - `Task Result` (`generation-result`) - `Google Veo 3.1` (`i2v-veo-v3-1`) - `Google Veo 3.1 Fast` (`i2v-veo-v3-1-fast`) ## Notes - Use exact `api_name` from `scripts/c_api_doc_detail.json` when invoking. - Generation APIs return `task_id`; poll with `Task Result`. ````


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