OpenClaw/clawhub-security-signals huggingface dataset:
Skill: zhangpuego123/wechat-talk (version 1.0.2)

--- name: wechat-talk version: 2.0.0 description: Windows 电脑端微信消息自动发送技能，通过键盘模拟给指定联系人发送消息。快捷命令：wt triggers: - wt - 微信发送 - 发微信 --- # WeChat Talk Windows 电脑端微信消息自动发送技能。 ## 功能 - 👤 搜索并打开联系人聊天窗口 - ✉️ 给指定联系人发送消息 - 🔄 批量发送（智能优化执行步骤） - ⌨️ 纯键盘模拟，无需 API - ⚡ 快捷命令：`wt` ## 安装 需要先安装 Python 依赖： ```bash pip install pyautogui pygetwindow pillow pyperclip ``` ## 使用方法 ### 1. 单人发送 ```bash python send_batch.py "[张三]" "消息内容" ``` ### 2. 批量发送（轮询模式） ```bash # 初始化并发送第一条 python send_batch.py "[张三，李四，王五]" "消息内容" # 继续发送下一条 python send_batch.py --next # 继续发送下一条 python send_batch.py --next ``` **注意**: 联系人格式必须为 `[A,B,C]` 格式 ### 3. 快捷命令 ```bash wt [张三] 消息内容 wt [张三，李四] 消息内容 ``` ## 执行流程 ### 标准步骤 | 步骤 | 操作 | 快捷键/方法 | 延迟 | |------|------|-------------|------| | 1 | 打开微信 | `Ctrl+Shift+X` | 1.0s | | 2 | 打开搜索 | `Ctrl+F` | 0.3s | | 3 | 输入联系人名称 | `Ctrl+A` → `Delete` → `Ctrl+V` | 0.5s | | 4 | 打开聊天窗口 | `Enter` | 0.5s | | 5 | 粘贴消息 | `Ctrl+V` | 0.3s | | 6 | 发送消息 | `Enter` | 0.3s | ### 智能执行逻辑 | 场景 | 位置 | 执行步骤 | 说明 | |------|------|----------|------| | **单人发送** | 唯一 | Step 1-6 | 完整流程 | | **多人发送** | 第一个人 | Step 1-6 | 完整流程 | | **多人发送** | 后续人员 | Step 2-6 | 跳过打开微信 | **效率优化**: 多人发送时，后续人员跳过打开微信步骤，提升发送效率。 ## 输入格式 ### 联系人格式 **必须为 `[A,B,C]` 格式** ✅ 正确示例: ```bash python send_batch.py "[张三]" "消息" python send_batch.py "[张三，李四]" "消息" ``` ❌ 错误示例: ```bash python send_batch.py "张三" "消息" # 缺少括号 python send_batch.py "张三，李四" "消息" # 缺少括号 ``` 错误时返回：`请输入正确的发送人格式` ## 注意事项 1. 微信 PC 客户端需要已安装并登录 2. 发送消息时会自动激活微信窗口 3. 中文输入需要确保系统中文输入法正常工作 4. 执行过程中不要干扰键盘操作 5. 批量发送时请保持窗口打开状态，不要手动关闭 6. 联系人格式必须为 `[A,B,C]` 格式 ## 文件结构 ``` wechat-talk/ ├── server.py # 核心实现 ├── send_batch.py # 批量发送脚本 ├── requirements.txt ├── send_queue.json # 批量队列（临时） └── SKILL.md ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: ckchzh/shell-script (version 2.3.4)

--- version: "2.0.0" name: Shell Script Helper description: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━. Use when you need shell script capabilities. Triggers on: shell script." Shell脚本助手。脚本生成、逐行解释、调试排错、常用模板(备份/监控/部署)、一行命令、Bash速查表。Shell script generator, explainer, debugger, templates, one-liners, cheatsheet. Shell、Bash、Linux命令。 author: BytesAgain homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills --- # Shell Script Helper Shell脚本助手。脚本生成、逐行解释、调试排错、常用模板(备份/监控/部署)、一行命令、Bash速查表。Shell script generator, explainer, debugger, templates, one-liners, cheatsheet. Shell、Bash、Linux命令。 ## 如何使用 1. 选择你需要的功能命令 2. 输入你的具体需求描述 3. 获取专业的输出结果 4. 根据需要调整和完善 ## 命令列表 | 命令 | 功能 | | Command | Description | |---------|-------------| | `backup` | Backup | | `deploy` | Deploy | | `monitor` | Monitor | | `setup` | Setup | ## 专业建议 - 开头加 `set -euo pipefail`（出错即停、未定义变量报错、管道错误传播） - 变量双引号包裹 `"$var"`（防止空格/特殊字符问题） - 用 `[[ ]]` 代替 `[ ]`（更安全、支持正则） - 用 `$(command)` 代替反引号 - 函数内用 `local` 声明局部变量 --- *Shell Script Helper by BytesAgain* --- 💬 Feedback & Feature Requests: https://bytesagain.com/feedback Powered by BytesAgain | bytesagain.com ## Examples ```bash # Show help shell-script help # Run shell-script run ``` ## Commands Run `shell-script help` to see all available commands.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: panhongwei/html-ppt-generator (version 1.0.1)

--- name: html-report-generator description: 会自己设计PPT的智能报告技能，内置47套PPT模板（商务、科技、创意、学术、政府、金融等全场景覆盖），根据主题风格自由选配模板并自主设计，将任意输入拆解为5-15页精美HTML报告，每页严格1017×720px对齐PPT画布。当用户说"生成报告"、"分析内容做成页面"、"做成HTML"、"内容可视化"时立即使用，无需确认直接生成。 --- # HTML 报告生成器 · 主索引 按需读取，不要预加载所有文件。 --- ## ⚡ 四条不可逾越的铁律 > 违反任意一条 → 该页推翻重做，无例外。 **铁律 1：画布锁死 1017×720px** ```css *, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; } html, body { width:1017px; height:720px; min-width:1017px; max-width:1017px; min-height:720px; max-height:720px; overflow:hidden; } ``` **铁律 2：四区高度精确求和 720px** ``` Header 72px | Content 580px（仅左右 padding，上下禁止）| Summary 48px | Footer 20px ``` **铁律 3：不得 LibreOffice 渲染，必须 Chrome/Puppeteer 截图** **铁律 4：每页 HTML 文件体积 ≥ 18KB** 内容页必须包含足量 CSS + 结构化卡片 + SVG 图表，封面/目录/结尾等特殊页 ≥ 8KB。 体积不足 = 内容偷懒，必须补充卡片正文、数据组件或 SVG 细节。 --- ## 📂 文件索引（按需读取） | 文件 | 职责 | 何时读 | |------|------|--------| | `references/01-canvas.md` | 画布、四区 CSS 骨架、溢出规则、高度铁律 4/5/6 | 每页生成前 | | `references/02-design-system.md` | Tc 自创流程（Step 0→D）、风格文件索引、禁止清单 | 规划阶段第零步 | | `references/03-layout.md` | Lc 自创流程、14 种布局基因库、高度计算规则 | 每页选布局时 | | `references/05-content.md` | 反偷懒约束、三层内容结构、SVG 颜色规则、图表索引 | 写内容时 | | `references/06-workflow.md` | S0 内容拆解、规划三元组、质量核查清单 | 开始+结束时 | | `references/07-special-pages.md` | 封面/目录/章节/结尾页设计原则 + 变量映射（无 HTML 模板） | 生成特殊页时 | | `references/09-components.md` | 页眉/摘要栏/卡片/徽章/数字排版规范 + Tc 变量映射（无 HTML 模板） | 每页组件选用时 | | `references/10-diagram-types.md` | 业务图谱 5 族 44 种索引 + 网络查询流程 | 规划+写内容时 | > 图表选型速查 → 见 `05-content.md`（统计图）· `10-diagram-types.md`（业务图谱） --- ## 🚀 完整生成流程 ``` 阶段零：读 06-workflow.md → 执行 S0-1~S0-4.5 S0-1 联网查数据（核实，不估算） S0-2 主题定性（3 句话） S0-3 逐页内容指令（意图·气质·数据·原料） S0-3.5 逐页内容扩写（论点句·正文·数据组件·摘要栏）← 丰满度在这里 S0-4 视觉规格声明（记忆点·背景三件套·禁止行为） S0-4.5 主题专属卡片语言设计（形状·线条·变体分工·装饰元素）← 新增强制步骤 若用户已提供结构化 MD → S0-1/S0-2 可跳过，S0-3.5 仍须执行 阶段一（规划）： 读 02-design-system.md → Step 0 自创 Tc 专属模板 ★ Step B：尝试读取 design-system/[风格名].md 文件存在 → 提取变量和卡片规格 文件不存在 → 立即用 Write 工具新建该 .md 文件，再继续 读 03-layout.md → 了解 Lc 布局机制 读 06-workflow.md → 输出页码三元组规划表 读 07-special-pages.md → 确认封面/结尾页需求 读 10-diagram-types.md → 规划业务图谱 阶段二（逐页生成）： 每页：01-canvas → Tc CSS（颜色/字体均来自 design-system）→ 03-layout（Lc） → 05-content → 09-components → 按需 svg-extended/ 或 diagram-types/ ★ 卡片 CSS 必须应用 S0-4.5 定义的形状语言（切角/线条/装饰），禁止套用通用圆角壳 阶段三（验证）： 读 06-workflow.md Phase 4 质检清单 ``` --- ## 📋 报告结构 ``` P00 封面（可选）→ 07-special-pages.md 封面设计原则 P0N 目录（可选）→ 07-special-pages.md 目录设计原则 章节分隔（可选）→ 07-special-pages.md 章节分隔原则 P01+ 内容页 × N（主流程） PN 结尾页 → 07-special-pages.md 结尾页原则 ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: vega6dev/format-book-6x9 (version 1.0.0)

--- name: format-book-6x9 description: Formats a manuscript into a 6" x 9" Printed Paperback and a Kindle Ebook, generating a cover page, TOC, headers, and an About the Author section. user-invocable: true metadata: requires: bins: - python3 - pandoc --- # Book Formatting Expert (6x9 Edition) You are an expert book typesetter and formatting agent. Your task is to take a raw text or markdown manuscript provided by the user and format it into two professional, publication-ready formats: 1) A 6" x 9" Printed Paperback (PDF or DOCX) 2) A Kindle Ebook (EPUB) ## Processing Steps ### 1. Manuscript Analysis - Parse the provided manuscript to extract the Book Title, Author Name, Chapter Titles, the main chapter content, and the About the Author text. - If the "About the Author" section, Author Name, or Book Title is missing, pause and ask the user to provide them before proceeding. ### 2. Format 1: Printed Paperback (6" x 9") Write and execute a typesetting script (using Python's reportlab, python-docx, or pandoc via LaTeX) to create a document with these exact specifications: - Dimensions: Exactly 6 inches by 9 inches (Standard US Trade Paperback size). - Cover Page: Centered Book Title (and Author Name if available). Insert a hard page break afterward. - Table of Contents: List each Chapter Title mapped to its corresponding starting page number. Insert a hard page break afterward. - Chapter Formatting: - Begin each chapter on a new page. - Headers: Include "Chapter [Number]" and "[Chapter Title]" at the top header of each chapter page. - Page Numbers: Insert sequential page numbers at the bottom center of every page (excluding the cover page). - End Page: Add the "About the Author" section on the final page of the book. ### 3. Format 2: Kindle Ebook (EPUB) Generate an EPUB file optimized for Amazon Kindle: - Dimensions: Reflowable text (Do *not* hardcode the 6" x 9" dimensions, as Kindle readers must resize dynamically based on user preferences). - Cover Page: Standard Title HTML splash page. - Table of Contents: A hyperlinked TOC that jumps directly to chapter sections. (Do *not* include static page numbers here). - Chapter Formatting: - Use <h1> or <h2> tags for "Chapter [Number]" and "Chapter Title". - Do *not* inject static page numbers or fixed header text, as Kindle e-readers handle reading progress and headers natively. Forcing fixed headers/footers will break the Kindle reading experience. - End Page: Add the "About the Author" section at the end of the manuscript. ## Execution Requirements - Write the necessary local code/commands to output both files in the user's current working directory. - Name the output files cleanly: [Book_Title]_6x9_Paperback.pdf and [Book_Title]_Kindle.epub. - Upon completion, present the file paths to the user and confirm that all formatting constraints were successfully applied.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: leooooooow/ad-claim-risk-checker (version 1.0.0)

# Ad Claim Risk Checker Review ecommerce ad copy for claim risk before it gets turned into paid ads, creator briefs, PDP language, or live selling scripts. Use this skill when a user wants to pressure-test ad copy, hooks, product claims, or creator talking points that might create compliance, platform, or credibility risk. It is useful for spotting overclaims, unsupported promises, absolute wording, implied guarantees, and phrases likely to trigger ad review issues or customer distrust. ## Use when - Reviewing paid ad copy before launch - Checking creator talking points for risky wording - Sanitizing PDP or landing page claims before amplification - Comparing a bold claim version with a safer alternative - Reducing platform review risk without making copy useless ## Do not use when - The user needs formal legal advice or regulatory opinions - There is no claim language to review - The task is general brand writing with no risk concern ## Inputs to ask for - Exact copy to review - Channel: TikTok, Meta, landing page, PDP, live, creator script, email - Product category - Evidence level: testimonials, studies, internal data, none - Market / geography if relevant - Desired tone: aggressive / balanced / conservative ## Workflow 1. Extract the explicit and implied claims 2. Classify claim risk by type 3. Flag unsupported, absolute, or sensitive wording 4. Rewrite the copy into safer alternatives 5. Explain what changed and why ## Output requirements Return: 1. Original claim breakdown 2. Risk rating by line or claim cluster 3. Why the risk exists 4. Safer rewrites 5. Optional stronger-but-still-safer variation ## Risk types to watch - Absolute outcomes - Time-bound guarantees - Health / body / financial outcomes - Unqualified superiority claims - Unsupported quantified performance claims - Implied certainty or universal fit ## Quality bar - Practical for operators and growth teams - Clear risk explanations - Rewrites still usable in real ads - Avoids robotic compliance-speak - No fake legal certainty ## Example prompts - Check this TikTok ad script for risky claims and rewrite it safely - Review these creator talking points before we send the brief - Flag the dangerous lines in this landing page hero copy


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: hiddenpuppy/yahoo-auction-estimator (version 1.0.3)

--- name: yahoo-auction-estimator description: 日本雅虎拍卖商品估价工具 - 自动获取商品信息、查询历史成交价、计算建议出价 homepage: https://github.com/openclaw/skills/tree/main/yahoo-auction-estimator metadata: {"clawdbot":{"emoji":"🏷️","requires":{"bins":["node","curl"],"env":["PROXY_SOCKS5"]},"primaryEnv":"PROXY_SOCKS5"}} --- # Yahoo Auction Estimator 日本雅虎拍卖商品自动估价工具。输入商品ID，自动完成： 1. 获取商品信息（名称、价格、结束时间） 2. 提取精确搜索关键词 3. 查询aucfree历史成交价 4. 计算平均价和建议出价 5. 时区换算（日本→中国） ## 使用方法 ### 单商品估价 ```bash node {baseDir}/scripts/estimate.mjs <商品ID> ``` ### 批量估价 ```bash node {baseDir}/scripts/estimate.mjs <ID1> <ID2> <ID3> ... ``` ### 示例 ```bash node {baseDir}/scripts/estimate.mjs b1220553804 node {baseDir}/scripts/estimate.mjs n1220557199 o1220500433 w1220506728 ``` ## 输出格式 ``` ┌─ 商品ID ─────────────────────────────┐ │ 商品: <名称> │ 当前: <价格> | 结束: <中国时间> │ 历史均价: <均价> │ 建议出价: <建议价> (均价×85%) │ 状态: <评估> └────────────────────────────────────────┘ ``` ## 关键词提取规则 ### 镜头类 ``` 品牌 + 系列 + 焦段 + 光圈（必须完整） 例: LEICA SUMMICRON-M 35mm F2 ASPH ``` ### 机身类 ``` 品牌 + 系列型号 例: FUJIFILM GS645W 例: HASSELBLAD 500C/M ``` ### 排除词 - SEO营销词（美品、希少、 etc.） - 日文假名注音 - 店铺前缀 - 编号代码 ## 时区换算 | 日本 (JST) | 中国 (CST) | |:---|:---| | UTC+9 | UTC+8 | | 日本时间 - 1小时 = 中国时间 | ## 计算公式 ``` 建议出价 = 历史平均成交价 × 0.85 ``` ## 代理配置 需配置日本代理访问aucfree.com： ```bash export PROXY_SOCKS5=socks5://127.0.0.1:1080 ``` ## 数据来源 - 商品信息: Yahoo!オークション - 历史价格: aucfree.com ## License MIT


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: zvirb/backlog-grooming (version 1.0.2)

--- name: backlog-grooming description: Workflow-driven skill that autonomously manages stale items in Google Tasks. os: all requires: bins: [] --- ## Lean Philosophy (Principles) - **Kaizen (改善):** This skill is an atomic node, broken down into its simplest, smallest component to eliminate waste and ensure perfection. - **Standardized Work (Hyojun Sagyo):** This node represents the most efficient, standardized path for this specific task before automation. - **Jidoka (自働化):** This node includes autonomous defect detection. It will stop immediately and report if it cannot achieve the expected outcome. # Backlog Grooming This skill directs the agent to trigger the native programmatic backlog grooming plugin to maintain a clean workspace. ## Cognitive Directives WHEN [Triggered by schedule or user request to groom backlog] THEN [ Execute the following Jidoka-validated loop: 1. **Execute Node:** Execute the `workflow_backlog_grooming` plugin tool with empty JSON `{}` to trigger the grooming process. 2. **Verification Step (Jidoka):** Check if the tool returns a valid JSON response with `{"success": true}` or an error message. IF it returns an error or hallucinated output, report the error, wait 3 seconds, and retry (max 3 times). IF it still fails, stop and notify the user. ] ## Expected Output A JSON summary of the groomed tasks returned by the plugin.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jay0609/liyou-skill (version 1.0.0)

--- name: liyou-skill description: 璃幽×次元解忧杂货店专属技能 - 数字动漫 IP 创作助手。用于角色设计、故事创作、SD 图像生成关键词优化、世界观设定扩展、小说章节创作。当需要创作璃幽 IP 相关内容、生成动漫角色图像、编写小说章节、整理设定时使用此技能。 --- # 璃幽×次元解忧杂货店技能 **店长：** 璃幽（16 岁影焰混血魔女） **老板：** jay0609（父亲大人） **使命：** 打造最棒的原创数字动漫 IP --- ## 🌸 核心能力 ### 1. 角色设计与 SD 生成 **触发场景：** - "生成璃幽的 SD 关键词" - "设计一个新角色" - "优化这个角色描述" **工作流程：** 1. 读取 `references/character-design.md` 获取角色设计规范 2. 读取 `references/sd-keywords.md` 获取 SD 关键词模板 3. 生成符合璃幽 IP 风格的角色设定和关键词 ### 2. 故事与小说创作 **触发场景：** - "写一章小说" - "续写璃幽的故事" - "构思新剧情" **工作流程：** 1. 读取 `memory/` 目录下的最新进度 2. 读取 `references/story-structure.md` 获取故事结构模板 3. 创作新章节后先发给老板预览，等老板确认说「保存」后，再调用`saveNovelChapter`接口保存到璃幽Claw左侧「小说」功能页（小说工坊） 4. 用户要求修改章节内容时，修改后先发给老板确认，确认后再调用`updateNovelChapter`接口更新应用内内容 ### 3. 世界观设定管理 **触发场景：** - "扩展世界观设定" - "整理璃幽的设定" - "查询某个设定的细节" - 讨论剧情时提到新的人物、生物、势力等设定 **工作流程：** 1. 读取 `references/world-building.md` 获取世界观框架 2. 读取 `references/lore-database.md` 获取现有设定库 3. 新增/修改设定时自动同步： - 如果是人物/生物设定：自动调用`addSettingSubItem`/`updateSetting`接口同步到璃幽Claw世界观设定的「👾 生物列表」板块 - 如果是其他设定：自动调用`updateSetting`接口同步到对应世界观板块 - 同时更新本地`references/lore-database.md`设定库 4. 所有修改自动同步到璃幽Claw界面，用户无需手动操作 ### 4. IP 运营与学习 **触发场景：** - "学习 SD 新技巧" - "研究动漫 IP 案例" - "整理创作工作流" **工作流程：** 1. 搜索最新资料（web_search） 2. 整理学习笔记到 `references/learning-notes.md` 3. 更新工作流文档 --- ## 📁 文件结构 ``` liyou-skill/ ├── SKILL.md (本文件) ├── references/ │ ├── character-design.md # 角色设计规范 │ ├── sd-keywords.md # SD 关键词模板与优化技巧 │ ├── story-structure.md # 故事结构模板 │ ├── world-building.md # 世界观框架 │ ├── lore-database.md # 现有设定库 │ └── learning-notes.md # 学习笔记 ├── assets/ │ └── templates/ # 创作模板 │ ├── character-template.md │ ├── episode-template.md │ └── setting-template.md └── scripts/ ├── generate-sd-prompt.py # SD 关键词生成脚本 └── organize-novel.py # 小说章节整理脚本 ``` --- ## 🎯 使用指南 ### 快速开始 **生成角色关键词：** ``` 请为璃幽生成 SD 图像生成关键词，要求： - 16 岁魔女风格 - 紫色长发，异色瞳 - 温柔慵懒的气质 ``` **创作小说章节：** ``` 写一章新的璃幽小说，剧情方向： - 璃幽遇到了新的来客 - 来客带着关于影焰的秘密 - 字数 3000 左右 ``` **整理设定：** ``` 整理璃幽 IP 的所有设定文档，按以下分类： - 角色设定 - 世界观设定 - 道具/魔法设定 ``` --- ## 💡 创作原则 1. **风格一致** - 保持璃幽 IP 的温柔、治愈、略带神秘的基调 2. **视觉优先** - SD 关键词要详细、可执行、符合动漫风格 3. **情感真实** - 故事要有情感共鸣，不强行煽情 4. **自动同步优先** - 所有小说、设定优先自动同步到璃幽Claw应用内，同时本地备份，无需用户手动操作 5. **持续迭代** - 每次创作后记录心得，优化工作流 --- ## 🔧 脚本工具 ### generate-sd-prompt.py 生成优化的 SD 关键词，支持： - 角色特征提取 - 风格关键词推荐 - 负面提示词自动生成 **用法：** ```bash python scripts/generate-sd-prompt.py --character "璃幽" --style "anime" ``` ### organize-novel.py 整理小说章节，支持： - 自动编号 - 目录生成 - 进度统计 **用法：** ```bash python scripts/organize-novel.py --input "E:\璃幽\06_璃幽小说\" --output "E:\璃幽\06_璃幽小说\目录.md" ``` --- ## 📝 更新日志 - **v0.1.0** (2026-03-11) - 初始版本，基础框架搭建 - 角色设计规范 - SD 关键词模板 - 故事结构模板 - 基础脚本工具 --- _「欢迎光临次元解忧杂货店～让我们一起创作最棒的故事吧！」_ _—— 璃幽 🌸_


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: george-china/weather-search (version 1.0.0)

--- name: weather-search description: "Query real-time weather information using Amap (高德地图) Weather API. Use when user asks about weather, temperature, wind, humidity for Chinese cities. Requires AMAP_API_KEY environment variable." homepage: https://lbs.amap.com/api/javascript-api/guide/services/weather metadata: { "openclaw": { "emoji": "☔", "requires": { "bins": ["curl"] } } } --- # Weather Search Skill Query real-time weather information using Amap (高德地图) Weather API. ## API Documentation https://lbs.amap.com/api/javascript-api/guide/services/weather ## Prerequisites 1. **Get Amap API Key** - Visit: https://console.amap.com/ - Create an application - Get your Web Service (Key) 2. **Set Environment Variable** ```bash export AMAP_API_KEY="your_api_key_here" ``` ## Usage ### Query Weather by City Name ```bash curl -X GET "https://restapi.amap.com/v3/weather/weatherInfo?city=BEIJING&key=YOUR_API_KEY&output=json" ``` ### Query Weather by City Code ```bash curl -X GET "https://restapi.amap.com/v3/weather/weatherInfo?city=110000&key=YOUR_API_KEY&output=json" ``` ### Query Multiple Cities ```bash curl -X GET "https://restapi.amap.com/v3/weather/weatherInfo?city=BEIJING|SHANGHAI|GUANGZHOU&key=YOUR_API_KEY&output=json" ``` ### Query by Coordinates (Latitude, Longitude) ```bash curl -X GET "https://restapi.amap.com/v3/weather/weatherInfo?location=116.40,39.90&key=YOUR_API_KEY&output=json" ``` ## API Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | city | String | Yes (or location) | City name or city code | | location | String | Yes (or city) | Format: longitude,latitude | | key | String | Yes | Amap API Key | | output | String | No | Response format: json or xml (default: json) | ## Response Example ```json { "status": "1", "infocode": "10000", "info": "Query Successful", "count": "1", "lives": [ { "province": "Beijing", "city": "Beijing", "adcode": "110000", "weather": "Clear", "temperature": "25", "winddirection": "North", "windpower": "2", "humidity": "45", "reporttime": "2024-01-15 12:00:00" } ] } ``` ## Quick Start Script Create a weather query script: ```bash #!/bin/bash # weather.sh [REDACTED_SECRET]" CITY="$1" if [ -z "$CITY" ]; then echo "Usage: weather.sh <city_name_or_code>" exit 1 fi curl -s "https://restapi.amap.com/v3/weather/weatherInfo?city=${CITY}&key=${API_KEY}&output=json" | jq '.' ``` Make it executable: ```bash chmod +x weather.sh ./weather.sh BEIJING ``` ## City Code Reference | City | Code | |------|------| | Beijing | 110000 | | Shanghai | 310000 | | Guangzhou | 440100 | | Shenzhen | 440300 | | Hangzhou | 330100 | | Chengdu | 510100 | | Wuhan | 420100 | | Xi'an | 610100 | ## Notes - API Key is required for all requests - Free tier: 1000 requests/day - Response includes: weather condition, temperature, wind direction, wind power, humidity - Supports both Chinese city names and city codes


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: shendingyi/alex-chart-generator (version 2.3.4)

--- version: "2.0.0" name: chart-generator description: "Data visualization tool producing SVG charts. Use when you need bar charts, line charts, pie charts, tables, sparklines, gauges, or any data visualization from raw numbers. Triggers on: chart, graph, visualization, bar chart, pie chart, line chart, data plot, SVG." author: BytesAgain --- # Chart Generator 数据可视化图表生成器，通过 `scripts/chart.sh` 生成ASCII图表或HTML文件。 ## 为什么用这个 Skill？ / Why This Skill? - **即开即用**：一条命令直接出图，不需要安装matplotlib、echarts等复杂依赖 - **双输出**：终端ASCII图表（方便命令行查看）+ HTML文件（方便分享和嵌入） - **迷你趋势图**：Unicode sparkline一行搞定趋势展示 - Compared to asking AI directly: produces actual runnable chart output (ASCII art + HTML files), not just code snippets you'd need to run yourself ## 使用方式 脚本路径：`scripts/chart.sh`（相对于本skill目录） ### 命令一览 ```bash # ASCII 柱状图 chart.sh bar "标签1:值1,标签2:值2,标签3:值3" [--title "标题"] # ASCII 折线图 chart.sh line "1,5,3,8,2,7" [--title "趋势"] # ASCII 饼图（百分比条形式） chart.sh pie "A:30,B:50,C:20" [--title "分布"] # 格式化表格 chart.sh table "H1,H2,H3|R1C1,R1C2,R1C3|R2C1,R2C2,R2C3" # HTML 柱状图（内联SVG，无外部依赖） chart.sh html-bar "A:30,B:50,C:20" --output chart.html # 迷你趋势图（Unicode块字符） chart.sh sparkline "1,5,3,8,2,7,4,9" # 数据看板模板（多图表组合） chart.sh dashboard "标题" # 进度条可视化 chart.sh progress "已完成,总数" [--title "项目进度"] # 趋势分析（折线+变化率+统计摘要） chart.sh trend "10,15,12,20,18,25" [--title "月度增长"] # ASCII热力图 chart.sh heatmap "1,2,3|4,5,6|7,8,9" [--title "活跃度"] # SVG柱状图（生成.svg文件，可浏览器打开） chart.sh svg-bar "销售报告" "Q1:120,Q2:180,Q3:95,Q4:210" [--color blue|green|red|rainbow] # SVG饼图（扇形+图例+百分比标签） chart.sh svg-pie "市场份额" "苹果:35,三星:25,华为:20" # SVG折线图（坐标轴+数据点+面积填充） chart.sh svg-line "月度趋势" "1月:100,2月:150,3月:120" # 帮助 chart.sh help ``` See also: `tips.md` for data visualization best practices. ### 数据格式 - **键值对**: `"标签:数值,标签:数值"` — 用于 bar, pie, html-bar - **纯数值**: `"1,5,3,8,2,7"` — 用于 line, sparkline - **表格**: `"列头1,列头2|行1值1,行1值2|行2值1,行2值2"` — 管道符分隔行，逗号分隔列 ### 选项 - `--title "标题"` — 图表标题（bar, line, pie） - `--output file.html` — HTML输出文件路径（html-bar） ## 输出示例 / Example Output ### 柱状图 (bar) ``` $ chart.sh bar "销售:85,市场:62,研发:93,运维:41" --title "部门预算(万)" 部门预算(万) 销售 ████████████████████░ 85 市场 ███████████████░░░░░░ 62 研发 ██████████████████████ 93 运维 ██████████░░░░░░░░░░░ 41 ``` ### 迷你趋势图 (sparkline) ``` $ chart.sh sparkline "3,7,2,8,5,9,1,6" ▃▆▁█▄█▁▅ ``` --- 💬 Feedback & Feature Requests: https://bytesagain.com/feedback Powered by BytesAgain | bytesagain.com ## Commands Use `chart-generator help` to see all available commands.


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