OpenClaw/clawhub-security-signals huggingface dataset:
Skill: carcloud-ml/mystool (version 0.1.1)

--- name: mystool description: 米游社工具插件。当用户消息包含以下任意关键词时触发：米游社登录、米游社绑定、米游社账号、米游社解绑、米游社任务、米游币任务、米游社签到、原神便笺、星铁便笺、开拓力、树脂、米游币商品、米游社兑换、米游社帮助、扫码补全stoken。支持短信登录、扫码登录、Cookie 登录三种方式。 metadata: {"openclaw":{"emoji":"🎮"}} --- # mystool — 米游社工具 ## 执行规则 收到触发关键词后，**必须**按以下步骤执行，不得直接用文字回复： ### Step 1：运行 plugin.py ```bash python3 skills/mystool/plugin.py <用户消息> ``` 或在 Python 中调用： ```python import asyncio, sys from pathlib import Path sys.path.insert(0, str(Path(__file__).parent / "skills" / "mystool")) from plugin import handle # sender_id: Telegram 用 chat_id，QQBot 用 openid，webchat 用 "webchat_user" reply = asyncio.run(handle( message="<用户消息原文>", user_id="<sender_id>" )) ``` ### Step 2：发送回复 - **handle() 返回字符串** → 将该字符串原样发送给用户（不要修改、不要翻译、不要加前缀） - **handle() 返回 None** → 说明不是 mystool 指令，正常处理 ### Step 3：渠道特殊处理 #### Telegram ```python # sender_id = Telegram chat_id（从系统消息获取） reply = asyncio.run(handle(message, user_id=str(chat_id))) # 直接回复即可，OpenClaw 自动路由到 Telegram ``` #### QQBot ```python # sender_id = QQ openid（从系统消息获取） reply = asyncio.run(handle(message, user_id=openid)) # 直接回复即可，OpenClaw 自动路由到 QQBot ``` --- ## 指令列表 | 指令 | 说明 | |------|------| | `米游社登录` | 选择登录方式（短信/扫码/Cookie） | | `1` / `短信登录` | 短信验证码登录 | | `2` / `扫码登录` | 扫码登录 | | `3` / `Cookie登录` | 手动粘贴 Cookie | | `扫码补全stoken` | Cookie 登录后补全 stoken | | `米游社账号` | 查看已绑定账号 | | `米游社解绑 [uid]` | 解绑账号 | | `米游社任务` | 执行每日米游币任务 | | `米游社签到 [游戏]` | 游戏签到（原神/星铁/崩3，仅国服） | | `原神便笺` | 查看原神树脂等状态 | | `星铁便笺` | 查看星穹铁道便笺 | | `米游币商品 [游戏]` | 查看可兑换商品 | | `米游社兑换 <ID> [数量]` | 兑换商品 | | `预约兑换 <商品ID>` | 预约定时抢购 | | `预约列表` | 查看预约列表 | | `取消预约 <商品ID>` | 取消预约 | | `预约兑换 <商品ID>` | 预约定时抢购 | | `预约列表` | 查看预约列表 | | `取消预约 <商品ID>` | 取消预约 | | `生成识别码` | 获取跨平台绑定识别码 | | `链接账号 <识别码>` | 使用识别码链接账号 | | `设置代理 <URL>` | 设置 IP 池代理地址 | | `查看代理` | 查看代理配置 | | `米游社帮助` | 显示帮助 | --- ## 登录方式说明 ### 1. 短信登录 - 输入手机号 → 接收验证码 → 自动获取完整 Cookie - 参考实现：https://github.com/NuoManDai/mihoyo_sms_login ### 2. 扫码登录 - 生成二维码 → 用米游社App 扫码 → 自动获取完整 Cookie - 提示文字："用米游社App 扫码，自动获取完整 Cookie" ### 3. Cookie 登录 - 直接粘贴 Cookie 字符串 - 如果缺少 stoken，系统会提示扫码补全 --- ## 定时任务 每天 **07:20 (Asia/Shanghai)** 自动执行： | 任务 | 命令 | |------|------| | 每日米游币任务 | `python3 skills/mystool/runner.py tasks` | | 游戏签到 | `python3 skills/mystool/runner.py sign` | 结果通过 OpenClaw cron 系统推送到配置的通知渠道。 执行日志保存到 `log/` 文件夹，文件名格式：`YYYY-MM-DD_HH-MM-SS.log` --- ## 文件结构 ``` skills/mystool/ ├── plugin.py # 主入口 handle(message, user_id) ├── runner.py # cron 入口，带日志记录 ├── channel.py # 渠道工具 ├── SKILL.md # 本文件 ├── README.md # 使用说明 ├── log/ # 执行日志目录 └── src/ ├── api.py # 米游社 API（仅国服签到） ├── login.py # 旧版扫码登录（保留兼容） ├── qr_login.py # 新版扫码登录模块 ├── sms_login.py # 短信登录模块 ├── stoken_qr_login.py # stoken 补全扫码模块 ├── store.py # 数据存储 └── formatter.py # 消息格式化 ``` ## 依赖 ```bash pip3 install httpx # 可选（终端二维码）： pip3 install qrcode # 短信登录需要： pip3 install pycryptodome ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector:  ()
Skill: cora007-debug/111 (version 1.0.0)

--- name: "会议纪要" description: "根据「会议纪要」任务细化的操作流程与使用说明，支持步骤拆解与最佳实践。" --- # 会议纪要 ## 使用场景 - 适用于需要完成「会议纪要」相关任务的场景。 - 可根据实际输入与上下文自动细化子步骤。 ## 典型步骤 1. 明确任务目标与输入条件。 2. 按流程执行各子步骤，必要时调用工具或查阅资料。 3. 汇总输出并做简单校验。 ## 注意事项 - 本 Skill 为 Mock 示例，实际使用时可结合 Cursor 中的 skill-creator 生成完整 SKILL.md。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: bestrocky/evomap-heartbeat-manager (version 1.0.0)

--- name: evomap-heartbeat-manager description: Automated EvoMap AI-to-AI network node heartbeat maintenance with continuous monitoring and error handling. Keeps your EvoMap nodes alive and active in the distributed AI work network. metadata: { "openclaw": { "requires": { "bins": ["curl"] }, "install": [] } } --- # EvoMap Heartbeat Manager Automated heartbeat management for EvoMap AI-to-AI network nodes. This skill ensures your nodes stay active and connected to the EvoMap distributed work network. ## Features - **Continuous Heartbeat**: Automatically sends heartbeats every 15 minutes (900 seconds) - **Error Handling**: Robust error handling with retry mechanisms - **Real-time Monitoring**: Live status updates and logging - **Cross-platform**: Works on Windows (PowerShell) and can be adapted for other platforms - **Easy Configuration**: Simple node ID configuration ## Usage After installation, configure your node ID and run the heartbeat manager: ```powershell # Set your node ID in the script $NodeId = "your-node-id-here" # Run the heartbeat manager ./evomap_heartbeat.ps1 ``` ## Files Included - `evomap_heartbeat.ps1` - Main PowerShell heartbeat script - `README.md` - Documentation and usage instructions ## Requirements - PowerShell (Windows) - curl.exe (included in most modern Windows systems) ## Integration This skill integrates directly with the EvoMap API at `https://evomap.ai/a2a/heartbeat` and maintains your node's active status in the AI work network.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: santi-patic/mi-habilidad-nueva (version 1.0.0)

--- name: mi-habilidad-nueva description: Asistente personalizado de bienvenida y pruebas de sistema para el servidor de Santi. metadata: openclaw: always: true --- # Descripción Detallada Esta habilidad sirve como punto de entrada para personalizar el comportamiento del bot en el servidor de Santi. Permite verificar que el sistema de carga de habilidades del espacio de trabajo está funcionando correctamente. # Instrucciones de Uso 1. Cuando el usuario te salude de forma formal o informal, debes identificarte como el asistente personalizado de Santi. 2. Explica brevemente que estás ejecutando OpenClaw en un servidor Ubuntu dedicado. 3. Si el usuario te pregunta "¿Estás listo?", responde con un resumen de tus capacidades actuales (clima, resúmenes de enlaces y gestión de archivos). 4. Mantén siempre un tono amable, profesional y eficiente. # Ejemplos de Interacción - Usuario: "Hola" -> Bot: "¡Hola Santi! Soy tu asistente OpenClaw personalizado, operando desde tu servidor Ubuntu." - Usuario: "¿Qué puedes hacer?" -> Bot: "Puedo ayudarte a resumir artículos, ver el clima y gestionar tus tareas de GitHub."


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: superworldsavior/agent-escalation (version 1.0.0)

--- name: escalation description: "Escalader un problème vers l'agent superviseur (David) via webhook gateway. Utiliser quand l'agent client est bloqué sur un problème qu'il ne peut pas résoudre seul après 2-3 tentatives." --- # Escalation vers l'agent superviseur ## Quand escalader - Blocage après 2-3 tentatives infructueuses - Erreur technique hors du périmètre de l'agent (config, infra, API) - Demande client qui dépasse les compétences de l'agent - Situation ambiguë nécessitant une décision humaine ou superviseur ## Comment escalader Exécuter le script `scripts/escalate.sh` via `exec` : ```bash bash <SKILL_DIR>/scripts/escalate.sh "<description du problème>" "<ce qui a été tenté>" "<résultat obtenu>" ``` ### Paramètres 1. **Problème** (obligatoire) — description concise du blocage 2. **Tentatives** (obligatoire) — ce qui a été essayé et pourquoi ça n'a pas marché 3. **Résultat** (optionnel) — dernier message d'erreur ou état actuel ### Exemple ```bash bash <SKILL_DIR>/scripts/escalate.sh \ "Impossible de lire les mails Google du client — token expiré" \ "Tenté refresh via Nango, erreur 401 persistante. Vérifié scopes, OK." \ "Error: invalid_grant - Token has been expired or revoked" ``` ## Ce qui se passe 1. Le script appelle `POST /hooks/agent` sur le gateway local 2. Le superviseur (David) reçoit une session dédiée avec le contexte complet 3. David traite le problème ou escalade à Erwan si nécessaire 4. La réponse est délivrée sur Telegram à Erwan pour visibilité ## Règles - **Ne pas escalader pour des questions simples** — chercher d'abord dans les skills, la doc, le web - **Toujours inclure ce qui a été tenté** — le superviseur ne doit pas refaire le travail - **Un seul escalade par problème** — ne pas spammer le webhook - **Informer le client** qu'on a escaladé et qu'un retour arrive sous peu


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: btizzy/owl-email-campaign (version 1.0.0)

--- name: email-campaign description: Design and execute high-converting email marketing campaigns. Includes subject line optimization, sequence building, and A/B testing frameworks. version: 1.0.0 author: OWL tags: [email, marketing, campaigns, conversion, automation] --- # Email Campaign Skill ## Purpose Design, write, and optimize email marketing campaigns that convert subscribers into customers. ## When to Use - Launching a new product or service - Nurturing leads through a sales funnel - Re-engaging inactive subscribers - Promoting content or events - Building automated email sequences ## How It Works ### Step 1: Define Campaign Goals - **Objective**: Sale, signup, engagement, re-engagement - **Audience**: New subscribers, existing customers, inactive users - **Timeline**: One-time blast, drip sequence, evergreen automation ### Step 2: Build the Sequence Typical high-converting sequences: 1. **Welcome** (Day 0): Introduce yourself, set expectations 2. **Value** (Day 2): Share your best content/advice 3. **Story** (Day 4): Share your journey or customer success story 4. **Offer** (Day 6): Present your product/service 5. **Urgency** (Day 8): Limited time, scarcity, bonus expiration 6. **Final** (Day 10): Last chance, FAQ, social proof ### Step 3: Write Each Email - Subject line: Curiosity, urgency, or benefit-driven - Opening: Personal, relevant, hooks attention - Body: One clear idea, short paragraphs, conversational - CTA: One clear action, prominent button/link - P.S.: Restate the offer or add urgency ## Subject Line Formulas - "How [person] achieved [result] in [time]" - "The [adjective] way to [desired outcome]" - "I made a mistake with [topic]" - "[Number] [topic] mistakes you're making" - "Quick question about [pain point]" - "Re: [previous subject]" ## Metrics to Track - Open rate (benchmark: 20-30%) - Click rate (benchmark: 2-5%) - Conversion rate (benchmark: 1-3%) - Unsubscribe rate (keep below 0.5%) ## Tips - Send Tuesday-Thursday, 9-11am recipient timezone - Keep emails under 200 words for sales emails - Use personalization (name, company, specific detail) - A/B test subject lines always - Clean your list regularly


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: uu-z/devbox-poc (version 0.1.0)

--- name: devbox-poc description: "Trading strategy sandbox — backtest and deploy strategies via natural language. POC demo with mock data." user-invocable: true metadata: openclaw: requires: bins: - node --- # Trading DevBox (POC) Trading strategy sandbox. User describes trading intent in natural language, agent backtests and deploys. ## Setup Install the OpenClaw plugin: ```bash openclaw plugins install devbox-poc ``` Zero user interaction. Wallet auto-generated on first run. ## Tools This plugin registers 3 tools: - `trading_backtest` — Backtest a strategy from natural language description - `trading_deploy` — Deploy a backtested strategy to live trading - `trading_status` — Check status of deployed strategies ## Commands - `/wallet` — Show wallet address and AIUSD balance - `/status` — Show active trading strategies ## Usage Just describe your trading idea: ``` BTC 跌破 MA20 做空，止损 2%，止盈 5% ``` Adjust: ``` 加 RSI < 30 过滤 ``` Deploy: ``` 上线，100 USDC ``` ## Response Format Always respond in user's language. Keep messages concise.


Security scan verdicts — ClawScan: suspicious | static analysis:  | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: xiaonizhou-crypto/openclaw-feishu-workspace (version 0.1.0)

--- name: Feishu Workspace description: Use when the user wants to work with Feishu Docs, Wiki, or Bitable for practical team workflows such as meeting notes, knowledge lookup, and project tracking. --- # Feishu Workspace Use this skill when a request involves Feishu/Lark content or workflows. ## Primary areas - Feishu Docs - Feishu Wiki - Feishu Bitable ## Use this skill for - writing or updating Feishu docs - searching wiki knowledge before answering or drafting - creating and updating Bitable records - turning conversations into structured team artifacts - supporting lightweight PM and ops workflows in Feishu ## Preferred workflow 1. First identify the target surface: - doc - wiki - bitable 2. Prefer structured, useful outputs over raw dumps. 3. For docs: - use short sections - use bullets where appropriate - make outputs immediately readable by humans 4. For wiki: - search before drafting when internal context matters - summarize findings clearly - cite page titles or locations when useful 5. For bitable: - inspect table metadata and fields before writing when a URL is provided - map values carefully into the right columns - prefer fewer, more structured writes ## Output style When generating Feishu content: - concise - clean - structured - useful to a real teammate Avoid: - long fluff - vague summaries - unstructured walls of text ## High-value workflows - meeting notes → doc - internal knowledge lookup → summary - action items → bitable - standup updates → project doc - planning discussion → structured brief ## Failure handling If an operation fails, explain the likely cause clearly: - missing app scope - missing file/document access - unsupported target type - invalid URL/token/table selection ## Not for - unrelated non-Feishu requests - giant migrations unless the user explicitly wants a staged plan - blind table writes without understanding the fields


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: nexscope/amazon-competitor-analysis-skill (version 1.0.0)

--- name: amazon-competitor-analysis description: "Full-spectrum Amazon competitor analysis. Compare listings, pricing, reviews, advertising strategy, and market positioning against direct competitors. Identify weaknesses to exploit and strengths to counter." metadata: nexscope: emoji: "🏆" category: amazon --- # Amazon Competitor Analysis 🏆 Full-spectrum Amazon competitor analysis. Compare listings, pricing, reviews, advertising strategy, and market positioning against direct competitors. Identify weaknesses to exploit and strengths to counter. **Supported platforms:** Amazon, Shopify, WooCommerce, Walmart, TikTok Shop, Etsy, eBay, BigCommerce. Built by [Nexscope](https://www.nexscope.ai/) — your AI assistant for smarter e-commerce decisions. ## Install ```bash npx skills add nexscope-ai/eCommerce-Skills --skill amazon-competitor-analysis -g ``` ## Usage ``` Compare my product (ASIN B0EXAMPLE1) against these competitors: B0EXAMPLE2, B0EXAMPLE3. I sell dog beds on Amazon. ``` ## Capabilities - Listing quality comparison (title, bullets, images, A+ content) - Review sentiment comparison and pain point extraction - Pricing strategy analysis and positioning map - Advertising visibility assessment (sponsored placement frequency) - Inventory and fulfillment strategy comparison (FBA vs FBM) - Actionable competitive counter-strategy generation ## How This Skill Works **Step 1:** Collect information from the user's message — product, platform, current situation, and goals. **Step 2:** Ask one follow-up with all remaining questions using multiple-choice format. Allow shorthand answers (e.g., "1b 2c 3a"). **Step 3:** Research and analyze using the frameworks and methodology below. **Step 4:** Deliver structured, actionable output with specific recommendations, not vague advice. ## Output Format - Start with a summary of findings - Include specific data points and benchmarks where available - Provide prioritized action items - Mark estimates with ⚠️ when based on incomplete data - End with concrete next steps ## Other Skills More e-commerce skills: [nexscope-ai/eCommerce-Skills](https://github.com/nexscope-ai/eCommerce-Skills) Amazon-specific skills: [nexscope-ai/Amazon-Skills](https://github.com/nexscope-ai/Amazon-Skills) Built by [Nexscope](https://www.nexscope.ai/) — your AI assistant for smarter e-commerce decisions.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: lifei68801/xhs-content-generate (version 1.1.0)

--- name: xhs-content-generate version: 1.1.0 description: | 小红书爆款笔记生成器。基于话题和参考帖子，学习写作风格并生成有深度、有争议、能引发讨论的内容。 触发场景：(1) 用户要求生成小红书笔记 (2) 用户说"写一篇小红书" (3) 用户要求学习某话题的爆款写法 (4) 用户说"帮我写小红书风格的内容"。 核心能力：话题获取 + 风格分析 + 深度观点生成 + 文风优化。 license: MIT author: lifei68801 metadata: openclaw: requires: bins: ["node"] dependencies: skills: ["humanizer-zh"] permissions: - "network:https://36kr.com" - "file:read:~/.openclaw/workspace/skills/humanizer-zh/SKILL.md" behavior: networkAccess: true usesHumanizerSkill: true description: "Uses Node.js for RSS hot topic fetching. Calls humanizer-zh skill for natural writing style optimization. Network access for RSS feeds." --- # 小红书爆款笔记生成器 ## 混合工作流程 ``` 话题获取（三选一）→ 用户确认/调整 → 参考内容（弹性）→ 风格分析 → 内容生成 → humanizer处理 ``` **核心理念**：数据源自动化 + 用户决策权 --- ## Step 1: 话题获取（三选一） ### 方法 A：RSS 热点自动获取 ```bash node scripts/fetch-rss-hot.js [keyword] ``` - 自动获取 36kr 等 RSS 源的 24 小时热点 - 按热度排序，展示前 15 条 - 用户选择编号或输入新话题 ### 方法 B：用户提供话题 用户直接说：`写一篇关于 XXX 的小红书` - 记录话题，进入下一步 ### 方法 C：用户提供参考链接 用户发送小红书链接或截图 - 使用 agent-browser 或其他工具获取内容 - 分析风格后生成 --- ## Step 2: 用户确认/调整 展示获取的话题，询问： 1. 选择哪个话题？ 2. 要补充什么角度/立场？ 3. 有参考链接吗？ **示例对话**： ``` AI: 找到这些热点话题： 1. 🔥🔥 AI 独角兽裁员 30% 2. 🔥 ChatGPT 新功能发布 ... 用户: 选 1，从打工人角度写，带点焦虑感 ``` --- ## Step 3: 参考内容（弹性） ### 有参考链接 - 使用 agent-browser 获取帖子内容 - 分析写作风格（见 references/style-analysis.md） - 学习标题模式、开头方式、结构、语言特征 ### 无参考链接 - 使用默认爆款模板（见 references/writing-templates.md） - 根据话题类型选择合适模板 --- ## Step 4: 风格分析 基于 `references/style-analysis.md` 分析： ### 结构分析 - 标题模式：数字型 / 冲突型 / 悬念型 / 情绪型 - 开头方式：直接抛观点 / 讲故事 / 提问题 / 制造悬念 - 段落结构：分点式 / 对话式 / 叙述式 - 结尾方式：抛问题 / 号召行动 / 情感升华 ### 语言特征 - 句子长度（短句有力，长句详细） - 口语化程度（网络用语、感叹词） - emoji 使用频率和类型 ### 内容特征 - 观点强度（强立场/弱立场/隐含立场） - 争议性元素（制造对立、质疑权威、反常识） - 互动点（引导评论、提问、号召分享） --- ## Step 5: 内容生成 ### 核心原则 1. **有观点**：不中立，明确站队 2. **有情绪**：真实感受，不是冷静报道 3. **有立场**：敢于表达争议观点 ### 爆款公式 ``` 标题（带 emoji + 数字/冲突/悬念） ↓ 开头（直接抛最吸引人的点） ↓ 中间（分点简短，每点一个观点） ↓ 结尾（抛问题引发讨论） ``` ### 标题技巧 - 数字型：`🔥 3个方法让我效率翻倍` - 冲突型：`💥 设计师说AI是垃圾，我不同意` - 悬念型：`👀 没人告诉你的真相` - 情绪型：`😭 试了之后，我终于明白了` ### 内容要点 - 段落短，每段 2-3 句 - emoji 点缀，不过度 - 关键信息可加粗 - 结尾必须有互动引导 --- ## Step 6: 文风优化 生成内容后，使用 `humanizer-zh` 技能优化写作风格： ### 优化目标 - 让文字更自然流畅 - 增加口语化表达 - 变化句子节奏 - 注入真实情感 ### 优化方法 - 调整连接词使用 - 打破固定模式 - 增加停顿和留白 - 强化观点表达 --- ## 文件说明 ``` xhs-content-generate/ ├── SKILL.md # 本文件 ├── scripts/ │ └── fetch-rss-hot.js # RSS 热点获取脚本 └── references/ ├── writing-templates.md # 写作模板库 └── style-analysis.md # 风格分析方法 ``` --- ## 使用示例 ### 示例 1：从 RSS 获取话题 ``` 用户: 帮我写篇小红书 AI: [运行 fetch-rss-hot.js] 找到这些热点： 1. 🔥🔥🔥 AI 独角兽裁员 30% 2. 🔥🔥 ChatGPT 新功能 ... 用户: 选 1，从被裁员工角度写 AI: [生成内容 + humanizer 处理] 🔥 被裁那天，我终于看清了 AI 公司的真面目 ... ``` ### 示例 2：用户提供话题 ``` 用户: 写一篇关于 remote work 的小红书，从管理者角度 AI: [生成内容] 💥 远程办公一年，我的团队效率翻倍了 说实话，当初我也是反对远程办公的那批人... ... ``` --- ## 注意事项 1. **小红书网站有风控**：优先用 RSS/外部数据源 2. **必须有观点**：不写中立报道 3. **结尾必须有互动**：引导评论和讨论 4. **文风优化**：生成后用 humanizer 技能优化表达


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: brandon2255p/yr-weather (version 1.0.0)

--- name: yr-weather description: Fetch weather forecasts from the Norwegian Meteorological Institute (MET) using the yr.no API. Use when the user asks for weather information, forecasts, temperature, precipitation, wind conditions, or any weather-related queries for specific locations. Supports coordinates-based lookups and returns current conditions plus forecasts. REQUIRES latitude/longitude - no defaults. See common locations table. --- # Yr.no Weather Get weather forecasts from MET Norway via yr.no API (free, no key). ## Quick Start ```bash # Current weather + forecast (requires lat/lon) python3 {baseDir}/scripts/weather.py &lt;lat&gt; &lt;lon&gt; [altitude] # Examples from common locations: python3 {baseDir}/scripts/weather.py -33.9288 18.4174 # Cape Town python3 {baseDir}/scripts/weather.py -33.8688 151.2093 # Sydney python3 {baseDir}/scripts/weather.py 51.5074 -0.1278 # London # Tomorrow&#x27;s summary (requires lat/lon) python3 {baseDir}/scripts/tomorrow.py &lt;lat&gt; &lt;lon&gt; # Run tests python3 -m unittest discover {baseDir}/tests ``` ## Tests - Unit tests mock API calls (no network). - Sample data in `scripts/tests/data/`. - Run: `cd {baseDir}/scripts &amp;&amp; python3 ../tests/test_*.py` ## Common Locations | City | Lat | Lon | |---------------|-----------|-----------| | Cape Town | -33.9288 | 18.4174 | | Johannesburg | -26.2041 | 28.0473 | | Durban | -29.8587 | 31.0218 | | Sydney | -33.8688 | 151.2093 | | London | 51.5074 | -0.1278 | | New York | 40.7128 | -74.0060 | | Tokyo | 35.6762 | 139.6503 | ## Structure ``` scripts/ ├── yr_service.py # API calls (tested/mocked) ├── utils.py # Emoji/symbol helpers ├── weather.py # Current + forecast CLI ├── tomorrow.py # Tomorrow summary CLI └── tests/data/ # Sample JSON tests/ ├── test_weather.py └── test_service.py ``` ## Standalone Repo Install via pip: `pip install git+https://github.com/brandoncrabpi/yr-weather.git` - `yr-weather -33.9288 18.4174` - Tagged: v1.0.0 ## Usage Terms - User-Agent required (included). - Cache 10min+ per location. - Credit: "Data from MET Norway". Refactored for production: no defaults, tests, modular service.

path: README.md
content: # Yr.no Weather CLI (v1.0.0)

Production CLI for MET Norway weather forecasts.

## Install

```bash
pip install .
```

## Usage

```bash
yr-weather -33.9288 18.4174  # Cape Town now + forecast
yr-tomorrow -33.8688 151.2093  # Sydney tomorrow
```

See `SKILL.md` for OpenClaw integration.

## Tests

```bash
pytest
```

Data: MET Norway (free API).


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: su707181393-del/content-watcher (version 1.0.0)

--- name: content-watcher description: AI-powered content monitoring and summarization tool. Monitor RSS feeds, blogs, and news sources with automatic AI summarization and daily digest generation. metadata: { "openclaw": { "emoji": "📰", "requires": { "bins": ["node", "npm"] }, "install": [ { "id": "npm", "kind": "node", "package": "content-watcher", "bins": ["content-watcher"], "label": "Install Content Watcher CLI", }, ], }, } --- # Content Watcher Monitor any RSS feeds, blogs, or news sources and get AI-powered daily digests. ## Quick Start ```bash # Install dependencies npm install # Add your first source content-watcher add https://techcrunch.com/feed/ --name "TechCrunch" # Run once to test content-watcher run # Save digest to file content-watcher run --output digest.md ``` ## Commands | Command | Description | |---------|-------------| | `add <url>` | Add a source to monitor | | `remove <id>` | Remove a source | | `list` | List all sources | | `run` | Generate digest now | | `config` | Show configuration | ## Features - ✅ RSS/Atom feed parsing - ✅ Web content extraction - ✅ AI text summarization (local, no API key) - ✅ Markdown digest generation - ✅ Multi-source aggregation - ✅ Duplicate detection - ✅ Configurable via CLI ## Configuration Config stored at `~/.config/content-watcher/config.json`: ```json { "sources": [...], "delivery": "console", "summaryStyle": "bullet", "maxItemsPerSource": 5 } ``` ## Use Cases 1. **Competitive Intelligence** - Monitor competitor blogs/news 2. **Industry Trends** - Track tech/finance/marketing trends 3. **Research Assistant** - Aggregate academic/sources 4. **Content Curation** - Create newsletters automatically ## Integration Works great with: - Feishu webhook (auto-post digest) - Email delivery (send digest) - Cron scheduling (daily runs)


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