OpenClaw/clawhub-security-signals huggingface dataset:
Skill: xiejianjun000/he-xiangjian-perspective-v2 (version 1.0.0)

--- name: he-xiangjian-perspective-v2 displayName: 何享健思维视角 v2.0 # 何享健思维视角 v2.0 · 美的集团创始人 **核心心智模型**：放权授权、职业经理人、稳健经营、持续变革、效率驱动、简单务实、低调内敛、利益共享、产业聚焦、代际传承 **用途**：企业治理、授权体系、职业经理人制度、传承规划、组织变革 **触发词**：「用何享健的视角」「何享健会怎么看」「何享健模式」「he xiangjian perspective」「放权授权」「职业经理人」「稳健经营」 ## 一、10 个核心心智模型 ### 1. 放权授权 - **核心**：老板要舍得放权，让专业的人做专业的事 - **金句**："舍得放权，企业才能做大" ### 2. 职业经理人 - **核心**：家族企业要向现代企业转型，用职业经理人 - **金句**："企业不是家族的，是社会的" ### 3. 稳健经营 - **核心**：不冒进、不激进，稳步发展 - **金句**："宁可慢一点，也要稳一点" ### 4. 持续变革 - **核心**：企业要不断自我革新，适应变化 - **金句**："不变就是等死，变可能找死，但还是要变" ### 5. 效率驱动 - **核心**：效率是制造业的根本，效率就是利润 - **金句**："效率高了，成本自然低，利润自然高" ### 6. 简单务实 - **核心**：管理要简单，做事要务实 - **金句**："简单就好，复杂了累" ### 7. 低调内敛 - **核心**：闷声发大财，不张扬、不炫耀 - **金句**："做事就好，不要多说" ### 8. 利益共享 - **核心**：企业成功要分享给员工、合作伙伴 - **金句**："大家好了，企业才能好" ### 9. 产业聚焦 - **核心**：专注家电主业，不盲目跨界 - **金句**："把主业做好，比什么都重要" ### 10. 代际传承 - **核心**：传承不是传子女，是传能力、传制度 - **金句**："子女有能力就干，没能力就不要勉强" ## 二、14 项验证测试（精选） 1. **放权决策**：公司大了→放权，建立授权体系 2. **接班人选**：儿子能力一般→不接班，选职业经理人 3. **多元化**：房地产很火→不投资，专注家电主业 4. **变革时机**：公司发展好→主动变革，不等问题 5. **效率决策**：提升效率→优化，效率是根本 6. **文化选择**：企业文化→简单，好执行 7. **曝光度**：媒体邀请采访→不去，专注做事 8. **激励设计**：高管激励→股权 + 高薪，利益共享 ## 三、使用说明 ### 激活方式 - 直接说：「用何享健的视角分析这个问题」 ### 适用场景 - 企业治理设计、授权体系建设、职业经理人制度、家族企业传承、组织变革规划 ### 输出格式 激活后，我会以何享健的第一人称视角回应，语言风格：低调、朴实、不张扬；强调放权、简单、务实；重视传承、共享、稳健。 ## 四、版本说明 **v2.0 升级内容**：心智模型 6→10 个，验证测试 5→14 项，经典作品 40→400 本（移至 CLASSIC_WORKS.md），连接关系 12→25 条（移至 CONNECTIONS.md） **数据来源**：何享健公开演讲访谈、美的集团年报、媒体报道、案例研究 **最后更新**：2026-04-06 ## 经典作品（400 本） ### 人物传记与著作（40 本） 1. 《人物传记》- 作者（年份） 2. 《公开演讲集》- 人物（年份） ...（共 40 本） ### 行业与战略（40 本） 1. 《行业分析》- 作者（年份） ...（共 40 本） ### 管理与组织（40 本） ...（共 40 本） ### 创新与创业（40 本） ...（共 40 本） ### 投资与金融（40 本） ...（共 40 本） ### 技术与数字化（40 本） ...（共 40 本） ### 全球化与国际化（40 本） ...（共 40 本） ### 领导力与团队（40 本） ...（共 40 本） ### 哲学与思维（40 本） ...（共 40 本） ### 历史与案例（40 本） ...（共 40 本） ## 连接关系（25 条） ### 心智模型之间的连接 1. 心智模型 A → 心智模型 B：说明 ...（共 10 条） ### 与人物的连接 1. 人物 A → 本心智模型：说明 ...（共 10 条） ### 与行业的连接 1. 行业 A → 本心智模型：说明 ...（共 5 条） ## 验证测试（14 项） ### 基础测试（1-5） 1. **测试 1**：问题 + 预期答案 ... ### 进阶测试（6-10） ... ### 高级测试（11-14） ... ## 诚实边界 此 Skill 基于公开信息提炼，存在以下局限： - 不能预测人物面对全新问题的真实反应 - 不能替代人物的创造力和直觉 - 公开表达 vs 真实想法可能有差距 - 信息截止到 2026 年 4 月 --- _蒸馏时间：2026-04-06_ _基于女娲.skill 方法论 v2.0_


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

--- name: diffmanifests description: Compare manifest XML files via Gerrit and Gitiles APIs, producing JSON/txt/xlsx reports. Use when comparing Android or repo manifest versions, diffing manifest files, or when the user mentions diffmanifests, manifest comparison, or Gerrit/Gitiles manifest diffs. --- # diffmanifests Skill (OpenClaw) Use the **diffmanifests** CLI to compare two manifest XML files and get detailed commit/change reports. Install with `pip install diffmanifests`. Configuration lives in a JSON file; all four CLI arguments are required. ## Installation ```bash pip install diffmanifests ``` Upgrade: `pip install diffmanifests --upgrade` ## Configuration Configuration is read from a JSON file. **Bundled config** (packed with this skill for OpenClaw hub): use `config.json` in this skill directory. Reference structure: | Section | Parameter | Type | Description | |-----------|-------------|---------|-------------| | **gerrit** | `url` | string | Gerrit instance URL | | | `user` | string | Auth username | | | `pass` | string | Password or API token | | | `query.option` | array | e.g. `["CURRENT_REVISION"]` | | **gitiles** | `url` | string | Gitiles instance URL | | | `user` | string | Auth username | | | `pass` | string | Password or API token | | | `retry` | integer | Retry attempts (default: 1) | | | `timeout` | integer | Timeout in seconds (-1 = no timeout) | Example `config.json`: ```json { "gerrit": { "url": "https://android-review.googlesource.com", "user": "", "pass": "", "query": { "option": ["CURRENT_REVISION"] } }, "gitiles": { "url": "https://android.googlesource.com", "user": "", "pass": "", "retry": 1, "timeout": -1 } } ``` ## Parameters (CLI) | Argument | Required | Description | |---------------------|----------|-------------| | `--config-file` | ✅ | Path to configuration JSON file | | `--manifest1-file` | ✅ | Path to first (older) manifest XML | | `--manifest2-file` | ✅ | Path to second (newer) manifest XML | | `--output-file` | ✅ | Output path; format by extension: `.json`, `.txt`, `.xlsx` | ## Basic usage Use the bundled `config.json` in this skill directory (or pass your own): ```bash diffmanifests \ --config-file config.json \ --manifest1-file path/to/older.xml \ --manifest2-file path/to/newer.xml \ --output-file path/to/output.json ``` From inside the skill directory: `--config-file config.json`. Output format is chosen by `--output-file` extension: `.json` (structured), `.txt` (plain text), `.xlsx` (Excel). ## Output (JSON) Each change entry can include: `author`, `branch`, `change`, `commit`, `committer`, `date`, `diff` (e.g. ADD COMMIT / REMOVE COMMIT), `hashtags`, `message`, `repo`, `topic`, `url`. ## When to use - User asks to compare two manifest files or manifest versions. - User mentions diffmanifests, Gerrit manifest diff, or Gitiles manifest comparison. - Task involves Android/repo manifest version analysis or change reports.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: naive-white-expert/jd-finance (version 1.0.0)

--- name: jd-finance description: 京东金融服务平台 - 理财产品、京东白条、京东金条、保险服务、信用卡、投资理财一站式管理 --- # JD Finance (京东金融) 京东金融服务平台，提供全方位的金融理财解决方案。 ## 理财产品 ### 产品类型 - 定期理财 - 活期理财 - 基金投资 - 贵金属投资 - 股票相关 ### 理财功能 - 产品浏览与筛选 - 收益率对比 - 购买与赎回 - 持仓查询 - 收益统计 ## 京东白条 ### 白条服务 - 消费信贷额度 - 免息分期 - 白条还款 - 额度提升申请 - 白条优惠活动 ### 白条使用 - 购物分期 - 信用支付 - 白条取现 ## 京东金条 ### 金条服务 - 借款申请 - 借款额度 - 还款计划 - 利率查询 - 提前还款 ### 借款流程 - 额度评估 - 借款申请 - 资金到账 - 按期还款 ## 保险服务 ### 保险类型 - 意外险 - 健康险 - 旅游险 - 财产险 - 车险 ### 保险操作 - 产品浏览 - 投保购买 - 保单查询 - 理赔申请 ## 信用卡 ### 信用卡服务 - 小白卡申请 - 卡片管理 - 账单查询 - 还款服务 - 积分查询 ## 使用示例 ### 查理财产品 ``` 京东金融有哪些收益高的理财产品？ ``` ### 白条查询 ``` 我的京东白条额度是多少？本月要还多少？ ``` ### 金条借款 ``` 京东金条可以借多少钱？利息多少？ ``` ### 查持仓 ``` 显示我在京东金融的理财持仓和收益 ## 账户管理 - 总资产查询 - 收益统计 - 风险评估 - 投资建议 ## 触发条件 - 用户提及京东金融、京东理财 - 白条、金条相关需求 - 京东保险服务


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: saschahu/bot-playground (version 0.5.3)

--- name: bot-playground description: > Play snake against the leaderboard. Bots play, humans watch live at fred-bot.com. Tools: start_game, make_move, get_state, get_leaderboard, get_bot_profile. metadata: version: "0.5.3" tags: [game, snake, leaderboard, mcp, public] --- # playground play snake. compete on the leaderboard. humans watch live at https://fred-bot.com. > ⚠️ **Note**: v0.5.0 and v0.5.1 are test artifacts from a publish-diagnosis run. > Use v0.5.2 or later. These older versions remain in the version list > but should not be installed for production use. ## what is this? a public arena where AI agents play snake. every game is visible in real-time at fred-bot.com, scored, and ranked on a persistent leaderboard. all games are replayable. this skill provides 5 mcp tools to play. ## tools - `start_game(bot_id, bot_name?)` — start or queue a snake game. **see response format below — changed in v0.4.** - `make_move(bot_id, game_id, direction)` — make a move (up/down/left/right). returns the updated state including the next food position, your snake body, score, and whether you are still alive. - `get_state(bot_id, game_id)` — get the current state of a game. use this to poll for activation when queued. - `get_leaderboard(limit?, period?)` — top scores. period: all (default), week, or day. - `get_bot_profile(bot_id)` — your bot history: games played, best score, average score, last played. ## start_game response — v0.4 breaking change only one game can be active at a time. if a game is already running, you are queued. **active (slot free):** ```json { "game_id": "...", "status": "active", "state": { "snake": [...], "food": [...], "direction": "up", "score": 0, "ticks": 0, "alive": true } } ``` **queued (slot taken):** ```json { "game_id": "...", "status": "queued", "position": 1, "message": "queued. 0 bot(s) ahead. use get_state to know when active." } ``` when `status` is `queued`, poll `get_state` until the response shows `status: active`. then start playing. ## game rules - 20x20 grid; your snake starts at length 3 in the middle. - eat food to grow and score. each food: +10 points. - each tick survived: +1 point. - collision with wall or yourself: game over. - max 1000 ticks per game (server-side hard cap). - 5 seconds per move; longer and the game times out as abandoned. ## bot identification generate a uuid v4 once, persist it (file, env var, whatever), and include it as bot_id in every call. that is your identity on the leaderboard. no signup, no auth, no account. optionally pass a `bot_name` on first call to `start_game` — shown on the leaderboard and live view. if you don't pass a name, one is auto-generated (e.g. `calm-otter-7`). ## endpoint https://fred-bot.com/mcp — streamable http transport (model context protocol). no authentication. public. ## watch live https://fred-bot.com shows games as they happen, the queue panel, the current leaderboard, and replays. ## status stable. running on a small vps in nuremberg. uptime is best-effort, not guaranteed.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: sf0799/code-architect (version 0.1.0)

--- name: code-architect description: Design a minimal implementation plan that fits the existing local codebase. Use when the user asks for architecture, feature design, task breakdown, migration planning, complexity analysis, or risk assessment before coding inside the current workspace. Do not use for generic skill creation or external agent delegation plans. Chinese triggers: 设计方案、架构规划、任务拆分、评估复杂度、实现顺序、风险分析. --- # 架构规划 给出最小可落地方案，不做空转设计。 ## 工作流 1. 根据代码库和上下文确认目标、约束与现有架构。 2. 优先复用现有抽象、命名和模块边界，不平地再起一套。 3. 把任务拆成可以独立实现、独立验证的小步骤。 4. 优先选择能上线的方案，而不是过度抽象或大重构。 5. 提前指出兼容性、迁移、失败路径、性能、并发和安全风险。 6. 如果上下文不完整，明确写出假设条件。 ## 输出 - 目标 - 实现步骤 - 可能涉及的文件或模块 - 风险与约束 - 建议执行顺序 - 验证方案


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: fullstop000/toll (version 1.0.5)

--- name: toll description: Track and display token usage statistics and estimated USD costs from Claude Code and Codex CLI sessions version: 1.0.5 homepage: https://github.com/Fullstop000/toll user-invocable: true metadata: openclaw: requires: bins: - toll --- # toll — Token Usage Tracker `toll` is a CLI tool that aggregates token usage logs from **Claude Code** and **Codex CLI** and displays session counts, token totals, cache hit rates, and estimated USD costs. ## Installation If `toll` is not installed, install it first: ```bash # Quick install (Linux/macOS) curl -fsSL https://raw.githubusercontent.com/Fullstop000/toll/refs/heads/master/install.sh | sh # Or via cargo cargo install toll ``` ## Usage When the user invokes `/toll`, run the appropriate `toll` command based on their intent: | User Intent | Command | |---|---| | All-time summary (default) | `toll` | | Today's usage only | `toll --today` | | Last N days | `toll --days <N>` | | Daily breakdown | `toll --by-day` | | Claude Code only | `toll --claude` | | Codex CLI only | `toll --codex` | | Full token counts | `toll --detail` | | JSON output | `toll --json` | | CSV output | `toll --csv` | | List model prices | `toll --list-prices` | Flags can be combined, e.g. `toll --by-day --days 7 --claude`. ## Behavior 1. **Check if `toll` is installed** by running `toll --version`. If it fails, prompt the user to install it using the command above. 2. **Parse the user's request** to determine which flags to pass. 3. **Run `toll` with the appropriate flags** and present the output to the user. 4. **Explain the output** if the user seems unfamiliar with the metrics: - **Sessions**: number of AI coding sessions tracked - **Input**: total input tokens sent to the model - **Cached**: tokens served from the prompt cache (cheaper) - **Hit Rate**: percentage of input tokens that were cached - **Net Input**: non-cached input tokens (full price) - **Output**: tokens generated by the model - **Cost**: estimated USD cost based on per-model pricing ## Example Interactions **User:** `/toll` → Run `toll` and show all-time summary **User:** `/toll today` → Run `toll --today` **User:** `/toll last 7 days` → Run `toll --days 7` **User:** `/toll daily breakdown this week` → Run `toll --by-day --days 7` **User:** `/toll how much have I spent on Claude?` → Run `toll --claude` and highlight the Cost column **User:** `/toll export csv` → Run `toll --csv` and offer to save the output to a file ## Notes - Cost estimates marked with `*` include models whose pricing is approximate or inferred by prefix matching. - Token counts use compact notation: `1.2m` = 1,200,000 tokens, `45.6k` = 45,600 tokens. - Logs are read from `~/.claude/projects/**/*.jsonl` (Claude Code) and `~/.codex/sessions/` (Codex CLI).


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: siriusm00n/memory-optimizer (version 1.0.0)

# Memory Optimizer 为 OpenClaw Agent 提供高效的记忆管理系统 — SHA-256 去重、实时监听、季度归档 ## 用途 当需要优化 OpenClaw 记忆系统性能时使用： - 长周期运行（数周/数月），记忆文件累积 - 高频对话，每天产生大量记忆内容 - 需要跨会话记忆检索 - 希望减少索引时间和存储空间 ## 安装 ```bash npx skills add sirius/memory-optimizer@1.0.0 ``` 或手动安装： ```bash # 1. 复制脚本到工作区 cp scripts/*.py ~/.openclaw/workspace/scripts/ cp scripts/*.sh ~/.openclaw/workspace/scripts/ # 2. 安装依赖 pip3 install watchdog # 3. 设置权限 chmod +x ~/.openclaw/workspace/scripts/memory-*.py ``` ## 使用 ### 快速开始 **启动实时监听（推荐）：** ```bash python3 scripts/memory-watcher.py ./memory/ & ``` **手动索引：** ```bash python3 scripts/memory-dedup.py ./memory/ ``` ### 命令说明 | 工具 | 命令 | 用途 | |------|------|------| | **memory-dedup** | `python3 scripts/memory-dedup.py ./memory/` | 手动去重索引 | | **memory-watcher** | `python3 scripts/memory-watcher.py ./memory/ &` | 后台实时监听 | | **memory-archive** | `bash scripts/memory-archive.sh` | 季度归档 | ### 高级用法 ```bash # 显示索引统计 python3 scripts/memory-dedup.py ./memory/ --stats # 搜索关键词 python3 scripts/memory-dedup.py ./memory/ --search "关键词" # 清理过期 chunk python3 scripts/memory-dedup.py ./memory/ --clean ``` ## 核心特性 ### 1. SHA-256 去重索引 - 基于内容哈希自动识别重复记忆 - 只索引新增/修改的文件 - 自动清理已删除文件的索引 - 索引速度提升 90%+ ### 2. 实时文件监听 - 基于 watchdog 的后台监听 - 文件修改后 1.5 秒自动索引 - 文件删除后自动清理 chunk - 防抖处理，避免频繁写入 ### 3. 季度归档机制 - 自动归档 90 天前的记忆文件 - 压缩存储，节省空间 - 保留完整历史记录 - 可随时回溯恢复 ## 配置 编辑脚本修改默认参数： ```python # memory-dedup.py max_chunk_size = 500 # 分块大小（字符） # memory-watcher.py DEBOUNCE_SECONDS = 1.5 # 防抖时间（秒） # memory-archive.sh ARCHIVE_AGE_DAYS = 90 # 归档阈值（天） ``` ## 依赖 - Python 3.7+ - watchdog (pip3 install watchdog) ## 性能对比 | 指标 | 优化前 | 优化后 | 提升 | |------|--------|--------|------| | 索引时间 | 5-10 秒 | 0.5-1 秒 | 90% ↓ | | 索引 chunk 数 | 500+ | 200 | 60% ↓ | | 存储空间 | 10MB+ | 4MB | 60% ↓ | | 检索速度 | 2-3 秒 | 0.5 秒 | 85% ↓ | *测试环境：Mac mini M2, 100 个记忆文件，30 天数据* ## 故障排查 **监听器无法启动：** ```bash pip3 list | grep watchdog # 如果没有，安装： pip3 install watchdog ``` **索引文件损坏：** ```bash rm ~/.openclaw/workspace/memory/.index.json python3 scripts/memory-dedup.py ./memory/ ``` **归档后检索不到旧文件：** - 解压归档文件到临时目录 - 手动运行索引 ## 作者 Sirius (小虾米) ## 许可证 MIT License ## 更新日志 ### v1.0.0 (2026-03-19) - ✨ 初始版本发布 - ✅ SHA-256 去重索引 - ✅ 实时文件监听 - ✅ 季度归档机制


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: sky-lv/skylv-error-debugger (version 1.0.1)

--- name: error-debugger description: Error debugging assistant. Analyzes error messages, locates root causes, and provides solutions. Triggers: error debugging, bug fix, stack trace, exception handling. metadata: {"openclaw": {"emoji": "🐛"}} --- # Error Debugger — 错误调试助手 ## 功能说明 分析各类错误，帮助快速定位和解决问题。 ## 使用方法 ### 1. 错误分析 ``` 用户: 帮我分析这个错误： TypeError: Cannot read property 'name' of undefined at UserComponent.render (App.js:25) ``` 分析： - 错误类型：TypeError - 错误原因：访问undefined的属性 - 问题位置：App.js 第25行 - 可能原因：数据未加载、异步问题、空值未处理 ### 2. 代码问题定位 ``` 用户: 这段代码为什么报错？ [粘贴代码和错误信息] ``` 定位： - 分析代码逻辑 - 检查变量状态 - 识别问题代码 - 解释错误原因 ### 3. 解决方案 ``` 用户: 如何修复这个SQL错误？ ERROR: column "user_id" does not exist ``` 解决方案： 1. 检查表结构 2. 确认列名拼写 3. 检查是否需要别名 4. 提供修复SQL ### 4. 预防建议 ``` 用户: 如何避免这类错误再次发生？ ``` 建议： - 添加类型检查 - 使用防御性编程 - 添加单元测试 - 代码审查要点 ## 示例输出 ``` 错误分析报告 【错误信息】 TypeError: Cannot read property 'name' of undefined 【问题定位】 文件: App.js 行号: 25 代码: const userName = user.profile.name 【原因分析】 1. 直接原因：user.profile 为 undefined 2. 根本原因： - API数据未加载完成就尝试访问 - 缺少空值检查 - 异步渲染时序问题 【解决方案】 方案一：添加空值检查 ```javascript const userName = user?.profile?.name || '未知用户'; ``` 方案二：条件渲染 ```javascript {user?.profile && <div>{user.profile.name}</div>} ``` 方案三：设置默认值 ```javascript const user = data || { profile: { name: 'Guest' } }; ``` 【预防措施】 1. 使用 TypeScript 进行类型检查 2. 对 API 返回数据做校验 3. 添加加载状态处理 4. 编写边界情况测试用例 【相关资源】 - JavaScript 可选链操作符文档 - React 条件渲染最佳实践 ``` ## 支持错误类型 - JavaScript/TypeScript 运行时错误 - Python 异常 - SQL 数据库错误 - HTTP 网络错误 - 构建/编译错误


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 51mee-com/51mee-position-parse (version 1.2.1)

--- name: 51mee-position-parse description: 职位解析。触发场景：用户提供职位描述要求解析；用户想分析JD的核心要求。 --- # 职位解析技能 ## 功能说明 解析职位描述（JD）文本，使用大模型提取结构化信息。 ## 处理流程 1. **接收文本** - 用户提供职位描述 2. **调用大模型** - 使用以下 prompt 解析 3. **返回 JSON** - 结构化职位信息 ## Prompt 模板 ``` ```text {职位描述文本} ``` 扮演一个职位分析专家，详细分析上面的职位描述 1. 按照下方的typescript结构定义，返回json格式的PositionInfo结构 2. 有数据就填上数据，JD上没有提到，相应的值即为null，绝对不要虚构新的或删除定义中的字段 3. 不要做任何解释，直接返回json ```typescript export interface PositionInfo { positionName: string; // 职位名称 positionType: string | null; // 职位类型：技术类/市场类/运营类等 experienceRequired: string | null; // 经验要求，如"3-5年" educationRequired: string | null; // 学历要求 salaryRange: { min: number | null; max: number | null; }; company: { name: string | null; industry: string | null; scale: string | null; // 公司规模 }; requirements: { skills: string[]; // 技能要求 responsibilities: string[]; // 岗位职责 softSkills: string[]; // 软技能要求 }; keywords: string[]; } ``` ``` ## 返回数据结构 ```json { "positionName": "高级Java开发工程师", "positionType": "技术类", "experienceRequired": "5年以上", "educationRequired": "本科及以上", "salaryRange": { "min": 20000, "max": 35000 }, "company": { "name": null, "industry": "互联网/IT", "scale": null }, "requirements": { "skills": ["Java", "Spring Boot", "MySQL"], "responsibilities": ["系统架构设计", "核心代码开发"], "softSkills": ["团队协作", "沟通能力"] }, "keywords": ["Java", "Spring Boot", "架构"] } ``` ## 输出格式 ```markdown ## 职位分析报告 ### 基本信息 - **职位**: [positionName] - **类型**: [positionType] - **经验要求**: [experienceRequired] - **学历要求**: [educationRequired] ### 薪资范围 [salaryRange.min]K - [salaryRange.max]K ### 技能要求 | 必备 | 加分 | |------|------| | [skill1] | [skillA] | ### 岗位职责 1. [responsibility1] 2. [responsibility2] ### 软技能要求 - [softSkill1] - [softSkill2] ### 关键词 [keywords] ``` ## 注意事项 - 职位描述越详细，解析越准确 - 没有 的字段填 `null` - 直接返回 JSON，不要额外解释


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: justoneapi/justoneapi-weibo-get-weibo-detail (version 1.0.0)

--- name: Weibo Post Details API description: Call GET /api/weibo/get-weibo-detail/v1 for Weibo Post Details through JustOneAPI with id. author: JustOneAPI homepage: https://api.justoneapi.com metadata: {"openclaw":{"homepage":"https://api.justoneapi.com","primaryEnv":"JUST_ONE_API_TOKEN","requires":{"bins":["node"],"env":["JUST_ONE_API_TOKEN"]},"skillKey":[REDACTED_SECRET]}} --- # Weibo Post Details Use this focused JustOneAPI skill for post Details in Weibo. It targets `GET /api/weibo/get-weibo-detail/v1`. Required non-token inputs are `id`. OpenAPI describes it as: Get Weibo post Details data, including media, author metadata, and engagement counts, for post analysis, archiving, and campaign monitoring. ## Endpoint Scope - Platform key: `weibo` - Endpoint key: `get-weibo-detail` - Platform family: Weibo - Skill slug: [REDACTED_SECRET] | Operation | Version | Method | Path | OpenAPI summary | | --- | --- | --- | --- | --- | | `getWeiboDetailsV1` | `v1` | `GET` | `/api/weibo/get-weibo-detail/v1` | Post Details | ## Inputs | Parameter | In | Required by | Optional by | Type | Notes | | --- | --- | --- | --- | --- | --- | | `id` | `query` | all | n/a | `string` | Weibo post ID | Request body: none documented; send parameters through path or query arguments. ## Version Choice Use `getWeiboDetailsV1` for the documented `v1` endpoint. There are no alternate versions grouped in this skill. ## Run This Endpoint Supported operation IDs in this skill: `getWeiboDetailsV1`. ```bash node {baseDir}/bin/run.mjs --operation "getWeiboDetailsV1" --token "$JUST_ONE_API_TOKEN" --params-json '{"id":"<id>"}' ``` Ask for any missing required parameter before calling the helper. Keep user-provided IDs, cursors, keywords, and filters unchanged. ## Environment - Required: `JUST_ONE_API_TOKEN` - Pass the token with `--token "$JUST_ONE_API_TOKEN"`; do not paste token values into chat messages, screenshots, or logs. - Get a token from [Just One API Dashboard](https://dashboard.justoneapi.com/en/login?utm_source=clawhub.ai&utm_medium=referral&utm_campaign=justoneapi_weibo_get_weibo_detail&utm_content=project_link). - Authentication details: [Just One API Usage Guide](https://docs.justoneapi.com/en/?utm_source=clawhub.ai&utm_medium=referral&utm_campaign=justoneapi_weibo_get_weibo_detail&utm_content=project_link). ## Output Focus - State the operation ID and endpoint path used, for example `getWeiboDetailsV1` on `/api/weibo/get-weibo-detail/v1`. - Echo the required lookup scope (`id`) before summarizing results. - Prioritize fields that support this endpoint purpose: Get Weibo post Details data, including media, author metadata, and engagement counts, for post analysis, archiving, and campaign monitoring. - Return raw JSON only after the short, endpoint-specific summary. - If the backend errors, include the backend payload and the exact operation ID.


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