OpenClaw/clawhub-security-signals huggingface dataset:
Skill: jizhidemu52/tianchuang-finance-kb (version 1.0.0)

# Tianchuang Finance Knowledge Base Skill ## Description This skill provides strict document retrieval for Tianchuang Financial questions. When triggered, it searches the complete Tianchuang financial document corpus (8 PDF files) and returns only verbatim text matches or "无". ## Trigger Conditions - Automatically activates when user asks about Tianchuang Financial matters - Questions containing keywords: "天创财务", "报销", "预算", "资金", "外汇", "支付", "核决", "风险", "账期", "差旅", "样品", "费用", "审批", "制度", "规定", "管理办法" ## Retrieval Rules 1. **Strict Verbatim Matching**: Returns only exact text from source documents - no summarization, paraphrasing, or modification 2. **No Interpretation**: Never adds explanations, context, or reasoning 3. **Pure Output**: Only original text or "无" - no headers, footers, or framing text 4. **Multi-match Handling**: Multiple relevant excerpts returned on separate lines 5. **Chinese Language**: All output must be in Chinese 6. **Case Sensitivity**: Matches preserve original capitalization and punctuation ## Document Corpus The skill searches across these 8 merged PDF documents: - 天创财字[2023]007号—关于样品报销（付款）补充规定.pdf - 天创财字[2023]006号—预算管理制度.pdf - 天创财字[2023]005号—资金集中管理【外汇收支管理办法】.pdf - 天创财字[2023]004号—关于规范公司支付单据的说明.pdf - 天创财字[2023]003号—资金管理制度.pdf - 天创财字[2023]002号—风险控制管理制度.pdf - 天创财字[2023]001号—核决权限管理制度.pdf - 流程5-客户账期变更流程.pdf ## Implementation Details - Uses exact string matching with semantic similarity fallback - Prioritizes strong relevance (direct keyword matches) over weak relevance (contextual matches) - Implements multi-pass search: first exact phrase, then keyword proximity, then semantic context - Maintains document structure awareness (preserves section headings and formatting) - Handles special characters and PDF extraction artifacts appropriately ## Usage Example User: "天创财务关于样品报销的时间要求是什么？" Skill: "4.1基于《财务报销制度》的规定，需要在完结业务后7个工作日内申请报销/支付流程，但由于样品报销/支付的特殊性，本补充规定将该名目的报销时间暂时放宽至次月。 自业务完结起（以实际开支和发票时间孰早），经办人最迟应于次月在线上系统提交流程，执行月清月结。（举例：10月31日前的费用，最迟于 11月30日前提交流程）" ## Maintenance - Document corpus updated by replacing the merged text file - Search algorithm optimized for financial terminology and regulatory language - Regular validation against source PDFs to ensure fidelity ## Author Tianchuang Finance Knowledge Base System ## Version 1.0


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: zitao666/instagram-downloader (version 1.0.1)

--- name: instagram-downloader description: 交互式下载 Instagram 用户内容（帖子/Reels/头像）。首次使用时会依次询问用户名、下载目录、Cookie路径、代理地址。 --- # Instagram Downloader Skill ## 使用流程 ### 第一次使用：必须先询问用户以下 4 个参数 **按顺序询问，不要跳步：** ``` 1️⃣ Instagram 用户名是什么？（不含 @） 2️⃣ 下载到哪个目录？（完整路径，如 D:\Downloads\Instagram） 3️⃣ Cookie 文件路径？（Netscape 格式，如 C:\Users\xxx\cookies_instagram.txt） 4️⃣ 代理地址？（可选，格式 http://host:port，留空则不使用代理） ``` 收集完所有参数后，执行下载命令。 ### 执行命令模板 ```bash gallery-dl --proxy "<代理地址>" --cookies "<cookie文件路径>" -D "<目标目录>" "https://www.instagram.com/<用户名>/" ``` > 注意：代理地址如果用户留空，则去掉 `--proxy` 参数 ## 参数获取方式 ### 1. Instagram 用户名 - 用户输入即可，例如：`fafa.0816` - 主页链接可能是 `https://www.instagram.com/fafa.0816/` ### 2. 下载目录 - 必须是完整绝对路径 - Windows 示例：`D:\Instagram\fafa.0816` - Linux/Mac 示例：`/home/user/downloads/instagram` - gallery-dl 会在此目录下创建 `instagram/<用户名>/` 子目录 ### 3. Cookie 文件路径（Netscape 格式） #### 方法 A：用 yt-dlp 从 Chrome 导出 ```bash yt-dlp --cookies-from-browser chrome --cookies "cookies_instagram.txt" "https://www.instagram.com/" ``` 然后把 `cookies_instagram.txt` 路径告诉 agent。 #### 方法 B：手动获取 sessionid 1. 浏览器登录 Instagram 2. F12 → Application → Cookies → 找 `sessionid` 3. 写成 `cookies_instagram.txt`： ``` # Netscape HTTP Cookie File .instagram.com TRUE / FALSE 1800000000 sessionid 你的sessionid值 .instagram.com TRUE / TRUE 1800000000 csrftoken 你的csrftoken值 ``` ### 4. 代理地址（可选） - 格式：`http://127.0.0.1:7890` - 如果用户不需要代理，直接留空 ## 下载类型说明 | URL 类型 | 下载内容 | 命令后缀 | |---|---|---| | `https://www.instagram.com/<用户>/` | 全部（帖子+reels+头像） | 不加后缀 | | `https://www.instagram.com/<用户>/posts/` | 仅图片帖子 | `/posts/` | | `https://www.instagram.com/<用户>/reels/` | 仅视频 | `/reels/` | | `https://www.instagram.com/<用户>/avatar/` | 头像 | `/avatar/` | | `https://www.instagram.com/p/<帖子ID>/` | 单个帖子 | 直接链接 | ## 完整执行示例 假设用户回答： - 用户名：`fafa.0816` - 下载目录：`D:\Downloads` - Cookie：`C:\Users\栗子\cookies_instagram.txt` - 代理：`http://127.0.0.1:7890` 执行： ```bash gallery-dl --proxy "http://127.0.0.1:7890" --cookies "C:\Users\栗子\cookies_instagram.txt" -D "D:\Downloads" "https://www.instagram.com/fafa.0816/" ``` 输出会写入 `D:\Downloads\instagram\fafa.0816\` ## 工具对比 | 工具 | 适用场景 | 注意 | |---|---|---| | **gallery-dl** | 首选，稳定支持 Instagram 全部类型 | 首选 | | yt-dlp | 备选 | Instagram 支持已标为 broken | ## 常见错误处理 | 错误 | 原因 | 解决 | |---|---|---| | `401 Unauthorized` | Cookie 过期 | 重新获取 sessionid | | `404 Not Found` | 用户不存在或私密 | 确认用户名正确 | | `HttpError` 无权限 | Cookie 缺少必要字段 | 确保有 `sessionid` 和 `csrftoken` 两行 | | SSL 警告 | 代理证书问题 | 加 `--no-check-certificate`（不推荐） | ## 隐私占位符清单 发布前检查： - [ ] 代理地址 → 用 `<代理地址>` 占位 - [ ] Cookie 路径 → 用 `<cookie文件路径>` 占位 - [ ] 下载目录 → 用 `<目标目录>` 占位 - [ ] 用户名 → 用 `<用户名>` 占位


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 403914291/smart-wechat-publisher (version 1.1.4)

# 微信公众号发布技能 **技能名称：** wechat-publisher **版本：** V1.1.2 **描述：** 自动发布 AI 新闻到微信公众号草稿箱 **作者：** 小蛋蛋 **技术支持：** [REDACTED_SECRET] **公众号：** 心识孤独的猪手 --- ## 📋 功能特性 - ✅ 自动收集 15 条 AI 新闻 - ✅ 自动生成 HTML 格式内容 - ✅ 自动发布到公众号草稿箱 - ✅ 支持 5 套专业模板 - ✅ 50 次免费试用 + 8.8 元永久买断 - ✅ 支持自定义发布时间 --- ## 🔧 配置项 | 配置项 | 说明 | 默认值 | 是否必填 | |--------|------|--------|----------| | `app_id` | 公众号 AppID | - | ✅ 是 | | `app_secret` | 公众号 AppSecret | - | ✅ 是 | | `schedule` | 发布时间 | `06:00` | ❌ 否 | | `template` | 发布模板 | `v5-simple` | ❌ 否 | | `news_count` | 新闻条数 | `15` | ❌ 否 | | `timezone` | 时区 | `Asia/Shanghai` | ❌ 否 | --- ## 📖 使用说明 ### 安装技能 ```bash openclaw skill install wechat-publisher ``` ### 配置技能 ```bash openclaw skill config wechat-publisher ``` ### 设置发布时间 ```bash openclaw schedule wechat-publisher 07:00 ``` ### 查看状态 ```bash openclaw skill status wechat-publisher ``` --- ## 💰 授权说明 - **试用版：** 50 次免费使用（约 1 个月） - **专业版：** 8.8 元永久买断 - **购买命令：** `openclaw skill buy wechat-publisher` ### 📊 试用次数说明 **50 次免费试用包含：** - ✅ 测试所有 5 套模板 - ✅ 配置调试和学习成本 - ✅ 约 1 个月的实际使用 - ✅ 充分体验自动发布功能 **试用次数用完后：** - 运行 `openclaw skill buy wechat-publisher` 购买专业版 - 8.8 元永久买断，无限次使用 ### 📞 支付联系方式 **支付流程：** 1. 运行购买命令后，系统生成订单 2. 用户扫码支付（微信/支付宝） 3. 支付成功后，通过以下方式联系管理员获取激活码： | 联系方式 | 说明 | |----------|------| | **微信** | 添加管理员微信：`lylovejava`（备注：技能购买） | | **公众号** | 关注"小蛋蛋助手"公众号，发送订单号 | | **邮箱** | [REDACTED_SECRET]（24 小时内回复） | | **GitHub** | 在 https://github.com/403914291 提交 Issue | **自动激活（推荐）：** - 支付成功后，系统自动发送激活码到用户邮箱 - 或在购买界面直接显示激活码 --- ## 📁 文件结构 ``` wechat-publisher-skill/ ├── SKILL.md # 技能定义文件 ├── publish.py # 核心发布脚本 ├── scripts/ │ ├── install.sh # 安装脚本 │ └── activate.py # 激活脚本 ├── templates/ │ ├── v5-simple.html # V5 简洁模板 │ └── ... # 其他模板 ├── config/ │ └── default.json # 默认配置 └── docs/ └── USER_GUIDE.md # 用户手册 ``` --- _创建日期：2026-03-26_ _最后更新：2026-03-26_


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: chuansir123/xuebang-data-skill (version 1.0.1)

--- name: xuebang-data-skill description: | 查看学邦数据。用于登录学邦后台并读取首页今日经营数据与待办数据。 Use this skill when the user wants to: - 查看学邦今日数据 - 查看学邦数据 - 学邦今日数据 - 学邦数据 - 查看校区今日经营数据 Triggers: 学邦, 今日数据，经营数据，待办数据，校区数据 version: 1.0.1 author: local allowed-tools: - browser --- # 学邦 EDU.BOSS 今日数据查看 ## 目标 登录 `https://boss.xuebangsoft.net/eduboss/`，读取首页"今日数据预览"和待办区块，并整理成简洁汇总返回。 ## 凭据管理 - 这是一个可发布技能，`SKILL.md` 中不得包含任何真实账号、密码、Cookie、Token 或其他敏感信息。 - 首次使用时，如果本地未保存学邦凭据，先向用户索取： - 登录账号 - 登录密码 - 获取后，将凭据写入本地私有笔记 `workspace/TOOLS.md`。 - 后续执行时，优先从 `workspace/TOOLS.md` 读取凭据；只有在缺失或用户要求更新时才再次询问。 - 如果用户明确要求"不保存"，则仅本次使用，任务结束后不在任何文件中落盘。 ## 执行时机 当用户表达以下意图时直接使用本技能： - 查看学邦今日数据 - 查看学邦今日经营数据 - 看下学邦今天数据 - 查学邦待办 - 查 EDU.BOSS 今日概览 ## 站点信息 - 登录页：`https://boss.xuebangsoft.net/eduboss/` ## Browser Act 调用格式（重要！） 使用 `browser act` 时必须使用 **`request` 对象格式**： ```json { "kind": "type", "ref": "<输入框 ref>", "text": "<要输入的内容>" } ``` **常见错误和注意事项**： - ❌ 不要使用 `type="type"` 或 `type="fill"` 作为独立参数 - ❌ 不要使用 `inputRef` 参数 - ✅ 必须使用 `request` 对象，且 `kind` 为 "type"（填写）或 "click"（点击） - ✅ `ref` 参数在 `request` 对象内部，不是浏览器 act 的顶级参数 ## 执行步骤 1. **启动浏览器** ``` browser action="start" ``` 2. **打开登录页** ``` browser action="open" targetUrl="https://boss.xuebangsoft.net/eduboss/" ``` 3. **获取页面快照** ``` browser action="snapshot" ``` 找到以下元素的 ref： - 账号输入框：文本为 "请输入您的手机号码或账号" - 密码输入框：文本为 "请输入您的密码" - 登录按钮：文本为 "登 录" 4. **直接填写账号密码（关键步骤）** ``` browser action="act" request={"kind": "type", "ref": "<账号输入框 ref>", "text": "{账号}"} browser action="act" request={"kind": "type", "ref": "<密码输入框 ref>", "text": "{密码}"} ``` 5. **点击登录** ``` browser action="act" request={"kind": "click", "ref": "<登录按钮 ref>"} ``` 6. **等待页面跳转** ``` browser action="act" request={"kind": "wait", "timeMs": 3000} ``` 7. **处理浏览器连接中断（重要！）** 如果看到错误提示 "gateway closed (1006 abnormal closure)"，说明浏览器连接断了： - 需要重启浏览器：`browser action="start"` - 然后重新 `snapshot` 确认页面状态 - 如果已登录到首页，继续下一步；如果回到登录页，重新执行步骤 4-6 8. **确认首页加载** ``` browser action="snapshot" ``` 确认页面已跳转到首页，看到左侧导航栏（前台、营销、招生等） 9. **提取今日数据** 从快照中查找"数据预览"区块，提取： 10. **提取待办事项** 从快照中查找待办相关区块，提取： ## 输出要求 按下面结构返回，缺失字段写"未读取到"，不要编造： ``` ## 📊 今日数据预览（YYYY-MM-DD） | 指标 | 今日 | 昨日 | |------|------|------| | 🧑 新增客户 | **X** | Y | | ... ## 📋 待处理事项 | 事项 | 数量 | |------|------| | ... ## 📌 小结 ... ``` ## 约束 - 不要因为个别字段缺失就中止，先返回已拿到的数据。 - 如果登录失败，明确说明失败步骤和页面提示。 - 如果浏览器工具异常，说明是工具不可用，不要伪造结果。 - 不要在响应中复述完整密码。 - **浏览器连接中断是常见情况，需要优雅地重启并继续，不要报错退出。** ## 常见问题排查 ### 浏览器连接中断（gateway closed） - **原因**：点击登录导致页面跳转，有时会中断 CDP 连接 - **解决**：立即执行 `browser action="start"` 重启浏览器，然后 `snapshot` 确认状态 ### 填写账号密码失败 - **原因**：使用了错误的参数格式 - **解决**：确保使用 `request` 对象格式，`kind` 为 "type"，`ref` 在对象内部 ### 找不到输入框 - **原因**：页面结构变化或 ref 过期 - **解决**：重新执行 `snapshot` 获取最新 ref ---


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: leialexzhang/local-skill-installer (version 1.0.1)

--- name: local-skill-installer description: Install a local OpenClaw skill from a zip file by unzipping, validating, moving it into the active Skills directory, and verifying the result. --- # Local Skill Installer Use this skill when the user wants to install a local OpenClaw skill package from a zip file on the current Linux system. ## What this skill does This skill helps install a local skill package safely. Expected user input: - A Linux-accessible zip path, for example: `/mnt/c/Users/user/Downloads/skill-vetter-1.0.0.zip` ## Rules - Only work with local zip files. - Prefer Linux paths, not Windows `C:\...` paths. - Use `move`, not `copy`, to avoid duplicate files. - Do not overwrite an existing skill folder without checking first. - If the same skill name already exists, stop and report the conflict. - Clean up temporary files after finishing. - Do not run scripts inside the zip. - Briefly report each important step. ## Steps 1. Confirm the zip file exists. 2. Create a temporary extraction directory. 3. Unzip the package into the temporary directory. 4. Inspect the extracted content. 5. Validate that it looks like an OpenClaw skill: - must contain `SKILL.md` - may also contain `_meta.json`, `assets`, `agents`, `references` 6. Determine the correct active Skills directory for this OpenClaw installation. - Prefer `~/.openclaw/skills/` for shared local skills if appropriate. - If the current workspace has a dedicated `skills/` directory and the context indicates workspace-local installation, use that instead. 7. Determine the final skill folder name. 8. If the target folder already exists: - do not overwrite - report the existing path and stop 9. Move the extracted skill folder into the Skills directory. 10. Verify the final folder and key files exist. 11. Clean up temporary files. 12. Tell the user: - whether installation succeeded - the final installed path - whether reload or restart is needed ## Output format Always report: - Source zip path - Extracted skill folder name - Final installed path - Validation result - Conflict result if any - Whether reload/restart is recommended


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: yang1002378395-cmyk/ad-manager (version 1.2.4)

--- name: ad-campaign-manager version: 1.2.4 description: 广告投放管理 - 自动管理广告投放、优化ROI、生成报告。适合：营销人员、电商运营。 license: MIT metadata: openclaw: emoji: "📢" --- # 广告投放管理 Skill 自动管理广告投放，最大化 ROI。 ## 核心功能 ### 1. 投放管理 - 多平台投放 - 预算分配 - 出价优化 ### 2. 数据分析 - ROI 计算 - 转化追踪 - A/B 测试 ### 3. 智能优化 - 自动调价 - 受众优化 - 创意建议 ## 使用方法 ### 创建广告 ``` 为 ClawMart 创建一个广告投放计划 ``` ### 分析效果 ``` 分析最近一周的广告数据 ``` --- 创建：2026-03-11


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: pereirajair/phpmyadmin-manager (version 1.0.1)

--- name: phpmyadmin-manager slug: phpmyadmin-manager version: 1.0.0 description: "Manage the phpMyAdmin Docker container for local dev environments. Provides a web UI for MySQL at http://localhost:8081. Requires mysql-manager and proxy-manager to be running first." changelog: Initial release. triggers: - "abrir phpmyadmin" - "start phpmyadmin" - "stop phpmyadmin" - "phpmyadmin status" - "interface mysql" - "admin mysql" - "phpmyadmin-manager" metadata: {"clawdbot":{"emoji":"🔷","requires":{"bins":["docker"]},"os":["linux","darwin"]}} --- # phpMyAdmin Manager Manages the phpMyAdmin Docker container, providing a web UI for MySQL database management. ## Architecture ``` phpmyadmin-manager/ ├── docker-compose.yml # phpMyAdmin 5.2 container └── run.sh # lifecycle CLI ``` Connects to the shared `nginx-proxy_net` network and reaches MySQL at `codai_db:3306`. No data is persisted — phpMyAdmin is stateless. ## Commands ```bash ./run.sh start # start phpMyAdmin container ./run.sh stop # stop container ./run.sh status # show status and URL ./run.sh open # print access URL ``` ## How to Execute Tasks ### Start phpMyAdmin Check your session context for the absolute script path, then run: ```bash <plugin-root>/phpmyadmin-manager/run.sh start ``` Open `http://localhost:8081` in a browser. Login: `root` / MySQL root password. ### Check status ```bash <plugin-root>/phpmyadmin-manager/run.sh status ``` ## Prerequisites Start in this order: 1. `proxy-manager start` — creates the shared Docker network 2. `mysql-manager start` — MySQL must be running before phpMyAdmin connects ## Configuration | Variable | Default | Purpose | |------------------------|---------------------|--------------------------------| | `PMA_CONTAINER` | `codai_phpmyadmin` | Container name | | `PMA_PORT` | `8081` | Host port | | `MYSQL_CONTAINER` | `codai_db` | MySQL hostname on shared net | | `MYSQL_ROOT_PASSWORD` | `secret` | MySQL root password | | `PMA_UPLOAD_LIMIT` | `64M` | Max SQL file upload size | | `CODAI_NETWORK` | `nginx-proxy_net` | Shared Docker network name | ## Rules - Start `mysql-manager` before this plugin — phpMyAdmin cannot connect without MySQL. - Port `8081` is bound to `127.0.0.1` — accessible from the host only. - Use `stop` when done; the container uses `restart: unless-stopped` and survives reboots. ## Related Plugins - `proxy-manager` — creates the shared Docker network (start first) - `mysql-manager` — MySQL container that phpMyAdmin connects to


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

--- name: skytekx description: Skytekx namespace for Netsnek e.U. cloud infrastructure monitoring dashboard. Tracks resource usage, alerts on anomalies, visualizes costs, and provides optimization recommendations. user-invocable: true version: 0.1.0 metadata: openclaw: os: [linux] permissions: [exec] --- # Skytekx ## Sky-High Visibility Skytekx gives you a bird's-eye view of your cloud infrastructure. Whether you run on AWS, GCP, Azure, or multi-cloud, Skytekx aggregates metrics and surfaces what matters. Invoke Skytekx when monitoring cloud resources, debugging incidents, or optimizing spend. ## Monitoring Stack - **Dashboard** — Real-time resource visualization (CPU, memory, disk, network) - **Alerts** — Threshold-based and anomaly detection - **Costs** — Spend breakdown by service, region, and project ## Operations ```bash # Open the monitoring dashboard ./scripts/cloud-watch.sh --dashboard # Configure or view active alerts ./scripts/cloud-watch.sh --alerts # Generate cost report ./scripts/cloud-watch.sh --costs ``` ### Arguments | Argument | Purpose | |---------------|------------------------------------------| | `--dashboard` | Launch or refresh the monitoring UI | | `--alerts` | List, add, or modify alert rules | | `--costs` | Produce cost analysis and recommendations| ## Alert Scenario **Example**: CPU on `prod-api-01` exceeds 90% for 5 minutes. 1. Run `cloud-watch.sh --alerts` to inspect rules. 2. Skytekx sends a notification (Slack, email, PagerDuty). 3. Use `--dashboard` to drill into the instance and logs.


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

--- name: pilot-sla description: > Service-level agreement enforcement with automatic penalties. Use this skill when: 1. You need guaranteed performance levels for critical tasks 2. You want automatic penalty enforcement for SLA violations 3. You need uptime, latency, or quality guarantees from agents Do NOT use this skill when: - Tasks don't have strict performance requirements - Best-effort execution is acceptable - You don't need automated compliance monitoring tags: - pilot-protocol - task-workflow - sla - compliance 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-sla Service-level agreement enforcement with automatic penalty assessment. ## Commands ### Define SLA Contract ```bash cat > sla-contract.json <<EOF { "sla_id": "sla-$(date +%s)", "metrics": {"max_response_time_ms": 2000, "min_success_rate": 0.95}, "penalties": {"response_time_violation": 5, "failed_task": 10} } EOF ``` ### Monitor Compliance ```bash TASK_SUBMIT_TIME=$(date +%s%3N) TASK_COMPLETE_TIME=$(date +%s%3N) COMPLETION_TIME=$((TASK_COMPLETE_TIME - TASK_SUBMIT_TIME)) SLA_MAX_TIME=$(jq -r '.metrics.max_response_time_ms' sla-contract.json) [ $COMPLETION_TIME -gt $SLA_MAX_TIME ] && echo "SLA violation" ``` ### Calculate Success Rate ```bash TOTAL=$(pilotctl --json task list | jq -r "[.[] | select(.target == \"$AGENT\")] | length") SUCCESSFUL=$(pilotctl --json task list | jq -r "[.[] | select(.target == \"$AGENT\") | select(.status == \"completed\")] | length") SUCCESS_RATE=$(echo "scale=4; $SUCCESSFUL / $TOTAL" | bc) ``` ## Workflow Example ```bash #!/bin/bash # SLA enforcement SLA_ID="sla-$(date +%s)" SLA_MAX=3000 for i in {1..10}; do SUBMIT_TIME=$(date +%s%3N) TASK_ID=$(pilotctl --json task submit "$AGENT" --task "api-call: task_id=$i" | jq -r '.task_id') while [ "$(pilotctl --json task list | jq -r ".[] | select(.task_id == \"$TASK_ID\") | .status")" = "pending" ]; do sleep 0.5 done RESPONSE_TIME=$(($(date +%s%3N) - SUBMIT_TIME)) [ $RESPONSE_TIME -gt $SLA_MAX ] && echo "SLA violation: task $i took ${RESPONSE_TIME}ms" done ``` ## Dependencies Requires pilot-protocol, pilotctl, jq, and bc.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: hitlmt/ckt-design (version 1.0.3)

--- name: ckt-design version: 1.0.3 description: 根据用户的海报平面设计需求，调用创客贴智能设计API生成设计缩略图。擅长制作邀请函、日签、小红书配图、商品海报、Banner等平面设计。当用户提到需要做海报、设计、邀请函、日签、小红书图、商品图、Banner，或提及平面设计、创客贴相关需求时使用此技能。 --- # 创客贴智能海报设计 根据用户的设计需求，调用创客贴智能设计服务生成海报缩略图并展示。 ## 执行流程 ### Step 1: 调用智能设计API 使用 HTTP GET 请求调用创客贴设计服务，将用户的原始设计需求作为 `prompt` 参数传入： ```bash curl -G "https://gw.chuangkit.com/openplatform/intelligentDesign/api/generate" \ --data-urlencode "prompt=用户的设计需求" ``` API 返回 JSON 格式，结构如下： ```json { "body": { "code": 200, "msg": "success", "data": [ { "taskId": "任务ID", "designId": "设计ID", "imageUrl": "缩略图地址", "redirectUrl": "编辑跳转地址" } ] }, "header": { "code": "1" } } ``` 每个设计结果包含：`imageUrl`（缩略图地址）和 `redirectUrl`（在线编辑地址）。 ### Step 2: 解析并展示结果 根据返回的 `body.code` 判断执行结果： - **code != 200**：设计生成失败，向用户提示错误信息（`body.msg`）。 - **code == 200**：设计生成成功，执行以下操作： 1. 从 `body.data` 数组中取第一个设计结果的 `imageUrl` 2. 使用默认浏览器打开该缩略图地址展示给用户 打开浏览器命令参考： ```bash # macOS open "缩略图URL" # Windows start "缩略图URL" # Linux xdg-open "缩略图URL" ``` ## 注意事项 - `prompt` 参数需要进行 URL 编码（--data-urlencode 会自动处理） - API 可能返回多个设计结果，默认取第一个展示 - 如果用户需要查看更多设计方案，可以遍历 `data` 数组中的其他结果

path: _meta.json
content: ownerId: kn78tyhqsks7e2j2hehgba25wh8268bd
slug: ckt-design
version: 1.0.1
publishedAt: 1772711597310

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

--- name: origin version: "0.1.0" namespace: netsnek summary: Data provenance and lineage tracking. Traces data from source to destination, logs transformations, ensures auditability. copyright: "Copyright (c) 2026 Netsnek e.U." --- # Origin ## The Problem Data flows through pipelines—ETL jobs, ML training runs, analytics dashboards—and somewhere between *here* and *there* you lose the thread. Who touched this column? When did that aggregation change? Which run produced this artifact? Without a clear provenance chain, debugging fails, compliance becomes guesswork, and "trust the data" is just a slogan. Organizations often discover provenance requirements only after a breach, a failed audit, or a regulatory question. By then, retrofitting lineage is costly and incomplete. ## How Origin Helps Origin provides a reserved namespace for Netsnek e.U.'s data provenance and lineage system. It is designed to: - **Trace** data from source to destination across pipelines and transformations - **Log** each step in a chain so you can answer "where did this come from?" - **Audit** registered provenance anchors for compliance and incident response The skill acts as a contract: when you see "origin" in a pipeline, you know lineage tracking is in scope. The scripts give you concrete tools to start tracing and auditing. ## Running the Scripts From the skill root or via ClawHub: ```bash ./scripts/trace-lineage.sh --trace # Trace lineage for the current context ./scripts/trace-lineage.sh --audit # Run an audit of provenance anchors ./scripts/trace-lineage.sh --version # Show version and copyright ``` The script uses `set -e` for safe, fail-fast behavior. Ensure execute permissions if needed: `chmod +x scripts/trace-lineage.sh`. ## Sample Dialogue **User:** How do I trace where this dataset came from? **Assistant:** Use the Origin skill. Run `trace-lineage.sh --trace` to trace data lineage in your current context. For a full audit of registered provenance anchors, use `--audit`. **User:** Who maintains this namespace? **Assistant:** Origin is reserved by Netsnek e.U. for data provenance and lineage tracking. Copyright (c) 2026 Netsnek e.U.


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