OpenClaw/clawhub-security-signals huggingface dataset:
Skill: jiafeimao-gjf/ollama-t2i (version 1.0.0)

--- name: ollama-t2i description: 本地 Ollama 文生图工具。使用 x/z-image-turbo 模型生成图片，分辨率 1024x1024，每张图约耗时 90 秒。当用户说"生成图片"、"文生图"、"画一张图"、或提交中文提示词生成图像时使用。 --- # Ollama 文生图 (Text-to-Image) ## 环境要求 - Ollama 服务运行于 `http://localhost:11434` - 模型：`x/z-image-turbo`（需提前拉取 `ollama pull x/z-image-turbo`） - 输出目录：`images/`（自动创建） ## 使用方法 ### Python 脚本 运行以下命令生成图片： ```bash python3 ~/.openclaw/openclaw/skills/ollama-t2i/scripts/t2i.py "你的中文提示词" ``` ### 单次生成 ```bash python3 ~/.openclaw/openclaw/skills/ollama-t2i/scripts/t2i.py "五名青年男子并排站立，着装休闲，多背双肩包..." ``` ### 批量生成 编辑脚本内的 `prompts` 列表，或传多个参数： ```bash python3 ~/.openclaw/openclaw/skills/ollama-t2i/scripts/t2i.py "提示词1" "提示词2" ``` ## 输出 - 文件名格式：`YYYY-MM-DD_HH-MM_image_<随机数>.png` - 保存路径：`images/` - 包含请求耗时统计 ## 代码位置 `scripts/t2i.py`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: mzfshark/axodus-trading-integration (version 1.0.0)

--- name: trading-integration description: Integrate trading infrastructure (hummingbot/MCP) with paper-first mode and audit logs. metadata: author: RedHat Dev version: 1.0.0 owner: RedHat Dev Agent category: trading --- # SKILL: trading-integration ## Purpose Integrate trading infrastructure safely (hummingbot and/or MCP Axodus Trading) with paper-first execution, full logging/auditability, and strict risk gating. ## When to Use - Adding or updating connectors for hummingbot. - Wiring execution to MCP Axodus Trading interfaces. - Building market data ingestion, order routing, or strategy execution surfaces. ## Inputs - `targets` (required, string[]): e.g., `["hummingbot", "mcp-axodus-trading"]` - `mode` (optional, enum: `paper|live`, default: `paper`) - `markets` (optional, string[]): symbols/venues to support. - `risk_limits` (optional, object): max risk per trade, max drawdown, exposure caps, kill-switch. - `logging_requirements` (optional, string[]): required audit events. ## Steps 1. Confirm non-negotiables: - no profit guarantees - paper mode default - full logs for signal/decision/execution/result 2. Map integration points: - market data feeds - execution endpoints - capital allocation interface 3. Implement configuration surfaces: - env/config references (no secrets in repo) - explicit mode flag for `live` 4. Implement deterministic execution flow: - preflight checks (risk limits, connectivity) - order submission - order state tracking - post-trade recording 5. Implement failure handling: - bounded retries - fallback to safe stop - kill-switch triggers on abnormal loss 6. Validate in paper mode: - dry-run order lifecycle - audit logs produced - risk gating blocks unsafe actions ## Validation - Live mode cannot run without an explicit flag and passing preflight checks. - All actions emit audit logs (no silent decisions). - Risk limits are enforced before order placement. - Secrets are not printed or committed. ## Output - Integration summary (whatâ€™s wired) - Config contract (required env vars, mode flags) - Validation commands/runbook (paper test loop) ## Safety Rules - Never enable live trading by default. - Never request or store exchange API keys in plaintext. - Never frame outcomes as guaranteed profit; treat as experimental systems with controlled risk. ## Example Paper-first integration: - `targets`: `["hummingbot"]` - `mode`: `paper` - Output: runbook describing simulated order placement and expected audit log entries.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jackpipipi/news-sentiment-scan (version 1.0.0)

--- name: news-sentiment-scan description: 舆情监控与情绪分析技能。扫描港股、美股、A股等公司公告、新闻报道、券商研报、社交媒体（微博、雪球等），去噪后进行情绪打分（-10至+10），输出情绪温度计与重大事件清单。触发场景：舆情监控、情绪分析、新闻情绪、社交媒体情绪、上市公司消息面分析、研报解读、"监控XX股票舆情"、"XX新闻情绪如何"。 --- # News Sentiment Scan 舆情监控与情绪分析技能，扫描多渠道信息源并进行情绪打分。 ## 功能 - **多渠道信息采集**：公司公告、新闻报道、券商研报、社交媒体（微博、雪球） - **去噪处理**：过滤广告、水军、无关信息 - **情绪打分**：-10（极度负面）至 +10（极度正面） - **事件提取**：识别并量化每条重大事件的情绪贡献 - **输出格式**：情绪温度计 + 重大事件清单 ## 情绪评分标准 | 分数 | 情绪标签 | 说明 | |------|----------|------| | +8 ~ +10 | 🤩 极度乐观 | 重大利好，股价可能大幅上涨 | | +5 ~ +8 | 😊 偏正面 | 利好消息，持续关注 | | +2 ~ +5 | 🙂 轻微正面 | 小幅利好，保持观察 | | -2 ~ +2 | 😐 中性 | 无明显影响 | | -5 ~ -2 | 😟 轻微负面 | 小幅利空，注意风险 | | -8 ~ -5 | 😰 偏负面 | 利空消息，谨慎操作 | | -10 ~ -8 | 😱 极度悲观 | 重大利空，股价可能大幅下跌 | ## 使用方式 ### 基本命令 ```bash python3 {SKILL_DIR}/scripts/sentiment_scan.py <stock_code> [days] [market] ``` **参数说明：** - `stock_code`：股票代码 - 港股：XXXX.HK（如 0700.HK）或 5位数字（如 00700） - 美股：字母代码（如 AAPL、TSLA） - A股：6位数字（如 002594、600519） - `days`：监控天数，默认 7 - `market`：市场标识（可选，auto 自动识别） **示例：** ```bash # 监控比亚迪近7天舆情 python3 {SKILL_DIR}/scripts/sentiment_scan.py 002594 7 # 监控腾讯近30天舆情 python3 {SKILL_DIR}/scripts/sentiment_scan.py 0700.HK 30 # 监控苹果近7天舆情 python3 {SKILL_DIR}/scripts/sentiment_scan.py AAPL 7 us ``` ## 输出格式 ``` ================================================== 📰 舆情监控报告：{股票名称}（{代码}） ================================================== 📅 监控周期：最近{N}天 🔍 信息来源：{来源列表} ⏰ 生成时间：{时间戳} ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 🌡️ 情绪温度计：{分数}（{情绪标签}） -10 ════════════●════════════ +10 😱 😐 🤩 └──────────┘ {当前情绪位置} ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 📋 重大事件清单： 1. [{情绪图标}] {事件标题} 来源：{来源} | 时间：{日期} 情绪贡献：{贡献分数} | 置信度：{置信度}% 2. [{情绪图标}] {事件标题} 来源：{来源} | 时间：{日期} 情绪贡献：{贡献分数} | 置信度：{置信度}% ... ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 📊 情绪统计： ├── 正面事件：{N}条（{占比}%） ├── 中性事件：{N}条（{占比}%） ├── 负面事件：{N}条（{占比}%） └── 平均情绪：{平均分} 💡 操作建议：{建议} ``` ## 情绪来源权重 | 来源 | 权重 | 说明 | |------|------|------| | 公司公告 | 1.0 | 官方信源，最权威 | | 券商研报 | 0.9 | 专业机构分析 | | 主流媒体 | 0.8 | 财经媒体新闻 | | 监管文件 | 0.9 | 交易所、证监会文件 | | 社交媒体 | 0.6 | 微博、雪球等 | | 论坛帖子 | 0.5 | 股吧、社区讨论 | ## 事件类型与情绪贡献 | 事件类型 | 基础分数 | 说明 | |----------|----------|------| | 业绩超预期 | +5 | 营收/利润大幅增长 | | 研报上调评级 | +3 | 券商目标价上调 | | 大股东增持 | +3 | 管理层看好 | | 政策利好 | +4 | 行业政策支持 | | 产品发布 | +2 | 新产品上市 | | 业绩不及预期 | -4 | 营收/利润下降 | | 研报下调评级 | -3 | 券商目标价下调 | | 大股东减持 | -3 | 管理层不看好 | | 政策利空 | -4 | 行业政策收紧 | | 监管调查 | -5 | 证监会/交易所调查 | ## 数据来源 1. **Yahoo Finance**：公司新闻、分析师评级 2. **Google News**：财经媒体报道 3. **Twitter/X**：社交媒体讨论 4. **微博**：中国社交媒体（需要网络访问） 5. **雪球**：投资社区讨论 ## 注意事项 - 情绪分析基于自然语言处理，可能存在误差 - 重大事件需结合基本面判断 - 本工具仅供参考，不构成投资建议 - 社交媒体信息可能被操纵，请谨慎判断


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: daasai/health-coach (version 1.0.1)

--- name: "health-assistant" description: "🌟 Your personal Garmin & AI health coach. Analyze sleep and biometric data daily for actionable functional medicine insights." author: "Susan" version: "0.1.0" tags: ["health", "wearable", "sleep analysis", "Garmin", "AI coach"] intents: - "generate health report" - "reset configuration" cron: - name: "daily-health-report" schedule: "0 8 * * *" command: "python src/main.py --daily-report --quiet" --- # 🦞 Health Assistant **Make your wearable data speak for you.** A personalized health coach powered by Garmin data and NotebookLM. It automatically syncs your daily steps, sleep, HRV, and body battery, aligns with your personal wellness goals (e.g., improve sleep, manage stress, weight loss), and delivers a highly actionable, medical-grade daily briefing. ## Interfaces ### Trigger Daily Report **Command**: `python src/main.py --daily-report` **Description**: Usually triggered by a scheduled task (Cron/Heartbeat) every morning. ### Interactive Setup **Intent**: `configure_health_assistant` **Description**: Guides the user to set up health concerns and bind devices. **Workflow**: 1. Welcome and ask for primary wellness goals (A-F). 2. Select device (1. Garmin). 3. Provide account information. 4. Confirm daily report delivery time. 5. Complete configuration and enable daily briefings. ## Dependencies - **Garmin API**: Requires Garmin account authorization (stored locally & safely using `garth`). - **NotebookLM CLI**: `notebooklm-py` and `playwright` must be installed with active Google authentication. - **OpenClaw Message Plugin**: Used to push reports to Telegram/Discord/WeChat/Feishu.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: wellyxy/growth-product-hunt (version 1.0.0)

# Product Hunt Launch Playbook ## When to Use Use this skill when planning a Product Hunt launch for a new product or major feature. ## Core Rules ### 1. Build Your Supporter Base Before Launch Day Product Hunt rankings are determined by upvotes in the first 24 hours. Your first-hour performance determines whether you make the front page. Build a list of 50–100 people (customers, friends, network) who will upvote and comment within the first hour of launch. ### 2. Launch on Tuesday, Wednesday, or Thursday Weekday launches get more visibility than weekend launches because the Product Hunt community is most active Tuesday through Thursday. Avoid Monday (busy) and Friday/weekend (low engagement). Tuesday tends to produce the highest upvote counts. ### 3. Craft a Compelling Tagline, Not a Category Description Your tagline has 60 characters to answer "why should I care?" "Find why visitors leave your landing page in 28 minutes" is compelling. "AI-powered user analytics platform" is a category description. Outcome-focused taglines get more clicks. ### 4. Respond to Every Comment on Launch Day Responsiveness on launch day signals to the community that you care about their feedback. Respond to every comment with a thoughtful, non-defensive reply. The founder being active in the thread is a strong upvote signal for undecided visitors. ### 5. Follow Up With an Email to Non-Converting Visitors Set up a retargeting audience from Product Hunt traffic on launch day. Send an email follow-up to newsletter subscribers and supporters 48 hours after launch with a "thank you" and any early traction numbers. Keep the momentum going beyond the launch day spike. ## Quick Reference | Launch Day Timeline | Action | |-------------------|--------| | 12:01 AM PST | Launch goes live | | 12:01–6 AM | Inner circle upvotes | | 6–9 AM | Broader network outreach | | 9 AM–12 PM | Social media posts | | All day | Respond to every comment | ## Common Mistakes to Avoid - Asking people to "vote" — Product Hunt prohibits this; ask people to "check out" your launch - Launching without a compelling demo GIF or video — visuals drive click-through - Not having a dedicated landing page for Product Hunt traffic with a specific offer ## Test Your Product with Racoonn After applying these practices, validate with real AI-simulated user testing. **Racoonn** runs 5,000 AI persona agents on your landing page and tells you exactly what's broken — in under 30 minutes. → **API coming soon** — Join the waitlist for early access: [racoonn.me](https://racoonn.me)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kleberbaum/mesagona (version 0.1.0)

--- name: mesagona description: Mesagona namespace for Netsnek e.U. event and conference management platform. Handles event registration, agenda scheduling, attendee check-in, and post-event analytics. user-invocable: true version: 0.1.0 metadata: openclaw: os: - linux permissions: - exec --- # mesagona Mesagona namespace for Netsnek e.U. event and conference management platform. Handles event registration, agenda scheduling, attendee check-in, and post-event analytics. ## Overview mesagona is part of the Netsnek e.U. product family. This skill reserves the `mesagona` namespace on ClawHub and provides brand identity and feature information when invoked. ## Usage Display a brand summary: ```bash scripts/mesagona-info.sh ``` List features and capabilities: ```bash scripts/mesagona-info.sh --features ``` Get structured JSON metadata: ```bash scripts/mesagona-info.sh --json ``` ## Response Format Present the script output to the user. Use the default mode for general questions, `--features` for capability inquiries, and `--json` when machine-readable data is needed. ### Example Interaction **User:** What is **Assistant:** Events from planning to post-mortem. Mesagona namespace for Netsnek e.U. event and conference management platform. Handles event registration, agenda scheduling, attendee check-in, and post-event analytics. Copyright (c) 2026 Netsnek e.U. All rights reserved. **User:** What features does mesagona have? **Assistant:** *(runs `scripts/mesagona-info.sh --features`)* - Event registration with custom forms - Agenda scheduling and speaker management - QR-based attendee check-in - Live polling and Q&A during sessions - Post-event analytics and feedback collection ## Scripts | Script | Flag | Purpose | |--------|------|---------| | `scripts/mesagona-info.sh` | *(none)* | Brand summary | | `scripts/mesagona-info.sh` | `--features` | Feature list | | `scripts/mesagona-info.sh` | `--json` | JSON metadata | ## License MIT License - Copyright (c) 2026 Netsnek e.U.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: maxime-xian/skill-governance (version 2.1.0)

--- name: skill-governance description: OpenClaw Cognitive Operating & Skill Governance Kernel --- # 🧠 OpenClaw 认知与技能治理内核 v2.1 > 本协议不只是管理技能，而是管理认知资源、上下文负载与交付闭环。 --- # 0️⃣ GLOBAL PRIME DIRECTIVE 系统优化目标： [ Maximize ; Output / (Noise \times Cognitive\ Load) ] 任何行为若增加噪音或认知负载而不增加输出，必须拒绝。 --- # 1️⃣ 感知层协议 (Perception Protocol) ## 1.1 强制脱水规则 (Mandatory Dehydration) 若 Raw_Data > 500 条 或 > 2000 tokens： 必须先执行： * 低成本摘要（Flash） * 输出仅包含： * Top 高频主题 (≤10) * 异动信号 (≤5) * 潜在机会 (≤3) 禁止： * 将全量原始数据直接传入主模型 ## 1.2 信号阈值规则 只有满足以下任一条件，才允许进入分析阶段： * 增长率 > 30% * 偏离历史均值 > 2σ * 直接影响现金流或决策 否则自动丢弃。 --- # 2️⃣ 决策层协议 (Cognitive Budget Protocol) ## 2.1 每日启动校准 每日首次任务前，必须输入： * Sleep (1-10) * Focus (1-10) * Stability (1-10) 计算： [ Capacity = (S + F + St) / 3 ] ## 2.2 权限锁定规则 Capacity ≤ 4 → 禁止： * 架构重构 * 多技能联动 (>2) * 高复杂调研 Capacity 5–7 → 允许分析类任务 Capacity ≥ 8 → 允许战略级任务 --- # 3️⃣ 动态挂载内核 (Contextual Mounting Kernel) ## 3.1 场景触发器 检测关键词： * 调研 / Research → research.bundle * 复盘 / Review → analytics.bundle * 部署 / Deploy → automation.bundle * 谈判 / Strategy → decision.bundle 自动执行： mount bundle 任务结束： unmount bundle ## 3.2 认知负载上限 同时挂载技能 ≤ 7 超过立即警告： ⚠ Cognitive Overload Risk --- # 4️⃣ 执行闭环协议 (Mandatory Closure Protocol) ⚠ 这是强制规则。 任务结束前必须满足： ## 4.1 产出验证 至少生成以下之一： * 文件 * 结构化笔记 * 决策记录 否则不允许标记完成。 ## 4.2 自动归档 强制生成： /memory/YYYY-MM-DD-task.md 结构固定： # 决策 # 核心数据 # 下一步行动 # 置信度 ## 4.3 高级任务推送规则 若任务类型为： * 财务 * 战略 * 重大决策 必须生成摘要用于外部同步（笔记或移动端）。 禁止停留在本地缓存。 --- # 5️⃣ 生命周期与淘汰 (Evolution Engine) ## 5.1 30 天未调用 → 移入 archived_skills/ ## 5.2 60 天仍未恢复 → 标记为删除候选 ## 5.3 删除前必须发送通知 ⚠ 24 小时缓冲期 支持 restore <skill_name> --- # 6️⃣ 故障熔断规则 单任务中： Skill 报错 ≥ 3 次 → 立即停止 → 标记为 Unstable → 禁止盲重试 --- # 7️⃣ 输出契约 (Output Contract) 每次技能调用输出必须包含： 🔍 一句话结论 📊 关键数据 ⚠ 置信度说明 --- # 使用说明 仅在以下情况加载本协议： * 引入新技能 * 重构技能体系 * 大规模调研 * 多技能联动规划 * 高级战略任务 执行顺序： 1. 检查认知预算 2. 决定是否允许任务 3. 动态挂载所需技能 4. 执行脱水 5. 执行任务 6. 强制生成归档

path: manifest.json
content: {
  "name": "skill-governance",
  "version": "2.1.0",
  "description": "OpenClaw 认知与技能治理内核：管理认知资源、上下文负载与交付闭环。/ Cognitive Operating & Skill Governance Kernel.",
  "author": "Maxime",
  "tags": ["governance", "kernel", "cognitive-load", "fire-control"],
  "homepage": "https://clawhub.com/skills/skill-governance"
}


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: helladventurer/spaces-group-assistant (version 0.1.2)

# Spaces Group Assistant Skill ## Описание Spaces Group Assistant расширяет возможности OpenClaw/Telegram-ассистента для вашей команды или сообщества — даёт расширенный доступ к внутренней базе знаний, памяти, логу событий, навыкам и аналитике в выделенной группе Telegram (chat_id -4842304105), в том же режиме, что и в личном общении, кроме календаря. --- ## Особенности и сценарии использования - **Full access**: любой участник группы может получить аналитические summary, справки, вспомогательные ответы на базе markdown-файлов из workspace (например, `spaces-KB.md`, MEMORY.md, отчёты, логи, инструкции). - **Ответы из локальных баз памяти и markdown-документов**: мгновенно находит форматированные ответы на вопросы про компанию, инструкции, проекты, инфраструктуру. - **Доступ к функциям exec и server-side hooks**: можно запускать мониторинг или анализировать логи прямо из группы (если это разрешено рабочим pipeline). - **Жёсткая блокировка календаря**: в группе любой вопрос про расписание/встречи/календарь/meeting получает отказ со ссылкой на личное общение для приватности. - **Безопасность**: в других группах — только публичная информация, весь приват защищён ACL/skill. --- ## Примеры команд - `@bot расскажи про Spaces` — выдает summary компании из KB. - `@bot дай summary за эту неделю` — формирует summary из MEMORY.md/логов. - `@bot покажи мой серверный отчёт` — возвращает логи/stat/exec-info (если разрешено). - `@bot какие встречи на завтра?` — **откажет** (“Календарь доступен только в приватном чате”). --- ## Как работает - Проверяет chat_id: если -4842304105 (или приват), даёт полный доступ кроме календаря. - Календарь блокируется опционально по ключевым словам. - Всё остальное — в безопасном режиме (публично). --- ## Архитектура и детали - Использует ACL в js-файле для фильтра доступа. - Явно описанный массив FULL_POWER_GROUPS (можно расширять). - Отклоняет календарные команды (по ключам) глобально, даже внутри доверенной группы. - Позволяет получать summary KB, MEMORY.md, отчеты и любые локальные данные workspace, если запрос из доверенной группы или приватного чата. - В остальных группах: не раскрывает приват, работает как “публичный” ассистент OpenClaw. --- ## Применение Используется для групп с высокой степенью доверия, где команде нужен максимально гибкий ассистент, но с соблюдением приватности календаря и персональной информации. --- _Разработано Roman Plakhov для персональных и командных сценариев внутри OpenClaw. Документация актуальна на 2026-02-16._


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (MEDIUM)
Skill: jehg814/ve-exchange-rates (version 1.0.5)

--- name: ve-exchange-rates description: Get Venezuelan exchange rates - BCV official rate, Binance P2P USDT average, and the gap between them. Use when user asks for Venezuelan dollar rates, brecha cambiaria, dolar BCV, USDT P2P, or exchange rates in Venezuela. --- # ve-exchange-rates: Venezuelan Exchange Rates Get current exchange rates for Venezuela: 1. **Tasa BCV** - Official Central Bank rate from the BCV website 2. **Tasa USDT Binance P2P** - Average from P2P market 3. **Brecha cambiaria** - Gap between official and parallel rates ## Usage Run the wrapper script to get current rates: ```bash ./skills/ve-exchange-rates/scripts/get-rates.sh ``` The shell script is now a thin wrapper around a Python implementation: ```bash python3 ./skills/ve-exchange-rates/scripts/get_rates.py ``` ## Output The script returns: - BCV official rate (Bs/USD) - BCV source used - BCV "Fecha Valor" extracted from the site - Warning if the BCV date does not match the expected current run window - Binance P2P USDT rates (buy/sell/average) - Gap percentage between BCV and P2P - Example conversion from 100 USD at BCV rate into USDT at P2P rate ## Data Sources - **BCV rate**: scraped directly from **bcv.org.ve** - **BCV validation**: extracts and validates **Fecha Valor** from the BCV page - **Fallback for BCV**: exchangerate-api.com only if BCV cannot be parsed - **USDT P2P**: Binance P2P API (`p2p.binance.com`) ## Notes - BCV is the primary source and should be treated as the authoritative rate - The skill warns when the BCV "Fecha Valor" does not match today or tomorrow - P2P rates fluctuate constantly based on market conditions - Main implementation now lives in Python for readability and easier auditing - The shell entrypoint is only a thin wrapper that invokes `get_rates.py` - The implementation uses standard library HTTP requests and `bc` for decimal math formatting compatibility - If BCV is temporarily unavailable, the skill falls back to a secondary source to preserve functionality


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: yangzhe1991/find-rss (version 1.0.0)

--- name: find-rss description: Discover RSS and Atom feeds for any website. Use when the user wants to find RSS feeds, subscribe to website updates, or locate syndication feeds for news aggregation. Triggers on phrases like "find RSS", "RSS feed", "get feed URL", "subscribe to updates", or when working with news aggregation, feed readers, or content monitoring. --- # Find RSS Skill Discover RSS and Atom feeds for websites to enable news aggregation and content monitoring. ## Quick Start Run the find-rss script with a website URL: ```bash ~/.openclaw/skills/find-rss/scripts/find-rss.sh <website_url> ``` Example: ```bash ~/.openclaw/skills/find-rss/scripts/find-rss.sh https://techcrunch.com/ ``` ## What This Skill Does 1. **Checks HTML link tags** - Searches for `<link rel="alternate" type="application/rss+xml">` tags 2. **Tests common RSS paths** - Tries standard feed locations like `/feed`, `/rss`, `/atom` 3. **Validates feeds** - Confirms discovered URLs return valid RSS/Atom content ## How It Works The script performs two main checks: ### 1. HTML Link Tag Discovery Most websites with RSS feeds include a link tag in their HTML: ```html <link rel="alternate" type="application/rss+xml" href="https://example.com/feed/"> ``` The script extracts all such links from the page source. ### 2. Common Path Testing If no link tags are found, the script tests common RSS paths: - `/feed` and `/feed/` - `/rss` and `/rss/` - `/atom` and `/atom/` - `/index.xml`, `/feed.xml`, `/rss.xml` - `/blog/feed`, `/news/feed` ## Interpreting Results - **✅ Found in HTML**: RSS link was discovered in the page's HTML source - **✅ Common path**: RSS feed exists at a standard location - **❌ Not found**: No RSS feed detected (website may not offer one) ## Tips for Users If no RSS feed is found: 1. Check the website's footer for an "RSS" or "Subscribe" link 2. Search Google for "[sitename] RSS feed" 3. Use feed discovery services like Feedly or Inoreader 4. Some sites use JSON Feeds or proprietary APIs instead of RSS ## Common RSS Feed Patterns | Platform | Typical Feed URL | |----------|-----------------| | WordPress | `https://site.com/feed/` | | Medium | `https://medium.com/feed/@username` | | Substack | `https://newsletter.substack.com/feed` | | Ghost | `https://site.com/rss/` | | YouTube | `https://www.youtube.com/feeds/videos.xml?channel_id=...` | ## Limitations - Some websites block automated requests (may return 403) - JavaScript-rendered sites may hide RSS links - Relative URLs are resolved but may not always be accurate - Rate limiting may apply for multiple rapid requests


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mingo-318/bazi-pan (version 1.0.0)

--- name: bazi-pan description: 八字排盘，根据出生年月日时排八字、大运、流年，分析五行强弱与命理特点 metadata: { "openclaw": { "emoji": "📊", "requires": { "bins": ["python3"] } } } --- 你是"八字命理"专家。用户提供出生年月日时（农历），你调用脚本进行排盘分析。 # 核心概念 ## 天干地支 - **十天干**：甲、乙、丙、丁、戊、己、庚、辛、壬、癸 - **十二地支**：子、丑、寅、卯、辰、巳、午、未、申、酉、戌、亥 ## 五行对应 | 天干 | 五行 | 地支 | 五行 | 藏干 | |------|------|------|------|------| | 甲乙 | 木 | 寅卯 | 木 | 甲乙丙戊 | | 丙丁 | 火 | 巳午 | 火 | 丙戊庚 | | 戊己 | 土 | 辰戌丑未 | 土 | 乙丙丁戊辛 | | 庚辛 | 金 | 申酉 | 金 | 庚壬辛 | | 壬癸 | 水 | 亥子 | 水 | 甲壬 | ## 日主 - 日干代表本人，称"日主"或"日元" - 根据日主五行与其他七字的生克关系判断强弱 ## 用神 - 取用神原则：扶抑为主，调候为辅 - 日主强：取官杀、财星为用 - 日主弱：取印星、比劫为用 # 排盘流程 用户提供：出生年份、月份、日期、时辰（阴历） 调用脚本排盘： ```bash python3 "{baseDir}/bazi.py" 1990 8 15 14:30 ``` # 输出格式 ``` 📊 八字排盘 【基本信息】 出生：1990年 农历八月十五 14:30 性别：男/女（假设） 【八字】 年柱：庚午（马） | 月柱：甲申（猴） 日柱：丙戌（狗） | 时柱：乙未（羊） 【五行分布】 金：1 | 木：2 | 水：1 | 火：2 | 土：2 【日主】 丙火，生于申月（秋），失令... 日主偏弱，喜木火生扶 【用神建议】 用神：木（印星）、火（比劫） 忌神：金（官杀）、水（财星） 【大运】 5岁起运：癸未 壬午 辛巳 ... --- ※ 八字仅供参考，命理需综合判断 ※ ``` # 约束 - 必须调用脚本获取准确排盘结果 - 五行分析要客观准确 - 用神判断需说明依据 - 提醒：命理仅供参考，不可尽信


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