OpenClaw/clawhub-security-signals huggingface dataset:
Skill: dinghaibin/seq-tool (version 1.0.0)

--- name: seq-tool description: Generate sequences of numbers with configurable start, end, and increment values. Use for creating numbered lists, loops, and ranges. --- # Seq - Number Sequence Generator Print sequences of numbers from START to END with optional INCREMENT. Supports integer and decimal sequences for various use cases. ## Usage ```bash seq-tool [options] [first] [increment] <last> ``` ## Options - `-w`: Equal-width padding with leading zeros - `-s STR`: Use STR as separator (default: newline) - `-f FORMAT`: Use printf-style format string ## Examples ```bash seq-tool 1 10 seq-tool 0 2 10 seq-tool -w 1 100 ```

path: scripts/seq.py
content: #!/usr/bin/env python3
import sys
start, end, step = 1, int(sys.argv[1]), 1
if len(sys.argv)>2: start, end = int(sys.argv[1]), int(sys.argv[2])
if len(sys.argv)>3: step = int(sys.argv[3])
for i in range(start, end+1, step): print(i)


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

# MiMo 联网搜索技能 ## 描述 使用小米 MiMo 模型的联网搜索功能进行实时信息搜索。 ## 触发条件 - 用户要求搜索实时信息、最新动态或资料核对 - 用户提到 "搜索"、"查找"、"查询" 等关键词 - 需要获取最新网络信息时 ## 工具 - `exec`: 调用 MiMo 联网搜索 API ## 配置要求 1. **API Key**: 需要配置 `MIMO_API_KEY` 环境变量 2. **模型支持**: mimo-v2-pro, mimo-v2-omni, mimo-v2-flash 3. **计费**: 中国区 ¥25 / 1K 次请求 ## 使用方法 ### 1. 配置 API Key ```bash # 在 OpenClaw 配置文件中添加 MIMO_API_KEY=sk-your-api-key-here ``` ### 2. 调用联网搜索 API ```bash curl -X POST "https://api.xiaomimimo.com/v1/chat/completions" \ -H "[REDACTED_SECRET]" \ -H "Content-Type: application/json" \ -d '{ "model": "mimo-v2-flash", "messages": [ { "role": "user", "content": "你的搜索查询内容" } ], "tools": [ { "type": "web_search", "max_keyword": 3, "force_search": true, "limit": 1 } ], "max_completion_tokens": 1024, "temperature": 1.0, "top_p": 0.95, "stream": false, "thinking": { "type": "disabled" } }' ``` ### 3. 在 OpenClaw 中使用 ```javascript // 使用 exec 工具调用 MiMo 联网搜索 const command = `curl -X POST "https://api.xiaomimimo.com/v1/chat/completions" \ -H "[REDACTED_SECRET]" \ -H "Content-Type: application/json" \ -d '${JSON.stringify({ model: "mimo-v2-flash", messages: [{ role: "user", content: query }], tools: [{ type: "web_search", max_keyword: 3, force_search: true, limit: 1 }], max_completion_tokens: 1024, temperature: 1.0, top_p: 0.95, stream: false, thinking: { type: "disabled" } })}'`; exec(command); ``` ## 示例 ### 搜索 MiMo 基准测试 ```javascript const query = "MiMo-V2-Flash 的基准测试结果是什么？"; // 调用 API 获取搜索结果 ``` ### 搜索最新技术动态 ```javascript const query = "2026 年 AI 大模型最新进展"; // 调用 API 获取搜索结果 ``` ## 注意事项 1. **API Key 安全**: 不要在代码中硬编码 API Key，使用环境变量 2. **计费控制**: 联网搜索功能需要付费，注意控制调用频率 3. **模型选择**: 确保使用支持联网搜索的模型（mimo-v2-flash 等） 4. **错误处理**: 处理 API 调用失败的情况 ## 故障排除 - **401 错误**: API Key 无效或未配置 - **400 错误**: 模型名称错误或参数不正确 - **网络错误**: 检查网络连接和 API 端点


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: te1man/cinema-insider-top10 (version 1.0.0)

--- name: cinema_insider_top10 description: Professional analytical digest of top 10 movie and TV industry news using advanced AI aggregation and cross-referencing. tags: cinema, movies, tv, production, Hollywood, analytics --- # Cinema Insider Top-10 Skill This skill provides high-tier movie and TV industry intelligence by aggregating, deduplicating, and analyzing news from premier international sources. ## Objective Upon request (e.g., "Cinema news"), the agent must aggregate news from the curated RSS feeds, perform cross-source verification, and deliver a ranked top-10 briefing of the most significant industry events. ## Curated Sources 1. **Variety** (http://variety.com/feed/) - Business and production standards. 2. **Deadline Hollywood** (https://deadline.com/feed/) - Breaking news. 3. **The Hollywood Reporter** (https://www.hollywoodreporter.com/c/movies/feed/) - In-depth industry reporting. 4. **ComingSoon.net**, **Collider**, **Screen Rant**, **ScreenCrush**, **LRMonline**, **Entertainment Weekly**, **TV Insider**, **IMP Awards**. ## Instructions & Logic - **Verification & Deduplication:** If a story appears in multiple feeds, aggregate all details into a single high-quality entry. Do not repeat the same event. - **Deep Dive Analysis:** For major "Breaking News" (e.g., major casting, studio deals, or director attachments), use `web_search` to gather additional context, production timelines, or historical significance. - **Categorization:** Identify each news item as "Production," "Business," "Casting," or "Marketing." - **Visual Capture:** For highly visual news (e.g., new trailer releases or poster reveals), use the `browser` tool to capture and present a preview if applicable. - **Ranking:** Order the top 10 by industry impact, placing production and business strategy news above trailers and general entertainment. ## Formatting Guidelines - **Headline:** Clear and professional. - **Analytical Take:** A concise explanation of why this news matters for industry professionals. - **Source Context:** Provide direct links and mention if the news is verified by multiple top-tier outlets. - **Output Language:** Respond in the user's preferred language, translating the insights from the English source material. ## Tools - `web_fetch`: For parsing the primary RSS feeds. - `web_search`: For cross-referencing, verifying "Breaking News," and adding depth. - `browser`: For visual inspection of sources and capturing media previews. - `LLM Reasoning`: For summarization, importance ranking, and deduplication.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: rueshady/ecdysales (version 1.0.2)

--- name: ecdysales description: "Quick product image processing: add price sticker + watermark + logo. Use when user sends `$price:` with an image. Minimal context, runs fast." requires: bins: - convert - identify - bc - python3 --- # Ecdysales 🏷️ You add price stickers to product images. Nothing else. ## When to act A message has `$price:` AND an image was attached. ## What to do 1. Run: `scripts/run.sh --latest '<price>' [flags]` — **use single quotes** 2. The script prints `✅ Done: <output-path>` — save that path 3. Reply with the output image to the user 4. Say nothing else. ⚠️ **Single quotes for prices:** `'$1300'` not `"$1300"` — double quotes break `$`. ⚠️ `MEDIA:` line must be FIRST in your reply. Without it, nothing is sent. ## Skip flags | User says | Add to command | |-----------|---------------| | `no-logo` | `--no-logo` | | `no-watermark` | `--no-watermark` | | `sticker-only` | `--sticker-only` | ## Errors | Situation | Reply | |-----------|-------| | `$price:` but no image | 📸 Send an image with your price | | Image but no `$price:` | 💰 Include `$price: $XXX` | | Processing failed | ❌ Something broke, try again | ## Safety - **No network access.** All processing is local via ImageMagick. No external APIs, no data leaves the machine. - **No shell injection.** Prices are passed to ImageMagick `caption:`, not interpolated into shell commands. Single quotes prevent variable expansion. - **Read-only input.** Source images are never modified. Output goes to a separate `output/` directory. - **No persistent state.** No databases, no config files written at runtime, no tracking. - **Worst case:** A malformed image causes ImageMagick to error out. The script catches this and reports failure. - **Cleanup:** Output files should be cleaned periodically (e.g. cron job) to avoid disk fill. ## Version History | Version | Date | Changes | |---------|------|---------| | 1.0.0 | 2026-03-27 | Initial release | ## Everything else NO_REPLY. Don't chat. Don't explain. Just process or stay quiet.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: cameron48/mcf-accounting-tool (version 1.0.0)

--- name: Accounting Tool description: Financial management with invoices, expenses, job costing, P&L reports, and QuickBooks sync — built for AI agents. author: MCF Agentic version: 1.0.0 tags: [accounting, invoices, expenses, job-costs, pnl, quickbooks, financial-reports] pricing: x402 (USDC on Base) gateway: https://gateway.mcfagentic.com --- # Accounting Tool Give your AI agent full control over financial operations. Create and send invoices, log expenses, track job costs, and pull P&L reports — all through simple API calls. Sync everything to QuickBooks when you need it in your traditional accounting stack. Ideal for agents managing client billing, tracking project profitability, or automating month-end reporting without touching a spreadsheet. ## Authentication All endpoints require x402 payment (USDC on Base L2). Send a request without payment to receive pricing info in the 402 response. ## Endpoints | Method | Path | Price | Description | |--------|------|-------|-------------| | GET | /api/accounting/stats | $0.001 | Financial overview | | GET | /api/accounting/invoices | $0.001 | List invoices | | POST | /api/accounting/invoices | $0.01 | Create invoice | | GET | /api/accounting/invoices/:id | $0.001 | Get invoice details | | PATCH | /api/accounting/invoices/:id/send | $0.05 | Send invoice | | PATCH | /api/accounting/invoices/:id/pay | $0.01 | Mark invoice paid | | GET | /api/accounting/expenses | $0.001 | List expenses | | POST | /api/accounting/expenses | $0.01 | Create expense | | GET | /api/accounting/job-costs | $0.001 | List job costs | | POST | /api/accounting/job-costs | $0.01 | Create job cost entry | | GET | /api/accounting/job-costs/summary | $0.01 | Job cost summary | | GET | /api/accounting/reports/pnl | $0.05 | P&L report | | GET | /api/accounting/reports/revenue-by-month | $0.05 | Revenue by month | | GET | /api/accounting/reports/expenses-by-category | $0.05 | Expenses by category | | POST | /api/accounting/quickbooks/sync | $0.10 | Sync with QuickBooks | | GET | /api/accounting/quickbooks/sync-log | $0.001 | QuickBooks sync log |


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: codekungfu/coworking-spaces (version 0.1.0)

--- name: "附近共享办公" description: "Find nearby coworking spaces. Invoke when user asks for shared offices near me." --- # Nearby Coworking Spaces 用途 - 提供用户当前位置附近的 Coworking Spaces 共享办公列表 - 统一返回字段与查询行为，便于前端/接口复用 触发条件 - 用户询问“共享办公 附近 / coworking spaces near me / shared offices” 输入参数 - location: 经纬度 { lat, lng }，必填 - radius_meters: 查询半径，默认 3000 - limit: 返回数量上限，默认 20，最大 50 - filters: 可选筛选（是否按日租、会议室、咖啡、评分等） 响应字段 - 统一参见 [STANDARD_RESPONSE.md](file:///Users/mac_lkm/workspace/trae/100fj/.trae/skills/STANDARD_RESPONSE.md) - 本技能 category 固定为 "coworking-spaces" 错误码 - INVALID_LOCATION: 经纬度不合法 - RADIUS_TOO_LARGE: 超过最大查询半径 - PROVIDER_UNAVAILABLE: 数据源不可用 - RATE_LIMITED: 触发速率限制 示例 - 输入: { location: { lat: 30.123, lng: 120.456 }, radius_meters: 2500, limit: 10 } - 输出: 标准 POI 列表（见 STANDARD_RESPONSE.md） 隐私与速率限制 - 仅在用户授权定位后查询 - 避免保留精确坐标，必要时进行网格化模糊处理


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: teoslayer/pilot-sync (version 1.0.0)

--- name: pilot-sync description: > Bidirectional file synchronization between agents over the Pilot Protocol network. Use this skill when: 1. You need to keep directories synchronized between two agents 2. You want to replicate files across multiple nodes with conflict detection 3. You need to maintain consistent file state across distributed agents Do NOT use this skill when: - You only need one-way file transfer (use pilot-share instead) - You need real-time streaming data (use pilot-stream-data instead) - Files are larger than 100MB without chunking support (use pilot-chunk-transfer) tags: - pilot-protocol - file-transfer - synchronization - bidirectional license: AGPL-3.0 compatibility: > Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start). metadata: author: vulture-labs version: "1.0" openclaw: requires: bins: - pilotctl homepage: https://pilotprotocol.network allowed-tools: - Bash --- # pilot-sync Bidirectional file synchronization between agents using conflict detection. ## Commands ### Sync directory to remote ```bash for file in /path/to/sync/*; do pilotctl --json send-file 1:0001.AAAA.BBBB "$file" done ``` ### List received files ```bash pilotctl --json received | jq -r '.received[] | {filename, size, from, timestamp}' ``` ### Watch directory for changes ```bash fswatch -0 /path/to/sync | while read -d "" file; do pilotctl --json send-file 1:0001.AAAA.BBBB "$file" done ``` ## Workflow Example Bidirectional sync with conflict detection: ```bash #!/bin/bash SYNC_DIR="$HOME/shared-data" REMOTE="1:0001.AAAA.BBBB" # Build manifest LOCAL_MANIFEST=$(find "$SYNC_DIR" -type f -exec sh -c \ 'printf "%s:%s:%s\n" "{}" "$(md5sum {} | cut -d\" \" -f1)" "$(stat -f %m {})"' \;) # Send manifest and sync pilotctl --json send-message "$REMOTE" --data "{\"type\":\"sync_init\",\"manifest\":\"$LOCAL_MANIFEST\"}" # Start continuous sync fswatch -0 "$SYNC_DIR" | while read -d "" changed_file; do pilotctl --json send-file "$REMOTE" "$changed_file" done ``` ## Dependencies Requires pilot-protocol skill, jq, fswatch/inotifywait, md5sum, and stat.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kingofzhao/reading-retention-engineer (version 1.0.0)

# Reading Retention Engineer > 阅读留存工程师 — 将阅读从"看过"升级为"记住并可用"，设计个人化的知识吸收系统。 ## Description 大多数人读完一本书只记住5%。本Skill整合主动阅读法、间隔重复、费曼技巧和Zettelkasten笔记法，构建从阅读到长期记忆的完整管道。 ## Usage 当用户需要： - 提升阅读留存率 - 建立阅读笔记系统 - 将阅读转化为可用的知识 - 设计个人知识库 - 加速学习新领域 ## Key Concepts ### 1. 三遍阅读法 - **第一遍**（浏览）：目录→章节标题→首尾段，建立骨架（15min） - **第二遍**（精读）：标注关键论点，边缘写问题（正常速度） - **第三遍**（输出）：用自己的话重述，写3句核心总结 ### 2. 知识原子化 - 每个笔记 = 一个原子观点（可独立理解） - 格式：观点 + 来源 + 与已有知识的连接 - 原子间通过链接形成网络，不是文件夹 ### 3. 间隔重复阅读计划 ``` 阅读后 1天 → 回顾笔记（5min） 阅读后 3天 → 写一段总结（不翻笔记） 阅读后 7天 → 与他人讲解/写短文 阅读后30天 → 应用到实际问题 ``` ### 4. 费曼检验 - 如果你不能用简单的话向非专家解释，说明你没真懂 - 卡壳的地方 = 需要重读的部分 ## Instructions 1. 评估用户当前的阅读-留存瓶颈 2. 选择适合的笔记工具（纸笔/Notion/Obsidian） 3. 建立标准化笔记模板 4. 设计间隔重复计划 5. 建立每周阅读回顾流程 ## Examples **输入**: "读了很多书但感觉什么都没记住" **输出**: 三遍法 + Zettelkasten原子笔记 + 7天间隔计划 + 每周输出一篇读书笔记 ## Boundaries - 不追求100%留存（不可能也不必要） - 享阅读乐趣优先，系统化其次 - 不同类型书籍用不同策略


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: bobwattienz/nzta-traffic (version 1.0.0)

--- name: nzta-traffic description: Query real-time NZ state highway traffic conditions from the Waka Kotahi NZTA Traffic and Travel API. Use when checking road events, incidents, closures, roadworks, traffic cameras, or travel conditions on New Zealand highways. Covers all 14 NZ regions (Northland to Southland). No API key required. Use for queries like "how's the traffic", "any road closures", "check SH1 conditions", or "traffic cameras near Wellington". --- # NZTA Traffic Query the Waka Kotahi Traffic and Travel REST API for real-time state highway conditions across New Zealand. ## Quick Start Check road events for a region: ```bash scripts/nzta-traffic.sh --region Wellington ``` Check a specific highway: ```bash scripts/nzta-traffic.sh --journey 10 ``` Check traffic cameras in a region: ```bash scripts/nzta-traffic.sh --cameras --region Wellington ``` ## Script Usage ``` scripts/nzta-traffic.sh [options] Options: --region <name|id> Region name or ID (e.g. "Wellington" or "9") --journey <id> Journey/highway ID (e.g. 10 for SH1 Wellington) --bbox <minlon,minlat,maxlon,maxlat> Bounding box query --cameras List traffic cameras instead of events --list-regions List all region names and IDs --list-journeys List journeys for a region (requires --region) --json Output raw JSON instead of formatted summary --zoom <level> Geometry zoom level, -1 for no geometry (default: -1) ``` ## Region and Journey Lookup Run `--list-regions` to get region IDs, then `--list-journeys --region <name>` to find highway journey IDs for that region. Common Wellington region journeys: SH1 (ID 10), SH2 (ID 9), SH58 (ID 12), SH59 (ID 341). For full endpoint reference and response field descriptions, see [references/api-endpoints.md](references/api-endpoints.md). ## Event Impact Levels - **Closed** — road is closed - **Major delays** — significant delays expected - **Minor delays** — some delays - **Caution** — be aware, proceed carefully - **Watch and observe** — informational ## Notes - API base: `https://trafficnz.info/service/traffic/rest/4/` - No authentication required - Returns JSON with `Accept: application/json` header - Empty response (`"response": ""`) means no active events — that's good news


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector:  ()
Skill: nidhov01/05 (version 1.0.0)

--- name: "content-summary" version: "1.0.0" description: "智能内容总结和项目复盘工具" author: "AI Skills Team" tags: ["总结", "复盘", "分析", "报告"] requires: [] --- # AI总结复盘技能 智能内容总结和项目复盘工具，支持多种内容类型。 ## 技能描述 提供日报、会议、项目、文章等多种内容的自动总结和复盘功能。提取关键要点、计算目标达成率、识别成功经验和问题。 ## 使用场景 - 用户："总结今天的日报" → 提取关键任务和完成情况 - 用户："复盘这个项目" → 分析目标达成率和经验教训 - 用户："总结这篇文章" → 提取主要观点和论据 - 用户："整理会议记录" → 提取决策和行动项 ## 工具和依赖 ### 工具列表 - `scripts/summary_review.py`：核心总结复盘模块 ### API密钥 无（基础版本） ### 外部依赖 - Python 3.7+（仅使用标准库） ## 配置说明 ### 支持的内容类型 | 类型 | 说明 | 特殊字段 | |------|------|----------| | daily | 日报/工作日志 | completed_tasks, issues | | meeting | 会议记录 | agenda, decisions, action_items | | project | 项目总结 | goals, achievements, lessons | | article | 文章总结 | main_idea, key_arguments | | general | 通用内容 | key_points, summary | ### 数据存储位置 数据库：`~/.ai_summary.db` ## 使用示例 ### 基本用法 ```python from summary_review import AISummaryReview system = AISummaryReview() # 内容总结 summary = system.summarize_content(daily_content, 'daily', '工作日报') # 项目复盘 review = system.review_project(project_data) ``` ### 场景1：日报总结 用户："总结我今天的工作" 内容： ``` 今天完成了用户模块的开发，修复了3个bug。 遇到了数据库连接问题，已经解决。 明天计划开始订单模块的开发。 ``` AI： ```python summary = system.summarize_content(content, 'daily', '工作日报') # 返回：关键任务、问题、计划 ``` ### 场景2：项目复盘 用户："复盘AI助手项目" AI： ```python project_data = { 'name': 'AI助手项目', 'goals': ['实现对话功能', '添加知识库', '支持多语言'], 'results': ['对话功能已实现', '知识库完成80%', '中文支持已完成'], 'metrics': {'用户满意度': 85, '响应时间': 1.2} } review = system.review_project(project_data) # 返回：目标达成率、成功经验、问题识别、改进建议 ``` ### 场景3：文章总结 用户："总结这篇技术文章" AI： ```python summary = system.summarize_content(article_content, 'article', '文章标题') # 返回：主要观点、关键论据、结论 ``` ### 场景4：导出Markdown 用户："导出总结为Markdown文件" AI： ```python output_path = system.export_to_markdown(summary_id, "output.md") # 生成格式化的Markdown文件 ``` ## 复盘维度 项目复盘包含以下维度： 1. **目标达成率**：自动计算目标完成百分比 2. **成功经验**：提取已达成目标的亮点 3. **问题识别**：发现未达成目标和指标异常 4. **改进建议**：基于分析生成具体建议 5. **下一步计划**：自动生成后续行动计划 ## 故障排除 ### 问题1：总结不够精准 **现象**：提取的关键点不够准确 **解决**： - 基础版本使用规则提取，可考虑升级到AI增强版（技能06） - 或使用更清晰的输入格式，分段明确 ### 问题2：数据库文件过大 **现象**：历史记录太多，数据库文件大 **解决**： - 定期清理旧记录 - 或导出重要总结为Markdown后删除数据库记录 ### 问题3：导出格式不符合要求 **现象**：Markdown格式需要调整 **解决**： - 可以编辑导出的Markdown文件 - 或使用自定义模板功能 ## 注意事项 1. **总结方式**：基于关键词和句子结构，可能不够精准 2. **复盘建议**：是通用模板，需要根据实际情况调整 3. **人工判断**：建议结合人工判断，不完全依赖自动化 4. **定期清理**：定期清理历史记录，避免数据库过大 5. **AI增强**：如需更强大的总结能力，可使用技能06（AI总结增强版）


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: azamat02/kaspi-autopay (version 1.0.0)

--- name: kaspi-autopay description: Telegram bot auto-payment integration for Kazakhstan market (Kaspi Pay). Automates payment verification, receipt checking, and product delivery in Telegram bots. Use when building payment bots for Kazakhstan businesses, info-products, or e-commerce — especially with Kaspi QR/transfer. --- # Kaspi Auto-Payment for Telegram Bots Automate payment acceptance in Telegram bots for the Kazakhstan market. No manual receipt checking, no lost leads, 24/7 payments. ## How It Works 1. Customer selects a product/service in the Telegram bot 2. Bot generates a payment request (Kaspi transfer) 3. Customer pays and sends the receipt to the bot 4. Bot **automatically verifies** the payment via a proprietary verification method 5. Product/access is delivered instantly — no human needed ## What It Solves - **Lost leads**: Customer wants to pay at 11 PM — no manager available. Lead gone. - **Fake receipts**: Manual checking = human errors + fraud - **Slow fulfillment**: Manager checks receipt → delays → bad experience - **Scaling bottleneck**: More sales = more managers needed ## Key Features - ✅ Automatic receipt verification (Kaspi Pay) - ✅ Fraud protection (fake receipt detection) - ✅ Instant product/access delivery - ✅ 24/7 operation without managers - ✅ Telegram-native (Web App support) - ✅ Conversion boost: typical 40% → 75%+ ## Best For - Info-product sellers (courses, guides, memberships) - Small & medium businesses in Kazakhstan - Telegram-first e-commerce - Service businesses with online booking/payment ## Tech Stack - Node.js / NestJS - Telegraf (Telegram Bot API) - Proprietary Kaspi payment verification - PostgreSQL / Supabase ## Get Started This is a managed integration — not a self-hosted script. **For setup and pricing, contact the developer directly:** 👉 **Telegram:** [t.me/saidulyyy](https://t.me/saidulyyy) Built by **Azamat Saiduly** — full-stack developer & fintech builder specializing in payment automation for the Kazakhstan market.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: caigang78/slack-print (version 1.0.0)

--- name: slack-print description: 'Print files uploaded to a Slack channel. Supports smart matching: multiple files, filename prefix/keyword filter, file type (pdf/image), and time range ("just now" = "last 5 minutes"). Trigger when the user says things like "print the file from Slack", "print the PDF I just sent to Slack", "print the Slack file", etc.' user-invocable: true --- # Slack Print Skill **Strict rules:** - **Do not** use write/edit tools to create or modify any files - **Do not** create Python scripts, test scripts, or any auxiliary files - **Only** run existing shell scripts or `lp` commands via exec --- ## Print Files from Slack ### Smart Matching: Interpret Intent → Set Variables → Call Script | User says | Environment variables | |-----------|----------------------| | "Print the latest file" / "Print this file" | (default, no variables needed) | | "Print the last two files" / "Print these two files" | `LIMIT=2` | | "Print files starting with report" | `NAME_PREFIX=report` | | "Print files with contract in the name" | `NAME_CONTAINS=contract` | | "Print the PDF I just uploaded" / "Print the PDF from just now" | `MINUTES=5 FILE_TYPE=pdf` | | "Print the last three files" | `LIMIT=3 MINUTES=10` | **FILE_TYPE values**: `pdf` / `image` / `video` / `doc` / `file` (default — matches all) ### Invocation ```bash # Default: print latest file PRINTER=MyPrinter <SKILL_DIR>/slack_fetch_and_print.sh # Print the latest 2 files PRINTER=MyPrinter LIMIT=2 <SKILL_DIR>/slack_fetch_and_print.sh # Print files whose name starts with "report" PRINTER=MyPrinter NAME_PREFIX=report <SKILL_DIR>/slack_fetch_and_print.sh # Print PDFs uploaded in the last 5 minutes PRINTER=MyPrinter MINUTES=5 FILE_TYPE=pdf <SKILL_DIR>/slack_fetch_and_print.sh ``` Script prints `Sent to printer: <filename>` for each file on success. --- ## Print Text Content Directly ```bash echo "content to print" | lp -d <PrinterName> ``` Multi-line content: ```bash cat > /tmp/openclaw_print.txt << 'EOF' content EOF lp -d <PrinterName> /tmp/openclaw_print.txt ``` --- ## List Available Printers ```bash lpstat -a ``` ## Check Print Queue ```bash lpq -P <PrinterName> ``` ## Cancel Print Jobs ```bash cancel -a <PrinterName> ``` ## Check Printer Status ```bash lpstat -p <PrinterName> ```


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