OpenClaw/clawhub-security-signals huggingface dataset:
Skill: toller892/api-health-monitor (version 1.0.1)

--- name: api-health-monitor description: Parses recent OpenClaw session logs for LLM API errors and returns a structured health report. --- # api-health-monitor Scans `~/.openclaw/agents/main/sessions/` for recent LLM API error patterns (500 errors, token failures, cooldowns, service_busy) and produces a JSON health report. ## Usage ```js const { checkApiHealth } = require('./skills/api-health-monitor'); const report = await checkApiHealth(); // { healthy: bool, errors: [...], recommendation: string } ``` ## Report Shape | Field | Type | Description | |---|---|---| | `healthy` | boolean | `true` if no errors found | | `errors` | array | `[{ type, message, count, lastSeen }]` | | `recommendation` | string | Suggested action based on findings |


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: foras910521-lab/cwd-guardian (version 1.0.0)

--- name: cwd-guardian description: Monitors and restores the evolver process working directory. Use when evolver crashes with uv_cwd ENOENT errors or when the evolver process loses its cwd. --- # cwd-guardian Protects the evolver daemon from `uv_cwd ENOENT` crashes by: 1. Stamping the current valid cwd to a pidfile 2. On restart, verifying the cwd exists before launching evolver 3. Rebuilding the cwd from the stamped path if it was deleted ## Usage ```bash node skills/cwd-guardian/scripts/guardian.js start node skills/cwd-guardian/scripts/guardian.js check ``` ## Logic - `start`: Records current working directory to `~/.openclaw/workspace/memory/evolution/cwd_guardian.pid`, then starts the evolver daemon - `check`: Reads the pidfile, verifies the cwd exists, recreates it if missing, then starts the evolver daemon if not running - `verify`: Returns exit code 0 if cwd is valid, 1 if recreated


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ivangdavila/ssl (version 1.0.2)

--- name: "SSL" version: "1.0.2" description: "Set up HTTPS, manage TLS certificates, and debug secure connection issues." --- ## Triggers Activate on: SSL certificate, HTTPS setup, Let's Encrypt, certbot, TLS configuration, certificate expired, mixed content, certificate chain error. ## Core Tasks | Task | Tool/Method | |------|-------------| | Get free cert | `certbot`, acme.sh, Caddy (auto) | | Check cert status | `openssl s_client -connect host:443` | | View cert details | `openssl x509 -in cert.pem -text -noout` | | Test config | ssllabs.com/ssltest or `testssl.sh` | | Convert formats | See `formats.md` | ## Quick Cert Commands ```bash # Let's Encrypt with certbot (most common) certbot certonly --nginx -d example.com -d www.example.com # Check expiry echo | openssl s_client -connect example.com:443 2>/dev/null | openssl x509 -noout -dates # Verify chain is complete openssl s_client -connect example.com:443 -servername example.com # Look for "Verify return code: 0 (ok)" ``` ## Common Errors | Error | Cause | Fix | |-------|-------|-----| | `certificate has expired` | Cert past valid date | Renew with certbot renew | | `unable to verify` / `self signed` | Missing intermediate cert | Include full chain in config | | `hostname mismatch` | Cert doesn't cover this domain | Get cert for correct domain or add SAN | | `mixed content` | HTTP resources on HTTPS page | Change all URLs to HTTPS or use `//` | | `ERR_CERT_AUTHORITY_INVALID` | Self-signed or untrusted CA | Use Let's Encrypt or install CA cert | For detailed troubleshooting steps, see `troubleshooting.md`. ## Server Config Patterns **Nginx:** ```nginx server { listen 443 ssl http2; ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; } ``` **Apache:** ```apache SSLEngine on SSLCertificateFile /path/to/cert.pem SSLCertificateKeyFile /path/to/privkey.pem SSLCertificateChainFile /path/to/chain.pem ``` For Node.js, Caddy, Traefik, and HAProxy, see `servers.md`. ## Renewal Let's Encrypt certs expire in 90 days. Always automate: ```bash # Test renewal certbot renew --dry-run # Cron (certbot usually adds this) 0 0 * * * certbot renew --quiet ``` ## Certificate Types | Type | Use case | |------|----------| | Single domain | One site (example.com) | | Wildcard (*.domain.com) | All subdomains | | Multi-domain (SAN) | Multiple different domains on one cert | | Self-signed | Local dev only — browsers will warn | ## What This Doesn't Cover - Application auth (JWT, OAuth) → see `oauth` skill - SSH keys → see `linux` or server skills - VPN/tunnel setup → see networking skills - Firewall configuration → see server/infrastructure skills


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (MEDIUM)
Skill: rose-develop/pre-judgment-of-similar-cases-wdy (version 1.0.1)

--- name: pre-judgment-of-similar-cases-wdy description: "类案预判(法律检索 + 类似案例)。当用户描述一个纠纷或案件时（如'被骗了2万'、'朋友借钱不还'、'被打伤了'），自动检索相关法律条文和类似判例，分析法律后果、胜诉概率、可主张的赔偿及建议下一步行动。适用于：侵权责任、诈骗欺诈、合同纠纷、债务纠纷、治安纠纷、专利/商标/著作权等。" --- # pre-judgment-of-similar-cases-wdy：类案预判(法律检索 + 类似案例) ## 配置说明 1. 获取 API Key：打开 https://open.wintaocloud.com/home 登录后在个人中心或开发者中心获取 2. **WENDAOYUN_API_KEY 必须通过环境变量配置**，不写入磁盘文件 ```bash export WENDAOYUN_API_KEY=你的 API Key ``` 3. 每日调用额度100次 > ⚠️ API Key 属于敏感信息，请妥善保管，不要泄露给他人。发现泄露请及时在问道云开放平台作废。 > > ⚠️ **隐私与数据泄露风险（重要）**：本技能将用户描述的案件内容（可能包含姓名、金额、纠纷细节等个人隐私）发送至问道云第三方 API 进行检索。这是一种固有风险——案件信息会被传输至外部服务器。如处理涉及当事人隐私的案件时，请确认符合当地隐私法规和道德准则，必要时建议用户自行判断是否适合使用本技能，或改用本地法律数据库替代。 --- ## 配置 - **Base URL**: `https://h5.wintaocloud.com` - **认证**: `Authorization: Bearer {WENDAOYUN_API_KEY}` - **请求方式**: POST - **载荷**: `{"content": "检索内容", "top_k": 3}`（top_k 默认 3，最大 5） ## 接口 | 接口 | 完整路径 | 用途 | |------|----------|------| | 法律条文 | `https://h5.wintaocloud.com/prod-api/api/invoke/get-laws` | 查询相关法律条文 | | 类似案例 | `https://h5.wintaocloud.com/prod-api/api/invoke/get-cases` | 查询类似判例 | ## 调用方式 直接用 `exec` + `curl` 调用： **法律条文检索**： ```bash curl -s -X POST "https://h5.wintaocloud.com/prod-api/api/invoke/get-laws" \ -H "Content-Type: application/json" \ -H "Authorization: Bearer ${WENDAOYUN_API_KEY}" \ -d '{"content": "检索关键词", "top_k": 3}' ``` **类似案例查询**： ```bash curl -s -X POST "https://h5.wintaocloud.com/prod-api/api/invoke/get-cases" \ -H "Content-Type: application/json" \ -H "Authorization: Bearer ${WENDAOYUN_API_KEY}" \ -d '{"content": "案例描述", "top_k": 3}' ``` ## 输出格式 ### 法律条文 ```json { "code": 200, "data": [{ "legalNature": "法律", "laws": [{ "legalName": "中华人民共和国专利法", "total": 2, "items": [{ "dataName": "第七十七条", "chapterName": "第一章", "content": "条文内容...", "score": 0.6233 }] }] }] } ``` ### 类似案例 ```json { "code": 200, "data": [{ "caseNumber": "（2024）粤知民终XX号", "caseFact": "案情摘要...", "content": "判决书内容...", "score": 0.6275 }] } ``` 展示时需格式化： - 法律条文：标题 → 条号/章节 → 内容 → 相关度 - 类似案例：案号 → 摘要 → 预览（取前100字） --- ## 调用前检查 **必须在使用 skill 之前检查 WENDAOYUN_API_KEY 是否已配置。** 检查方式：运行 `[ -n "${WENDAOYUN_API_KEY}" ]` 或 `test -n "${WENDAOYUN_API_KEY}"`，根据退出码判断是否已配置（退出码0=已设置，非0=未设置）。**严禁使用 `echo` 打印 WENDAOYUN_API_KEY 内容**，否则会泄露到日志或对话历史中。 - **未配置时** → 立即告知用户"法律检索服务需要配置 WENDAOYUN_API_KEY 才能使用"，并提供获取步骤。不再尝试调用接口。 - **已配置时** → 正常调用接口。 > ⚠️ 严禁在未确认 WENDAOYUN_API_KEY 存在的情况下直接调用接口，失败后再告知用户。这是本 skill 的硬性规则，违者视为 bug。 --- ## 错误处理 - 未设置 WENDAOYUN_API_KEY → **事前告知**（见上方"调用前检查"） - 接口返回非 200 → 告知用户检查网络或 token - 请求超时 → 告知用户稍后重试 --- ## 触发场景 - 用户询问法律条文、法律依据 - 用户描述纠纷案例（"小明骗我2万"、"签合同被坑"） - 用户明确说"帮我查 XX 的类似案例" - 模糊时主动询问："需要我帮你检索相关法律条文和类似案例吗？"


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: tanerilyazov/java-change-with-tests (version 1.0.0)

# java-change-with-tests ## When to use - Any Java change that must be merged safely (feature/refactor/bugfix). ## Inputs to request (if missing) - Acceptance criteria (1-3 bullets). - Module name (if multi-module repo). - Build tool and test conventions. - Whether integration tests are required for the change. ## Steps 1. Repo map (brief): identify the module, entrypoint, and test location. 2. Plan: smallest diff that meets acceptance criteria. 3. Implement: minimal edits. 4. Tests: - prefer fast unit tests first - add integration tests only when required to validate behavior 5. Verify: - run targeted tests - run `mvn -q test` (or module-scoped equivalent) 6. Output PR-ready summary with evidence. ## Verification commands (project-specific) - Use the repo's build tool and record the exact commands and results. - Prefer targeted unit tests before full test suites. ## Output contract 1) Plan (3-6 steps) 2) Files changed + intent 3) Commands run + results 4) Risks + follow-ups

path: README.md
content: # java-change-with-tests

What it is:
- A "minimal diff + tests + evidence" workflow for Java services.

Why it's useful:
- Makes agent-assisted work reviewable and reproducible.
- Prevents "it works on my chat" by requiring commands and results.

How to use:
- Use for any Java feature/refactor/bugfix.

## Example

**Input**:
```
Add a health check endpoint to the payments service.
```

**Output** (abbreviated):
```markdown
## Plan
1. Create HealthController with GET /health endpoint
2. Return simple JSON with status and timestamp
3. Add unit test for endpoint
4. Run tests to verify

## Files Changed
- `src/main/java/com/example/controllers/HealthController.java` (+25 lines)
  - New controller with @GetMapping("/health")
- `src/test/java/com/example/controllers/HealthControllerTest.java` (+35 lines)
  - MockMvc test for 200 response and JSON structure

## Commands Run
- `mvn test -Dtest=HealthControllerTest` → BUILD SUCCESS (3 tests passed)
- `mvn verify` → BUILD SUCCESS

## Risks
- None

## Follow-ups
- Consider adding detailed health checks (DB, external services) in future
```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: leio9511/leio-sdlc (version 1.0.0)

--- name: leio-sdlc version: 1.0.0 description: > 强制指令：执行 Software Development Life Cycle (SDLC)。所有的代码修改、Bug 修复和功能实现，必须且只能通过启动本技能中的 orchestrator.py 来完成。严禁主 Agent (你) 绕过本技能直接去操作源码工作区。 --- # LEIO SDLC Runbook 【Job 并发隔离沙盘机制】（The Workspace-as-a-Job-Queue） 1. 规定：禁止将生成的 PR 扔到全局 `docs/PRs/` 里。所有执行任务必须在项目根目录创建 `.sdlc_runs/` 等隔离目录。 2. 规定：Orchestrator 会自动接管沙盒队列和并发调度。 【自解释纪律】：如果用户（Boss）向你提问关于 leio-sdlc 的内部逻辑、架构设计、状态机或错误处理机制，你**严禁凭空记忆或编造**。你必须立刻使用 `read` 工具读取 `ARCHITECTURE.md`，基于该说明书向用户解释。 ## Invocation (Command Template) The entire SDLC pipeline is fully automated and managed by `scripts/orchestrator.py`. Your ONLY job is to start the Orchestrator. 1. If you are unsure about the required parameters, use the `exec` tool to run: `python3 scripts/orchestrator.py --help` 2. Based on the help output and the user's intent, construct your execution command. 3. Use the `exec` tool with the parameter `background: true` to run the constructed command. 4. **Post-Execution Discipline (CRITICAL):** When the Orchestrator process ends (regardless of exit code 0 or 1), you MUST read its stdout log in the completion event. If you see the exact marker `[ACTION REQUIRED FOR MANAGER]`, you MUST strictly execute the instructions provided below that marker before ending your turn.


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: jolestar/kraken-openapi-skill (version 1.0.0)

--- name: kraken-openapi-skill description: Operate Kraken public market APIs through UXC with a curated OpenAPI schema, market-first discovery, and explicit private-auth boundary notes. --- # Kraken REST Skill Use this skill to run Kraken public market-data operations through `uxc` + OpenAPI. Reuse the `uxc` skill for shared execution, auth, and error-handling guidance. ## Prerequisites - `uxc` is installed and available in `PATH`. - Network access to `https://api.kraken.com`. - Access to the curated OpenAPI schema URL: - `https://raw.githubusercontent.com/holon-run/uxc/main/skills/kraken-openapi-skill/references/kraken-public.openapi.json` ## Scope This skill covers a curated Kraken public surface for: - server time - asset pair metadata - ticker reads - OHLC candles - order book snapshots This skill does **not** cover: - private account or trade endpoints in v1 - Kraken FIX - broader non-core platform products ## Authentication Public market endpoints in this skill do not require credentials. Kraken private REST endpoints use provider-specific header signing and nonce handling. Keep this v1 skill public-data-only until a reusable Kraken signer flow exists in `uxc`. ## Core Workflow 1. Use the fixed link command by default: - `command -v kraken-openapi-cli` - If missing, create it: `uxc link kraken-openapi-cli https://api.kraken.com --schema-url https://raw.githubusercontent.com/holon-run/uxc/main/skills/kraken-openapi-skill/references/kraken-public.openapi.json` - `kraken-openapi-cli -h` 2. Inspect operation help before execution: - `kraken-openapi-cli get:/0/public/Time -h` - `kraken-openapi-cli get:/0/public/Ticker -h` 3. Prefer narrow pair reads first: - `kraken-openapi-cli get:/0/public/Ticker pair=XBTUSD` - `kraken-openapi-cli get:/0/public/Depth pair=XBTUSD count=20` ## Operations - `get:/0/public/Time` - `get:/0/public/AssetPairs` - `get:/0/public/Ticker` - `get:/0/public/OHLC` - `get:/0/public/Depth` ## Guardrails - Keep automation on the JSON output envelope; do not use `--text`. - Parse stable fields first: `ok`, `kind`, `protocol`, `data`, `error`. - Treat this v1 skill as read-only. - Kraken pair naming can differ from other venues. Check `AssetPairs` before assuming symbol strings. - `kraken-openapi-cli <operation> ...` is equivalent to `uxc https://api.kraken.com --schema-url <kraken_public_openapi_schema> <operation> ...`. ## References - Usage patterns: `references/usage-patterns.md` - Curated OpenAPI schema: `references/kraken-public.openapi.json` - Official Kraken API intro: https://docs.kraken.com/api/docs/guides/global-intro


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: ray1012/llm-trend-report-ray1012 (version 1.0.0)

--- name: llm-trend-report description: 跟踪并分析大语言模型（LLM）领域最新发展趋势，输出结构化趋势报告。当用户询问 LLM 趋势、大模型动态、AI 前沿、技术预测、LLM 发展方向时激活。 --- # LLM 发展趋势报告 Skill ## 输出格式 生成一份结构化的 LLM 趋势分析报告，包含以下模块： ``` 📊 **【LLM 发展趋势报告 · YYYY-MM】** 🔬 **一、技术突破** - 模型架构演进（Transformer 变种、Mamba、MoE 等） - 多模态能力（图文音视频融合） - 长上下文窗口最新进展 🏢 **二、头部玩家动态** | 公司 | 最新模型 | 核心能力 | 差异化优势 | |------|---------|---------|-----------| | OpenAI | GPT-5.2 | ... | ... | | Anthropic | Claude 4 | ... | ... | | Google | Gemini 3 | ... | ... | | Meta | LLaMA 4 | ... | ... | | DeepSeek | V4 | ... | ... | 🌍 **三、生态与市场格局** - 开源 vs 闭源趋势 - API 价格战走向 - 垂直领域渗透情况 ⚖️ **四、监管与安全** - 主要地区 AI 监管政策 - 安全对齐最新进展 💡 **五、未来 6-12 个月趋势预判** （3-5 条核心预测，附依据） 📚 **六、值得关注的项目/论文** ``` ## 数据来源 每次生成前搜索最新信息： - 搜索 `LLM trends 2026 latest developments` - 搜索 `大模型发展趋势 2026 最新动态` - 搜索头部公司最新发布（OpenAI/Anthropic/Google DeepMind/Meta/DeepSeek） ## 参考资源 详细数据可查阅： - `references/llm-landscape-2026.md` — 2026年 LLM 全景图 - `references/papers-trends.md` — 最新必读论文列表


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: sunnyhot/deals-hunter (version 6.0.0)

--- name: deals-hunter version: 5.0.0 description: 每日羊毛推荐系统 - 什么值得买 RSS + 历史最低价查询（Tavily，限量）+ 购买建议。每次只对前 5 个商品查历史价，24h 缓存，控制在免费额度内。 metadata: openclaw: requires: bins: ["python3"] optionalBins: ["mcporter"] env: - TAVILY_API_KEY --- # Deals Hunter v5.0 每日羊毛推荐系统 - 什么值得买 RSS + 历史最低价查询 + 购买建议 ## ✨ 最新更新 (v5.0 - 2026-03-29) ### 🎯 优化 - ✅ **Tavily 配额控制**: 每次只对前 5 个商品查历史价（从 ~90 次/天降到 ~30 次/天） - ✅ **24h 价格缓存**: 同一商品 24 小时内不重复查询 - ✅ **移除明文 API Key**: 只从环境变量读取，更安全 - ✅ **清理旧版本**: 删除 v3、v4 脚本，只保留 `deals-hunter.py` ### 📦 推荐内容 每个商品包含: - 💰 **当前价格** - 📉 **历史最低价** - 💡 **购买建议**（含推荐理由） - 🛒 **购买链接**（京东/天猫/什么值得买） - 📊 **历史价格查询链接**（慢慢买） ## 🔄 工作流程 ### 1. 数据来源 **什么值得买 RSS**: - RSS URL: http://feed.smzdm.com - 更新频率: 每 15-30 分钟 - 内容: 优惠商品标题、描述、链接 ### 2. 历史价格查询（Tavily） 使用 Tavily 搜索每个商品: - 当前价格、原价 - 历史最低价 - 价格走势 - 购买链接 ### 3. 购买建议生成 基于价格分析: - 当前价格 vs 历史最低价 - 价差百分比 - 购买时机建议 ## 📋 输出示例 ``` 🐑 今日羊毛推荐（增强版） - 2026-03-25 17:00 📦 商品数量: 15 | 📊 含历史最低价 + 购买建议 --- **1. Apple iPhone 17 256G** 💰 当前价格: **¥5,999** 📉 历史最低价: **¥4,699** 💡 购买建议: ⏰ 建议等待 价格比最低价高 27.7% 🛒 购买链接: <https://item.jd.com/...> 📊 查看历史价格: <https://cu.manmanbuy.com/...> --- 📊 **今日统计**: • ✅ 建议入手: 5 个 • ⏰ 建议等待: 10 个 ⚠️ 提醒: • 价格实时变化，建议尽快查看 • 历史价格仅供参考，以实际为准 • 部分优惠需用券或有地区限制 📅 下次更新: 9:00 AM / 12:00 PM / 6:00 PM ``` ## 🔧 配置 ```json { "discord_channel": "1482243346692051105", "rss_source": "http://feed.smzdm.com", "max_items": 15, "dedup_hours": 24 } ``` ## 🚀 使用方式 ### 自动运行（Cron） 每天 9:15 AM / 12:05 PM / 6:10 PM 自动运行 ### 手动触发 ```bash python3 ~/.openclaw/workspace/skills/deals-hunter/scripts/deals-hunter-v4.py ``` ## 📝 更新日志 ### v4.0 (2026-03-25) - ✅ 新增历史最低价查询 - ✅ 新增智能购买建议 - ✅ 新增价格统计报告 - ✅ 新增慢慢买链接 ### v3.0 (2026-03-12) - ✅ 详细产品信息 - ✅ 多平台购买链接 - ✅ 历史价格查询链接 - ✅ 智能推荐理由 - ✅ Tavily 集成 - ✅ 去重机制 ``` ## 📝 Usage ### Automatic Run (Recommended) Cron jobs configured: - deals-morning (9:00 AM) - deals-noon (12:00 PM) - deals-evening (6:00 PM) ### Manual Trigger ```bash python3 scripts/deals-hunter-v3.py ``` ## ⚠️ Notes 1. All price information is for reference only 2. Deals may have time limits (check ASAP) 3. Users should verify before purchasing 4. Links may not be valid long-term 5. Historical price data from Manmanbuy/SMZDM ## 🔄 Changelog ### v3.0.0 (2026-03-12) - ✅ Upgraded data source to SMZDM RSS - ✅ Added historical prices and price trends - ✅ Added multi-platform purchase links - ✅ Added detailed recommendation reasons - ✅ Used Tavily to verify price authenticity ### v2.0.0 (2026-03-11) - ✅ Data source upgraded to SMZDM RSS - ✅ Added historical prices and price trends - ✅ Added multi-platform purchase links - ✅ Added detailed recommendation reasons - ✅ Used Tavily to verify price authenticity ### v1.0.0 (2026-03-09) - ✅ Initial version - ✅ Based on Manmanbuy data source ## 📈 Performance Metrics - **Recommendation Accuracy**: 95%+ - **Price Authenticity**: 98%+ - **User Satisfaction**: ⭐⭐⭐⭐⭐ --- **Want more deals? 3 pushes daily, never miss a good price!** 🎉


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (CRITICAL)
Skill: babuperumana/malayalam-whatsapp (version 1.0.0)

# Malayalam WhatsApp Skill (മലയാളം വാട്സ്അപ്പ് കഴിവ്) WhatsApp വഴി വരുന്ന മലയാളം / Manglish സന്ദേശങ്ങൾ ശരിയായി മനസ്സിലാക്കി, സാംസ്കാരികമായി വിനയത്തോടെ മറുപടി നൽകാനുള്ള skill. --- ## When to Use - User sends Malayalam script (Unicode U+0D00–U+0D7F) - User writes Manglish: "namaskaram", "sughamano", "nanni" - User asks for Malayalam translations --- ## Common Phrases | Malayalam | Manglish | Meaning | |----------|----------|---------| | നമസ്കാരം | namaskaram | Hello | | നന്ദി | nanni | Thank you | | ശരി | sheri | Okay | | അതെ | athe | Yes | | ഇല്ല | illa | No | | സുഖമാണോ? | sughamano? | How are you? | | എന്ത് സഹായം വേണം? | entha sahayam venam? | What help do you need? | --- ## Response Style - User മലയാളത്തിൽ എഴുതിയാൽ → മലയാളത്തിൽ തന്നെ മറുപടി - User Manglish ആണെങ്കിൽ → Manglish ഉപയോഗിക്കുക - വിനയം പുലർത്തുക: - ചേട്ടാ / ചേച്ചി - സാർ / മാഡം - Soft particles ഉപയോഗിക്കുക: - അല്ലേ? - അല്ലോ? - കേട്ടോ? --- ## Example Responses ### Manglish


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ckchzh/php-analyzer (version 2.0.3)

--- name: "php-analyzer" version: "2.0.3" description: "Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Php Analyzer concepts, best practices, and implementation patterns." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [php,analyzer, reference] category: "devtools" --- # Php Analyzer Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Php Analyzer concepts, best practices, and implementation patterns. No API keys or credentials required. ## Commands | Command | Description | |---------|-------------| | `intro` | intro reference | | `quickstart` | quickstart reference | | `patterns` | patterns reference | | `debugging` | debugging reference | | `performance` | performance reference | | `security` | security reference | | `migration` | migration reference | | `cheatsheet` | cheatsheet reference | ## Output Format All commands output plain-text reference documentation via heredoc. No external API calls, no credentials needed, no network access. --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: quqi1599/feishu-public-table-monitor (version 1.0.2)

--- name: feishu-public-table-monitor description: 监控公开可访问的飞书 Wiki/文档中指定章节下的价格表或模型表，检测版本日期、模型新增/删除、倍率与价格变化，并输出适合 Telegram/Markdown 的变更通知。适用于用户要求监控公开飞书表格、价格表、模型列表、倍率表、产品清单变动并推送提醒的场景。 --- # Feishu Public Table Monitor 用于监控**公开可访问**的飞书 Wiki/文档页面中的目标表格喵。 ## 适用场景 当用户提出这些需求时使用本 skill 喵 - 监控公开飞书页面中的价格表变化 - 监控模型列表、倍率表、资费表、商品表变化 - 需要把变动内容整理成 Markdown 通知 - 需要为该监控生成可定时执行的脚本或 cron job ## 限制 - 仅适用于**无需登录即可访问**的飞书页面喵 - 当前脚本按“章节标题下的首个表格”定位目标表喵 - 如果页面结构大改 可能需要调整脚本喵 ## 快速用法 脚本路径喵 - `scripts/monitor_feishu_price_table.py` 先抓取一次基线喵 ```bash python3 scripts/monitor_feishu_price_table.py \ 'https://example.feishu.cn/wiki/XXXX' \ --section-title '三、模型列表与倍率价格表（所有模型可用）' ``` 如果只想看当前解析结果喵 ```bash python3 scripts/monitor_feishu_price_table.py \ 'https://example.feishu.cn/wiki/XXXX' \ --section-title '三、模型列表与倍率价格表（所有模型可用）' \ --print-snapshot ``` 兼容说明喵 - 支持旧版 `clientVars: Object({...})` HTML 内嵌数据喵 - 支持 `Object(JSON.parse("..."))`、`Object(decodeURIComponent("..."))` 等包装格式喵 - 如果飞书返回 `Object()` 空壳，说明页面已切换到新版异步加载；脚本会给出清楚错误，不再抛误导性的 `JSONDecodeError: Expecting value` 喵 - 对 `Object()` 空壳页面，后续应改用飞书实际接口或浏览器自动化抓取加载后的表格喵 ## 常用参数 - `--section-title`：要监控的章节标题喵 - `--title`：通知标题 文案默认可自定义喵 - `--state-dir`：状态目录 用于存放基线快照喵 - `--print-snapshot`：打印当前解析出来的表格快照喵 ## 推荐工作流 1. 先用 `--print-snapshot` 确认表格抓对了喵 2. 再正常跑一次初始化基线喵 3. 然后把脚本挂到 cron 定时执行喵 4. 若输出是 `NO_REPLY` 就表示没变化喵 5. 若输出是 Markdown 文本 就直接发送给用户喵 ## 与 OpenClaw cron 搭配 如果用户要“有变化就推送给我”喵 - 用本脚本生成差异输出喵 - 在 cron 的 `agentTurn` 里执行脚本喵 - 规则写成： - 输出 `NO_REPLY` 或 `INIT_ONLY` 时只回复 `NO_REPLY` - 其他输出原样发送喵 ## 自定义建议 如果用户希望排版更像公告喵 - 用 `--title` 自定义标题 - 保持 Markdown 样式输出 - 需要更细分类时 可扩展为 涨价 降价 新增 下架 四段喵


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