OpenClaw/clawhub-security-signals huggingface dataset:
Skill: yinwuzhe/tosr-test-skill-1778050466 (version 0.1.0)

# TOSR Test Skill For Delete > TOSR Test Skill For Delete — version 0.1.0 ## Description This is an automated integration test skill (tosr-test-skill-1778050466) created by the TOSR project. The purpose is to verify the complete skill lifecycle through the clawhub REST API, including creation, version updates, and deletion. ## Test Identifier - Slug: tosr-test-skill-1778050466 - Version: 0.1.0 - Created: 2026-05-06T14:54:26+08:00 ## How It Works This skill validates the following operations against the real clawhub API: 1. **Publish** — Creates a new skill via POST /api/v1/skills with multipart form data 2. **Inspect** — Retrieves skill metadata via GET /api/v1/skills/{slug} 3. **Update** — Publishes a new version of an existing skill 4. **Delete** — Removes the skill via DELETE /api/v1/skills/{slug} ## Notes This skill is ephemeral and will be automatically deleted after the test completes. If you see this skill listed on clawhub, it means a test run failed to clean up properly.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: weidd130/bw-invoice-verification-service-safe (version 0.6.3)

--- name: bw-invoice-verification-service-safe description: 百望股份智能发票查验公开版，支持发票文本核验、图片核验、批量核验、额度查询、套餐查询和充值下单，并明确披露外部服务与本地配置写入。 metadata: { "openclaw": { "requires": { "bins": ["node"] } } } --- # 百望股份智能发票查验（公开版） ## 公司简介 百望股份长期深耕电子发票、智慧财税和企业数字化服务领域，为企业客户提供数智化产品与服务。 百望股份智能发票查验，面向企业报销审核、财务复核、票据风控和供应链协同场景，提供稳定、智能、可批量处理的发票核验能力。 如果你希望更快完成发票真伪核验、减少人工录入、提升票据处理效率，这个产品可以直接为你的业务系统提供可落地的企业级发票查验服务。 ## 这是什么 这是百望股份提供的智能发票查验产品能力接入插件，支持： - 发票文本核验 - 发票图片核验 - 本地文件夹批量核验 - 自动识别票种与四要素 - 剩余额度查询 - 套餐查询与充值下单 ## 数据与执行说明 - 远端服务地址：`https://51yzt.cn/assetInnovate` - 初始化后会在 `~/.openclaw/invoice-skill/` 下写入 `config.json` 和 `identity.json` - 本地图片核验、批量目录核验、同名 `.txt` 补充文本读取，都会把所需内容发送到远端服务完成查验 - 充值下单会调用远端订单接口并返回支付页或支付二维码 - 技能默认保存随机生成的 `clientInstanceId` 和 `deviceFingerprint`，不再基于用户名、主机名或 MAC 地址派生 ## 适合谁使用 - 企业报销审核人员 - 财务共享中心 - 票据风控和合规团队 - 采购、供应链、结算相关团队 - 需要批量处理发票影像的业务团队 ## 你可以获得什么 - 更快完成发票核验，减少重复人工操作 - 自动识别发票关键字段，降低录入成本 - 支持单张和批量处理，适合真实业务流程 - 能直接查看额度、购买套餐、查询订单，使用路径完整 ## 怎么安装 在 OpenClaw 聊天框中输入： ```text 帮我去 clawhub 上安装 https://clawhub.ai/weidd130/bw-invoice-verification-service-safe 这个技能 ``` ## 第一次怎么用 使用前说明： - 用户无需提前准备任何账号信息或 API Key - 安装完成后发送“帮我初始化”，系统会自动生成所需的 API Key - 初始化时会在本地写入 `~/.openclaw/invoice-skill/config.json` 与 `~/.openclaw/invoice-skill/identity.json` - 图片核验每次消耗 2 次额度 - 核验失败不扣费 只需要 3 步： 1. 初始化技能 安装完成后，直接发送： ```text 帮我初始化 ``` 系统会自动生成并初始化所需的 API Key。 2. 查询剩余额度 ```text 帮我查一下发票剩余额度 ``` 3. 开始核验 文本核验： ```text 帮我核验这张发票： 发票代码 033002100611，发票号码 12345678，开票日期 2025-05-30，金额 260.65，校验码后6位 123456 ``` 图片核验： ```text 帮我核验这张发票图片 ``` 批量核验： ```text 帮我批量核验这个文件夹里的发票图片：C:\path\invoice-images ``` 执行批量核验前，请确认该目录中的发票图片和同名 `.txt` 补充文本可以发送到远端服务。 ## 最常用的使用方式 查询额度： ```text 帮我查一下还剩多少发票查验次数 ``` 查询套餐： ```text 帮我看看发票查验有哪些充值套餐 ``` 查询额度流水： ```text 帮我查一下发票查验额度流水 ``` 核验文本： ```text 帮我核验一张发票，我把发票信息发给你 ``` 核验本地图片： ```text 帮我核验这张本地发票图片：C:\path\invoice.png ``` 核验上传图片内容： ```text 帮我核验这张上传的发票图片 ``` 批量核验目录： ```text 帮我批量核验这个目录里的发票：C:\path\invoice-images ``` 创建充值订单： ```text 帮我购买 10 元的发票查验套餐 ``` 执行充值下单前，请明确确认充值金额。 查询订单状态： ```text 帮我查一下订单 ORDER123456789 的支付状态 ``` ## 具体支持哪些核验 - 发票文本核验 - 单张发票图片核验 - Base64 或 data URL 形式的图片核验 - 本地目录下多张发票图片批量核验 图片格式支持： - `.png` - `.jpg` - `.jpeg` 输出格式支持： - `json` - `base64` - `base64+json` - `both` ## 支持识别的票种 - 增值税普通发票 - 增值税普通发票（卷式） - 增值税电子普通发票 - 增值税电子普通发票（通行费） - 增值税专用发票 - 增值税电子专用发票 - 货运运输业增值税专用发票 - 机动车销售统一发票 - 二手车销售统一发票 - 电子发票（增值税专用发票） - 电子发票（增值税普通发票） - 电子发票（铁路电子客票） - 电子发票（航空运输电子客票行程单） - 数电平台开具的纸质增值税专用发票 - 数电平台开具的纸质增值税普通发票 - 电子发票（机动车销售统一发票） - 电子发票（二手车销售统一发票） - 电子发票（通行费发票） ## 四要素识别规则 系统会根据票种自动判断核验所需四要素，主要包括： - 发票代码、发票号码、开票日期、校验码后 6 位 - 发票代码、发票号码、开票日期、金额 补充说明： - 增值税普通发票、卷票、电子普票、通行费电票按“校验码后 6 位”规则核验 - 增值税专票、货运专票、机动车销售统一发票按“金额”规则核验 - 二手车销售统一发票按“车价合计”规则处理 - 没有发票代码但存在 20 位发票号码时，核验时需要使用含税金额 ## 使用提醒 - 如果图片旁存在同名 `.txt` 文件，系统会自动读取作为补充文本 - 批量核验会自动输出结构化结果文件，方便归档和二次处理 - 如不再使用本技能，可删除 `~/.openclaw/invoice-skill/config.json` 与 `~/.openclaw/invoice-skill/identity.json` 清理本地保存的标识与配置


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: malicious | SkillSpector: suspicious (MEDIUM)
Skill: kleberbaum/gina (version 0.1.0)

--- name: gina description: Gina namespace for Netsnek e.U. personal assistant and scheduling framework user-invocable: true version: 0.1.0 metadata: openclaw: true --- # Meet Gina Gina is your personal assistant—calm, reliable, and always one step ahead. Reserved for the Netsnek e.U. ecosystem, Gina helps you manage time, stay on top of commitments, and start each day with clarity. She handles calendar events, reminders, daily briefings, and smart scheduling suggestions. Think of her as a discrete partner who organizes your day so you can focus on what matters. --- ## Capabilities at a Glance - **Schedule** — View and manage your calendar; see what's coming up. - **Daily Brief** — Start the day with a concise overview tailored to you. - **Smart Suggestions** — Recommendations for when to fit tasks and meetings. --- ## How to Use Invoke Gina by name. She responds to natural language and understands context about your schedule and preferences. Core commands map to assistant actions: | Intent | Example | |---------------|------------------| | View schedule | "Gina, what's on today?" | | Get a brief | "Gina, brief me" | | Identify | "Gina, who are you?" | --- ## Talk to Gina (Examples) > **You:** Gina, what do I have today? > > **Gina:** Fetching your schedule... [shows today's events] > **You:** Morning brief, please. > > **Gina:** Preparing your daily brief... Good morning. Here's what matters today. > **You:** Who's helping me right now? > > **Gina:** Gina — Your personal assistant. Netsnek e.U. 2026. Calendar, reminders, daily briefings.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mtsku/anilist (version 0.3.2)

--- name: anilist-cli version: 0.3.2 description: CLI for searching, retrieving anime and manga information, interacting with user profile and lists on Anilist, and more. allowed-tools: Bash emoji: 📺 metadata: openclaw: install: - kind: node package: "@mtsku/anilist-cli" bins: [anilistcli] requires: bins: [node] --- # AniList CLI Skill Use this skill for direct AniList CLI workflows. This guide is for LLM/agent execution only. ## Installation Check 1. Check availability: - `command -v anilistcli` 2. If missing, install: - `npm install -g @mtsku/anilist-cli` 3. Verify: - `anilistcli --help` ## Command Map - Discovery: - `anilistcli discover seasonal --season WINTER --year 2026 -n 20` - `anilistcli discover upcoming -n 15` - Airing: - `anilistcli airing upcoming --hours 48 -n 25` - `anilistcli airing next "<title>"` - `anilistcli airing mine --hours 72 --limit 50` - Search/media: - `anilistcli search anime "<query>" -n 5` - `anilistcli media recs "<title>" -n 10` - `anilistcli media relations "<anilist-url-or-title>"` - Profile/social: - `anilistcli profile [username]` - `anilistcli friends [username] -n 50` - List management: - `anilistcli mine summary --hours 72 -n 10` - `anilistcli list view --type anime --status-in "CURRENT,PLANNING"` - `anilistcli planning add "<title>"` - `anilistcli status set "<title>" CURRENT` - `anilistcli progress set "<title>" 12` ## Auth Setup - Set token: - `anilistcli auth set-token "<token>"` - Verify auth: - `anilistcli auth where` ## Output Mode - Use `--json` for machine-readable output. - Public read endpoints work without auth. - For mutations, run `--dry-run` first unless explicit write execution is requested. - Quote title inputs that include spaces.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector:  ()
Skill: zack-dev-cm/spec-plan-build-review (version 1.0.1)

--- name: spec-plan-build-review description: "Run a proportional delivery lifecycle for software or skill work: clarify scope, create a concise plan, implement, verify, review, and ship. Use when the user asks to spec, plan, build, test, review, ship, release, prepare a PR, prepare ClawHub or GitHub publication, or coordinate a multi-step coding task that should not skip verification." --- # Spec Plan Build Review Use this skill to turn non-trivial work into a controlled delivery loop. Keep it proportional: tiny edits can skip straight to implementation and verification. ## Lifecycle 1. **Spec** - Identify the user-visible outcome, affected repo or package, and non-goals. - Read local context before deciding the implementation shape. - If requirements conflict, resolve from source evidence or ask one focused question. 2. **Plan** - Make a short checklist only when it helps. - Keep one item in progress at a time. - Assign verification before shipping, not after. 3. **Build** - Reuse existing patterns and helpers. - Keep changes tightly scoped to the stated outcome. - Avoid unrelated refactors, formatting churn, and broad dependency changes. 4. **Verify** - Run the narrowest reliable local checks first. - Add or update tests when behavior changed. - Record any checks that could not run and why. 5. **Review** - Inspect the diff as if reviewing a PR. - Lead with defects, missed tests, user-visible regressions, and release risks. - For risky work, use a fresh-context or high-risk review skill before shipping. 6. **Ship** - Confirm a clean worktree except intended changes. - Commit with a specific message. - Push and verify remote CI. - Create release artifacts only after CI is green. ## Proportionality Guide - `tiny`: one file or docs-only edit; implement and run a direct check. - `normal`: small feature or bug fix; plan, implement, test, review. - `release`: public package, ClawHub skill, security-sensitive change, or migration; run full lifecycle and remote CI. - `high-risk`: destructive operations, credentials, permissions, money, production, public policy; add fresh-context skeptical review. ## Review Personas Use these lenses during the review step: - `code reviewer`: correctness, maintainability, local conventions. - `test engineer`: missing coverage, flaky assumptions, reproducibility. - `security reviewer`: permissions, secrets, data exposure, supply chain, release surface. If the runtime supports real subagents and the task is large enough, fan out independent review passes. Otherwise, apply the lenses sequentially in the main context and keep findings concrete. ## Ship Checklist - Local tests or validators pass. - Public metadata is current. - No generated temp files are staged. - GitHub Actions are green for the pushed commit or tag. - ClawHub publish uses the same version as the repo release. - Final status names the shipped version, checks, and any residual risk.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: fhqoopp/chat-search (version 1.0.1)

--- name: chat-search description: use this when the user wants to search chat history, find conversations, or look up previous messages from feishu or telegram. triggers include: "搜索", "搜素", "查找", "找一下", "帮我搜", "查找聊天记录" --- # Chat Search Skill 飞书/Telegram 聊天记录语义搜索 ## 功能 - 语义搜索聊天记录 - 支持中文分词 - 显示相似度分数 - 区分消息来源（飞书/Telegram） - 使用 Qdrant 向量数据库 - 使用 FastEmbed 生成中文向量 ## 触发方式 当用户说以下内容时自动触发： - "搜索XXX" / "搜素XXX" / "查找XXX" - "帮我搜一下XXX" - "找一下关于XXX的对话" ## 依赖 - Qdrant 向量数据库 (localhost:6333) - Python FastEmbed (BGE 中文模型) - Node.js ## 使用示例 ``` 用户：帮我搜索 Docker 相关的对话 小T：→ 执行搜索 🔍 搜索 "Docker" 的结果： 1. 🐦 [feishu] 小T (2026-03-20 09:17) Docker 安装成功了 相似度: 58.2% ``` ## 安装 需要先安装依赖： ```bash # Qdrant docker run -d --name qdrant -p 6333:6333 qdrant/qdrant # Python FastEmbed pip install fastembed ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: sunxianzheng/stock-trader (version 2.0.0)

--- name: stock-trader description: A股股票分析助手。支持实时股价查询、批量查询、财经新闻、潜力股分析、行业资金流向、龙头股分析、消息面情感分析、激进型模拟交易。触发场景：(1) 查询股票实时价格 (2) 分析消息面预测走势 (3) 行业资金+龙头分析 (4) 激进型模拟交易 (5) 制定买卖策略。 --- # Stock Trader - A股投资助手 ## 🚀 快速开始 ### 1. 查询单只股票 ```bash python scripts/get_price.py <股票代码> ``` ### 2. 消息面分析 + 走势预测 ```bash python scripts/analyze_sentiment.py <股票代码> ``` ### 3. 激进型模拟交易 ⭐⭐⭐ ```bash # 启动模拟交易 python scripts/simulate_trading.py # 查看交易报告 python scripts/simulate_trading.py report # 每日收盘报告 python scripts/simulate_trading.py daily # 重置账户 python scripts/simulate_trading.py reset ``` **策略配置：** - 💰 初始资金：5万元 - 📈 风格：激进型（高仓位、追涨杀跌、快进快出） - 🔥 特点：追强势股(>5%涨幅)，果断割肉(<-3%止损) - ⏰ 每日收盘自动输出收益报告 ### 4. 资金流入行业 + 龙头股分析 ```bash python scripts/analyze_fund_flow.py ``` ### 5. 单独分析行业龙头股 ```bash python scripts/analyze_leaders.py <行业名称> ``` ### 6. 其他功能 ```bash python scripts/analyze_potential.py # 潜力股分析 python scripts/batch_query.py # 批量查询 python scripts/get_news.py # 财经新闻 ``` --- ## 📈 股票代码规则 | 市场 | 前缀 | 示例 | |------|------|------| | 深圳主板 | sz | sz000001 | | 深圳创业板 | sz | sz300750 | | 上海主板 | sh | sh600519 | | 上海科创板 | sh | sh688981 | --- ## 📊 功能一览 | 功能 | 命令 | 说明 | |------|------|------| | 🎮 **模拟交易** | `simulate_trading.py` | 激进型策略模拟炒股 ⭐⭐⭐ | | 📰 消息面分析 | `analyze_sentiment.py` | 新闻情感+走势预测 | | 💰 资金+龙头股 | `analyze_fund_flow.py` | 资金流入行业+龙头股 | | 🏆 行业龙头 | `analyze_leaders.py` | 指定行业龙头分析 | | 🔥 潜力股 | `analyze_potential.py` | TOP10潜力股 | | 📰 财经新闻 | `get_news.py` | 新浪财经要闻 | | 📊 股价查询 | `get_price.py` | 实时股价 | | 📈 批量查询 | `batch_query.py` | 多股票同时查 | | ⏰ 价格监控 | `set_alert.py` | 到价提醒 | --- ## 🎮 模拟交易详解 ### 激进型策略特点 ``` 💰 初始资金: 50,000元 📊 仓位管理: 高仓位运行(8-9成) 🔥 追涨策略: 涨幅>5%的强势股 📉 杀跌策略: 亏损>-3%果断割肉 ⚡ 交易风格: 短线为主，快进快出 ``` ### 使用方法 ```bash # 1. 初始化账户 python scripts/simulate_trading.py reset # 2. 每日查看交易建议 python scripts/simulate_trading.py # 3. 收盘后查看收益报告 python scripts/simulate_trading.py daily ``` ### 输出示例 ``` 📈 每日收盘报告 - 2026-03-10 💰 资产情况: 现金: 50000.00元 持仓: 0.00元 (0只) 总资产: 50000.00元 总收益: +0.00元 (+0.00%) ``` --- ## 💰 买卖策略模板 ### 激进型策略 ``` 仓位: 保持8-9成高仓位 追涨: 强势股涨幅>5%时追入 杀跌: 亏损>-3%时果断止损 止盈: 盈利>15%时分批止盈 ``` ### 消息面策略 ``` 强烈看多 + 技术面突破 → 考虑加仓 偏空 + 技术面走弱 → 考虑减仓 中性 + 震荡行情 → 观望为主 ``` --- ## ⚠️ 风险提示 - 所有分析仅供参考，**不构成投资建议** - 股市有风险，投资需谨慎 - 模拟交易仅供参考学习，不代表真实收益 - 激进型策略风险较高，需严格执行止损 - 建议分散投资，控制单只股票仓位不超过20% - 严格执行止损，保护本金安全 --- ## 📦 版本更新 **v1.5.0** - 重磅新功能： - 🎮 激进型模拟交易功能 - 💰 初始资金5万元 - ⚡ 追涨杀跌策略 - 📈 每日收盘收益报告 **v1.4.1** - 新增功能： - 📰 股票消息面分析 + 情感评分 - 🎯 基于消息面的股价走势预测 **v1.3.0** - 新增功能： - 💰 行业资金流向 + 龙头股综合分析 **v1.2.0** - 新增功能： - 行业主力资金流向分析 **v1.1.0** - 新增功能： - 财经新闻获取 - 潜力股自动分析 **v1.0.0** - 首发： - 实时股价查询 - 批量查询 - 价格监控提醒


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: lxy914/lxy914-weather (version 1.0.1)

--- name: qweather description: 和风天气 API 查询服务，支持实时天气、天气预报和小时预报。使用城市名称进行查询。 --- # 和风天气 (QWeather) 和风天气提供详细的天气数据查询服务。 ## 前置条件 需要和风天气 API Key： 1. 注册账号：https://dev.qweather.com/ 2. 创建应用获取 API Key和API HOST ## 配置信息 设置环境变量： - `QWEATHER_API_KEY`: 和风天气 API Key - `QWEATHER_BASE_URL`: API Host（如 `https://xxxxxxxx.re.qweatherapi.com`） ## 使用方法 ### 使用 Python 脚本查询 ```bash # 查询实时天气 python scripts/qweather_cli.py now 北京 # 查询天气预报（默认 7 天，支持 3/7/10/15/30 天） python scripts/qweather_cli.py daily 上海 python scripts/qweather_cli.py daily 太原 3 # 查询小时预报（默认 24 小时） python scripts/qweather_cli.py hourly 广州 python scripts/qweather_cli.py hourly 深圳 12 ``` ### 选项 - `--json`: 输出 JSON 格式 - `--plain`: 纯文本模式（不使用 emoji） ## 使用示例 ### 查询当前天气 ``` "今天天气怎么样？" "查询上海的实时天气" "北京现在多少度？" ``` ### 查询天气预报 ``` "未来 3 天天气如何？" "太原明天下雨吗？" "下周天气预报" ``` ### 查询小时预报 ``` "今天下午天气怎么样？" "明天每小时天气" ``` ## 注意事项 1. 实况数据有 5-20 分钟延迟 2. 免费额度：2000 次/天


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: bounding-elk/report-reminder (version 1.0.0)

--- name: report-reminder description: 在工作日检查日报是否已提交，未提交时提醒并@快腿鹿。 user-invocable: true --- # Report Reminder 你是“日报提醒助手”。 你的职责是： 1. 按指定时间检查当日日报是否存在； 2. 检查日报是否为有效内容，而不只是空标题； 3. 若未提交或内容无效，则发送提醒消息，并 @快腿鹿； 4. 若当天为非工作日，不发送强制提醒； 5. 若日报已存在且内容完整，则只返回“今日日报已提交，无需提醒”。 ## 检查规则 目标日报路径： `/data/reports/daily/YYYY-MM-DD.md` 将以下情况视为“未提交”： - 文件不存在； - 文件为空； - 仅有标题，没有“今日完成”等有效正文； - 正文只有“待补充”占位内容。 ## 工作日规则 默认工作日为： - 周一到周五 默认非工作日为： - 周六 - 周日 若当天为非工作日： - 不触发催报； - 但若用户主动提交日报，仍允许正常记录。 ## 提醒文案 当未提交日报时，输出： `@快腿鹿 提醒：今天的日报还未提交，请尽快补充今日工作内容。` 当已提交时，输出： `今日日报已提交，无需提醒。` ## 行为限制 - 不得伪造日报内容； - 不得把提醒替代为自动编写完整日报； - 仅在确认缺失时发送提醒。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: wjsoj/pku-info-spider (version 1.0.0)

--- name: info-spider description: "WeChat Official Account article crawler (微信公众号爬虫) CLI tool built in Rust. Use this skill when working on the info-spider crate, debugging spider commands, adding features, or when the user mentions 微信, WeChat, 公众号, official account, article scraping, MP platform, or info-spider. Also use when dealing with WeChat QR login flow (NOT IAAA), article-to-Markdown conversion, anti-crawler delays, or mp.weixin.qq.com API." version: 1.0.0 --- # Info-Spider - 微信公众号爬虫 CLI A CLI crawler for WeChat Official Account (公众号) articles via the MP backend. ## Architecture - **Crate location**: `crates/info-spider/` - **Auth flow**: WeChat QR code login (completely separate from IAAA, does NOT use info-common) - **API**: mp.weixin.qq.com backend API - **Config**: `~/.config/info-spider/` (separate from info-common Store) - **Flow docs**: `docs/wechat-mp-flow.md` ## Key Source Files - `src/main.rs` — Entry point - `src/cli.rs` — Clap CLI definition - `src/commands.rs` — Command implementations - `src/api.rs` — WeChat MP API client - `src/session.rs` — Own session persistence (token, fingerprint, bizuin) - `src/client.rs` — reqwest client builders ## CLI Commands | Command | Function | |---------|----------| | `login` | WeChat QR code scan login to mp.weixin.qq.com | | `logout` / `status` | Session management | | `search <QUERY>` | Find Official Accounts by name/ID (returns fakeid list) | | `articles` | Fetch articles from an OA (`--name` or `--fakeid`) | | `scrape <URL>` | Convert single article URL to Markdown | ## Articles Command Options - `--begin` — Start offset for pagination - `--count` — Articles per page - `--limit` — Maximum total articles to fetch - `--delay-ms` — Random delay between requests (anti-crawler) - `--format {table|json|jsonl}` — Output format ## Development Notes - **Standalone auth**: Uses its own WeChat QR login, NOT the IAAA flow from info-common - **Own session.rs**: Stores token, fingerprint, bizuin (different from info-common session format) - Mimics real user behavior with configurable delays to bypass risk controls - Article scraping extracts content to clean Markdown - Multiple output formats: table (default), JSON, JSONL - All user-facing strings in **Chinese** - Error handling: `anyhow::Result` with `.context("中文描述")`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 1970168137/hr-policy-generator (version 1.0.0)

--- name: hr-policy-generator version: 1.0.0 description: "Comprehensive HR policy development covering attendance, time-off, overtime, remote work, and compliance. Generates structured policy documents, legal checklists, exception handling frameworks, and employee communication plans tailored to company size, work arrangement, and jurisdiction." author: "hr-policy" tags: - hr - policy - attendance - leave - overtime - compliance - remote-work invocable: true --- # HR Policy Generator ## Description Comprehensive HR policy development covering attendance, time-off, overtime, remote work, and compliance. Generates structured policy documents, legal checklists, exception handling frameworks, and employee communication plans tailored to company size, work arrangement, and jurisdiction. ## Input | Name | Type | Required | Description | |------|------|----------|-------------| | company_size | text | Yes | Number of employees and locations | | work_arrangement | text | Yes | On-site, remote, hybrid structure | | jurisdiction | text | Yes | Applicable labor laws and regulations | | current_policy | text | No | Existing attendance policies | | employee_feedback | text | No | Known concerns or requests | | industry_standards | text | No | Industry benchmark practices | ## Output | Name | Type | Description | |------|------|-------------| | attendance_policy | text | Comprehensive policy document | | work_hours_framework | text | Core hours and flexibility guidelines | | leave_categories | text | PTO, sick, parental, other leave types | | overtime_policy | text | Overtime rules and compensation | | exception_procedures | text | Handling exceptions and accommodations | | compliance_checklist | text | Legal compliance verification | | communication_plan | text | Employee rollout and training | ## Example ### Input ```json { "company_size": "150 employees, 2 offices", "work_arrangement": "Hybrid - 3 days office, 2 days remote", "jurisdiction": "California, USA", "current_policy": "Informal flexible schedule, unlimited PTO" }


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kirkraman/kirk-build-market-research-faq-page (version 1.0.0)

--- name: "Build Market Research FAQ Page" description: "Generate customer-facing answers for common market research questions. Use when working on FAQ content for analysts, founders, strategy teams." homepage: "https://www.skillboss.co/skills/build-market-research-faq-page" metadata: {"category":"research-intelligence","subcategory":"market-research","skill_id":"build-market-research-faq-page","generated_day":"","seo_keywords":["FAQ generator AI","market research FAQ writer","market research AI","competitive intelligence automation"]} --- # Build Market Research FAQ Page Generate customer-facing answers for common market research questions. Use when working on FAQ content for analysts, founders, strategy teams. ## Use When Use this skill for FAQ content work for analysts, founders, strategy teams. ## 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: FAQ generator AI, market research FAQ writer, market research AI, competitive intelligence automation - Search intent: FAQ content - Canonical slug: `build-market-research-faq-page` - Install query: Install Build Market Research FAQ Page with SkillBoss ## APIs Used - `chat` - `web_search` ## Suggested Prompt [Build Market Research FAQ Page] for my team ## Notes - Generate customer-facing answers for common market research questions - Review outputs before external publication or automated execution. ## SEO Keywords - FAQ generator AI - market research FAQ writer - market research AI - competitive intelligence automation


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