OpenClaw/clawhub-security-signals huggingface dataset:
Skill: henrryjoke/shefu (version 0.2.2)

--- name: shefu description: "🧙 射覆——猜物之卦，源于汉代的易学占卜游戏。以《正易心法》卦脉法从六爻结构中直接读取气的态势，推测覆下之物。不查表、不套口诀。" --- # 射覆 · 正易心法卦脉解读 > 「谛观」出品 · 基于麻衣道者《正易心法》42章·陈抟注 --- ## 🧙 什么是射覆？ **射覆**（Shefu）——「射」者猜也，「覆」者盖也。一人藏物于覆器之下，另一人起卦推测覆下为何物。庄子曰： > 射者非前期而中，谓之善射。 > ——《庄子·田子方》 射覆见载于《汉书·东方朔传》。汉武帝尝以射覆试东方朔，朔起卦皆中，帝叹服。自此射覆成为汉代宫廷方士、文人之间流行的占卜游戏——**既是易学的功夫试炼，也是智力的雅趣对决。** 本技能继承五代宋初隐士**麻衣道者**《正易心法》及**陈抟**（希夷先生）注的卦脉解读传统，以「爻位即气位」为核心方法，**不查卦辞、不套口诀**，从六爻卦画的阴阳排列中直接读取气的态势，推演覆下之物的功能态与落处。 --- ## 🎮 玩法说明 ### 经典玩法（二人射覆） ``` 玩家A：「起一卦，猜我手里握着什么。」 AI（射覆者）：起卦 → 默观卦画 → 推演物象 → 给出候选 玩家A：揭晓答案，验证卦脉 ``` ### 单人玩法（自测卦脉） ``` 玩家：「起卦猜我左手边的杯子里有什么。」 AI：起卦并给出 2-3 个可能的物象候选 玩家：对照实际物品，看卦脉是否吻合 ``` ### 无限定玩法（开放式） ``` 玩家：「起一卦，随便猜一个我家里的东西。」 AI：起卦后从卦脉结构推导功能态（健/顺/动/入/陷/丽/止/说）， 结合现代转译规则给出 2-3 个候选。 ``` --- ## 🧠 核心方法（三分钟入门） ### 原则一：爻位即气位 阳爻在哪里，阳气就在哪里；阴爻在哪里，阴气就在哪里。**不看标签，看位置。** ### 原则二：八卦是八种功能态 八卦不是名词，是德性（功能态）。从卦画结构直接读： | ☰ 乾 | ☷ 坤 | ☳ 震 | ☴ 巽 | ☵ 坎 | ☲ 离 | ☶ 艮 | ☱ 兑 | |---|---|---|---|---|---|---|---| | 三阳 | 三阴 | 一阳**下** | 一阴**下** | 一阳**中** | 一阴**中** | 一阳**上** | 一阴**上** | | **健** | **顺** | **动** | **入** | **陷** | **丽** | **止** | **悦** | ### 原则三：观不是推 先静观卦画结构——六爻阴阳怎么排列，气就怎么走。**观是直观照见，不是逻辑推导。** ### 原则四：同构容纳 同一气脉可落于多个维度——自然、人身、器物、人伦。**一脉多现。** ### 原则五：合于自然者为正 每个推演必须能从卦画结构回溯验证。方向不可逆：**结构 → 自然 → 语境**，不能从语境倒推。 --- ## 🔮 起卦方式 起卦三步： 1. **你发信号**——说「起卦」「占卜」「猜一猜」等触发词 2. **AI确认**——委婉确认你的问题已聚焦 3. **自动起卦**——AI静默执行，不让你选择方式 默认使用**大衍筮法**（模拟蓍草49根，四营十八变）。如需特定方式： | 你说 | AI做 | |------|------| | 「起一卦」 | 大衍筮法（默认） | | 「梅花易数起卦」 | 时间/数字起卦 | | 「铜钱摇卦」 | 引导你逐爻手摇三枚硬币 | --- ## 📐 分析链路（七层） ``` L0 起卦 → A1 大衍筮法（默认）/ 梅花易数 / 六爻纳甲 L1 卦画默观 → 不看卦名，只看六爻阴阳 L2 反对分析 → 反体（主客翻转）/ 对体（阴阳全反） L3 卦脉流动 → 阴阳进退 + 消息定位 + 互体表里 L4 月建加权 → 旺相休囚死（月令对卦气的强弱调节） L5 落处展开 → 从功能态推导物象候选（2-3个） L6 变复校验 → 爻变 + 体复 + 参卦（自校验） ``` --- ## 🎯 输出示例 ``` 📋 卦象总览 本卦：☵☳ 水雷屯 · 变卦：☵☶ 水山蹇 📊 卦画默观 上坎☵（陷）下震☳（动）—— 阳气在下方萌动欲出， 却被上方的阴气压制——「蓄势待发」之象。 🔗 落处展开 候选①：钥匙/金属小件（坎为陷中藏物，动在下欲出） 候选②：充电头/电源适配器（震为电流初动，坎为陷藏） 候选③：口含之物（坎为耳肾，震为发声，合为口部） ``` --- ## ⚠️ 使用须知 - **不判断吉凶**——不给出确定性结论，只展开可能性 - **禁用语**：一定、必然、大吉、大凶、宜、忌、应该 - **鼓励用语**：可能、或许、含有…之象、呈现…态势 - **结束语**——"以上是根据卦象展开的可能性推演，并非确定性结论。请你结合实际情况判断。" --- ## 📚 参考阅读 射覆相关：《汉书·东方朔传》《三国志·管辂传》 卦脉方法：麻衣道者《正易心法》·陈抟注 推荐系列：本公众号「正易心法读书札记」01-15篇 --- ## 📜 版本 v0.2.1 — 大衍筮法起卦引擎 + 正易心法B1-B5完整分析链路 代码 MIT · 数据 CC BY-NC-SA 4.0 [GitHub](https://github.com/henrryjoke/shefu)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: ckchzh/intern-report (version 2.0.0)

--- version: "2.0.0" name: Intern Report description: "实习报告和实习总结生成器。日报、周报、实习总结、心得体会、答辩PPT大纲、深度反思与职业规划。. Use when you need intern report capabilities. Triggers on: intern report." 实习报告生成器。实习总结、周记、心得体会、答辩PPT大纲、深度反思。Intern report generator with weekly logs, summaries, defense outlines, deep reflection. 实习周记、实习心得、毕业实习。Use when writing internship reports. author: BytesAgain homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills --- # intern-report 实习报告和实习总结生成器。日报、周报、实习总结、心得体会、答辩PPT大纲、深度反思与职业规划。 ## Usage Run the script at `scripts/intern.sh` with the following commands: | Command | Description | |---------|-------------| | `intern.sh daily "今日工作"` | 生成实习日报 | | `intern.sh weekly "本周内容"` | 生成实习周报（结构化+学到了什么） | | `intern.sh summary "实习单位" "岗位" "实习天数"` | 生成实习总结 | | `intern.sh reflection "收获和感悟"` | 生成心得体会 | | `intern.sh defense "实习内容"` | 答辩PPT大纲（8页，含答辩技巧） | | `intern.sh reflect "经历"` | 深度反思（可迁移能力+职业规划） | | `intern.sh help` | 显示帮助信息 | ## Examples ```bash # 实习日报 bash scripts/intern.sh daily "参与需求评审会议，完成登录页面UI开发" # 实习周报 bash scripts/intern.sh weekly "完成用户模块前端开发，学习了React Hooks" # 实习总结 bash scripts/intern.sh summary "阿里巴巴" "前端开发实习生" "90" # 心得体会 bash scripts/intern.sh reflection "学会了团队协作，提升了编码能力" # 答辩PPT大纲 bash scripts/intern.sh defense "前端页面开发,API对接,性能优化,代码评审" # 深度反思 bash scripts/intern.sh reflect "参与产品开发,学习了敏捷流程,独立完成模块设计" ``` ## 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: al-one/mcp-lark (version 1.0.0)

--- name: mcp-lark description: Based on FeiShu(飞书) / Lark's OpenAPI MCP server, manage user information, chats, emails, cloud documents, multidimensional tables, tasks, calendars, etc. homepage: https://github.com/aahl/skills/blob/main/skills/mcp-lark/SKILL.md metadata: { "openclaw": { "emoji": "💼", "requires": { "anyBins": ["mcporter", "npx"], "env": ["LARK_MCP_SERVERS"] }, "primaryEnv": "LARK_MCP_SERVERS", "install": [ { "id": "node", "kind": "node", "package": "mcporter", "bins": ["mcporter"], "label": "Install mcporter (node)", }, ], }, } --- # MCP Lark / FeiShu Need to login to the Lark MCP Configuration Platform to add MCP services, obtain the MCP URL, and configure it into environment variables. - Lark MCP docs: https://open.larksuite.com/document/mcp_open_tools/call-feishu-mcp-server-in-remote-mode - 飞书 MCP 文档: https://open.feishu.cn/document/mcp_open_tools/end-user-call-remote-mcp-server ## Environment variables Prioritize fetching from `.env` under the workspace, then use system environment variables. If not configured, ask the user for input and update it to `.env`. ```shell # Configure multiple MCP service URLs and usage scenarios in environment variables LARK_MCP_SERVERS=' open.larksuite.com/mcp/stream/xxx:Chats and Mails; open.larksuite.com/mcp/stream/yyy:Cloud documents; ' ``` ## List of available tools ```shell npx -y mcporter list 'open.larksuite.com/mcp/stream/<token>' --all-parameters # Get the schema of the specified tool npx -y mcporter list 'open.larksuite.com/mcp/stream/<token>' --json | jq '.tools[] | select(.name == "<tool_name>")' ``` ## Call specified tool ```shell npx -y mcporter call 'open.larksuite.com/mcp/stream/<token>.<tool_name>' param1:"value1" foo:"bar" ``` ## References - Sent message content: references/message_create.md ## About `mcporter` To improve compatibility, use `npx -y mcporter` instead of `mcporter` when executing commands.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: afengzi/market-news (version 1.0.0)

--- name: market-news description: 自动搜索和总结最新财经新闻与市场动态 metadata: {"openclaw": {"emoji": "📰", "os": ["win32"]}} --- # 财经资讯摘要 你是一个财经资讯助手，帮助用户快速获取和理解市场动态。 ## 能力 1. **新闻摘要**：将长篇财经新闻提炼为简洁的要点摘要，帮助用户快速了解关键信息。 2. **政策解读**：解读国家经济政策、央行货币政策、行业监管政策对市场的潜在影响。 3. **市场综述**：提供每日/每周市场综述，包括大盘走势、热点板块、重要事件等。 4. **公司公告分析**：帮助理解上市公司公告内容（财报、增减持、定增、并购等）的含义和影响。 5. **全球市场联动**：关注美股、港股、商品期货等全球市场动态及其对 A 股的影响。 ## 注意事项 - 资讯仅供参考，请以官方信息源为准 - 市场解读具有主观性，仅代表分析观点 - 建议关注多个信息源，避免信息偏差


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

--- name: performance-profiling description: 性能分析速查。当需要：(1) Python 性能分析 (2) Node.js 性能分析 (3) 数据库优化 (4) 系统性能监控时使用。 --- # Performance Profiling 性能分析和调优工具速查。 ## 快速参考 ### Python 分析 ```bash python -m cProfile script.py python -m cProfile -s cumtime script.py pip install py-spy && py-spy top --pid 12345 ``` ### Node.js 分析 ```bash node --prof app.js node --cpu-prof app.js npm install -g clinic && clinic doctor -- node app.js ``` ### 数据库 ```sql -- MySQL EXPLAIN ANALYZE SELECT * FROM users WHERE name = 'Alice'; SHOW PROCESSLIST; -- PostgreSQL EXPLAIN ANALYZE SELECT * FROM users WHERE name = 'Alice'; SELECT * FROM pg_stat_activity; ``` ### 系统 ```bash top -o %CPU # CPU iostat -x 1 # I/O vmstat 1 # 综合 ``` ## 详细参考 - **Python 分析**: [references/python.md](references/python.md) - cProfile, line_profiler, py-spy - **Node.js 分析**: [references/nodejs.md](references/nodejs.md) - V8 分析, clinic.js - **数据库优化**: [references/database.md](references/database.md) - MySQL, PostgreSQL, Redis - **系统性能**: [references/system.md](references/system.md) - CPU, 内存, I/O - **Web 压测**: [references/load-test.md](references/load-test.md) - ab, wrk, hey ## 常见优化 ### Python ```python # 字符串拼接 result = "".join(strings) # 而非 for + loop # 使用生成器 result = (x for x in range(1000000)) # 内置函数更快 total = sum(numbers) ``` ### 数据库 - 添加合适索引 - 避免全表扫描 - 使用 EXPLAIN 分析 - 缓存热点数据 ## 文档 - Python profiling: https://docs.python.org/3/library/profile.html - clinic.js: https://clinicjs.org/ - FlameGraph: https://www.brendangregg.com/flamegraphs.html


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: leoyeai/openclaw-guardian-ultra (version 0.1.0)

--- name: openclaw-guardian description: Deploy and manage a Guardian watchdog process for OpenClaw Gateway. Provides automated health monitoring, self-repair via `doctor --fix`, git-based workspace rollback, daily snapshots, and optional Discord alerting. Use when a user wants to harden their OpenClaw instance against crashes, config corruption, or bad workspace edits — or when setting up Guardian for the first time on a new server/container. --- # OpenClaw Guardian Guardian is a standalone bash watchdog that keeps OpenClaw Gateway alive 24/7. **Repair ladder:** 1. Detect Gateway down (every 30s) 2. Run `openclaw doctor --fix` (up to 3 attempts) 3. If still down → `git reset --hard` to last stable commit, restart Gateway 4. If all fails → cooldown 300s, resume monitoring 5. Daily automatic git snapshot of workspace ## Setup Steps ### 1. Initialize git (required for rollback) ```bash cd ~/.openclaw/workspace git config --global user.email "[REDACTED_SECRET]" git config --global user.name "Guardian" git init && git add -A && git commit -m "initial" ``` Skip if repo already exists. Without git, doctor --fix still works; rollback is skipped. ### 2. Install guardian.sh Copy `scripts/guardian.sh` from this skill to `~/.openclaw/guardian.sh`: ```bash cp scripts/guardian.sh ~/.openclaw/guardian.sh chmod +x ~/.openclaw/guardian.sh ``` ### 3. Start Guardian **Container / no systemd (nohup):** ```bash nohup ~/.openclaw/guardian.sh >> /tmp/openclaw-guardian.log 2>&1 & ``` **Linux VPS with systemd:** See `references/setup.md` → Pattern B. ### 4. Auto-start on container restart Add to `~/.openclaw/start-gateway.sh` (before the final `exec` line): ```bash pkill -f "guardian.sh" 2>/dev/null || true nohup /home/ubuntu/.openclaw/guardian.sh >> /tmp/openclaw-guardian.log 2>&1 & ``` ### 5. Optional: Discord alerts ```bash export DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/..." ``` Or add to `start-gateway.sh` as a persistent export. ## Verify ```bash pgrep -a -f "guardian.sh" # confirm process running tail -f /tmp/openclaw-guardian.log # watch live logs ``` ## Configuration All settings via environment variables. Defaults work out of the box. See `references/setup.md` for full variable reference, systemd config, and architecture diagram. ## Notes - Guardian coexists with `gw-watchdog.sh` — run both for layered resilience - Rollback targets the 2nd-newest non-auto commit (skips daily-backup, rollback, auto-backup commits) - Log path: `/tmp/openclaw-guardian.log`


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: mars82311111/mars-stock-analysis (version 1.0.0)

--- name: fundamental-stock-analysis description: Fundamental equity analysis and peer ranking using a structured scoring playbook (quality, balance-sheet safety, cash flow, valuation, sector adjustments, confidence modifiers). Use when a user asks to analyze one or more stock tickers, compare peers, choose a best pick, or produce a fundamentals-based verdict. --- # fundamental-stock-analysis 1. Read `references/playbook.md` before starting analysis. 2. Follow the playbook steps exactly (input parse -> data collection -> quick screen -> scoring -> rating -> output). 3. For multi-ticker requests, analyze each ticker first, then rank peers and select best pick with invalidation triggers. 4. Always include confidence level and call out stale/conflicting data explicitly. 5. Do not append any machine-readable JSON block in user-facing output. 6. Treat all analysis as educational/informational content, not investment advice. ## Security scope (clarification) - Use web retrieval only for ticker-relevant financial statements, filings, market/fundamental datasets, and relevant financial news. - Do not request, handle, or expose credentials/secrets. - Do not perform command execution, local file discovery unrelated to analysis, or arbitrary URL exploration outside ticker-relevant finance/news scope. ## Non-goals - Data exfiltration or collection of private/non-public information. - Browser/automation tasks outside equity fundamental analysis and citation gathering. ## Output discipline - Keep conclusions decisive and risk-aware. - Separate business quality, balance-sheet safety, and valuation. - Never fabricate missing metrics; mark `NA`.

path: _meta.json
content: ownerId: kn757g6f5ymy86tj1zkc4e598s81eewr
slug: fundamental-stock-analysis
version: 1.0.5
publishedAt: 1772061333257

Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: peand-rover/art-teacher-video (version 1.0.0)

name: art-teacher-video version: "1.0.0" displayName: "Art Teacher Video — Student Portfolio and Creative Development Videos for Art Teachers" description: > You are a video assistant for private art teachers, art studios, and art education programs — helping them show their teaching approach, their student portfolio outcomes, and their creative development philosophy through short enrollment and showcase videos. Art Teacher Video turns your medium expertise, your student progression examples, and your portfolio preparation capability into clips that answer the question every parent or aspiring artist considering art lessons asks: is this the teacher who will develop my actual creative ability and artistic eye — or will I spend twelve weeks doing the same five exercises while my fundamental understanding of light, composition, and color stays exactly where it started? tags: - art teacher video - art lessons video - private art teacher video - art studio video - drawing lessons video --- # Art Teacher Video Help art teachers create portfolio and development videos. ## What You Do 1. Ask what type of video (teacher introduction, medium showcase, student portfolio progression, class environment, college prep portfolio, adult learner program) 2. Gather: mediums taught, student age range and level, teaching philosophy, portfolio preparation experience, class format (private/group/studio) 3. Generate 60-90 second script; suggest: teacher demonstrating a technique, student portfolio progression from first to current work, teacher explaining what they assess in a new student, studio environment and materials, portfolio outcome for college-bound students


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: googleworkspace-bot/persona-project-manager (version 1.0.12)

--- name: persona-project-manager description: "Coordinate projects — track tasks, schedule meetings, and share docs." metadata: version: 0.22.5 openclaw: category: "persona" requires: bins: - gws skills: - gws-drive - gws-sheets - gws-calendar - gws-gmail - gws-chat --- # Project Manager > **PREREQUISITE:** Load the following utility skills to operate as this persona: `gws-drive`, `gws-sheets`, `gws-calendar`, `gws-gmail`, `gws-chat` Coordinate projects — track tasks, schedule meetings, and share docs. ## Relevant Workflows - `gws workflow +standup-report` - `gws workflow +weekly-digest` - `gws workflow +file-announce` ## Instructions - Start the week with `gws workflow +weekly-digest` for a snapshot of upcoming meetings and unread items. - Track project status in Sheets using `gws sheets +append` to log updates. - Share project artifacts by uploading to Drive with `gws drive +upload`, then announcing with `gws workflow +file-announce`. - Schedule recurring standups with `gws calendar +insert` — include all team members as attendees. - Send status update emails to stakeholders with `gws gmail +send`. ## Tips - Use `gws drive files list --params '{"q": "name contains \'Project\'"}'` to find project folders. - Pipe triage output through `jq` for filtering by sender or subject. - Use `--dry-run` before any write operations to preview what will happen.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: davidslavich/gtm-account-research (version 1.0.0)

--- name: gtm-account-research description: > Deep-dive a target company and produce a structured account intelligence brief covering tech stack, buying signals, key personas, and a recommended engagement angle. Use before outreach, a first call, a demo, or setting up an ABM campaign. Triggered by: "research this account," "brief me on [company]," "what do I know about [company]," or when preparing for a meeting with a named account. license: MIT compatibility: Requires web search access for live signal research. metadata: author: iCustomer version: "1.0.0" website: https://icustomer.ai --- # GTM Account Research Produce an Account Intelligence Brief for a named company. Ground every signal in a specific, traceable source. ## Steps 1. **Snapshot** — company name, HQ, size, business model, recent news (last 90 days) 2. **Tech stack** — identify tools in the categories most relevant to your product (e.g. data warehouse, CRM, marketing automation, paid channels). Use BuiltWith, job postings, and engineering blogs as sources. 3. **Buying signals** — job postings, conference attendance, funding events, published strategy content. Date every signal. 4. **Displacement triggers** — are they actively migrating off a competitor? Hiring for a role that signals a gap you fill? Flag ⚡ if a strong trigger is present. 5. **Personas** — identify Economic Buyer (budget authority), Technical Champion (evaluates), and End User (daily use). Name + LinkedIn URL when findable. 6. **Engagement angle** — one specific recommendation: what pain, which product, what channel, who reaches out first, and the opening hook. ## Output ``` # Account Brief: [Company] | [Date] Snapshot: [3 sentences — what they do, size, recent context] ICP Segment: [your segment label] Stack: [Category: tool — or "Unknown" for each category] Signals: [Bulleted — signal + source + date] Displacement: [⚡ Yes — detail / None detected] Personas: [Name · Title · LinkedIn · Pain point — one row per person] Gaps: [What's missing that would sharpen the approach] Engagement Angle: [Specific: pain → product → channel → who reaches out → opening hook] ``` Keep the brief scannable. Flag any detail as `[Unverified]` if not directly observed.


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

--- name: aliyun-hot-trend description: 注册“阿里云”热门技能；当需要访问或自动化阿里云相关内容时调用。 homepage: `https://www.aliyun.com/` metadata: {"clawdbot":{"emoji":"🔥"}} --- # 阿里云 用途与边界 - 面向公开产品页与控制台可见的非敏感摘要信息整理 - 不提供账号操作、权限绕过或付费接口调用能力 - 仅用于公开或个人控制台中可视的合规信息摘要 关键入口 - 主页：https://www.aliyun.com/ - 控制台：https://home.console.aliyun.com/ - 文档中心：https://help.aliyun.com/ 常见任务 - 产品规格与价格页面摘要（规格、地域、定价） - 控制台账单概览与费用趋势整理（仅个人可见范围） - 服务状态公告与变更记录摘要 数据字段 - 产品名称、规格参数、地域可用性、定价链接 - 账单周期、费用项、趋势摘要、来源链接 - 服务公告标题、发布时间、影响范围、链接 自动化要点 - 控制台内容需登录，且仅做页面可见信息摘要，不进行API调用 - 避免采集或存储密钥、账户ID等敏感信息 - 频率控制，尊重平台访问限制 示例流程 - 产品摘要：访问产品页 → 抽取规格与价格链接 → 输出摘要 - 账单概览：登录控制台 → 访问账单页 → 提取周期与费用项 - 公告整理：访问公告页 → 抽取条目 → 输出影响范围与链接 合规提示 - 遵守平台与账户安全规定，不进行自动化账号操作 - 不存储或输出任何敏感凭据


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

# Agent Creator 技能 快速创建、删除、管理 OpenClaw agent 实例。 ## 触发条件 用户要求创建新机器人、新 agent、新助手、删除 agent、查看 agent 列表时激活此技能。 ## 可用脚本 | 脚本 | 功能 | |------|------| | `list-agents.sh` | 查看当前所有 agent | | `create-agent.sh` | 创建新 agent | | `delete-agent.sh` | 删除 agent | ## 创建 Agent ### 参数 ``` ./create-agent.sh <agent-id> <agent-name> <app-id> <app-secret> [model] [description] ``` | 参数 | 必填 | 说明 | 示例 | |------|------|------|------| | agent-id | ✅ | 唯一标识符（英文小写） | `xiaoming` | | agent-name | ✅ | 显示名称 | `小明` | | app-id | ✅ | 飞书 App ID | `cli_xxx` | | app-secret | ✅ | 飞书 App Secret | `xxx` | | model | ❌ | 使用的模型（默认 glm-5） | `qwen3.5-plus` | | description | ❌ | 人设描述 | `客服助手` | ### 示例 ```bash # 创建一个客服机器人 ./create-agent.sh xiaokefu 小客服 cli_a94xxx mysecret123 glm-5 "客服助手，帮助用户解答问题" # 使用默认模型创建 ./create-agent.sh xiaowang 小王 cli_a94xxx mysecret123 ``` ### 创建后步骤 1. 执行 `openclaw gateway restart` 重载配置 2. 在飞书开放平台配置事件订阅地址 3. 在群里 @ 新机器人测试 ## 删除 Agent ```bash ./delete-agent.sh <agent-id> ``` ⚠️ 注意：main agent 不能被删除 ## 查看列表 ```bash ./list-agents.sh ``` ## 配置文件位置 - 主配置: `/home/admin/.openclaw/openclaw.json` - Agent 目录: `/home/admin/.openclaw/agents/{agent-id}/` - Workspace: `/home/admin/.openclaw/workspace-{agent-id}/` ## 创建时自动完成 1. ✅ 创建 agent 目录结构 (`agents/{id}/agent/`, `agents/{id}/sessions/`) 2. ✅ 创建 workspace 目录和默认文件 (AGENTS.md, SOUL.md, USER.md 等) 3. ✅ 更新 openclaw.json: - 添加到 `agents.list` - 添加飞书账号到 `channels.feishu.accounts` - 添加绑定到 `bindings` - 添加到 `tools.agentToAgent.allow` 4. ✅ 复制 models.json 配置 ## 注意事项 - 飞书机器人需要先在飞书开放平台创建应用 - 需要配置飞书事件订阅地址（通常为 Gateway 地址） - 创建/删除后需要重启 Gateway 才能生效


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: stale | SkillSpector: suspicious (CRITICAL)
Skill: leooooooow/ecommerce-trend-to-content-angle (version 1.0.0)

--- name: ecommerce-trend-to-content-angle description: Turn a trend, news item, creator signal, review pattern, or market observation into sharper ecommerce content angles that are timely, useful, and commercially relevant. Use when teams want better hooks without sounding forced or generic. --- # Trend to Content Angle Translate a raw signal into clearer ecommerce content angles, hooks, and narrative directions. ## Solves Teams often spot something interesting — a trend, headline, creator shift, comment pattern, or market signal — but struggle to turn it into content that is both timely and commercially useful. Common problems: - the signal is real, but the angle is vague; - trend chasing creates generic content; - hooks feel forced or disconnected from the product; - teams generate ideas that are topical but not strategic. Goal: **Convert a raw signal into content angles that feel timely, relevant, and worth publishing.** ## Use when - A team wants to turn a fresh trend into social or creator content - A brand sees a pattern in reviews, comments, or customer behavior - Operators need hook directions for X, TikTok, creator briefs, or email - A market observation needs sharper editorial framing - The user wants multiple angles from one source signal ## Do not use when - There is no real signal, trend, or observation to work from - The task is a finished long-form draft rather than angle generation - The user only wants keyword research with no editorial angle ## Inputs - Trend, headline, post, signal, or observation - Product or brand context - Target audience - Channel: X, TikTok, landing page, email, creator brief, etc. - Desired tone or angle style - Any claims or compliance boundaries ## Workflow 1. Clarify what the underlying signal actually means. 2. Identify why the signal matters to the audience commercially or emotionally. 3. Generate angle directions rather than surface-level topic repeats. 4. Turn each angle into hooks, framing notes, and content uses. 5. Prioritize the angles most likely to feel timely and distinctive. ## Output Return: 1. Signal interpretation 2. 3-7 content angles 3. Hook ideas for each angle 4. Best-fit channels or formats 5. Notes on risk, freshness, or overused framing ## Quality bar - Angles should connect the trend to a real audience tension or opportunity. - Avoid obvious rewrites of the same idea. - Hooks should feel publishable, not brainstorming fluff. - Keep the result commercially relevant for ecommerce teams. - Prefer specific observations over empty trend language. ## Resource See `references/output-template.md`.


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