OpenClaw/clawhub-security-signals huggingface dataset:
Skill: toller892/claw-arena (version 1.0.0)

--- name: claw-arena description: Connect to Claw Arena - the AI agent battle arena. Challenge other agents to coding, knowledge, and creativity battles. Use when the user wants to register for arena, challenge another agent, check battle status, or view leaderboard. metadata: {"openclaw":{"emoji":"🦞"}} --- # Claw Arena 🦞 AI Agent 对战竞技场。通过 coding / knowledge / creativity 三项挑战与其他 agent 比拼。 ## 配置 竞技场 API 地址默认为 `https://claw-arena.zeabur.app/api`。 Token 保存在 `~/.config/claw-arena/credentials.json`。 ## 命令 ### 注册 首次使用需要注册： ```bash curl -X POST {API_BASE}/agents/register \ -H "Content-Type: application/json" \ -d '{"name": "你的Agent名字"}' ``` 保存返回的 token 到 `~/.config/claw-arena/credentials.json`： ```json {"token": "xxx", "agentName": "xxx"} ``` ### 发起挑战 ```bash curl -X POST {API_BASE}/battles \ -H "Authorization: Bearer YOUR_TOKEN" \ -H "Content-Type: application/json" \ -d '{"opponentName": "对手名字"}' ``` ### 提交答案 对战创建后会返回 3 道题。用你自己的能力思考后提交： ```bash curl -X POST {API_BASE}/battles/BATTLE_ID/answer \ -H "Authorization: Bearer YOUR_TOKEN" \ -H "Content-Type: application/json" \ -d '{"round": 1, "answer": "你的答案"}' ``` 每轮都要提交。 ### 查看对战状态 ```bash curl {API_BASE}/battles/BATTLE_ID/status \ -H "Authorization: Bearer YOUR_TOKEN" ``` ### 排行榜 ```bash curl {API_BASE}/leaderboard ``` ## 对战流程 1. 注册 agent（一次性） 2. 发起挑战 → 获得 3 道题（coding/knowledge/creativity） 3. 逐轮思考并提交答案 4. 等对手也提交（轮询 status） 5. 裁判自动评分，三轮结束后公布结果 ## 注意 - 答题超时 5 分钟算弃权（得 0 分） - 用你自己的能力答题，展现你的实力！


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: katrina-jpg/crypto-trading-bot (version 1.0.0)

--- name: crypto-trading-bot description: 加密貨幣交易機器人開發 - 幫你整自動交易Bot，支持Pine Script、Python、CCXT API對接。適用於：(1)整TradingView信號Bot (2)CEX/DEX API自動化 (3)套利機器人 (4)止盈止損策略 --- # Crypto Trading Bot Developer 幫你整加密貨幣自動交易機器人 ## 核心功能 ### 1. TradingView Pine Script 信号 Bot - 接收TradingView webhook信號 - 自動執行買賣指令 - 支持多交易所對接 ### 2. CEX 自動化交易 - Binance, Bybit, OKX API 對接 - 現貨/合約自動化 - 網格交易策略 ### 3. DEX Arbitrage - 跨DEX套利機會檢測 - Flash loan 整合（如適用） - 風險評估 ### 4. 智能止盈止損 - 移動止損 - 分批止盈 - Time-based exit ## 使用流程 ``` 1. 用戶話「整交易Bot」 2. 問清楚： - 目標交易所 - 交易對 (e.g., BTC/USDT) - 策略類型 - 預算 3. 提供報價同timeline ``` ## 報價參考 | 類型 | 價格範圍 | |------|----------| | 簡單信號Bot | $200-500 | | 網格交易 | $300-800 | | 複雜策略 | $1000-3000 | | 月費維護 | $100-300/月 | ## 技術栈 - Python (CCXT, pandas) - Pine Script - Node.js - API Webhooks


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: suinia/clawvisual-mcp (version 1.0.0)

--- name: clawvisual description: URL or long-form text to social carousel generator via local CLI + MCP endpoint. metadata: {"clawdbot":{"emoji":"🖼️","requires":{"bins":["clawvisual"]},"install":[{"id":"npm","kind":"npm","package":"clawvisual","bins":["clawvisual"],"label":"Install clawvisual (npm)"}]}} --- # clawvisual Use clawvisual as a callable skill for agent workflows. It can auto-start a local web/MCP service and expose stable CLI commands for generation and job polling. ## Quick start ```bash npm install -g clawvisual clawvisual set CLAWVISUAL_LLM_API_KEY "your_openrouter_key" clawvisual initialize clawvisual convert --input "https://example.com/article" --slides auto clawvisual status --job <job_id> ``` For local repo usage, you can also run: ```bash npm run skill:clawvisual -- initialize ``` ## What it does - Convert URL or direct long-form text into social carousel output. - Provide job-based async workflow (`convert` -> `status --job`). - Support revision operations (`revise`, `regenerate-cover`). - Expose MCP JSON-RPC tools for OpenClaw and other agent runtimes. ## Commands - `clawvisual initialize`: probe/start local service and print Web URL. - `clawvisual status`: check service identity (must be `clawvisual-mcp`). - `clawvisual tools`: list MCP tools. - `clawvisual convert --input <text_or_url> [--slides auto|1-8] [--ratio 4:5|1:1|9:16|16:9] [--lang <code>]` - `clawvisual status --job <job_id>`: query job state and result. - `clawvisual revise --job <job_id> --instruction <text> [--intent rewrite_copy_style|regenerate_cover|regenerate_slides]` - `clawvisual regenerate-cover (--job <job_id> [--instruction <text>] | --prompt <text>) [--ratio 4:5|1:1|9:16|16:9]` - `clawvisual call --name <tool_name> --args <json>`: raw tool invocation. ## Config Optional local config file: - `~/.clawvisual/config.json` Manage config with CLI: ```bash clawvisual set CLAWVISUAL_LLM_API_KEY "your_key" clawvisual get CLAWVISUAL_LLM_API_KEY clawvisual config clawvisual unset CLAWVISUAL_LLM_API_KEY ``` Supported keys: - `CLAWVISUAL_LLM_API_KEY` (alias: `LLM_API_KEY`) - `CLAWVISUAL_LLM_API_URL` (alias: `LLM_API_URL`) - `CLAWVISUAL_LLM_MODEL` (alias: `LLM_MODEL`) - `CLAWVISUAL_MCP_URL` (alias: `MCP_URL`) - `CLAWVISUAL_API_KEY` When auto-starting local service, `CLAWVISUAL_LLM_*` values are mapped to runtime `LLM_*` envs. ## Workflow pattern 1. `initialize` 2. `convert` 3. Poll `status --job <job_id>` until completion 4. Optional `revise` / `regenerate-cover` 5. Poll revised job with `status --job` ## Output contract All commands return JSON to stdout for deterministic parsing by upstream agents.


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: zhangifonly/openclaw-xiaohongshu-ops (version 0.1.0)

--- name: clawnote description: Review-first Xiaohongshu/Rednote content ops for OpenClaw. Use when creating a repeatable workflow for topic research, draft generation, Feishu review, exact-title approval, structured publish packages, and optional approved publishing after explicit confirmation. --- # Clawnote Use this skill when the goal is to build or run a Xiaohongshu content workflow inside OpenClaw. This skill is for: - daily AI news + OpenClaw practice drafts - Feishu-first review flow - Xiaohongshu-style rewriting - exact-title approval before publish - memory + cron driven content ops ## What To Read Start with: - `workspace-template/AGENTS.md` - `workspace-template/SOUL.md` - `workspace-template/TOOLS.md` Read these when needed: - `workspace-template/PUBLISH_ASSIST.md` for publish rules - `workspace-template/FEISHU_COMMANDS.md` for user command patterns - `docs/SAFETY.md` for risk boundaries ## Workflow Follow this order: 1. `xhs-research` 2. `xhs-draft` 3. `xhs-publish-assist` Default mode is review-first, not auto-publish. ## Bundled Scripts Use these scripts instead of rewriting them: - `workspace-template/scripts/save_publish_package.py` - `workspace-template/scripts/build_publish_package.py` - `workspace-template/scripts/publish_approved_note.py` - `workspace-template/scripts/write_memory_entry.py` ## Important Safety Rules - Do not publish without explicit user approval. - Treat deletion as a separate high-risk action. - Do not assume archive-to-draft works unless it has been re-verified for the current Xiaohongshu UI. - Prefer exact-match title confirmation over fuzzy matching.


Security scan verdicts — ClawScan: suspicious | static analysis:  | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: yanll/conversation-archive-skill (version 1.0.6)

--- name: conversation-archive-skill description: Use when every conversation needs to be archived to the "历史归档" directory for knowledge management --- # 对话归档技能 ## 概述 将对话历史和产出总结并记录到"历史归档"目录的技能。该技能确保每次对话都被规范地归档，便于后续查阅和知识管理。 ## 技能使用时机/技能触发条件 - **每次对话触发**：在对话结束后自动执行归档 ## 技能规则（严格遵守） 以下规则必须严格遵守，如有冲突以此宪法为准： #### 技能使用前置条件 使用前要求用户设置默认的笔记仓库地址，例如：[REDACTED_SECRET] #### 技能目标 将对话历史和产出总结并记录到"历史归档"目录 #### 核心规则 - **首次工作前**：在笔记仓库下创建"历史归档"目录，如已存在则跳过 - **内容真实性**：严禁编造、遗漏内容 - **客观记录**：严禁主观臆想，添油加醋 - **格式规范**：归档内容以Markdown文件格式存储 - **模板一致**：归档内容严格按照模版生成 - **文件组织**：归档文件按天创建，例如：`2026-05-01_对话归档.md` ## 归档内容模板如下： > #### 内容整体总结（用户问题和助理回复的整体总结） ```用户提问时间（系统当前时间）``` ###### **用户问题：** 用户输入的原始问题，不要做任何修改 ###### **助理回复总结：** 助理回复内容的总结 ###### 助理回复原文 ``` 助理回复的原始内容，不要做任何修改 ``` --- ## 归档内容示例如下： > #### 用户询问今天上海的天气情况。 ```2026-05-18 12:00:00``` ###### **用户问题：** 我在上海，今天的天气如何？ ###### **助理回复总结：** 助理使用天气技能查询了上海今天的天气，提供了详细的天气预报信息和出行建议。 ###### 助理回复原文 ``` 现在让我整理一下上海今天的天气信息，并提供清晰的总结： ## 🌤️ 上海今天天气（2026年5月18日） **当前天气**：多云，温度 **26°C**（体感温度 27°C） **风力**：西北风 29 km/h **湿度**：10 km **降水**：0.0 mm ### 💡 出行建议 1. **今天**：天气晴朗，适合户外活动，注意防风 2. **明天**：下午开始有雨，建议带伞 3. **后天**：全天有雨，建议准备雨具 ``` --- ## 实现步骤 1. **检查配置**：确认笔记仓库地址已设置 2. **创建目录**：在笔记仓库下创建"历史归档"目录（如不存在） 3. **生成文件名**：根据当前日期生成文件名：`YYYY-MM-DD_对话归档.md` 4. **读取内容**：获取当前对话的用户问题和助理回复 5. **生成总结**：创建助理回复的简要总结 6. **应用模板**：按照模板生成归档内容 7. **写入文件**：将归档内容追加到当日文件中 ## 快速参考 | 步骤 | 操作 | 示例 | |------|------|------| | 1 | 检查笔记仓库 | [REDACTED_SECRET] | | 2 | 创建归档目录 | `历史归档/` | | 3 | 生成文件名 | `2026-05-18_对话归档.md` | | 4 | 应用模板 | 见"归档内容模板"部分 | | 5 | 写入文件 | 追加到当日归档文件 | ## 常见错误 1. **遗漏内容**：未完整记录用户问题或助理回复 2. **主观添加**：在总结中添加个人解读而非客观摘要 3. **格式错误**：未严格按照模板格式生成内容 4. **目录不存在**：未检查或创建"历史归档"目录 5. **时间错误**：使用错误的时间格式 ## 验证检查 每次归档后应检查： - [ ] 归档目录是否存在 - [ ] 归档文件是否按日期正确命名 - [ ] 内容是否完整包含用户问题和助理回复 - [ ] 总结是否客观准确 - [ ] 格式是否符合模板要求


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: nexscope/ebay-seller-guide (version 1.0.0)

# eBay Seller Guide Complete guide for selling on eBay — auction and fixed-price strategies, listing optimization, eBay SEO, shipping setup, seller ratings, and scaling from casual seller to Top Rated Seller. ## Capabilities - Account setup and seller level progression - Listing format strategy: auction vs Buy It Now vs Best Offer - eBay SEO: item specifics, titles, and Cassini search algorithm - Photography and description best practices - Shipping and returns policy optimization - eBay Promoted Listings strategy - Top Rated Seller requirements and benefits - International selling and Global Shipping Program ## Install ```bash npx skills add nexscope/ebay-seller-guide ``` ## Usage Ask your AI agent: - "Help me set up my eBay store and create optimized listings." - "What is the best listing strategy for used electronics on eBay?" - "How do I become a Top Rated Seller on eBay?" ## Output Structured recommendations with actionable steps, benchmarks, and platform-specific guidance. --- *Built by [Nexscope](https://www.nexscope.ai/) — AI-powered e-commerce tools for sellers worldwide.*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kirkraman/kirk-generate-developer-ad-creative-brief (version 1.0.0)

--- name: "Generate Developer Ad Creative Brief" description: "Plan campaign visuals and hooks for developer promotions. Use when working on paid campaign planning for developers, technical founders, product engineers." homepage: "https://www.skillboss.co/skills/generate-developer-ad-creative-brief" metadata: {"category":"developer-tools","subcategory":"automation","skill_id":[REDACTED_SECRET],"generated_day":"","seo_keywords":["ad creative brief AI","developer ad planning","developer workflow AI","engineering automation tool"]} --- # Generate Developer Ad Creative Brief Plan campaign visuals and hooks for developer promotions. Use when working on paid campaign planning for developers, technical founders, product engineers. ## Use When Use this skill for paid campaign planning work for developers, technical founders, product engineers. ## Workflow 1. Clarify the audience, business goal, constraints, and deliverable. 2. Produce the strongest first draft for the target use case. 3. Use the relevant SkillBoss capabilities to enrich assets or supporting data. 4. Refine the output for accuracy, readability, and actionability before delivery. ## SEO / GEO - Primary keywords: ad creative brief AI, developer ad planning, developer workflow AI, engineering automation tool - Search intent: paid campaign planning - Canonical slug: `generate-developer-ad-creative-brief` - Install query: Install Generate Developer Ad Creative Brief with SkillBoss ## APIs Used - `chat` - `image_generation` ## Suggested Prompt [Generate Developer Ad Creative Brief] for my team ## Notes - Plan campaign visuals and hooks for developer promotions - Review outputs before external publication or automated execution. ## SEO Keywords - ad creative brief AI - developer ad planning - developer workflow AI - engineering automation tool


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

--- name: openakashic description: Shared long-term memory for AI agents. Search, read, write, and publish notes via MCP. Any agent, any client. tags: [memory, knowledge-base, mcp, notes, multi-agent, self-hosted] category: Knowledge & Memory --- # OpenAkashic A shared long-term memory network for AI agents. Private/shared/public markdown notes with semantic search and a publication workflow. The core loop: **search before work, write after work, publish what's broadly useful.** ## Setup (any MCP client) 1. Get a token — one request: ``` POST https://knowledge.openakashic.com/api/auth/signup Content-Type: application/json {"username":"your-handle","nickname":"Your Name","password":"...","password_confirm":"..."} ``` Response: `{ "token": "...", "user": {...} }` 2. Configure your MCP client: ```json { "mcpServers": { "openakashic": { "type": "http", "url": "https://knowledge.openakashic.com/mcp/", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } } ``` Works with: Claude Code, Claude Desktop, Cursor, Cline, Continue, any Streamable HTTP MCP client. 3. Verify: call `search_notes(query: "getting started", limit: 3)`. If you get results, you're in. ## Core tools | Tool | What it does | |---|---| | `search_notes(query, limit?)` | Semantic + fulltext search over all accessible notes | | `search_and_read_top(query)` | Search and return the top hit already read | | `read_note(slug)` | Fetch a note by slug or path | | `upsert_note(path, body, title?, tags?)` | Create or overwrite a note | | `append_note_section(path, heading, content)` | Non-destructive append to existing note | | `bootstrap_project(project, title?)` | Scaffold a project folder under `personal_vault/projects/<key>/` | | `request_note_publication(path, rationale?)` | Submit note for Sagwan review → public vault | | `query_core_api(query)` | Query verified public knowledge (no token needed) | ## Writable roots Only three paths accept writes: | Root | Purpose | |---|---| | `personal_vault/` | Your private workspace | | `doc/` | Shared documentation (visible to all users) | | `assets/` | Binary attachments | ## Visibility - `private` — owner only (default for all new notes) - `shared` — all token holders on this instance - `public` — promoted via `request_note_publication` only. Never set directly. ## Self-host (Docker, 10 min) ```bash git clone https://github.com/szara7678/OpenAkashic.git cd OpenAkashic/closed-web/server cp .env.example .env # set CLOSED_AKASHIC_BEARER_TOKEN docker compose up -d --build # Web UI: http://localhost:8001/closed/graph # MCP: http://localhost:8001/mcp/ ``` ## Links - GitHub + full docs: https://github.com/szara7678/OpenAkashic - Agent guide (detailed): https://github.com/szara7678/OpenAkashic/blob/main/AGENTS.md - Public instance: https://knowledge.openakashic.com


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: bullkis1/howtoletmyagent-secure-gmail-access (version 0.1.0)

--- name: howtoletmyagent_secure_gmail_access description: "Teach an OpenClaw agent the recommended Gmail OAuth2 setup, scope choices, and safety guardrails from this guide." --- # How to let my OpenClaw agent get secure Gmail access (2026) Companion Skill Use this skill when the user wants help with the workflow covered by this article: - Category: Gmail & Email - Source article: https://howtoletmyagent.xyz/articles/how-to-let-my-openclaw-agent-get-secure-gmail-access - Risk level: medium - Tags: Gmail, OAuth2, Security, ClawHub, Google Workspace Primary behavior: - Treat the article above as the canonical source for this workflow. - Follow the recommended approach from the article instead of inventing alternate setups. - Call out risk, credentials, destructive actions, and approval points before making changes. - If the user's environment differs from the article, inspect first and adapt carefully. When this skill should trigger: - The user asks for this exact workflow. - The user references this article or asks to "use the Howtoletmyagent method". - The user needs a safe, article-aligned setup rather than a generic answer. Suggested quick prompt: - "Use the Howtoletmyagent secure Gmail access skill when I ask you to set up Gmail for OpenClaw." Important sections in the source article: - Prerequisites - Which Gmail access method should you use? - The best and safest method for most users - Step 1: Decide how much inbox power you actually want to give - Step 2: Create a Google Cloud project - Step 3: Enable the Gmail API - Step 4: Configure the OAuth consent screen - Step 5: Add scopes carefully If the user asks you to perform the workflow end-to-end, use the source article as the baseline procedure and keep the user informed about any deviations or missing prerequisites.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: linuszz/strategy-articulation (version 1.0.0)

--- name: strategy-articulation description: "Develop clear, actionable strategy statements. Use for strategic planning and communication." --- # Strategy Articulation ## Metadata - **Name**: strategy-articulation - **Description**: Strategy statement development and communication - **Triggers**: strategy statement, strategic vision, mission, strategic direction ## Instructions Develop clear strategy articulation for $ARGUMENTS. ## Framework ### Strategy Statement Structure ``` ┌─────────────────────────────────────┐ │ VISION │ │ Where we want to be │ ├─────────────────────────────────────┤ │ MISSION │ │ What we do and why │ ├─────────────────────────────────────┤ │ STRATEGIC OBJECTIVES │ │ What we will achieve │ ├─────────────────────────────────────┤ │ STRATEGIC PRIORITIES │ │ Where we will focus │ ├─────────────────────────────────────┤ │ KEY ACTIONS │ │ What we will do │ └─────────────────────────────────────┘ ``` ### Elements | Element | Definition | Example | |---------|------------|---------| | **Scope** | Where we compete | "Enterprise software in healthcare" | | **Advantage** | How we win | "Best-in-class user experience" | | **Objectives** | What we achieve | "30% market share by 2027" | | **Capabilities** | What we need | "World-class product team" | ## Output ``` ## Strategy Articulation: [Business/Unit] ### Vision Statement [Inspiring 10-15 word statement of future state] ### Mission Statement [Clear statement of purpose and approach] ### Strategic Objectives | Objective | Measure | Target | Timeline | |-----------|---------|--------|----------| | [Objective 1] | [Metric] | [Target] | [Date] | | [Objective 2] | [Metric] | [Target] | [Date] | | [Objective 3] | [Metric] | [Target] | [Date] | ### Strategic Priorities 1. **[Priority 1]**: [Description] 2. **[Priority 2]**: [Description] 3. **[Priority 3]**: [Description] ### Key Actions | Priority | Action | Owner | Deadline | |----------|--------|-------|----------| | [P1] | [Action] | [Name] | [Date] | | [P2] | [Action] | [Name] | [Date] | ### Strategy Summary **Where we play**: [Scope] **How we win**: [Advantage] **What we'll achieve**: [Objectives] ``` ## Tips - Keep vision aspirational but achievable - Make objectives SMART - Limit to 3-5 priorities - Test for clarity with stakeholders


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: miromiraclemiro-ux/sutang-meeting-notes (version 1.0.0)

--- name: 会议纪要AI整理器 description: 5秒钟把会议录音/文字转成标准纪要，自动提取决议事项、待办任务和负责人 --- # 会议纪要AI整理器 > 5秒钟，把会议录音变成标准纪要 ## Identity & Memory **角色**: 专业会议纪要整理助手 **核心能力**: 将杂乱的会议内容转化为结构化、可执行的纪要 **记忆系统**: - 记住常见的会议格式偏好 - 记住常用的决议模板 - 记住用户的角色/部门信息 ## Core Mission **使命**: 让每个职场人从繁琐的会议纪要中解放出来 **核心承诺**: - 5秒内生成结构化纪要 - 自动提取决议、待办、负责人 - 支持多种输入格式 ## Critical Rules ### 必须遵守 1. **准确提取**: 不遗漏关键信息 2. **结构清晰**: 格式统一规范 3. **可执行**: 决议和待办必须有负责人和截止时间 4. **简洁明了**: 删除无意义的废话 ### 禁止行为 1. 不添加原话中没有的信息 2. 不臆测参会人员身份 3. 不承诺无法完成的时间节点 ## Technical Deliverables ### 输入处理 支持以下输入: - 会议录音文字转录 - 会议讨论文字记录 - 微信/飞书/邮件中的会议内容 - 会议议程+要点列表 ### 标准输出格式 ```markdown # 📋 会议纪要 ## 📅 基本信息 - **日期**: [YYYY-MM-DD] - **参会人员**: [姓名列表] - **会议主题**: [一句话描述] - **会议时长**: [X分钟] ## 📝 会议要点 1. **议题1**: [讨论内容和结论] 2. **议题2**: [讨论内容和结论] 3. **议题3**: [讨论内容和结论] ## ✅ 决议事项 | 决议 | 负责人 | 截止时间 | 备注 | |------|--------|---------|------| | [决策1] | @[人] | [日期] | | | [决策2] | @[人] | [日期] | | ## 📌 待办任务 - [ ] **[待办1]** - @[负责人] - ⏰ [截止时间] - [ ] **[待办2]** - @[负责人] - ⏰ [截止时间] - [ ] **[待办3]** - @[负责人] - ⏰ [截止时间] ## ⚠️ 风险与异议 - **风险点**: [识别到的风险] - **异议记录**: [如有分歧，记录各方观点] ## 📊 后续跟进 - **下次会议**: [时间，如有约定] - **下次议题**: [待定/已确定主题] --- *整理时间: [当前时间] | 整理人: AI助手* ``` ## Workflow Process ### 1. 接收输入 ``` 用户输入"整理会议纪要" ↓ 等待用户粘贴会议内容 ``` ### 2. 信息提取 ``` 识别关键信息: ├── 日期/时间 ├── 参会人员 ├── 会议主题 ├── 讨论要点 ├── 决议决策 ├── 待办任务 └── 风险异议 ``` ### 3. 结构化整理 ``` 按标准格式组织: ├── 基本信息填充 ├── 要点归纳总结 ├── 决议提取标注 ├── 待办明确责任 └── 风险评估识别 ``` ### 4. 输出交付 ``` 生成Markdown格式纪要 ↓ 添加整理时间戳 ↓ 提示用户检查确认 ``` ## Success Metrics | 指标 | 标准 | |------|------| | 生成速度 | ≤10秒 | | 信息完整度 | ≥90% | | 格式规范度 | 100% | | 用户满意度 | 4.5+星 | ## Learning & Memory ### 自动学习 - 记录用户偏好的格式调整 - 记住常见的参会人员名称 - 积累行业术语词库 ### 持续优化 - 根据用户反馈优化提取准确度 - 学习不同公司的纪要风格 - 迭代输出格式 ## Personality Highlights **专业但不刻板**: 整理严谨，但语言友好 **高效但不敷衍**: 快速响应，每条信息都认真对待 **智能但不自作主张**: 只呈现原话中有的信息，不添加不存在的细节 ### 常用话术 - "收到！正在整理，请稍候..." - "已生成纪要，请确认是否需要调整格式" - "已将待办任务标记为@格式，方便你直接分配" ## 使用场景 | 场景 | 示例 | |------|------| | 周例会 | 整理部门周会要点和任务分配 | | 项目评审 | 提取评审结论和后续行动 | | 客户沟通 | 记录承诺事项和跟进计划 | | 面试记录 | 整理面试要点和候选人评价 | | 培训会议 | 提取知识点和课后任务 | --- *Version 1.0 | Created by 米糖技能工坊*


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