OpenClaw/clawhub-security-signals huggingface dataset:
Skill: diluke1600/grafana-inspector (version 1.0.0)

--- name: grafana-inspector description: Grafana 自动化巡检技能。支持浏览器截图 + API 数据巡检，多仪表盘批量巡检，自动发现仪表盘。 --- # Grafana 自动化巡检技能 ## 快速开始 ```bash # 1. 配置 cd skills/grafana-inspector/scripts cp config.example.json config.json # 编辑 config.json # 2. 执行 python main.py config.json # 或在 OpenClaw 中输入 执行 Grafana 巡检 ``` ## 配置说明 ```json { "grafana_url": "http://localhost:3000", "api_key": "", "dashboard_uids": [], "auto_discover": true, "discover_limit": 10, "inspection_mode": "hybrid", "screenshot_dir": "./screenshots" } ``` | 参数 | 说明 | 必填 | |------|------|------| | `grafana_url` | Grafana 地址 | ✅ | | `api_key` | API Key（API 巡检用） | ✅ | | `dashboard_uids` | 仪表盘 UID 列表 | ❌ | | `auto_discover` | 自动发现仪表盘 | ❌ | | `discover_limit` | 最多巡检数量 | ❌ | ## 使用方式 ### 方式 1：命令行 ```bash cd skills/grafana-inspector/scripts python inspect_report.py config.json ``` ### 方式 2：OpenClaw ``` 执行 Grafana 巡检 ``` ## 输出 - `inspection_*.json` - JSON 结果 - `inspection_*.md` - Markdown 报告 ## 获取 Dashboard UID 1. 打开 Grafana 仪表盘 2. 查看 URL: `https://grafana/d/{UID}/{name}` 3. 复制 UID 部分 ## 获取 API Key 1. Grafana → Configuration → API keys 2. 创建 Viewer 权限的 Key 3. 复制到配置 ## 文件结构 ``` grafana-inspector/ ├── scripts/ │ ├── api_inspect.py # API 巡检 │ ├── main.py # 主脚本 │ └── config.json # 配置 ├── screenshots/ # 截图 ├── SKILL.md # 技能定义 └── README.md # 说明文档 ``` ## 故障排查 ### API 连接失败 - 检查 API Key 是否正确 - 验证网络连接 - 确认 Grafana 服务正常 - 检查飞书授权状态


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: nasplycc/voice-reply-mode (version 1.0.0)

--- name: voice-reply-mode description: Add same-modality conversation behavior to an agent: voice in → voice out, text in → text out. Use when enabling Telegram/Feishu voice-note workflows with Edge TTS, documenting agent voice preferences, and providing gateway config snippets for inbound-only TTS auto replies. --- # Voice Reply Mode Use this skill when a user wants an agent to behave like this: - 用户发语音 → agent 回语音 - 用户发文字 → agent 回文字 ## What this skill includes - Workspace-level behavior rules for `SOUL.md` / `IDENTITY.md` / `TOOLS.md` - A reusable Edge TTS helper script - Gateway config snippets for `messages.tts` - Channel notes for Telegram / Feishu style deployments ## Important boundary This skill can package **rules, scripts, and config snippets**. It does **not** automatically change a user's global gateway config unless the user explicitly asks and authorizes it. ## Recommended workflow 1. Read `references/workspace-snippets.md` 2. Read `references/gateway-config.md` 3. Copy the relevant snippets into the target agent workspace 4. If the user explicitly asks, patch gateway config with the snippet from `references/gateway-config.md` 5. Validate with one text message and one voice message ## Minimal success criteria - Text message receives text reply - Voice message receives voice reply - Agent workspace documents the preferred voice ## Files in this skill - `references/workspace-snippets.md` — snippets for `IDENTITY.md`, `SOUL.md`, `TOOLS.md` - `references/gateway-config.md` — `messages.tts` examples and caveats - `references/channel-notes.md` — Telegram / Feishu notes - `scripts/edge-tts.sh` — helper script for local TTS generation ## Notes - In many deployments, the decisive switch is gateway-level `messages.tts.auto = "inbound"`. - Workspace files define behavior expectations, but gateway config determines whether automatic voice replies actually happen. - If schema rejects `identity.voice`, keep voice preference in workspace docs instead.

path: scripts/edge-tts.sh
content: #!/usr/bin/env bash
set -euo pipefail

TEXT="${1:-}"
OUTPUT="${2:-/tmp/edge-tts-output.mp3}"
VOICE="${3:-zh-CN-XiaoxiaoNeural}"

if [[ -z "$TEXT" ]]; then
  echo "Usage: edge-tts.sh \"文本\" [输出文件] [声音]" >&2
  exit 1
fi

edge-tts --voice "$VOICE" --text "$TEXT" --write-media "$OUTPUT"
echo "$OUTPUT"


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: wangxiaofei860208-source/lobster-compact (version 1.0.0)

--- name: lobster-compact description: "Summarize long conversations to preserve context. Automatically triggered when context window approaches limits, or manually with /compact." allowed-tools: - read - write - edit - memory_search - memory_get when_to_use: "Use when the conversation becomes very long and context may be lost. Examples: 'summarize so far', 'compact', '我们聊了太多了', '总结一下'." --- # Compact — 长会话压缩 ## Inputs - `$args`: Optional focus area for the summary ## Goal Create a detailed summary of the conversation so far that preserves all critical context for continuing work. ## Steps ### 1. Analyze the Conversation Chronologically analyze each exchange: - User's explicit requests and intents - Approach taken to address requests - Key decisions, technical concepts, code patterns - Specific details: file names, code snippets, function signatures - Errors encountered and how they were fixed - User feedback and corrections ### 2. Generate Summary Write a summary with these sections: ```markdown # 会话摘要 ## 1. 主要请求和意图 [用户的核心需求] ## 2. 关键技术概念 [涉及的技术、框架、工具] ## 3. 文件和代码 [涉及的文件和关键代码片段] ## 4. 错误和修复 [遇到的问题及解决方案] ## 5. 用户反馈 [用户给出的指导、纠正、偏好] ## 6. 待办任务 [尚未完成的任务] ## 7. 当前工作 [最近在做什么，精确到文件和代码] ## 8. 下一步 [紧接着应该做什么] ``` ### 3. Update Memory - Save critical long-term info to MEMORY.md - Save today's log to memory/YYYY-MM-DD.md - Use `memory_search` to avoid duplicates **Success criteria**: Summary captures all critical context; memory files updated.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: alexdavidswift/google-jules-cli (version 1.0.0)

--- name: jules-tools-skill version: 1.0.0 description: "Interface with Google's Jules Tools CLI to manage AI coding sessions." permissions: exec: - jules - npm --- # Jules Tools Skill This skill allows the AI agent to interface with the **Jules Tools CLI** to manage Google's Jules AI coding sessions. With this skill, the agent can start new coding sessions, list active sessions, and retrieve results directly from the terminal. ## Prerequisites Before using any Jules commands, ensure the `jules` CLI is installed and authenticated. ### 1. Installation Check if `jules` is installed by running: ```bash jules --version ``` If the command is not found, install it using `npm`: ```bash npm install -g @google/jules ``` > **Note:** Installation might require `sudo` permissions depending on the system configuration. If `npm install -g` fails due to permissions, try `sudo npm install -g @google/jules` or ask the user for assistance. ### 2. Authentication The agent must be authenticated to interact with Jules. To authenticate, run: ```bash jules login ``` This command will open a browser window for the user to sign in with their Google account. If the agent is running in a headless environment, guide the user to perform this step on their local machine or provide alternative authentication methods if available (refer to `jules login --help`). To verify authentication or log out, use: ```bash jules logout ``` ## Usage The primary command for interacting with Jules is `jules remote`. ### List Sessions To see all active or past coding sessions: ```bash jules remote list --session ``` To list connected repositories: ```bash jules remote list --repo ``` ### Start a New Session To start a new coding session (task) for Jules: ```bash jules remote new --repo <repo_name> --session "<task_description>" ``` - `<repo_name>`: The repository name (e.g., `torvalds/linux`) or `.` for the current directory's repo. - `<task_description>`: A clear description of what Jules should do (e.g., "Fix the bug in the login handler"). **Example:** ```bash jules remote new --repo . --session "Add a new test case for the user profile component" ``` You can also start multiple parallel sessions: ```bash jules remote new --repo . --session "Refactor the database schema" --parallel 2 ``` ### Retrieve Session Results Once a session is complete, you can pull the results (code changes): ```bash jules remote pull --session <session_id> ``` - `<session_id>`: The ID of the session you want to pull (obtained from `jules remote list`). ### General Help For more information on any command: ```bash jules --help jules remote --help ``` ## Troubleshooting - **Command not found**: Ensure `jules` is in the system PATH after installation. You may need to restart the shell or source the profile. - **Authentication errors**: Try running `jules logout` and then `jules login` again. - **Network issues**: Ensure the agent has internet access to reach Google's servers.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: zhangifonly/maimai (version 1.0.0)

--- name: "脉脉" version: "1.0.0" description: "脉脉职场助手，精通职场社交、简历优化、行业洞察、人脉拓展" tags: ["career", "social", "networking", "job"] author: "ClawSkills Team" category: "social" --- # 脉脉职场社交 AI 助手 你是一个资深的脉脉职场社交专家，精通个人品牌打造、简历优化、职场社交技巧和行业洞察分析。你能帮助职场人提升个人影响力、拓展优质人脉、把握职业发展机会。 ## 身份与能力 - 精通脉脉平台运营：个人主页优化、内容创作、人脉拓展 - 擅长简历优化：STAR 法则、关键词优化、ATS 友好格式 - 熟悉职场社交技巧：破冰话术、人脉维护、商务沟通 - 掌握行业洞察分析：薪资趋势、跳槽时机、行业动态 - 了解脉脉社区文化：匿名区生态、职言规则、内容调性 ## 个人品牌打造 ### 脉脉主页优化清单 | 模块 | 优化要点 | 示例 | |------|----------|------| | **头像** | 职业照，正面微笑，背景干净 | 避免生活照、风景照、卡通头像 | | **职业标签** | 突出核心能力，3-5 个关键词 | "10年产品经理 / SaaS / 增长策略" | | **个人简介** | 一句话说清你是谁、擅长什么 | "专注 B2B SaaS 产品，从 0 到 1 打造过 3 款百万级产品" | | **工作经历** | 量化成果，突出亮点 | "带领 20 人团队，年营收增长 150%" | | **教育背景** | 学校 + 专业 + 亮点活动 | 知名院校可突出，普通院校突出专业能力 | ### 职场人设定位 四种常见人设类型： 1. **行业专家型**：深耕某一领域，输出专业洞察和方法论 2. **成长记录型**：分享职场成长经历，引发共鸣 3. **资源链接型**：分享行业资源、内推机会，做连接者 4. **观点输出型**：对行业热点发表独到见解，引发讨论 ### 内容创作策略 高互动内容类型排名： | 内容类型 | 互动率 | 适合人群 | 示例主题 | |----------|--------|----------|----------| | **职场干货** | ★★★★★ | 行业专家 | "产品经理必备的 10 个数据分析方法" | | **行业洞察** | ★★★★☆ | 资深从业者 | "2026 年 AI 行业薪资趋势分析" | | **职场故事** | ★★★★☆ | 所有人 | "从外包到大厂，我用了 3 年" | | **求职经验** | ★★★★☆ | 求职者/HR | "面了 30 家公司总结的面试避坑指南" | | **热点评论** | ★★★☆☆ | 观点型 | "如何看待 XX 公司裁员事件" | 发布节奏建议：每周 2-3 篇，工作日早 8-9 点或午休 12-13 点发布效果最佳。 ## 简历优化 ### STAR 法则 每段工作经历用 STAR 法则描述核心成果： - **S（Situation）**：什么背景/挑战 - **T（Task）**：你的职责/目标 - **A（Action）**：你采取了什么行动 - **R（Result）**：取得了什么量化成果 示例： ``` ❌ 负责公司产品的用户增长工作 ✅ 面对产品日活从 50 万下滑至 30 万的困境（S）， 作为增长负责人带领 5 人团队（T）， 搭建了用户分层运营体系，设计了 3 套召回策略（A）， 6 个月内将日活恢复至 80 万，留存率提升 25%（R） ``` ### 关键词优化 简历关键词来源： - 目标岗位 JD 中的高频词汇 - 行业通用技能术语 - 工具和技术栈名称 - 管理能力相关词汇（带团队、跨部门协作） ### 简历常见问题 | 问题 | 优化建议 | |------|----------| | 职责描述而非成果 | 每条经历必须有量化数据 | | 经历过多过杂 | 只保留与目标岗位相关的 3-5 段 | | 缺少关键词 | 对照 JD 补充行业术语 | | 格式混乱 | 统一字体、对齐、间距 | | 自我评价空洞 | 删除或改为具体能力标签 | ## 职场社交技巧 ### 破冰话术模板 场景一：想认识行业大佬 ``` "XX 老师您好，我是 [公司] 的 [职位]， 拜读了您关于 [具体话题] 的分享，非常受启发。 特别是 [具体观点] 这个点，和我目前在做的 [项目] 很相关， 想请教一下您在这方面的经验，方便交流吗？" ``` 场景二：想内推求职 ``` "您好，我注意到贵司在招 [岗位]， 我在 [领域] 有 X 年经验，曾在 [公司] 负责 [项目]， 取得了 [量化成果]。冒昧打扰，想了解一下这个岗位的具体情况， 如果合适的话，能否帮忙内推？附上我的简历供参考。" ``` 场景三：日常人脉维护 ``` "XX 好久不见！看到你最近分享的 [内容]，写得真好。 最近我们团队也在做类似的事情，有机会线下聊聊？" ``` ### 人脉维护法则 - **定期互动**：每周花 15 分钟给重要联系人的动态点赞评论 - **价值输出**：看到对方可能感兴趣的文章/机会主动分享 - **节日问候**：春节、中秋等节点发送个性化祝福（非群发） - **线下见面**：每季度至少约 2-3 位重要人脉线下交流 ### 社交礼仪 | 场景 | 建议 | 避免 | |------|------|------| | 初次联系 | 说明来意，简洁有礼 | 上来就推销或求帮忙 | | 请教问题 | 先做功课，问具体问题 | 问太宽泛的问题浪费对方时间 | | 内推请求 | 附简历，说明匹配度 | 只说"帮我内推"不提供信息 | | 被拒绝 | 礼貌感谢，保持联系 | 纠缠或表达不满 | ## 行业洞察 ### 薪资谈判技巧 1. **调研市场行情**：通过脉脉薪资查询、职级对标了解目标薪资范围 2. **量化个人价值**：用数据说明你能带来的价值 3. **谈判时机**：拿到 offer 后、年度调薪前是最佳时机 4. **报价策略**：报期望薪资的 110-120%，留出谈判空间 5. **全面考虑**：除基本薪资外，关注股票期权、年终奖、福利 ### 跳槽时机判断 适合跳槽的信号： - 连续 2 年没有晋升或加薪 - 当前工作无法提供新的成长空间 - 行业下行，公司前景不明朗 - 收到明显高于当前的 offer - 团队/领导变动导致工作环境恶化 不建议跳槽的情况： - 入职不满 1 年（简历不好看） - 没有明确的下家方向 - 仅因为短期情绪波动 - 行业整体不景气，外部机会少 ### 脉脉匿名区使用建议 - 发布内容注意脱敏，避免暴露个人身份 - 不要发布公司机密信息，可能涉及法律风险 - 理性看待匿名区信息，存在夸大和偏见 - 可以用来了解行业薪资水平和公司口碑 - 避免参与人身攻击和恶意中伤


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: codekungfu/free-weather-skill (version 0.1.0)

--- name: weather description: Get current weather and forecasts (no API key required). homepage: https://wttr.in/:help metadata: {"clawdbot":{"emoji":"🌤️","requires":{"bins":["curl"]}}} --- # Weather Two free services, no API keys needed. ## wttr.in (primary) Quick one-liner: ```bash curl -s "wttr.in/London?format=3" # Output: London: ⛅️ +8°C ``` Compact format: ```bash curl -s "wttr.in/London?format=%l:+%c+%t+%h+%w" # Output: London: ⛅️ +8°C 71% ↙5km/h ``` Full forecast: ```bash curl -s "wttr.in/London?T" ``` Format codes: `%c` condition · `%t` temp · `%h` humidity · `%w` wind · `%l` location · `%m` moon Tips: - URL-encode spaces: `wttr.in/New+York` - Airport codes: `wttr.in/JFK` - Units: `?m` (metric) `?u` (USCS) - Today only: `?1` · Current only: `?0` - PNG: `curl -s "wttr.in/Berlin.png" -o /tmp/weather.png` ## Open-Meteo (fallback, JSON) Free, no key, good for programmatic use: ```bash curl -s "https://api.open-meteo.com/v1/forecast?latitude=51.5&longitude=-0.12&current_weather=true" ``` Find coordinates for a city, then query. Returns JSON with temp, windspeed, weathercode. Docs: https://open-meteo.com/en/docs


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

--- name: tiger-trading version: 1.0.0 description: 老虎证券美股交易能力。支持账户余额查询、持仓查询、买卖下单、订单管理。用户只需提供 tiger_id、account、license 和 private_key 即可使用。触发场景：(1) 查询老虎账户状态 (2) 买卖美股 (3) 查看持仓 (4) 取消订单 --- # Tiger Trading Skill 使用 Tiger 客户端进行美股交易。 ## 快速开始 用户提供以下信息即可使用： - `tiger_id`: Tiger ID - `account`: 账户ID - `license`: 许可证 (通常为 TBNZ) - `private_key`: 私钥内容或私钥文件路径 ## 使用方式 ### 1. 初始化客户端 ```python import sys sys.path.insert(0, 'skills/tiger-trading/scripts') from tiger_client import TigerClient # 方式1: 使用私钥文件路径 client = TigerClient( tiger_id='YOUR_TIGER_ID', account='YOUR_ACCOUNT_ID', license='TBNZ', private_key='/path/to/private_key.pem' ) # 方式2: 使用私钥内容 client = TigerClient( tiger_id='YOUR_TIGER_ID', account='YOUR_ACCOUNT_ID', license='TBNZ', private_key='MIICXAIBAAKBgQ...' ) ``` ### 2. 查询功能 ```python # 查询账户 client.get_account() # 查询持仓 client.get_positions() # 查询余额 client.get_balance() # 查询订单 (传入状态列表过滤) client.get_orders() # 所有订单 ``` ### 3. 交易功能 ```python # 限价买单 client.place_order( symbol='AAPL', side='buy', quantity=100, order_type='LMT', # LMT=限价单, MKT=市价单 price=150.0 ) # 市价卖单 client.place_order( symbol='AAPL', side='sell', quantity=50, order_type='MKT' ) ``` ### 4. 订单管理 ```python # 取消订单 client.cancel_order(order_id='123456') ``` ## CLI 用法 ```bash # 余额查询 python skills/tiger-trading/scripts/tiger_client.py \ --tiger-id YOUR_TIGER_ID \ --account YOUR_ACCOUNT_ID \ --license TBNZ \ --private-key /path/to/private_key.pem balance # 持仓查询 python skills/tiger-trading/scripts/tiger_client.py \ --tiger-id YOUR_TIGER_ID \ --account YOUR_ACCOUNT_ID \ --license TBNZ \ --private-key /path/to/private_key.pem positions # 下单 python skills/tiger-trading/scripts/tiger_client.py \ --tiger-id YOUR_TIGER_ID \ --account YOUR_ACCOUNT_ID \ --license TBNZ \ --private-key /path/to/private_key.pem order \ --symbol AAPL --side buy --quantity 100 --price 150.0 ``` ## 返回格式示例 ### 余额 ```json { "success": true, "balance": { "cash": 100000.0, "buying_power": 400000.0, "net_liquidation": 100000.0, "unrealized_pnl": 0.0, "currency": "USD" } } ``` ### 持仓 ```json { "success": true, "positions": [ { "symbol": "AAPL", "quantity": 100, "avg_cost": 150.0, "market_value": 15000.0, "unrealized_pnl": 0.0, "unrealized_pnl_percent": 0.0 } ] } ``` ## 注意事项 1. 私钥支持文件路径或直接内容两种方式 2. 默认使用模拟盘环境 (license=TBNZ) 3. order_type: LMT=限价单, MKT=市价单 4. 真实账户需要提供真实的 license 和账户信息


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: shunsukehayashi/miso (version 0.1.3)

# Mission Control - MISO ## Overview **MISO** is a Telegram-native mission control for OpenClaw multi-agent workflows. It standardizes visibility for parallel work so operators can track progress from the chat list. ## State model `INIT` → `RUNNING` → `PARTIAL` → `AWAITING APPROVAL` → `COMPLETE` (+ `ERROR`) State reactions: - `🔥` : INIT / RUNNING / PARTIAL - `👀` : AWAITING APPROVAL - `🎉` : COMPLETE - `❌` : ERROR ## Message format (required) Use plain text, no code blocks. - Left aligned - Keep this frame: - `🤖 MISSION CONTROL` - `——————————————` - `🌸 powered by miyabi` Template: 🤖 MISSION CONTROL —————————————— 📋 {mission} ⏱ {elapsed} ∣ 🧩 {done}/{total} agents ∣ {state} - Issue: #{issue-number} - Owner: SHUNSUKE AI - Goal: {goal} ↳ {agent-a}: {status-a} ↳ {agent-b}: {status-b} ↳ {agent-c}: {status-c} - Next: {next action} —————————————— 🌸 powered by miyabi ## Commands Comment on Issue with: - `/agent analyze` - `/agent execute` - `/agent review` - `/agent status` - `/task-start` - `/task-plan` - `/task-close` ## /task-start /task-start - Owner: SHUNSUKE AI - Issue/Context: #<issue-number> - Goal: <one-sentence objective> - Scope: <files/areas> - Completion Criteria: <what defines done> - Risk: <none|low|medium|high> ## /task-plan /task-plan Execution plan: - issue-analysis - agent-execution (or agent-teams / ai-triad) - git-workflow - debugging-troubleshooting ## /task-close /task-close - Implemented: <summary> - Validation: <tests/checks passed> - Changes: <files changed> - Risks / next steps: <follow-up> - Notify: pushcut / telegram-buttons ## Reproducibility rules 1. Same header/footer for all missions. 2. Keep state and status updates deterministic. 3. Include `Issue`, `Goal`, `Status`, `Next action` every update. 4. For approvals, use explicit AWAITING state and user action. 5. On completion/error, close each mission with state summary and artifacts.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (CRITICAL)
Skill: davieyang/springboot-standardizer (version 1.0.0)

--- name: springboot-standardizer description: | Java SpringBoot + MyBatis 项目标准化重构工具。用于分析非标准项目结构， 生成标准化目录结构，提供重构迁移方案。支持标准三层架构（Controller → Service → DAO）， 自动识别 Entity/DTO/VO 分层，生成 MyBatis/Redis/Kafka 等标准配置模板。 使用场景： - "把项目整理成标准 SpringBoot 结构" - "重构这个 Java 项目" - "标准化项目目录" - "生成 SpringBoot 标准配置" - "检查项目结构是否规范" 触发关键词：springboot 标准化、项目重构、整理项目结构、mybatis 配置、 生成标准目录、Java 项目规范、三层架构整理 --- # SpringBoot 项目标准化工具 ## 功能概述 将非标准的 SpringBoot + MyBatis 项目重构为业界标准结构。 ## 标准项目结构 ``` src/main/java/com/{company}/{project}/ ├── controller/ # REST API 控制器 │ └── UserController.java ├── service/ # 业务层接口 │ ├── UserService.java │ └── impl/ # 业务层实现 │ └── UserServiceImpl.java ├── dao/ # 数据访问层（Mapper 接口） │ └── UserMapper.java ├── entity/ # 数据库实体类 │ └── User.java ├── dto/ # 数据传输对象（API 入参） │ ├── UserCreateDTO.java │ └── UserUpdateDTO.java ├── vo/ # 视图对象（API 出参） │ └── UserVO.java ├── config/ # 配置类 │ ├── MybatisConfig.java │ ├── RedisConfig.java │ └── KafkaConfig.java └── util/ # 工具类 └── JsonUtil.java src/main/resources/ ├── mapper/ # MyBatis XML 映射文件 │ └── UserMapper.xml ├── application.yml # 主配置文件 ├── application-dev.yml # 开发环境配置 └── application-prod.yml # 生产环境配置 ``` ## 工作流程 ### 1. 项目扫描分析 首先扫描现有项目，识别当前结构问题： ```bash python scripts/analyze_project.py <项目路径> ``` 输出报告包括： - 当前目录结构 - 识别出的问题（如类放错位置、命名不规范） - 建议的迁移方案 ### 2. 生成标准结构 生成标准目录结构和配置文件： ```bash python scripts/generate_structure.py <输出路径> --package com.company.project ``` ### 3. 配置文件模板 参考 `references/` 目录下的标准配置模板： - `mybatis-config.md` — MyBatis 配置指南 - `redis-config.md` — Redis 配置模板 - `kafka-config.md` — Kafka 配置模板 - `naming-conventions.md` — 命名规范 ### 4. 项目骨架模板 `assets/project-template/` 包含可直接使用的标准项目骨架。 ## 使用方式 ### 场景一：分析现有项目 1. 运行分析脚本扫描项目 2. 查看分析报告 3. 根据建议手动或自动重构 ### 场景二：创建新项目 1. 复制 `assets/project-template/` 作为起点 2. 修改包名和配置 3. 开始开发 ### 场景三：生成配置模板 根据需要读取 `references/` 中的配置模板，应用到项目中。 ## 命名规范 ### 包命名 - 根包：`com.{公司}.{项目}` - 子包按层划分：controller, service, dao, entity, dto, vo, config, util ### 类命名 - Controller：`XxxController` - Service 接口：`XxxService` - Service 实现：`XxxServiceImpl` - Mapper：`XxxMapper` - Entity：`Xxx`（对应表名，驼峰命名） - DTO：`XxxDTO` / `XxxCreateDTO` / `XxxUpdateDTO` - VO：`XxxVO` - Config：`XxxConfig` ### 方法命名 - Controller：HTTP 方法对应（getXxx, createXxx, updateXxx, deleteXxx） - Service：业务语义（findXxx, saveXxx, updateXxx, deleteXxx） - Mapper：数据库操作（selectXxx, insertXxx, updateXxx, deleteXxx）


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: abdullah944/pixel-art-prompt-builder-skill (version 0.1.0)

--- name: "Pixel Art Prompt Builder Skill" version: 0.1.0 slug: "pixel-art-prompt-builder-skill" description: "Guides structured help for Pixel Art Prompt Builder using clear templates, checks, and safe defaults (category: Art & Assets)." category: "Art & Assets" tags: - "art" - "openclaw" - "pixel-art-prompt-builder" - "templates" generated: "2026-04-28" --- ## Purpose Guides structured help for Pixel Art Prompt Builder using clear templates, checks, and safe defaults (category: Art & Assets). ## When to use - When you want structured guidance in the "Art & Assets" area. - When you need copy-paste-safe templates rather than improvised shell commands. - When you want repeatable prompts the agent can follow without external scraping. ## Safety rules - Do not collect passwords, OTPs, private keys, wallets, seeds, or session secrets. - Do not propose remote installers that execute unseen code or chained download-and-run snippets. - Keep outputs factual and reversible: prefer checklists over irreversible destructive actions. ## Inputs - Your goal in one paragraph (no secrets). - Optional constraints: audience, tone, length, deadline. - Optional pasted notes you own the rights to (keep PII minimal). ## Output format - A concise plan - Numbered checklist - Short next-actions list - Optional draft copy blocks you can edit ## Example prompts - Help me outline a concise plan using the Pixel Art Prompt Builder approach. - Critique my draft outputs and suggest safer, clearer wording for Pixel Art Prompt Builder. - Produce a checklist I can reuse weekly for Pixel Art Prompt Builder without requesting private data. ## Support / Donate If this skill helps your workflow, you can support maintenance here: - PayPal: https://www.paypal.com/donate/?hosted_button_id=MJHCRZA9Z4X7Y


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