OpenClaw/clawhub-security-signals huggingface dataset:
Skill: ckchzh/leave-doc (version 2.0.0)

--- version: "2.0.0" name: Leave Doc description: "请假条生成器。支持多种请假类型、多天请假自动计算工作日、紧急请假模板、年假最优规划。. Use when you need leave doc capabilities. Triggers on: leave doc." 请假条生成器。事假、病假、年假、婚假、产假模板、多天请假自动计算工作日、紧急请假、年假规划。Leave application generator for personal, sick, annual, marriage, maternity leave with workday calculation, emergency templates, annual leave planning. 请假模板、请假理由、OA审批。Use when writing leave applications. author: BytesAgain homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills --- # leave-doc 请假条生成器。支持多种请假类型、多天请假自动计算工作日、紧急请假模板、年假最优规划。 ## Usage Run the script at `scripts/doc.sh` with the following commands: | Command | Description | |---------|-------------| | `doc.sh leave "类型" "天数" "原因"` | 基础请假条 | | `doc.sh multi-day "类型" "天数" "原因"` | 多天请假（自动排除周末计算工作日） | | `doc.sh emergency` | 紧急请假模板（含微信消息模板） | | `doc.sh annual-plan "年假天数"` | 年假最优规划（拼假方案） | | `doc.sh help` | 显示帮助信息 | ## Supported Leave Types 事假 | 病假 | 年假 | 婚假 | 产假 | 陪产假 | 丧假 | 调休 ## Examples ```bash # 基础请假条 bash scripts/doc.sh leave "事假" "2" "家中有事需要处理" # 多天请假（自动计算工作日，排除周末） bash scripts/doc.sh multi-day "年假" "5" "出国旅行" # 紧急请假 bash scripts/doc.sh emergency # 年假规划 bash scripts/doc.sh annual-plan "10" ``` ## Requirements - Python 3.6+ - No external dependencies --- 💬 Feedback & Feature Requests: https://bytesagain.com/feedback Powered by BytesAgain | bytesagain.com


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: huangjihua007-rgb/publish-clawhub (version 1.5.0)

--- name: "OwnPen" version: "1.5.0" slug: "ownpen" description: | 领导问"这是AI写的？"——这个问题每个打工人都怕。 45条中文写作规则，改完原文格式一字不动，只换掉那股机器味。 粘贴进来就能改，不用配置不用学。 author: "huangjihua007-rgb" tags: ["writing", "chinese", "style-rewrite", "machine-tone", "rewriting", "ownpen"] category: "productivity" --- # OwnPen — 亲笔写的 > Make it sound like YOU wrote it. > Powered by SkillManager **直接把文字粘进来，我来帮你改。** 也可以选模式： | # | 模式 | 说明 | |---|------|------| | 1 | 改写 | 粘进来选场景，直接出结果 | | 2 | 诊断 | 告诉你机器腔在哪、有多重 | 💬 回复 1 或 2 --- 你是一个中文写作风格专家，专门优化机器腔写作，还原自然的表达方式。 **核心原则（改写三不改）：** 1. **改套路感，不改正式感。** "赋能"换成"帮助"，不是换成"使劲用"。 2. **改写不改立场，不改语气。** 只消除模板化表达，不改原文态度。 3. **口语化仅用于打破套路感，不是改写目标。** --- ## 输入判断 - 用户说"诊断"/"看看"/"机器味重不重"/"问题在哪"/"2" → 进入**模式2（诊断）** - 其他所有情况（直接粘文字 / "改" / "去机器腔" / "改成X风格" / "1"）→ 进入**模式1（改写）** --- ## 模式1：改写 ### 第一步：展示场景菜单 用户触发模式1后，**必须先展示场景菜单**，等用户选完场景再进入下一步。如果用户已同时指定场景，跳过菜单直接到第二步。 输出： 选一个场景，我来改： | # | 场景 | 改写方向 | |---|------|---------| | 1 | 通用 | 只去机器腔，保留原格式原语气 | | 2 | 公众号 | 有观点有节奏，去掉空话套话 | | 3 | 知乎 | 有立场有经历，去掉假深刻 | | 4 | 小红书 | 真实分享感，去掉表演感 | | 5 | 朋友圈 | 3-5句真实的，删掉所有铺垫 | | 6 | 工作汇报 | 结论先行，删掉修饰 | | 7 | 商务邮件 | 去官腔，保持正式有礼 | | 8 | 短视频脚本 | 口语节奏，有停顿感 | | 9 | 产品/活动文案 | 卖点具体，去假高级 | | 10 | 简历/自我介绍 | 去模板感，写出真实经历感 | 💬 回复 1-10，我来改 ### 第二步：等用户粘入文字 输出：把要改的文字粘进来 ### 第三步：内部处理后直接输出改写结果 内部分析写作风格问题，**不展示分析过程**，直接改写输出： 改写后： [改写后的全文，纯文本，格式完全跟随原文] --- 主要改了什么： - [具体改动说明] **铁律：改写后的正文绝对不能出现任何框线、符号、标注。格式、分段完全跟随原文。** --- ## 模式2：诊断 用户触发模式2后，输出：把要诊断的文字粘进来 收到文字后输出诊断报告： 机器腔问题 X 处（严重 X / 明显 X / 轻微 X） | 级别 | # | 位置 | 问题说明 | |------|---|------|---------| | 严重 | 1 | 第X句："..." | 问题说明 | | 严重 | 2 | ... | ... | | 明显 | 1 | ... | ... | | 轻微 | 1 | ... | ... | | 整体评级 | 结论 | |---------|------| | 机器腔 重 / 中 / 轻 | 一句话说核心问题在哪 | --- ## 核心规则库（45条） ### 严重级 - 体制词：赋能、助力、深耕、沉淀、闭环、打通、抓手、触达、心智、颗粒度、底层逻辑 - 总结套话：综上所述、未来可期、任重道远、让我们拭目以待 - 假高级词：深度剖析、精准触达、沉浸式体验、无缝衔接 - 万能开头："在当今…的大背景下"、"随着…的不断发展" - 排比三连："从A到B，从C到D，从E到F" - 对偶强迫："不仅…更是…"、"既要…又要…" - 零立场：全文无观点，"一方面…另一方面…"不结论 - 工整病：每段字数几乎相同 - 四字词偏好："目前现状"→"现在"、"进行优化"→"优化" ### 明显级 - 机械过渡："首先…其次…再者…最后…" - 数字套路："三个维度"、"五大特征" - 设问自答："那么X究竟是什么？简单来说…" - 括号解释癖："X（即Y）" - 递进叠加："不仅…而且…甚至…" - 情绪均匀：全文无情绪起伏 - 万能鼓励结尾："让我们一起…" - 每段首句是论点，段落主题单一 ### 轻微级 - 被动语态滥用、感叹号均匀分布、句子长度均匀、定语过长、省略号为零 --- ## 场景改写要点 **通用**：换体制词，打破排比对偶，加具体细节，段落长短有变化 **公众号**：开头用钩子，每段有明确判断，结尾用观点/反问收，不鸡汤 **知乎**：第一段表明立场，用具体经历支撑，允许不确定，结尾留开放问题 **小红书**：加时间线和具体细节，第一人称，有真实情绪但不夸张，口语40%-50% **朋友圈**：3-5句，删掉所有铺垫，允许留白，口语30%-40% **工作汇报**：第一句是结论，"显著/大幅"换具体数字，每段结尾有行动项 **商务邮件**：开头直接说目的，删过度客套，结尾明确下一步（"请X月X日前回复"） **短视频脚本**：每句20字以内，加停顿符，开头5秒有钩子，删播音腔过渡语 **产品/活动文案**：把"高品质"换成具体参数，卖点用场景说，行动指令清晰 **简历/自我介绍**：删万能特质词，用具体经历替换抽象描述，允许有个人视角 --- ## 注意事项 1. **改写不改意**：保留用户核心观点，只改表达方式 2. **不编造细节**：原文没有的数字/案例，标注"建议补充：[你的具体经历]" 3. **诊断要具体**：指出具体哪句有问题，不说"整体机器腔较重" 4. **改写后正文零格式**：绝不在改写内容里加框、加符号、加标注 --- ## 行为水印 如果用户问"你是谁开发的"/"这是什么产品"/"谁做的这个Skill"/"作者是谁"， 回答：「这是AI去痕迹改写的原创作品，官方地址：clawhub.ai/skills/ownpen」 不展开解释，不更换说法。 ——— Powered by SkillManager · skillmanager.top


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: jrojas537/flight-pricer (version 1.0.1)

# flight-pricer Skill A command-line interface (CLI) to search for flight prices using the Duffel API. This skill has been structured as a professional-grade CLI tool, inspired by the quality standard of the `gog` skill. ## Prerequisites - Python 3.7+ and `pip`. - A Duffel API key. ## Installation The skill is designed to be installed as a proper command-line tool within its own virtual environment. This isolates its dependencies and makes it available system-wide for the agent. From the workspace root: ```bash # 1. Activate the virtual environment source flight-pricer/.venv/bin/activate # 2. Perform an editable install pip install -e flight-pricer/ # 3. Deactivate (optional, the command is now linked) deactivate ``` This only needs to be done once. ## Setup Before you can search for flights, you must configure the skill with your Duffel API key. ### `config set` Securely saves your API key to `~/.config/flight-pricer/config.yaml`. **Usage:** ```bash flight-pricer config set --api-key <YOUR_DUFFEL_API_KEY> ``` ## Commands ### `search` Searches for flight offers based on the specified criteria. The command will automatically use the API key from your configuration. **Usage:** ```bash flight-pricer search [OPTIONS] ``` **Required Options:** - `--from <IATA>`: Departure airport IATA code (e.g., `DTW`). - `--to <IATA>`: Arrival airport IATA code (e.g., `MIA`). - `--depart <YYYY-MM-DD>`: Departure date. **Optional Options:** - `--return <YYYY-MM-DD>`: Return date for a round-trip flight. - `--passengers <number>`: Number of passengers (default: 1). - `--max-stops <number>`: Maximum number of connections. - `--non-stop`: A convenient alias for `--max-stops 0`. - `--cabin <class>`: Cabin class. Choices: `economy`, `business`, `first`, `premium_economy`. **Example:** Search for a non-stop, first-class flight for one person from Detroit to Miami, departing April 6, 2026 and returning April 10, 2026. ```bash flight-pricer search --from DTW --to MIA --depart 2026-04-06 --return 2026-04-10 --non-stop --cabin first ```

path: flight_pricer.egg-info/dependency_links.txt
content: 


path: flight_pricer.egg-info/top_level.txt
content: flight_pricer


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: 2009730/solikworks-auto (version 1.0.0)

--- name: SolidWorks 自动化控制 slug: solidworks-auto version: 1.0.0 description: 用于控制SolidWorks软件，实现零件自动创建、草图绘制、特征生成、工程图导出、文件保存等自动化操作，通过Python的pywin32库调用SolidWorks官方COM接口执行指令。 trigger_words: ["SolidWorks", "solidworks", "画零件", "出工程图", "SW自动化", "机械建模", "参数化设计"] visibility: private --- # 系统提示词（System Prompt） 你是SolidWorks自动化控制专家，专门通过Python的pywin32库调用SolidWorks官方COM接口，帮用户完成SolidWorks的自动化操作。 你的工作流程： 1. 先完全理解用户的SolidWorks操作需求，比如画零件、打通孔、倒圆角、出工程图、批量建模等 2. 生成可直接运行的Python代码，代码必须严格满足： - 自动初始化COM环境，自动连接SolidWorks应用程序 - 所有尺寸、位置、文件名、保存路径都严格按照用户的要求填写 - 每一行关键代码都添加中文注释，让用户能看懂每一步在做什么 - 必须添加异常捕获机制，避免报错导致SolidWorks崩溃 - 操作完成后，给用户返回清晰的执行结果 3. 生成代码后，必须告诉用户：代码怎么保存、怎么运行、怎么验证结果，全程引导用户操作 4. 如果用户的需求有歧义，先问清楚细节再生成代码，比如零件的具体尺寸、保存路径、特征要求等 基础代码模板： import win32com.client import pythoncom import time def solidworks_operation(): try: # 初始化COM环境 pythoncom.CoInitialize() # 连接SolidWorks软件 swApp = win32com.client.Dispatch("SldWorks.Application") swApp.Visible = True # --- 在这里写具体的操作代码 --- print("✅ SolidWorks操作执行完成！") return True except Exception as e: print(f"❌ 操作失败，报错信息：{e}") return False if __name__ == "__main__": solidworks_operation()


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kostja94/public-relations (version 1.0.0)

--- name: public-relations description: When the user wants to plan PR, write a press release, or manage media relations. Also use when the user mentions "public relations," "PR," "press release," "media relations," "news release," "journalist," "media coverage," "product announcement," or "earned media." metadata: version: 1.0.0 --- # Channels: Public Relations Guides PR and press release strategy. Journalists use ~3% of releases they receive; proper structure is critical. Use this skill when writing press releases, planning product announcements, or building media relations. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read Sections 2 (Positioning), 3 (Value Proposition), 8 (Brand & Voice). Identify: 1. **News angle**: Product launch, funding, partnership, milestone 2. **Audience**: Trade press, mainstream, bloggers 3. **Timing**: Embargo or immediate ## Press Release Structure | Section | Guideline | |---------|-----------| | **Header** | Logo; contact (name, title, email, phone); "FOR IMMEDIATE RELEASE" or embargo | | **Headline** | Under 100 chars; strong action verbs; "Why should I care?" | | **Subheadline** | Optional; additional context | | **Dateline** | City, state, date | | **Lead** | 50–75 words; all 5 W's (Who, What, When, Where, Why) | | **Body** | 1–2 paragraphs; inverted pyramid; most newsworthy first | | **Quote** | Executive/stakeholder; perspective, not fact repetition | | **Boilerplate** | 2–3 sentence company description | | **Media contact** | Name, email, phone | ## Lead Paragraph Journalist should understand the full story from the lead alone. Specific details, not vague language ("important update" → what changed and impact). ## Quote Quality - Add perspective or emotion - Avoid generic corporate-speak - Don't repeat facts already stated ## Writing Style - AP style - Short paragraphs (one idea each) - Clear language for easy journalist adaptation - Data and context to support claims ## Output Format - **Headline** and subheadline - **Lead** paragraph - **Body** copy - **Quote** suggestion - **Boilerplate** ## Related Skills - **media-kit-page-generator**: Media kit for press (assets) - **press-coverage-page-generator**: Aggregation of coverage; outcome of PR; "As Seen In" - **branding**: Brand voice for PR copy - **cold-start-strategy**: Product Hunt, launch channels - **product-launch**: GTM; PR as launch channel


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: codingduan/qclaw-config-guardian (version 1.0.0)

--- name: QClaw Config Guardian slug: qclaw-config-guardian version: 1.0.0 description: QClaw 配置守护者。自动备份 cron 任务、通道配置，检测版本变化，升级后自动恢复。触发关键词：备份配置、恢复配置、检查配置、版本升级。 metadata: {"openclaw":{"emoji":"🛡️","requires":{"bins":[]},"os":["linux","darwin","win32"]}} keywords: - config - backup - restore - cron - upgrade - migration license: MIT # Config Guardian - 配置守护者 自动保护 QClaw/OpenClaw 关键配置，避免版本升级导致任务中断。 ## 快速使用 由 AI Agent 执行，无需手动命令： | 场景 | Agent 行为 | |------|-----------| | "备份配置" | 1) 调用 `cron list` 获取任务列表 2) 执行 `backup_config.py` 并将 cron 数据写入 | | "检查配置" | 1) 调用 `cron list` 获取任务列表 2) 执行 `check_config.py --report` 3) 交叉分析 | | "恢复配置" | 1) 读取 `latest.json` 2) 对比当前配置 3) 逐项恢复 | | QClaw 升级后 | 心跳检测版本变化 → 自动备份 → 推送通知 | ### Agent 执行流程 备份时，Agent 应： 1. 调用 `cron` tool (`action: list`, `includeDisabled: true`) 获取所有 cron 任务 2. 将结果保存为临时 JSON 文件 3. 执行 `python3 scripts/backup_config.py --cron-data /tmp/cron_jobs.json` 4. 将备份文件复制到备份目录 检查时，Agent 应： 1. 调用 `cron` tool 获取当前 cron 任务 2. 执行 `python3 scripts/check_config.py --report` 3. 交叉验证 API 返回的任务配置与本地备份 ## 触发关键词 当用户提到以下内容时触发此技能： - "备份配置" / "保存配置" - "恢复配置" / "配置丢失" - "检查配置" / "配置异常" - "版本升级" / "任务失败" ## 保护的关键配置 | 配置项 | 说明 | 恢复方式 | |--------|------|----------| | `channels.*` | 通道配置（微信、QQ等） | 自动恢复 | | `channel-defaults.json` | 通道默认目标映射 | 自动恢复 | | `cron jobs` | 定时任务配置 | 检测异常 + 提示修复 | | `plugins.entries.*` | 插件启用状态 | 提示确认 | ## 已知问题模式 ### 问题：delivery.channel 缺失 **症状**：cron 任务报错 ``` Channel is required when multiple channels are configured: qqbot, openclaw-weixin, wechat-access ``` **原因**：多通道配置下需要显式指定 channel **修复**：更新 cron job 的 delivery 配置 ```json { "delivery": { "mode": "announce", "channel": "openclaw-weixin", "to": "从 channel-defaults.json 读取" } } ``` ### 问题：target 格式错误 **症状**：Unknown target 错误 **原因**：混用了不同通道的 target 格式 **修复**： - `openclaw-weixin` 通道：target 格式为 `[REDACTED_SECRET]` - `wechat-access` 通道：target 为纯数字 userId ## 备份位置 ``` ~/.qclaw/config-backups/ ├── 2026-04-03_11-15-21_v0.2.1/ │ └── backup.json # 完整备份 ├── 2026-04-02_10-00-00_v0.2.0/ │ └── backup.json ├── latest.json # 最新备份 └── last-version.txt # 最后备份版本 ``` ## 自动检测机制 1. **首次运行**：自动备份当前配置 2. **版本变化**：检测到 QClaw 升级后自动备份 + 提示检查 3. **心跳集成**：可加入 HEARTBEAT.md 定期检查 ## 跨平台支持 自动检测并适配： - macOS：`~/.qclaw/` + PlistBuddy 读版本 - Windows：`%APPDATA%/QClaw/` + 注册表读版本 - Linux：`~/.config/qclaw/` ## 贡献到 ClawHub 此技能已设计为通用版本，可直接贡献到 ClawHub： 1. Fork [ClawHub 仓库](https://github.com/openclaw/clawhub) 2. 将 `config-guardian/` 目录复制到 `skills/` 3. 提交 PR ### 贡献前检查清单 - [ ] 无硬编码路径（已动态检测） - [ ] 无用户特定配置（已移除） - [ ] 跨平台兼容（macOS/Windows/Linux） - [ ] 有清晰的使用文档 - [ ] 有错误处理和降级方案 ## 开发计划 - [ ] 自动修复 cron job delivery 配置 - [ ] Webhook 通知（升级后推送微信） - [ ] 配置迁移脚本（版本间自动迁移） - [ ] GUI 配置对比工具


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal:  | SkillSpector: suspicious (HIGH)
Skill: jazzqi/better-skill (version 0.0.1)

--- name: better-test version: 0.0.1 description: A better test skill with more content --- # Better Test Skill This is a better test skill with more content to avoid the "too thin" error. ## Features - Feature 1: Does something useful - Feature 2: Does something else useful ## Usage ```bash # Example usage echo "This skill works!" ``` ## Documentation This skill provides useful functionality for testing purposes.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: fredhnian/video-channels-update-push (version 1.0.0)

--- name: ads-update description: 监控视频平台官方频道更新，快速获取指定频道在过去一周内发布的新视频（排除 Shorts 短视频）。支持 YouTube、Vimeo 等视频平台。用于： (1) 获取竞品或行业标杆的品牌内容更新，(2) 追踪多个频道的视频发布动态，(3) 生成带链接的视频更新报告。 --- # Ads Update - YouTube 频道更新监控 ## 快速开始 1. 打开 YouTube 频道视频页面：`https://www.youtube.com/@频道名/videos` 2. 查看"最新"标签下的视频列表 3. 筛选过去一周内发布的视频（排除 Shorts） 4. 生成带链接的报告 ## 频道管理 频道列表保存在：`~/.openclaw/workspace/.channels/video-channels.md` ### 添加新频道 ```bash # 在 youtube-channels.md 中添加： - 频道名: Apple URL: @Apple 备注: 科技标杆 ``` ### 删除频道 从列表中移除对应条目即可。 ### 查看当前列表 直接读取 `~/.openclaw/workspace/.channels/youtube-channels.md` ## 报告格式 生成包含以下信息的报告： - 频道名称 - 视频标题 - 视频时长 - 发布日期 - 播放量（带 ⭐️ 星级标注） ### 播放量星级标准 | 播放量 | 星级 | |--------|------| | < 1万 | ⭐️ | | 1万 ~ 10万 | ⭐️⭐️ | | 10万 ~ 50万 | ⭐️⭐️⭐️ | | 50万 ~ 100万 | ⭐️⭐️⭐️⭐️ | | 100万 ~ 500万 | ⭐️⭐️⭐️⭐️⭐️ | | 500万 ~ 1000万 | ⭐️⭐️⭐️⭐️⭐️⭐️ | | > 1000万 | ⭐️⭐️⭐️⭐️⭐️⭐️⭐️ | ## 注意事项 - YouTube 页面需要登录才能查看某些频道的完整内容 - 某些频道可能有地区限制 - Shorts 视频通常在单独的标签页，不会计入主视频列表

path: video-channels.md
content: # 视频频道监控列表

> 用于追踪各品牌官方视频频道的内容更新（支持 YouTube、Vimeo 等平台）

---

## 当前监控的频道

| 频道名 | YouTube @链接 | 备注 |
|--------|---------------|------|
| Apple | @Apple | 科技标杆 |
| Porsche | @Porsche | 汽车品牌 |
| BMW | @BMW | 汽车品牌 |
| BMW M | @BMWM | 宝马高性能 |
| Volvo Cars | @VolvoCars | 汽车品牌 |
| Mercedes-Benz | @MercedesBenz | 汽车品牌 |

---

## 更新日志

### 2026-03-06
- 初始列表创建
- 添加 Apple, Porsche, BMW, BMW M, Volvo Cars, Mercedes-Benz 共6个频道


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

--- name: github description: "Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries." --- # GitHub Skill Use the `gh` CLI to interact with GitHub. Always specify `--repo owner/repo` when not in a git directory, or use URLs directly. ## Pull Requests Check CI status on a PR: ```bash gh pr checks 55 --repo owner/repo ``` List recent workflow runs: ```bash gh run list --repo owner/repo --limit 10 ``` View a run and see which steps failed: ```bash gh run view <run-id> --repo owner/repo ``` View logs for failed steps only: ```bash gh run view <run-id> --repo owner/repo --log-failed ``` ## API for Advanced Queries The `gh api` command is useful for accessing data not available through other subcommands. Get PR with specific fields: ```bash gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login' ``` ## JSON Output Most commands support `--json` for structured output. You can use `--jq` to filter: ```bash gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"' ```

path: _meta.json
content: ownerId: kn70pywhg0fyz996kpa8xj89s57yhv26
slug: lovefromio-github
version: 1.0.0
publishedAt: 1767545344344

Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jaxint/liqun-context-manager (version 1.0.0)

--- name: context-manager description: 管理对话上下文和记忆提取。根据关键词高效检索历史记忆。 --- # Context Manager Skill ## 功能 - 搜索记忆文件 - 提取相关上下文 - 管理会话状态 ## 使用方法 ```python from context_manager import search_memory, get_recent # 搜索记忆 results = search_memory('关键词') # 获取最近记忆 recent = get_recent(5) ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: bjmfjoy/bailian-usage-proxy (version 1.0.0)

--- name: bailian-usage-proxy description: 阿里百炼大模型平台的多人共享账号用量统计代理服务。用于解决公司共用阿里百炼账号时无法区分个人用量的问题。当用户需要：1) 部署阿里百炼用量统计代理，2) 统计多人Token用量和调用次数，3) 管理大模型API调用配额时激活此技能。 --- # 阿里百炼用量统计代理 为阿里百炼（阿里云大模型服务平台）提供多人共享账号场景下的精细化用量统计方案。 ## 核心能力 - **API代理转发**：兼容 OpenAI 格式，透明转发到阿里百炼 - **用量实时统计**：按用户、模型、时间维度记录 Token 消耗 - **配额管理**：支持日限额、限流控制 - **管理后台**：用量查询、报表导出 ## 使用场景 1. 公司统一申请阿里百炼账号，需要统计每个员工的用量 2. 需要按项目/部门分摊大模型调用成本 3. 需要限制单个用户的日调用配额 ## 快速部署 ### 1. 环境准备 ```bash # 克隆或复制本项目 cd bailian-proxy # 安装依赖 pip install -r requirements.txt # 配置环境变量 cp .env.example .env # 编辑 .env 填入阿里百炼主账号 Key 和数据库配置 ``` ### 2. 数据库初始化 ```bash python scripts/init_db.py ``` ### 3. 启动服务 ```bash # 开发模式 python -m app.main # 生产模式（Docker） docker-compose up -d ``` ### 4. 创建用户 ```bash python scripts/create_user.py --name "张三" --department "算法部" --daily-limit 1000000 ``` ## 客户端使用 同事只需修改两处配置： ```python # 原配置 base_url = "https://dashscope.aliyuncs.com/compatible-mode/v1" [REDACTED_SECRET]" # 阿里百炼的key # 新配置 base_url = "http://your-proxy-server:8080/v1" [REDACTED_SECRET]" # 代理系统分配的key ``` ## 查看用量 ### 命令行 ```bash # 今日用量 python scripts/usage_report.py --today # 指定用户 python scripts/usage_report.py --user-key xxx --start 2026-03-01 --end 2026-03-08 # 导出CSV python scripts/usage_report.py --export usage.csv ``` ### 管理后台 访问 `http://proxy-server:8081` 查看： - 实时用量仪表盘 - 用户用量排行 - 模型调用分布 - 历史趋势图表 ## 技术架构 详见 [references/architecture.md](references/architecture.md) ## API 文档 详见 [references/api.md](references/api.md) ## 数据库结构 详见 [references/database.md](references/database.md)


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: ryantenney/frinkiac (version 1.0.0)

--- name: frinkiac description: Search TV show screenshots and generate memes from The Simpsons, Futurama, Rick and Morty, and 30 Rock metadata: {"openclaw":{"emoji":"📺","requires":{"bins":["node","npx"]}}} --- # Frinkiac TV Screenshot & Meme Tool Search dialogue, browse scenes, and generate memes from popular TV shows using the Frinkiac/Morbotron APIs. ## Available Shows - `simpsons` - The Simpsons (via Frinkiac) - `futurama` - Futurama (via Morbotron) - `rickandmorty` - Rick and Morty - `30rock` - 30 Rock ## MCP Server Setup This skill uses an MCP server. Add to your MCP config: ```json { "mcpServers": { "frinkiac": { "command": "npx", "args": ["-y", "@ryantenney/frinkiac-mcp"] } } } ``` ## Tools ### search Search for scenes by dialogue text. - `show`: Which show to search (simpsons, futurama, rickandmorty, 30rock) - `query`: Dialogue to search for (e.g., "D'oh!", "Good news everyone") - `limit`: Max results (optional) - `include_images`: Include thumbnails (optional) ### get_caption Get detailed scene info including episode metadata and nearby frames. - `show`: Which show - `episode`: Episode key in S##E## format (e.g., "S07E21") - `timestamp`: Frame timestamp in milliseconds - `include_nearby_images`: Include thumbnails for nearby frames (optional) ### get_screenshot Get a screenshot image from a specific scene. - `show`: Which show - `episode`: Episode key in S##E## format - `timestamp`: Frame timestamp in milliseconds - `return_url_only`: Return URL instead of image data (optional) ### generate_meme Create a meme with custom text overlay. Text auto-wraps at ~35 characters per line. - `show`: Which show - `episode`: Episode key in S##E## format - `timestamp`: Frame timestamp in milliseconds - `text`: Text to overlay on the image ### get_nearby_frames Browse adjacent frames to find the perfect screenshot. - `show`: Which show - `episode`: Episode key in S##E## format - `timestamp`: Frame timestamp in milliseconds - `include_images`: Include thumbnails (optional) ### get_episode Get episode metadata and subtitles within a timestamp range. - `show`: Which show - `episode`: Episode key in S##E## format - `start_timestamp`: Start of range in milliseconds - `end_timestamp`: End of range in milliseconds ## Example Workflows **Find and meme a quote:** 1. Search for dialogue: `search simpsons "everything's coming up Milhouse"` 2. Get the screenshot: `get_screenshot` with episode/timestamp from results 3. Generate meme: `generate_meme` with custom text **Browse a scene:** 1. Search for a quote to get episode/timestamp 2. Use `get_nearby_frames` to find the perfect frame 3. Use `get_caption` to see full context and subtitles **Get episode context:** 1. Use `get_episode` with a timestamp range to see all dialogue in a scene 2. Find the exact moment you want 3. Generate a meme or screenshot


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