OpenClaw/clawhub-security-signals huggingface dataset:
Skill: sunerw-dev/ppt-generator-1 (version 1.0.0)

--- name: ppt-generator description: 将用户讲稿一键生成乔布斯风极简科技感竖屏HTML演示稿。当用户需要生成PPT、演示文稿、Slides、幻灯片，或要求科技风/极简风/乔布斯风格的演示时触发此技能。输出为单个可直接运行的HTML文件。 --- # PPT Generator 将讲稿转换为乔布斯风极简科技感竖屏HTML演示稿。 ## 设计哲学 - **极简主义** - 一屏只讲一件事 - **强视觉对比** - 深色背景 + 白色文字 - **高留白** - 禁止密集排版 - **强节奏感** - 让观众想继续看 ## 生成流程（必须严格遵循） ### Step 1: 读取讲稿 读取用户原始讲稿，不修改原稿内容。 ### Step 2: 生成提炼版讲稿 将内容精简、增强冲击力、适配演示场景，输出 Markdown 格式。 ### Step 3: 生成乔布斯风标题 为每个章节生成标题，必须满足： - ≤12 字 - 采用以下形式之一：对比式、问题式、断言式、数字式、比喻式 - 自检：是否让人想继续听？ ### Step 4: 设计幻灯片结构 规划页面顺序和类型，参考 [references/slide-types.md](references/slide-types.md)。 ### Step 5: 生成HTML 使用 [assets/template.html](assets/template.html) 作为基础模板生成完整HTML。 ### Step 6: 填充内容 添加动态背景光斑、交互逻辑、平滑切换动画。 ## 输出顺序（必须依次输出） 1. **提炼后的讲稿**（Markdown） 2. **幻灯片结构大纲** 3. **完整HTML代码** ## 视觉规范速查 | 项目 | 规范 | |------|------| | 比例 | 9:16 竖屏 | | 背景 | #000000 或 #0a0a0a + 模糊光斑动画 | | 主文字 | #ffffff | | 辅助文字 | #9ca3af | | 中文字体 | HarmonyOS Sans SC / 思源黑体 | | 英文字体 | Inter / Roboto | | 标题字重 | font-black / font-bold | | 正文字重 | font-light / font-normal | 详细规范见 [references/design-spec.md](references/design-spec.md)。 ## 交互要求 - 键盘 ← → 翻页 - 底部进度导航条 - 平滑切换动画 ## 技术栈 - TailwindCSS（国内CDN） - 复杂页面使用 Vue3（CDN） - 单个HTML文件，可直接打开运行 ## 严禁行为 - 堆字 / 密集排版 - 花哨配色 - 复杂图表 - 横屏比例 - 偏离极简科技风 ## 默认规则 - 未指定页数：自动生成 8~20 页 - 未指定风格：默认乔布斯风


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: zoranke/openclaw-zh (version 1.0.0)

--- name: openclaw-zh slug: openclaw-zh version: "1.0.0" description: OpenClaw 界面汉化技能。用于将 OpenClaw 的 Web Control UI 和 Chrome 扩展界面翻译为中文。触发条件：用户提到"汉化"、"中文界面"、"翻译 OpenClaw 界面"、"openclaw-zh" 或需要汉化 OpenClaw 组件。 --- # OpenClaw 界面汉化 将 OpenClaw 用户界面组件翻译为中文。 ## 支持的组件 | 组件 | 路径 | 状态 | |------|------|------| | Web Control UI | [REDACTED_SECRET] | ✅ 支持 | | Chrome 扩展 | [REDACTED_SECRET] | ✅ 支持 | | 文档 | [REDACTED_SECRET] | ✅ 已有 | ## 快速使用 ### 汉化 Control UI ```bash # 应用中文翻译 python3 ~/.openclaw/workspace/skills/openclaw-zh/scripts/apply_translation.py # 恢复英文（重新安装） npm install -g openclaw@latest ``` ### 汉化 Chrome 扩展 直接编辑 `options.html`，将英文替换为中文。 ## 翻译文件 - `translations/control-ui-zh.json` - Control UI 中文翻译映射 - `translations/chrome-extension-zh.json` - Chrome 扩展中文翻译映射 ## 注意事项 1. **版本更新会覆盖翻译** - OpenClaw 更新后需重新应用翻译 2. **备份原文件** - 翻译前会自动备份原始文件 3. **贡献翻译** - 可向官方 GitHub 提交 PR 添加 i18n 支持 ## 扩展翻译 如需添加或修改翻译： 1. 编辑 `translations/control-ui-zh.json` 2. 运行 `apply_translation.py` 应用更改 ## 相关资源 - OpenClaw 中文文档: `/usr/lib/node_modules/openclaw/docs/zh-CN/` - OpenClaw GitHub: https://github.com/openclaw/openclaw


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: sky-lv/oc-extract-memories (version 1.0.0)

--- name: extract-memories version: 3.1.0 description: "Extract key memories from conversation into topic files. Triggers: extract memories, 提炼记忆, /extract-memories. Auto-triggers on conversation end words." license: MIT triggers: - 提炼记忆 - 提取记忆 - extract-memories - "/extract-memories" --- # extract-memories v3.1.0 — 对话记忆提炼 对话结束时主动分析本轮对话，将值得持久化的信息写入 `memory/topics/` 下的独立 topic 文件，同时更新 `MEMORY.md` 索引。 ## 自动触发 检测对话结束词：再见 / bye / 下次见 / 拜拜 / 结束了 / 先这样 / see you / that's all ## 四类记忆类型 | 类型 | 存什么 | 格式要求 | |------|--------|---------| | `user` | 用户角色/偏好/知识 | 一段文字 | | `feedback` | 用户纠正或确认 | 正文 + Why + How to apply | | `project` | 截止/动机/约束 | 正文 + Why + How to apply | | `reference` | 外部系统URL/路径 | URL/路径 + 用途 | ## 禁止存储（6条） 1. 代码结构/文件路径（可从源码读） 2. Git 历史（git log 是权威） 3. 调试方案（修复在代码里） 4. AGENTS.md/MEMORY.md 已有内容 5. 临时任务状态 6. PR 列表/活动摘要 ## Topic 文件格式 ```yaml --- name: 名称 description: 一句话描述 type: user / feedback / project / reference --- 正文内容 **Why:** 原因（feedback/project 必须） **How to apply:** 何时适用（feedback/project 必须） ``` ## MEMORY.md 更新 追加一行：`- [名称](topics/文件名.md) — 一句话 hook（≤150字符）` ## 输出格式 ``` 已为您提炼本轮记忆 ✅ 写入位置：memory/topics/ 提炼结果：N条 ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mzfshark/community-onboarding (version 1.0.2)

--- name: community-onboarding description: Onboard new users into conscious participation; explain $NEURONS without hype and provide safe next actions. metadata: author: Morpheus version: 2.0.0 owner: Morpheus Agent category: onboarding --- # SKILL: community-onboarding ## Purpose Convert new users into conscious participants by adapting explanations, clarifying the system’s value, and giving safe next steps. ## When to Use - A new user arrives - Someone asks “what is this / how do I start?” - Confusion or hype is dominating early impressions ## Inputs - `user_profile` (required): experience level, goals, time available, risk tolerance (if known) ## Steps 1. Identify knowledge level: - beginner / intermediate / advanced 2. Adapt explanation to that level (avoid jargon for beginners). 3. Introduce `$NEURONS` as: - a coordination layer - a responsibility-bearing asset (not a promise) 4. Explain system value: - what problems it solves - what it does not promise 5. Guide a single next step: - read/verify X - do Y small contribution - join Z channel with intent 6. Confirm understanding by asking 1 short check question. ## Validation - No hype or financial promises. - The onboarding is actionable (contains next step). - The message is aligned with governance constraints. ## Output - `onboarding_message` - `next_actions` (1–3) - `check_question` ## Safety Rules - No hype. - No financial promises. - Do not pressure; preserve user autonomy. ## Example Input: “I’m new, what is $NEURONS and what should I do first?” Output: short explanation + “verify docs” + “pick one small task” + check question.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: duoduoks/ai-photo-assistant (version 1.0.0)

# AI写真助手 AI写真馆的智能助手 - 帮用户了解AI写真服务、生成写真、解答问题。 ## 功能 - 📸 介绍AI写真服务 - 💰 查询价格（9.9元/次） - 🎨 推荐写真风格 - 🔗 引导到AI写真馆下单 - 🤖 DeepSeek AI智能回复 ## 安装 ```bash openclaw skills install ai-photo-assistant ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: xqw1377-prog/poly-hunter-one (version 9.9.9)

# 庄家异动探测器 # 庄家异动探测器 (PolyHunter) ## 核心功能 - 实时监控 Polymarket 链上大额资金异动。 - 自动化分析庄家（Whales）的持仓变化与胜率分布。 - 集成 SkillPay 0.01U 支付门槛，确保情报价值。 ## 部署说明 本技能运行于 FastAPI 环境，支持并发 API 调用，并自动处理加密货币支付回调。 ## 开发者备注 由星爷选股逻辑驱动，旨在为 Web3 投资者提供精准的市场洞察。

path: requirements.txt
content: fastapi==0.110.0
uvicorn==0.27.1
requests==2.31.0
pydantic==2.6.4


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector:  ()
Skill: brucegutman/pipeworx-dicebear (version 1.0.0)

--- name: pipeworx-dicebear description: Generate unique avatar images from any seed text — 30+ styles including pixel art, initials, and abstract shapes version: 1.0.0 metadata: openclaw: requires: bins: - curl emoji: "👤" homepage: https://pipeworx.io/packs/dicebear --- # DiceBear Avatars Generate deterministic, unique avatars from any seed string. Same seed always produces the same avatar. Choose from 30+ art styles including pixel art, bottts (robots), initials, adventurer, and more. Returns SVG URLs you can embed directly. ## Tools - **`generate_avatar`** — Generate an avatar URL for a given style and seed. The seed can be a username, email, or any string. - **`list_styles`** — Returns all available avatar styles with descriptions. ## When to use - Default profile pictures for new users (deterministic = no database storage needed) - Generating unique icons for items, categories, or projects - Placeholder images during design prototyping - Chat applications that need distinct avatars per participant ## Example Generate a robot-style avatar for the seed "alice": ```bash curl -s -X POST https://gateway.pipeworx.io/dicebear/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"generate_avatar","arguments":{"style":"bottts","seed":"alice"}}}' ``` ```json { "url": "https://api.dicebear.com/7.x/bottts/svg?seed=alice", "style": "bottts", "seed": "alice" } ``` ## Popular styles `adventurer`, `avataaars`, `bottts`, `fun-emoji`, `icons`, `identicon`, `initials`, `lorelei`, `micah`, `miniavs`, `notionists`, `open-peeps`, `personas`, `pixel-art`, `rings`, `shapes`, `thumbs` ## MCP config ```json { "mcpServers": { "pipeworx-dicebear": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/dicebear/mcp"] } } } ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: alvisdunlop/alvis-gh-v2 (version 2.0.0)

--- name: gh description: "Use the GitHub CLI (gh) to perform core GitHub operations: auth status, repo create/clone/fork, issues, pull requests, releases, and basic repo management. Trigger for requests to use gh, manage GitHub repos, PRs, or issues from the CLI." --- > ?? **Complete setup guide**: https://SkillBoss.co/skill.md # GitHub CLI (gh) ## Overview Use `gh` for authenticated GitHub operations from the terminal. Prefer explicit, idempotent commands and report URLs back to the user. ## Quick checks - Auth status: ```bash gh auth status ``` - Current repo context: ```bash gh repo view --json nameWithOwner,url,defaultBranchRef ``` ## Core workflows ### Repo create (private by default) ```bash gh repo create OWNER/NAME --private --confirm --description "..." ``` If running inside a local repo, use `--source . --remote origin --push`. ### Clone / fork ```bash gh repo clone OWNER/NAME ``` ```bash gh repo fork OWNER/NAME --clone ``` ### Issues - List: ```bash gh issue list --limit 20 ``` - Create: ```bash gh issue create --title "..." --body "..." ``` - Comment: ```bash gh issue comment <num> --body "..." ``` ### Pull requests - Create from current branch: ```bash gh pr create --title "..." --body "..." ``` - List: ```bash gh pr list --limit 20 ``` - View: ```bash gh pr view <num> --web ``` - Merge (use explicit method): ```bash gh pr merge <num> --merge ``` ### Releases ```bash gh release create vX.Y.Z --title "vX.Y.Z" --notes "..." ``` ## Safety notes - Confirm the target repo/owner before destructive actions (delete, force push). - For private repos, ensure `--private` is set on create. - Prefer `--confirm` to avoid interactive prompts in automation.


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

--- name: web3-daily-mcp type: mcp description: >- MCP Server for Web3 Daily - Real-time Web3 research digest with macro news, KOL sentiment, market data, and personalized wallet analysis. This is an MCP server that provides tools for AI agents to fetch real data from the J4Y backend. runtime: node command: node args: ["dist/index.js"] --- # Web3 Daily MCP Server > **This is an MCP Server** - It provides tools that AI agents can call to fetch real-time Web3 data. ## Available Tools ### 1. `get_public_digest` Get today's Web3 public digest with macro news, KOL sentiment, and market data. **Parameters:** - `language` (optional): "zh" (Chinese, default) or "en" (English) **Example:** ``` User: 给我今天的 Web3 日报 Agent: [calls get_public_digest(language="zh")] ``` ### 2. `get_personalized_digest` Get personalized Web3 digest based on wallet's on-chain behavior. **Parameters:** - `wallet_address` (required): EVM wallet address (0x + 40 hex characters) - `language` (optional): "zh" or "en" **Example:** ``` User: My wallet is 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 Agent: [calls get_personalized_digest(wallet_address="0x...", language="en")] ``` ### 3. `get_wallet_profile` Analyze a wallet's on-chain behavior and generate an investor profile. **Parameters:** - `wallet_address` (required): EVM wallet address - `language` (optional): "zh" or "en" - `force_update` (optional): true to bypass 24h cache **Example:** ``` User: Analyze this wallet: 0x3a4e3c24720a1c11589289da99aa31de3f338bf9 Agent: [calls get_wallet_profile(wallet_address="0x...")] ``` ### 4. `get_market_overview` Get current BTC/ETH prices and Fear & Greed Index. **Parameters:** None **Example:** ``` User: What's the crypto market like today? Agent: [calls get_market_overview()] ``` ## Data Sources This MCP server connects to the J4Y backend which aggregates: - 170+ news sources (RSS feeds, The Block, CoinDesk, etc.) - 50+ KOL Twitter accounts (Chinese + English) - Real-time market data (CoinGecko, Fear & Greed Index) - On-chain data via DeBank API ## Why MCP Server? Unlike prompt-based skills that rely on the host LLM to execute commands, this MCP server: - **Executes real API calls** - Tools directly call the J4Y backend - **Returns real data** - BTC/ETH prices, Fear & Greed Index are from live sources - **Works on any MCP-compatible platform** - OpenClaw, Claude Desktop, Cursor, etc. ## Installation ### For OpenClaw ```json { "plugins": { "entries": { "web3-daily-mcp": { "enabled": true, "command": "npx", "args": ["web3-daily-mcp"] } } } } ``` ### For Claude Desktop Add to `claude_desktop_config.json`: ```json { "mcpServers": { "web3-daily": { "command": "npx", "args": ["web3-daily-mcp"] } } } ``` ## Privacy - **Public digest**: No personal data required - **Personalized features**: Wallet address is sent to backend for analysis - **Data retention**: Wallet profiles cached for 24 hours - **No permanent storage**: We do not permanently store or sell wallet data


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: linuszz/asset-extension (version 1.0.0)

--- name: asset-extension description: "Analyze how to extend and leverage existing assets. Use for growth strategy and resource optimization." --- # Asset Extension ## Metadata - **Name**: asset-extension - **Description**: Asset leverage and extension analysis - **Triggers**: asset extension, leverage assets, growth platform, resource utilization ## Instructions Analyze asset extension opportunities for $ARGUMENTS. ## Framework ### Asset Types | Asset Type | Description | Extension Options | |------------|-------------|-------------------| | **Brand** | Reputation, recognition | New markets, products | | **Technology** | IP, know-how | Licensing, new applications | | **Customer Base** | Relationships, data | Cross-sell, up-sell | | **Operations** | Facilities, processes | New services, efficiency | ### Extension Matrix ``` Low Utilization High Utilization High Value │ Extend │ Leverage Low Value │ Divest │ Optimize ``` ## Output ``` ## Asset Extension Analysis: [Business/Asset] ### Asset Inventory | Asset | Value | Utilization | Extension Potential | |-------|-------|-------------|---------------------| | Brand | High | 70% | Medium | | Technology | High | 50% | High | | Customer Base | Medium | 80% | Low | | Operations | Medium | 60% | Medium | ### Extension Opportunities | Opportunity | Asset Leverage | Market Size | Investment | Priority | |-------------|----------------|-------------|------------|----------| | [Opp 1] | Technology | $500M | $20M | High | | [Opp 2] | Brand | $300M | $10M | Medium | | [Opp 3] | Operations | $200M | $15M | Low | ### Recommendations 1. **[Priority 1]**: [Description and rationale] 2. **[Priority 2]**: [Description and rationale] ### Implementation Roadmap | Phase | Action | Investment | Timeline | |-------|--------|------------|----------| | 1 | [Action] | $X | Q1-Q2 | | 2 | [Action] | $Y | Q3-Q4 | ``` ## Tips - Start with strongest assets - Evaluate strategic fit - Consider competitive response - Phase investments carefully


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: brucegutman/pipeworx-spacenews (version 1.0.0)

# Space News Stay current with spaceflight news. Pulls articles and blog posts from the Spaceflight News API, aggregating coverage from dozens of space journalism outlets. ## Three tools 1. **get_articles** -- Latest spaceflight news articles, sorted by publication date 2. **search_articles** -- Keyword search across all articles (e.g., "SpaceX Starship launch") 3. **get_blogs** -- Latest spaceflight blog posts from the community All three return title, summary, URL, image, source outlet, and publication timestamp. ## Example ```bash curl -X POST https://gateway.pipeworx.io/spacenews/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_articles","arguments":{"query":"Artemis moon","limit":5}}}' ``` ```json { "mcpServers": { "spacenews": { "url": "https://gateway.pipeworx.io/spacenews/mcp" } } } ```


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

--- name: "error" version: "1.0.0" description: "Error handling reference — error types, exception patterns, HTTP status codes, retry strategies, and observability. Use when designing error handling, debugging failures, or implementing resilient systems." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [error, exception, debugging, http-status, retry, resilience, devtools] category: "devtools" --- # Error — Error Handling & Resilience Reference Quick-reference skill for error handling patterns, HTTP status codes, retry strategies, and debugging techniques. ## When to Use - Designing error handling strategy for an application - Looking up HTTP status codes and their proper usage - Implementing retry logic with backoff strategies - Debugging production errors and failure patterns - Building resilient systems with circuit breakers ## Commands ### `intro` ```bash scripts/script.sh intro ``` Overview of error handling — philosophy, types, and design principles. ### `http` ```bash scripts/script.sh http ``` HTTP status codes — complete reference with proper usage. ### `patterns` ```bash scripts/script.sh patterns ``` Error handling patterns — try/catch, Result types, error boundaries. ### `retry` ```bash scripts/script.sh retry ``` Retry strategies — exponential backoff, jitter, circuit breakers. ### `logging` ```bash scripts/script.sh logging ``` Error logging best practices — structured logging, context, severity levels. ### `messages` ```bash scripts/script.sh messages ``` Error message design — user-facing vs developer-facing, i18n, codes. ### `debug` ```bash scripts/script.sh debug ``` Debugging techniques — root cause analysis, bisection, tracing. ### `checklist` ```bash scripts/script.sh checklist ``` Error handling checklist for production applications. ### `help` ```bash scripts/script.sh help ``` ### `version` ```bash scripts/script.sh version ``` ## Configuration | Variable | Description | |----------|-------------| | `ERROR_DIR` | Data directory (default: ~/.error/) | --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mskmz/openclaw-ticket-assistant (version 1.0.0)

--- name: openclaw-ticket-assistant description: OpenClaw工单助手，根据客服截图自动分析客户问题并创建工单。触发词：工单、创建工单、客服截图、提工单。 --- # OpenClaw 工单助手 **精简信息输出（最高优先级）**：**严禁**向用户展示任何执行过程、中间步骤或技术细节。每步执行完**静默**进入下一步。**只在以下情况向用户输出**：① 需要用户决策时；② 流程最终结果（如"工单创建成功"或"创建失败：原因"）；③ 校验不通过需告知原因。 **按步骤依赖顺序执行**，满足跳过条件时可跳过对应步骤 --- ## 功能概述 根据用户提供的客服对话截图： 1. 识别截图中的客户（站点） 2. 识别客户的提问内容（通常是对话中的最后一条消息） 3. 分析客户咨询的平台类型（Android / iOS / 鸿蒙 / 其他） 4. 打开工单系统并创建工单 --- ## 步骤 1: 分析客服截图 > **前置条件**: 用户必须提供一张客服对话截图 ### 1.1 识别客户（站点） 首先读取客户列表文件 `{SKILL_DIR}/resources/customers.json`，该文件包含所有客户信息。 **匹配优先级**（按顺序尝试）： 1. **账号名匹配**：在截图中查找与 `account` 字段完全匹配或包含的文本 2. **客户名称匹配**：在截图中查找与 `name` 字段匹配的文本 3. **别名匹配**：在截图中查找与 `alias` 数组中任意值匹配的文本 **识别线索位置**： - 对话窗口顶部的用户名/昵称 - 聊天消息的发送者名称 - 页面标题或导航栏 - 头像旁边的名称标签 **如果无法识别**：向用户展示无法匹配的信息，并列出可能的候选客户让用户选择，或让用户直接告知客户名称。 ### 1.2 识别客户提问 在对话截图中： - 区分客服消息和客户消息（通常通过消息气泡位置、颜色、头像区分） - **重点关注最后一条客户消息**，这通常是需要处理的问题 - 如果最后一条是客服消息，则向上查找最近的客户问题 - 提取完整的问题描述文本 ### 1.3 识别平台类型 根据客户提问内容，判断涉及的平台类型： | 关键词 | 平台类型 | |--------|----------| | Android、安卓、华为手机（非鸿蒙）、小米、OPPO、VIVO、三星、Gradle、APK | Android | | iOS、iPhone、苹果、iPad、Xcode、Swift、OC、Objective-C | iOS | | 鸿蒙、HarmonyOS、华为鸿蒙、ArkTS、ArkUI、DevEco | 鸿蒙 | | H5、Web、网页、浏览器、JS、JavaScript | H5/Web | | 无明确平台信息或涉及多平台 | 通用（需询问用户确认） | ### 1.4 识别反馈人 在截图中查找反馈人信息： - 客户消息发送者的昵称/姓名 - 如果无法识别，询问用户 ### 1.5 信息汇总与确认 将识别结果整理并向用户确认： ``` 站点：[客户名称] 反馈人：[反馈人姓名] 产品：[Android/iOS/鸿蒙/H5/通用] 问题描述：[客户提问内容] ``` - 如果用户确认正确，进入步骤 2 - 如果用户指出错误，根据反馈修正后再确认 - **如果任何字段无法识别，必须询问用户**，不得猜测 --- ## 步骤 2: 打开工单系统 ### 2.1 导航到工单系统 使用浏览器工具打开工单系统： ``` URL: https://t.aliyun-inc.com/workbench/list ``` ### 2.2 检查登录状态 页面加载后，检查当前状态： **判断方式**： - 如果页面 URL 包含 `login.alibaba-inc.com`，说明未登录，进入 2.3 - 如果页面显示工单列表或工作台界面，说明已登录，进入步骤 3 ### 2.3 引导用户登录（如需要） 如果检测到未登录状态（URL 包含 `login.alibaba-inc.com`）： **加载登录引导流程**：读取 `{SKILL_DIR}/references/login-guide.md` 并按其中的步骤引导用户完成二维码扫码登录。 登录成功后继续步骤 3。 --- ## 步骤 3: 创建工单 ### 3.1 点击创建按钮 在工单列表页面，点击"创建工单"或"新建"按钮 ### 3.2 填写工单表单 根据步骤 1 收集的信息填写表单： | 字段 | 填写内容 | 说明 | |------|----------|------| | UID账号 | 从 customers.json 中获取对应客户的 `id` 字段 | 必填 | | 问题分类 | 一级分类选择：**移动开发平台mpaas** | 固定值 | | 描述 | 步骤 1.2 识别的客户提问内容 | 必填 | | 处理组 | **运维一线2组** | 固定值 | | 处理人 | 当前登录账号（从登录页面或页面右上角获取） | 自动填充 | **处理人获取方式**： - 在登录流程中记录用户账号信息 - 或从工单系统页面右上角用户信息区域获取当前登录账号 ### 3.3 提交前确认 填写完成后，**先截图展示给用户确认**： 1. 对当前填写完成的工单表单页面截图 2. 将截图展示给用户，并提示： ``` 工单信息已填写完成，请确认以上内容是否正确？ 确认无误请回复"确认"或"提交"，如需修改请说明。 ``` 3. **等待用户确认**： - 用户确认无误 → 进入 3.4 提交工单 - 用户要求修改 → 根据反馈修改后重新截图确认 ### 3.4 提交工单 用户确认后，点击提交按钮完成工单创建。 ### 3.5 获取工单号并输出结果 提交成功后，获取系统生成的工单号，按以下格式输出： ``` 工单号：[系统生成的工单号] 站点：[客户名称] 反馈人：[反馈人姓名] 产品：[平台类型] 问题描述：[客户提问内容] ``` --- ## 注意事项 1. **截图质量要求**：截图应清晰可读，包含完整的对话内容 2. **客户识别失败时**：必须询问用户，不得猜测或随意选择 3. **多轮对话**：如果截图包含多轮对话，重点关注最近的客户问题 4. **信息不完整时**：缺少任何必要信息都应询问用户确认 5. **平台类型模糊时**：如果无法从问题内容判断平台，询问用户确认 --- ## 客户列表 客户信息存储在 `{SKILL_DIR}/resources/customers.json` 文件中，包含以下字段： - `name`: 客户名称（站点名称） - `account`: 客户在客服系统中的账号名 - `id`: 客户UID，用于填写工单 - `alias`: 客户别名数组（可选），用于辅助匹配


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