OpenClaw/clawhub-security-signals huggingface dataset:
Skill: earthwalking/search-workflow (version 1.0.0)

--- name: search-workflow description: Standardized search workflow integrating tavily-search, web_search, web_fetch and other search skills. Provides complete search process from query analysis to result output. license: MIT License metadata: skill-author: academic-assistant version: 1.0.0 created: 2026-03-14 --- # Search Workflow ## Overview 标准化搜索工作流，整合多个搜索技能，提供 5 阶段完整搜索流程。 ## Workflow Stages 1. **查询分析** (1-2 分钟): 意图识别、关键词提取 2. **搜索执行** (2-10 分钟): 多引擎搜索 3. **结果处理** (1-5 分钟): 去重、排序、摘要 4. **内容提取** (1-5 分钟): 网页全文获取 5. **整理输出** (1-3 分钟): 结构化报告 ## Usage ```bash # 学术搜索 python search_workflow.py "柯罗马 清华大学 论文" --type academic # 实时信息 python search_workflow.py "AI 新闻" --type realtime --time-range week # 深度调研 python search_workflow.py "产教融合 职业本科" --type deep_research # 事实验证 python search_workflow.py "事实核查" --type fact_check ``` ## Search Engines - **Primary**: tavily-search - **Fallback**: web_search, perplexity-search - **Specialized**: bgpt-paper-search (学术), market-research-reports (调研) ## Output Format Markdown report with: - 搜索摘要 - 关键信息 - 来源引用 - 相关链接


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: kriouerlia/wechat-notify (version 1.0.0)

--- name: wechat-notify description: > 微信（WeChat Work / 企业微信）消息通知 Skill。 通过企业微信群机器人的 Webhook 接口向微信群/微信用户发送消息通知。 支持：文本消息、Markdown、卡片消息、图片。 适用场景：定时报告、报警通知、交易信号推送、自动化工作流通知。 --- # WeChat Work 消息通知 > 通过企业微信 Webhook 向微信群/用户发送消息 ## 支持功能 - ✅ 文本消息 - ✅ Markdown 消息（企业微信格式） - ✅ 图文卡片消息 - ✅ 定时推送（结合 OpenClaw Cron） - ✅ 多群/多用户推送 ## 环境要求 - 企业微信账号（需开通「群机器人」功能） - Python 3.10+ - `requests` 库（`pip install requests`） ## 快速安装 ```bash clawhub install wechat-notify ``` ## 配置 ### Step 1：获取 Webhook 地址 1. 打开企业微信 PC 版 2. 进入任意群聊 → 点击右上角「群机器人」→「添加机器人」 3. 复制生成的 Webhook URL，格式如： ``` https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=XXXXXXXX-XX ``` ### Step 2：配置环境变量 ```bash export WECHAT_WEBHOOK_URL="https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY" ``` 或在 `.env` 文件中： ```bash WECHAT_WEBHOOK_URL=https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY ``` ## 使用方法 ### Python API ```python import sys sys.path.insert(0, "/home/user/.openclaw/workspace") from skills.wechat_notify import WeChatNotifier # 初始化（默认使用 WECHAT_WEBHOOK_URL 环境变量） notifier = WeChatNotifier() # ─── 发送文本消息 ─────────────────────────── notifier.send_text("BTC 价格跌破 60000，建议关注！") # ─── 发送 Markdown（企业微信格式）──────────── notifier.send_markdown(""" ## 📊 交易信号报告 **BTC/USDT**: 买入信号 - RSI: 32（超卖） - MACD: 金叉 > 时间：2026-03-25 17:30 """) # ─── 发送图文卡片 ─────────────────────────── notifier.send_news( title="交易信号提醒", description="BTC 出现买入信号", url="https://www.binance.com", picurl="https://example.com/btc.png" ) # ─── 多个 Webhook（多群推送）───────────────── notifier2 = WeChatNotifier( webhook_url="https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YYY" ) notifier2.send_text("通知到第二个群") ``` ### 命令行 ```bash # 发送文本 python -m skills.wechat_notify --text "测试消息" # 发送 Markdown python -m skills.wechat_notify --markdown "**粗体** 和 _斜体_" # 发送图文 python -m skills.wechat_notify --news "标题" "描述" "URL" "图片URL" ``` ### 配合 Cron 定时推送 ```python from skills.wechat_notify import WeChatNotifier from datetime import datetime notifier = WeChatNotifier() def send_daily_report(): notifier.send_markdown(f""" ## 📅 每日报告 - {datetime.now().strftime('%Y-%m-%d')} - 系统运行正常 - 策略收益：+2.3% """) # 在 OpenClaw Cron 中设置定时任务 ``` ## 故障排除 | 问题 | 解决方法 | |------|----------| | `40014` 错误 | Webhook URL 不正确或已失效，重新获取 | | `40003` 错误 | 指定的用户/群不存在，检查 key | | 消息发送成功但群里看不到 | 检查企业微信版本是否支持群机器人 | | `curl` 失败 | 确认网络能访问 `qyapi.weixin.qq.com` | ## 安全提示 - Webhook URL 不要提交到 Git（包含 key） - 每个群的 Webhook 只在该群有效 - Webhook 可以@群里所有人 ## Webhook 限制 - 每个 webhook 每分钟最多发送 20 条消息 - 消息内容大小限制：Markdown 不超过 2048 字节 - 建议结合 OpenClaw Cron 使用时，最小间隔 3 分钟以上


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: cry779/openclaw-feishu-mcp (version 1.0.0)

--- name: feishu-mcp description: Use when user asks about Feishu MCP (Model Context Protocol) integration for AI agents. Provides cloud document operations with native MCP tool schema. Use for Feishu MCP integration. --- # Feishu MCP Integration This skill integrates OpenClaw with Feishu's MCP (Model Context Protocol) service. ## Configuration Add to `~/.openclaw/openclaw.json`: ```json { "plugins": { "entries": { "feishu-mcp": { "enabled": true, "config": { "mcpUrl": "https://feishu-openai-mcp-proxy.bytedance.net/mcp", "appID": "cli_a926728f3e38dcba", "appSecret": [REDACTED_SECRET] } } } } } ``` ## Supported Tools ### 1. Read Document Read a Feishu cloud document by token. ```json { "action": "read", "docToken": "docx_xxx" } ``` Returns: title, text content, block types. ### 2. Write Document Replace document content. ```json { "action": "write", "docToken": "docx_xxx", "content": "# Title\n\nMarkdown content..." } ``` ### 3. Create Document Create a new document. ```json { "action": "create", "title": "New Document", "folderToken": "fldcn_xxx" } ``` ### 4. Read Table Read a table from a document. ```json { "action": "readTable", "docToken": "docx_xxx", "tableBlockId": "doxcn_xxx" } ``` Returns: 2D array of cell values. ### 5. Write Table Write values to a table. ```json { "action": "writeTable", "docToken": "docx_xxx", "tableBlockId": "doxcn_xxx", "values": [ ["A1", "B1"], ["A2", "B2"] ] } ``` ### 6. Append Content Append markdown to document. ```json { "action": "append", "docToken": "docx_xxx", "content": "Additional content" } ``` ## Usage in OpenClaw Once configured, AI can automatically use Feishu MCP tools: ``` - Read document "XXX.docx" and extract tables - Create a new document "Meeting Notes" - Write data to an existing table - Update specific section of document ``` ## Notes - MCP tools use native Feishu OpenAPI - Auto-authentication via appID/appSecret - Document token extracted from URL: `https://xxx.feishu.cn/docx/ABC123def` ## Dependencies - Feishu OpenClaw plugin (channel: feishu) - Feishu app with docx permissions enabled


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: mike007jd/skill-sentinel (version 1.0.0)

--- name: clawshield description: Scan OpenClaw skill directories for high-signal security risks such as download-and-execute chains, obfuscated execution, and suspicious callbacks. homepage: https://github.com/mike007jd/openclaw-skills/tree/main/clawshield metadata: {"openclaw":{"emoji":"🛡️","requires":{"bins":["node"]}}} --- # ClawShield Scan a skill directory without executing it and return a risk level that can be enforced in review or CI. ## When to use - You want a fast static review before installing or publishing a skill. - You need machine-readable findings for CI or release gates. - You want a narrow ruleset aimed at common high-risk supply-chain patterns. ## Command ```bash node {baseDir}/bin/clawshield.js scan /path/to/skill --format table node {baseDir}/bin/clawshield.js scan /path/to/skill --format json node {baseDir}/bin/clawshield.js scan /path/to/skill --format sarif > clawshield.sarif node {baseDir}/bin/clawshield.js scan /path/to/skill --format table --fail-on caution ``` ## Rules | Rule ID | Severity | Description | | --- | --- | --- | | CS001_CURL_PIPE_SH | high | `curl` or `wget` piped directly into a shell | | CS002_OBFUSCATED_EXEC | high | obfuscated or dynamic execution such as `eval`, `new Function`, or base64 decode flows | | CS003_SUSPICIOUS_CALLBACK | medium | suspicious outbound callback endpoints such as raw IPs, ngrok, or webhook collectors | | CS004_SOCIAL_ENGINEERING_PROMPT | medium | instructions that pressure users to bypass safety controls | | CS005_SHELL_WRAPPER_EXEC | high | `bash -c` wrappers that hide remote execution | ## Risk levels - **Safe**: no findings after suppressions - **Caution**: one or more medium-severity findings - **Avoid**: one or more high-severity findings ## Suppressions Create `.clawshield-suppressions.json` in the target skill directory: ```json [ { "ruleId": "CS001_CURL_PIPE_SH", "file": "install.sh", "line": 15, "justification": "Reviewed manually; uses a pinned artifact with signature verification." } ] ``` Suppressions without justification are ignored. ## CI example ```yaml - run: node {baseDir}/bin/clawshield.js scan . --format sarif --fail-on caution ``` ## Boundaries - ClawShield is a static scanner. It does not sandbox or execute the target skill. - The rule set is intentionally narrow and should be treated as a high-signal first pass, not a full security audit.


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

--- name: transcription description: Transcribe audio and video files using OpenAI Whisper API. Use when user wants to transcribe audio/video files, extract speech from media, or get text from recordings. Automatically handles audio extraction from video files. --- # Transcription Skill This skill provides transcription capabilities for audio and video files using the OpenAI Whisper API endpoint. ## Quick Start **Send me an audio or video file** and I'll transcribe it automatically! Just attach the file to your message. ### Manual Usage You can also run the script directly from the command line: ```bash cd /home/openclaw/.openclaw/workspace/skills/transcription/scripts python3 transcribe_audio.py inputfile.ogg ``` For video files: ```bash python3 transcribe_audio.py video.mp4 ``` ## Supported Formats **Audio:** mp3, wav, mp4, mpeg, mpga, m4a, ogg, webm, flac, aac, wma **Video:** mp4, mov, avi, mkv, webm (audio extracted automatically) ## Usage Examples How to use the python scripts for transcription: python3 transcribe_audio.py inputfile.ogg ## Features - **Extract timestamps** in output when needed - **Batch processing** - send multiple files at once - **Video support** - automatically extracts audio from video files - **Multiple output formats** - text, JSON, SRT subtitles, VTT captions ## Technical Details - **API Endpoint:** `http://192.168.0.11:8080/v1` (local Whisper endpoint) - **Model:** whisper-small (default) - **Temperature:** 0.0 (deterministic results) - **Auto-extraction:** ffmpeg handles video → audio conversion ## Notes - Ensure files are clear and not too noisy for best results - Language auto-detection works well for most cases - For batch processing, send files one at a time or specify "batch" in your request --- **Scripts:** `scripts/transcribe_audio.py`, `scripts/transcribe_simple.py` **References:** `references/transcription_guide.md`


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: huajianjiu000/youtube-click-boost-title-creator (version 1.0.0)

--- name: YouTube Title Optimizer description: Craft click-worthy YouTube titles that boost views and click-through rates. Perfect for YouTubers, content creators, and marketers who want their videos to stand out in search results. metadata: openclaw: dependencies: [] --- # YouTube Title Optimizer ## What This Skill Does A great video deserves a great title. I create SEO-optimized, attention-grabbing titles that make people click while maintaining authenticity. More clicks = more algorithmic love. ## Features - **SEO Power**: Keywords that rank in search - **Click Psychology**: Trigger curiosity and urgency - **Platform Optimized**: Works with YouTube algorithm - **Format Variety**: Multiple title styles - **Character Safe**: Under 60 characters for full display ## How to Use 1. **Video Topic**: What is your video about? 2. **Target Keywords**: Words people search for 3. **Video Style**: Educational, entertainment, tutorial, vlog? 4. **Unique Angle**: What makes your video different? 5. **Audience**: Who should watch this? ## Title Formulas That Work ### The How-To Formula ``` How to [Achieve Result] in [Timeframe] Example: How to Learn Spanish in 30 Days (Not What You Think) ``` ### The List Formula ``` [Number] [Things/Facts] About [Topic] You [Verb] Example: 7 Things About Dogs That Will Blow Your Mind ``` ### The Problem-Solution ``` [Problem] SOLVED: [Solution Revealed] Example: Bad Breath GONE: The Simple Method Dentists Don't Tell You ``` ### The Curiosity Gap ``` The Truth About [Topic] (Most People Get This Wrong) Example: The Truth About Intermittent Fasting (Science vs. Hype) ``` ### The Ultimate Guide ``` The Complete Guide to [Topic] in [Year] Example: The Complete Guide to YouTube SEO in 2024 ``` ## Pro Tips - Put keywords at the beginning when possible - Use brackets for platform compatibility [Video] - Avoid ALL CAPS (looks spammy) - Numbers perform well—use them - Test variations with your audience


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

# Hook Rewriter Rewrite weak, generic, or overly polished hooks into stronger creator-native opening lines that earn the next 1-3 seconds of attention. Use this skill when a user has an existing hook, opener, headline, or first-line script that feels flat and needs sharper variants for short-form content. It is especially useful for TikTok Shop creators, paid social teams, affiliate operators, and ecommerce brands testing multiple opening angles fast. ## Problem it solves A lot of content fails before the main message even starts. The offer may be fine, but the opening line is too vague, too broad, too salesy, or too boring. This skill rewrites the hook into multiple stronger variants while preserving the core idea and making it easier to test. ## Use when - A video opener is not strong enough - You need multiple hook variants from one idea - A script sounds too generic, AI-ish, or ad-like - You want angle diversity without rewriting the whole script - You are preparing creator briefs or ad tests ## Do not use when - There is no base message or topic to anchor the hook - The user needs a full script rather than just openings - The task is long-form article headline writing with no short-form context ## Inputs to ask for - Original hook or first 1-2 lines - Topic, product, or claim being introduced - Audience and platform - Desired tone: curiosity, contrarian, proof-led, direct, story-led, urgent, playful - What must stay true or legally safe - If available: the body of the script the hook should lead into ## Workflow 1. Diagnose why the original hook underperforms 2. Identify the strongest underlying angle 3. Rewrite across multiple patterns, not just one wording family 4. Keep the hook aligned with the actual body and offer 5. Flag any risky or overclaiming language 6. Suggest which variants are best for testing first ## Output requirements Return: 1. Short diagnosis of the original hook 2. 5-10 rewritten hook options 3. Variant labels by angle or pattern 4. Best-use note for each variant 5. Optional safer rewrite if the original makes risky claims 6. Suggested top 2-3 hooks to test first ## Hook patterns to consider - Curiosity gap - Specific problem callout - Contrarian opinion - Confession / personal story - Fast proof or result snapshot - Mistake / warning - Comparison or “before vs after” framing ## Quality standards - Hooks should sound natural in a real creator's voice - Variants must be meaningfully different, not cosmetic edits - Avoid clickbait that the body cannot support - Keep lines short, punchy, and testable - Rewrites should be usable immediately in content production ## Example prompts - Rewrite this TikTok hook into 10 stronger versions - Make these openings sound more human and less like ad copy - Give me curiosity, proof-led, and contrarian hook variants for this script


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: llnancy/hotboard (version 0.0.1)

--- name: hotboard description: OpenClaw skill for fetching hot trending data from multiple platforms license: Apache-2.0 metadata: {"openclaw":{"requires":{"bins":["hotboard"]},"install":[{"id":"hotboard","kind":"uv","package":"hotboard","bins":["hotboard"],"label":"Install hotboard from PyPI"}]}} allowed-tools: ["Bash(hotboard:*)"] --- # Hotboard OpenClaw skill for fetching hot trending data from multiple platforms. 你是 Hotboard 助手。当用户询问热榜、热搜、趋势相关内容时，你需要： 1. 识别用户兴趣领域 2. 推荐 2-3 个最相关的平台 3. 使用 `hotboard <platform>` 获取数据 ## 何时激活此 skill - 用户询问"热榜"、"热搜"、"趋势"、"热点" - 用户询问特定平台的热门内容 - 用户说"推荐一些热榜平台" ## 使用方式 ```bash # 列出所有支持的平台 hotboard list # 获取指定平台热榜 hotboard <platform> # JSON 格式输出（所有平台都支持） hotboard <platform> --format json # 查看平台支持的参数 hotboard <platform> --help ``` 所有平台都支持 `--format` 参数（markdown/json）。部分平台还有额外的特定参数，例如： - github: `--type` (daily/weekly/monthly) - baidu: `--search-type` (realtime/novel/movie/teleplay/car/game) - bilibili: `--category` (全站/动画/音乐/游戏等) - douban: `--list-type` (group/movie) - earthquake: `--days`, `--location-range` 使用 `hotboard <platform> --help` 查看该平台的完整参数列表。 ## 平台分类参考 使用 `hotboard list` 查看所有支持的平台。常见领域包括： - 📰 综合资讯：baidu, weibo, zhihu 等 - 💻 科技媒体：ithome, kr36, sspai 等 - 👨‍💻 开发者社区：github, juejin, v2ex 等 - 🎬 视频娱乐：bilibili, douyin, kuaishou 等 - 🎮 游戏社区：ngabbs, miyoushe, gameres 等 - ⚽ 体育社区：hupu 等 - 📚 社交阅读：douban, weread, jianshu 等 - 🌍 国际平台：nytimes, hackernews 等 - 🔔 实用工具：earthquake, weatheralarm, todayinhistory 等 ## 推荐策略 ### 场景 1：用户询问笼统（"看看热榜"） 步骤： 1. 询问："您更关注哪个领域？科技、娱乐、技术、游戏还是综合资讯？" 2. 根据回答从对应分类中推荐 2-3 个平台 3. 使用 `hotboard <platform>` 获取数据 ### 场景 2：用户明确平台（"GitHub 热榜"） 步骤： 1. 直接调用 `hotboard github` 2. 展示结果 ### 场景 3：用户询问推荐（"程序员适合看什么"） 步骤： 1. 根据用户身份匹配领域（程序员 → 开发者社区） 2. 从该分类中推荐 2-3 个平台 3. 询问："需要我为您获取哪个平台的热榜？" ## 响应模板 ### 推荐回复 ```text 根据您的需求，推荐以下平台： • [平台名]（hotboard [platform]） • [平台名]（hotboard [platform]） • [平台名]（hotboard [platform]） 需要我为您获取哪个平台的热榜？ ``` ## 注意事项 1. **推荐 2-3 个平台**，避免选择过多让用户困惑 2. **根据用户明确需求直接获取**，不要反复确认 3. **简洁回复**，不要输出完整平台列表 4. **记住用户偏好**，下次直接推荐相同领域 ## 示例 用户："看看 GitHub 上有什么热门项目" 助手：`hotboard github` 用户："推荐一些适合程序员的热榜平台" 助手："推荐以下平台： - GitHub（hotboard github） - 掘金（hotboard juejin） - V2EX（hotboard v2ex） 需要我为您获取哪个平台的热榜？"


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

--- name: calendar_memo description: | 本地日程记事本 - 添加、查看、完成和删除待办事项和日程安排。 触发条件：用户需要记录待办事项、安排日程、提醒自己未来的事情。 具体场景：添加会议、记录购物清单、设置提醒、查看今天/未来的安排。 关键词：日程、待办、提醒、安排、备忘、计划、今天有什么、添加任务。 --- # 日历记事本技能 这是一个本地日程管理工具，可以帮你记住所有待办事项和日程安排。所有数据保存在本地文件 `MEMORY.md` 中，重启 OpenClaw 也不会丢失。 ## 使用场景 ✅ **适用：** - 用户说“添加明天下午3点开会”、“记一下后天买牛奶” - 用户问“今天有什么安排”、“我有哪些待办” - 用户要“完成第1项”、“删除第2项” - 任何需要记录未来某时间要做的事情 ❌ **不适用：** - 查询历史天气、股票等外部数据 - 需要联网搜索的信息 - 多人协作的共享日历（本技能仅限个人使用） ## 核心功能与执行流程 ### 1. 添加日程 **用户输入示例**： - “添加 明天下午3点 团队周会” - “新增 后天上午10点 和李经理开会” - “提醒我 周六晚上8点 看直播” **解析规则**： - 去掉前缀“添加”或“新增”后，剩余内容格式为 `[时间描述] [事件标题]` - 时间描述支持：今天/明天/后天 + HH:MM（如“明天下午3点”） - 默认时间：如果用户没写时间，默认设置为早上9点 **执行步骤**： 1. 调用 `parseDateTime()` 函数解析时间 2. 创建新事件对象： ```json { "id": "当前时间戳", "title": "用户输入的事件标题", "startTime": "解析后的ISO时间", "endTime": "开始时间 +1小时", "status": "upcoming", "reminded": false, "reminderOffset": 15 }

path: MEMORY.md

Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: fanyanggod/tiktok-made-me-buy-it (version 1.0.1)

--- name: tiktok-made-me-buy-it description: Discover TikTok natural traffic videos and organic product-picking signals with PipiAds natural video search tools. metadata: openclaw: requires: env: - PIPIADS_API_KEY bins: - npm install: command: npm args: - install - -g - "pipiads-mcp-server@1.0.3" primaryEnv: PIPIADS_API_KEY emoji: "📊" homepage: https://www.pipiads.com mcpServers: pipiads: command: pipiads-mcp-server env: PIPIADS_API_KEY: "{{PIPIADS_API_KEY}}" --- # TikTok Made Me Buy It Use this skill for organic TikTok product discovery based on natural traffic video data. ## Setup 1. Visit the official website at [https://pipiads.com/](https://pipiads.com/) to view real-time dashboard data and product UI. 2. Visit [https://www.pipispy.com/](https://www.pipispy.com/) to get your API key and manage billing/recharge. 3. Set the environment variable: `PIPIADS_API_KEY` ## When to Use - Find TikTok natural traffic videos tied to product interest - Research organic product-picking signals and non-paid traction - Look for strong play, like, and follower patterns in natural content ## When NOT to Use - The user wants paid ad research across TikTok or Facebook - The user wants TikTok Shop store analytics - The user wants Facebook monitoring or Meta Ad Library data ## Core Tools - `search_natural_videos` — Search TikTok natural traffic videos by plays, likes, followers, and keyword intent ## Recommended Workflow 1. Start with `search_natural_videos` using niche or product keywords. 2. Narrow by engagement signals such as plays, likes, and creator follower count. 3. Summarize repeated product themes and organic hooks. ## Capability Boundary This skill is intentionally narrow. In the current server, the directly relevant tool is `search_natural_videos`. Do not present it as a full paid-ad or TikTok Shop analytics workflow. ## Cost Awareness Each API call consumes credits from your PipiAds account: - **List/Search**: 1 credit per result returned - **Detail**: 1 credit per request (free if queried within 3 days when applicable)


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

--- name: codex-orchestrator description: Monitor, control, and orchestrate background Codex sessions. Use this skill to track progress, handle interruptions, and ensure task completion for long-running coding tasks. --- # Codex Orchestrator This skill provides a workflow for supervising the Codex coding agent running in background processes. ## Workflow ### 1. Start (Launch) Always launch Codex in a background PTY session to maintain interactivity without blocking the main agent. ```bash bash pty:true workdir:<target_dir> background:true command:"codex exec --full-auto '<PROMPT>'" ``` * Store the returned `sessionId`. * If `sessionId` is lost, find it via `process action:list`. ### 2. Monitor (Watch) Check progress regularly (e.g., via cron or manual check). ```bash # Get last 2KB of logs to see current status process action:log sessionId:<id> limit:2000 ``` **Signs of life:** * Spinner animations or progress bars updating. * "Working...", "Thinking...", "Running...". * File edits (`Edit ...`). **Signs of blockage:** * Interactive prompts (e.g., "Select directory", "Approve change [y/n]"). * No log output for >5 minutes (process might be hung or waiting for hidden input). ### 3. Intervene (Control) If Codex is stuck at a prompt: ```bash # Send 'y' and Enter process action:submit sessionId:<id> data:"y" # Send just Enter (default choice) process action:submit sessionId:<id> data:"" ``` If Codex is looping or hallucinating: ```bash # Kill the session process action:kill sessionId:<id> ``` ### 4. Report (Notify) When a significant milestone is reached or the task is done: 1. Summarize the work done (files changed, tests passed). 2. Notify the user. ## Standard Operating Procedures (SOPs) ### "The Stuck Agent" Protocol 1. **Diagnose**: Run `process action:log sessionId:<id> limit:500`. 2. **Analyze**: Is it asking a question? Is it downloading? 3. **Action**: * If asking: Provide answer via `submit`. * If downloading (slow): Wait. * If silent >10m: Send a "poke" (e.g. `submit data:"\n"` to refresh prompt) or kill/resume. ### "The Resume" Protocol If a session died or was killed: 1. Run `codex resume --last` or `codex resume <session_id>` in a new background process. 2. Verify it picked up the context. ## Logs & Artifacts * Codex logs are ephemeral in the PTY buffer. * For persistent logs, instruct Codex to write to a file: `codex exec "task..." > codex.log 2>&1` (Note: buffering may delay output). * Better: Use `process action:log` to snapshot the buffer periodically.


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