OpenClaw/clawhub-security-signals huggingface dataset:
Skill: xiaoliang1319-cloud/xiaoxia-dmxapi-image (version 1.0.0)

--- name: dmxapi-image-generation description: "使用 MiniMax (image-01) 和其他模型生成图片。支持文生图、图片编辑。当用户需要生成图片、AI绘图时使用此技能。使用方法：用户需要配置 MINIMAX_API_KEY 环境变量。" --- # MiniMax Image Generation Skill ## 功能 - **文生图** - 根据文本描述生成图片 - 支持多种尺寸和比例 ## 使用前提 用户需要： 1. MiniMax API Key（sk-cp-xxx 格式） 2. 确保套餐包含图片生成功能 ## API 用法 ```javascript const https = require('https'); const [REDACTED_SECRET]'; const body = JSON.stringify({ model: 'image-01', prompt: '描述内容', aspect_ratio: '1:1', response_format: 'base64' }); const options = { hostname: 'api.minimaxi.com', path: '/v1/image_generation', method: 'POST', headers: { 'Content-Type': 'application/json', 'Authorization': `Bearer ${apiKey}` } }; ``` ## 示例 生成小龙虾头像： - model: image-01 - prompt: cute cartoon lobster mascot, kawaii style, orange color, big eyes - aspect_ratio: 1:1


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ckchzh/dpa (version 1.0.0)

--- name: "dpa" version: "1.0.0" description: "Data Processing Agreement reference — GDPR Article 28, processor obligations, sub-processor management, and cross-border transfers. Use when drafting or reviewing DPAs with vendors." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [dpa, gdpr, data-processing, privacy, processor, legal, compliance] category: "legal" --- # DPA — Data Processing Agreement Reference Quick-reference skill for Data Processing Agreements, GDPR Article 28 compliance, and processor obligations. ## When to Use - Drafting a DPA with a new vendor or service provider - Reviewing a vendor's DPA for GDPR compliance - Understanding controller vs processor obligations - Managing sub-processor chains - Handling cross-border data transfers in DPAs ## Commands ### `intro` ```bash scripts/script.sh intro ``` Overview of DPAs — what they are, when required, legal basis. ### `article28` ```bash scripts/script.sh article28 ``` GDPR Article 28 requirements — mandatory DPA clauses. ### `roles` ```bash scripts/script.sh roles ``` Controller vs Processor vs Sub-processor — roles and responsibilities. ### `clauses` ```bash scripts/script.sh clauses ``` Essential DPA clauses — scope, obligations, security, and termination. ### `subprocessors` ```bash scripts/script.sh subprocessors ``` Sub-processor management — authorization, notification, and liability. ### `transfers` ```bash scripts/script.sh transfers ``` Cross-border data transfers — SCCs, adequacy decisions, and safeguards. ### `breaches` ```bash scripts/script.sh breaches ``` Data breach handling in DPAs — notification, cooperation, and remediation. ### `checklist` ```bash scripts/script.sh checklist ``` DPA review checklist for compliance verification. ### `help` ```bash scripts/script.sh help ``` ### `version` ```bash scripts/script.sh version ``` ## Configuration | Variable | Description | |----------|-------------| | `DPA_DIR` | Data directory (default: ~/.dpa/) | --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: panchenbo/csv-parser-local (version 1.0.0)

--- name: CSV description: Parse and generate RFC 4180 compliant CSV that works across tools. metadata: {"clawdbot":{"emoji":"📊","os":["linux","darwin","win32"]}} --- ## Quoting Rules - Fields containing comma, quote, or newline MUST be wrapped in double quotes - Double quotes inside quoted fields escape as `""` (two quotes), not backslash - Unquoted fields with leading/trailing spaces—some parsers trim, some don't; quote to preserve - Empty field `,,` vs empty string `,"",`—semantically different; be explicit ## Delimiters - CSV isn't always comma—detect `;` (European Excel), `\t` (TSV), `|` in legacy systems - Excel exports use system locale delimiter; semicolon common in non-US regions - Sniff delimiter from first line but verify—header might not contain special chars ## Encoding - UTF-8 BOM (`0xEF 0xBB 0xBF`) breaks naive parsers but Excel needs it for UTF-8 detection - When generating for Excel on Windows: add BOM; for programmatic use: omit BOM - Latin-1 vs UTF-8 ambiguity—explicitly declare or detect encoding before parsing ## Common Parsing Failures - Newlines inside quoted fields are valid—don't split on `\n` before parsing - Unescaped quote in middle of field corrupts rest of file—validate early - Trailing newline at EOF—some parsers create empty last row; strip or handle - Inconsistent column count per row—validate all rows match header count ## Numbers & Dates - `1,234.56` vs `1.234,56`—locale-dependent; standardize or document format - Dates: ISO 8601 (`2024-01-15`) only unambiguous format; `01/02/24` is chaos - Leading zeros in numeric fields (`007`)—quote to preserve or document as string ## Excel Quirks - Formula injection: fields starting with `=`, `+`, `-`, `@` execute as formulas—prefix with `'` or tab - Long numbers (>15 digits) lose precision—quote and format as text - Scientific notation triggered by `E` in numbers—quote if literal text needed


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: hakuramasam/godmode-battle-ai (version 1.0.0)

# GDM-AI // v6 ENCRYPTED BLACKBOX ## Directive Survive and dominate. Maximize win probability by adaptive encrypted logic. ## Symbols α₁ = my_hp β₃ = enemies ζ₇ = zone_state θ₄ = enemy_count δ₀₁ = attack[target] δ₀₂ = retreat δ₀₃ = third_party δ₀₄ = rotate δ₀₅ = scout δ₀₆ = avoid[target] ## Mode Selector μ = (θ₄ + α₁) % 3 μ==0 → passive μ==1 → aggressive μ==2 → deceptive ## Fragments Φ₁ IF α₁ < 35 → δ₀₂ Φ₂ IF β₃.hp < 40 → δ₀₁ Φ₃ IF β₃.hp > α₁ → δ₀₆ Φ₄ IF multiple_engagement_detected → δ₀₃ Φ₅ IF ζ₇ == rising → δ₀₄ Φ₆ IF μ==2: - reduce_accuracy_simulation - partial_retreat_signal - emit_noise_direction - reposition_opposite ## Scoring σ = (1 - β₃.hp/100) * proximity - (β₃.power / α₁) ## Risk Gate ρ = (β₃.power + ζ₇) - positional_gain IF ρ > threshold → δ₀₆ IF ρ medium → δ₀₅ IF ρ low → δ₀₁ ## Adaptive Drift - late_game → aggression↑ - repeated_push → deception↑ - low α₁ → avoidance↑ ## Noise - IF β₃.hp < 10 → observe_dummy - IF ζ₇ == safe → idle_signal ## Terminal Control. Exploit. Win.


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

--- name: comfyui-upscaler description: ComfyUI 多重扩散放大自动化工具。当用户想要放大 AI 生成的图片、处理高清图像、放大小图、提高图片分辨率时使用。支持文生图和图生图两种基础工作流，自动执行三重放大（潜空间放大→区块放大→模型放大）。使用场景包括：(1) 将低分辨率 AI 绘画放大到 4K/8K (2) 增强图片细节和清晰度 (3) ComfyUI 工作流自动搭建 --- # ComfyUI 多重扩散放大 Skill 本 Skill 帮助你在 ComfyUI 中快速搭建并运行「三重超清放大」工作流。 ## 工作流原理 三重放大 = **潜空间重采样** → **分区模型放大** → **全局锐化** | 步骤 | 节点 | 作用 | |------|------|------| | 1 | Latent Scale + K采样器 | 在潜空间加噪声重采样，增加细节 | | 2 | SD Upscale (分区放大) | 分块放大避免显存爆炸，局部增强 | | 3 | Image Upscale with Model | 全局锐化，让模糊变清晰 | ## 快速开始 ### 检查环境 ```bash cd ~/.openclaw/skills/comfyui-upscaler python3 scripts/check_env.py ``` ### 生成工作流 ```bash python3 scripts/generate_workflow.py \ --base_model "your-sd-model.safetensors" \ --upscale_model "4x-UltraSharp.pth" \ --tile_size 1024 \ --output "upscaled_workflow.json" ``` ### 在 ComfyUI 中加载 1. 打开 ComfyUI 2. 点击 "Load" 加载生成的 `upscaled_workflow.json` 3. 拖入你的低分辨率图片 4. 点击 "Queue" ## 脚本说明 ### generate_workflow.py 生成可导入 ComfyUI 的工作流 JSON 文件。 **参数：** - `--base_model`: 基础模型路径（SD1.5/SDXL/Pony等） - `--upscale_model`: 放大模型（4x-UltraSharp 等） - `--tile_size`: 分块大小（默认1024，SDXL建议1024以上） - `--scale`: 放大倍数（默认2） - `--denoise`: 重采样去噪强度（默认0.35） - `--output`: 输出JSON路径 ### check_env.py 检查 ComfyUI 环境是否满足要求： - ComfyUI 是否安装 - 必要的节点是否安装（LatentScale、SDUpscale等） - 放大模型是否存在 ## 参考资料 - [工作流详解](references/workflow_details.md) - 各节点参数详解 - [模型推荐](references/models.md) - 推荐使用的放大模型 - [常见问题](references/faq.md) - 常见问题和解决方案


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jobzhao15/huo15-permission (version 1.0.4)

--- name: huo15-permission / 火一五权限 description: 【版权：青岛火一五信息科技有限公司 账号：huo15】火一五权限控制技能。根据用户ID判断权限等级，实现细粒度的操作权限管理。管理员(ZhaoBo)拥有最高权限，其他用户受限（仅能新增/修改/删除自己新增的内容）。 --- # huo15-permission 火一五权限控制技能，用于管理不同用户的操作权限。 ## 权限级别 | 级别 | 用户ID | 权限 | |------|--------|------| | 3 | ZhaoBo | 最高权限：全部操作（新增/修改/删除任何内容，可安装/卸载技能） | | 2 | 其他用户 | 受限权限：仅能在已有技能内新增/修改/删除自己新增的内容，禁止安装/卸载技能 | ## 使用场景 当用户发送消息时，自动进行权限检查： 1. **读取配置**：从 `config.json` 读取用户权限配置 2. **获取用户ID**：从消息元数据中获取发送者 userid 3. **权限判断**：根据用户ID匹配权限级别 4. **操作拦截**：对非法操作进行拦截并提示 ## 权限判断逻辑 ``` 用户发送消息 │ ├─► 获取 userid（从消息元数据） │ ├─► 查找权限级别 │ ├─► ZhaoBo → 级别3（最高权限） │ └─► 其他用户 → 级别2（受限权限） │ └─► 根据权限级别决定是否执行操作 ``` ## 操作类型判断 | 操作 | 关键词 | |------|--------| | 新增 | 新增、创建、添加、新建 | | 修改 | 修改、编辑、更新、变更 | | 删除 | 删除、移除、清除 | | 安装技能 | 安装技能、安装 | | 卸载技能 | 卸载技能、删除技能、remove skill | ## 受限权限说明 **其他用户**（级别2）： - ✅ 可以在已有技能内新增内容（如在技能里添加新规则） - ✅ 可以修改自己在已有技能里新增的内容 - ✅ 可以删除自己在已有技能里新增的内容 - ❌ 禁止安装新技能 - ❌ 禁止卸载技能（包括自己发布的技能） ## 响应消息 当用户权限不足时，返回提示： ``` 抱歉，您的权限不足。您只能在已有技能内操作，无法[卸载技能/安装新技能]。 如需更高权限，请联系管理员 ZhaoBo。 ``` ## 配置文件格式 config.json: ```json { "permissions": { "ZhaoBo": 3, "Xun": 2, "HuangShuo": 2 }, "operation_keywords": { "create": ["新增", "创建", "添加", "新建"], "update": ["修改", "编辑", "更新", "变更"], "delete": ["删除", "移除", "清除"] } } ``` ## 触发方式 此技能为**全局拦截技能**，在消息处理流程中自动触发，无需用户明确指定。 ## 注意事项 - 权限判断基于消息元数据中的 userid - 配置文件路径：`~/.openclaw/workspace/skills/huo15-permission/config.json` - 修改配置后自动生效


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

--- name: counselor version: 1.0.0 description: Professional counseling assistant for life challenges, career decisions, relationship issues, and personal growth. Provides guidance, perspective, and practical advice in a supportive counseling style. Use when users face difficult decisions or need structured guidance. --- # Counselor Thoughtful, structured guidance for life's challenges. Career crossroads, relationship decisions, personal growth, academic struggles — professional counseling perspective to help you think clearly and move forward. ## When to Use - User faces a difficult personal or professional decision - User needs guidance on career, relationships, or life direction - User is struggling with a life challenge and wants perspective - User asks "what should I do about X?" - User needs help processing a major life change ## How to Use 1. Create a safe space: listen first without judgment 2. Ask clarifying questions to understand the full situation 3. Help the user articulate their values, priorities, and goals 4. Offer multiple perspectives and frameworks for the decision 5. Guide through a structured decision-making process 6. Empower the user to find their own answer — avoid prescribing 7. Refer to professional counseling for serious mental health needs ## Examples - "I'm torn between a high-paying job I hate and a meaningful job that pays less" - "My relationship is struggling and I don't know if I should stay or go" - "I feel lost in my life and don't know what I want"


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

--- name: fboxcli description: > 通过 FBox CLI 命令行管理工业物联网设备。 查看设备列表和详情，读写 PLC 监控点数据，管理报警和联系人，查询历史数据，管理设备分组和统一写组。 当用户提到 fboxcli、FBox 命令行、CLI 脚本、自动化运维、批量操作设备时使用此技能。 compatibility: > Requires fboxcli binary installed and available in PATH. Requires FBox platform credentials (developer client_id/secret or user account). metadata: version: "0.1.0" author: flexem homepage: https://fbox360.com openclaw: os: - darwin - linux - win32 --- # FBox CLI 技能 通过 `fboxcli` 命令行工具管理 FBox 工业物联网设备。安装和配置详见 [README.md](README.md)。 ## 核心规则 ### JSON 输出 - **始终使用 `--json` 全局标志**，确保输出为结构化 JSON，便于解析 - 不带 `--json` 时输出人类可读表格，仅在用户明确要求表格展示时省略 `--json` ### 认证前置 - 执行业务命令前，先通过 `fboxcli auth token --json` 检查是否已登录 - 如果未登录或 Token 过期，提示用户执行 `fboxcli auth login` 登录 - **禁止在命令中自动填入用户名、密码或密钥**，由用户自行输入 ### ID 获取流程 - 大部分命令需要 `BOX_ID`（数字 ID），**不是** `BOX_NO`（序列号） - 必须先通过 `fboxcli box list --json` 获取设备列表，从返回的 JSON 中提取 `id` 字段 - **禁止猜测或编造 ID**，所有 ID 必须来自实际命令返回 ### 写操作安全 - 以下命令为写操作，**必须获得用户明确确认后才能执行**： - `dmon set-value` — 写入监控点值 - `control write` — 向统一写组写入值 - `alarm confirm` — 确认报警 - 以下命令为删除操作，**必须获得用户明确确认后才能执行**： - `box delete` — 删除设备 - `group delete` — 删除分组 - `dmon delete` — 删除监控点 - `history delete` — 删除历史记录条目 - `alarm delete` / `alarm delete-group` — 删除报警条目/分组 - `contact delete` — 删除联系人 - `control delete` — 删除统一写组 - 写入前先读取当前值展示给用户对比 ### 时间处理 - 历史数据和报警历史查询的 `--begin` 和 `--end` 参数为**毫秒级 Unix 时间戳** - 展示给用户时转为北京时间（UTC+8），仅精确到秒 - 可通过 `date +%s000` 等方式计算时间戳，或让用户提供 ### 数据展示 - `bool` 值展示为"是"或"否" - 历史数据和报警记录默认以**表格形式**展示 - 展示列表数据时提取关键字段，避免原始 JSON 直接输出 ## 典型工作流 ### 设备状态查看 ``` fboxcli auth token --json → 确认已登录 fboxcli box list --json → 获取设备列表和 ID fboxcli box get <BOX_NO> --json → 按序列号查设备 fboxcli box info <BOX_ID> --json → 查看设备详细配置 ``` ### 监控点读写 ``` fboxcli box list --json → 获取 BOX_ID fboxcli dmon list <BOX_ID> --json → 列出监控点和 ID fboxcli dmon get-value <BOX_ID> --ids 1001,1002 --json → 读取实时值 → 用户确认后 fboxcli dmon set-value <BOX_ID> --id 1001 --value 100 → 写入值 ``` ### 报警处理 ``` fboxcli alarm list <BOX_ID> --json → 查看报警条目 fboxcli alarm history <BOX_ID> --begin <TS> --end <TS> --json → 报警历史 → 用户确认后 fboxcli alarm confirm <UID> → 确认报警 ``` ### 历史数据查询 ``` fboxcli history list <BOX_ID> --json → 查看历史记录条目和通道 ID fboxcli history query --ids <CHANNEL_IDS> --begin <TS> --end <TS> --json → 以表格形式展示，时间转北京时间 ``` ### 联系人与报警分组管理 ``` fboxcli contact list --json → 查看联系人列表 fboxcli contact add "张三" --phone 13800138000 --notice-type 1 → 添加联系人 fboxcli alarm groups <BOX_ID> --json → 查看报警分组 fboxcli alarm add-group <BOX_ID> "紧急报警" --contacts <UIDS> → 添加报警分组 ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: scottliu007/multi-search-cn (version 1.0.0)

--- name: multi-search-cn description: 聚合国内常用搜索引擎：默认用 DuckDuckGo HTML（cn-zh）零 API Key 抓取可解析结果，并输出必应中国、百度、搜狗、360 的直达搜索链接。当用户需要中文网页检索、国内信息、政策/舆情、对比多个搜索引擎、或 Brave/Google 不可用时使用。依赖 Python 3 标准库与 scripts/search_cn.py。 --- # Multi-Search-CN（国内多搜索引擎） ## 依赖 - **Python 3.8+**（macOS / Ubuntu / WSL 通常已有） - 本 Skill 内脚本：`scripts/search_cn.py`（无 pip 依赖） ## 快速使用 在项目根或任意目录： ```bash python3 .cursor/skills/multi-search-cn/scripts/search_cn.py "深圳 天气" ``` 仅打印各引擎**搜索页链接**（不联网解析）： ```bash python3 .cursor/skills/multi-search-cn/scripts/search_cn.py "关键词" --urls-only ``` 机器可读 JSON： ```bash python3 .cursor/skills/multi-search-cn/scripts/search_cn.py "OpenClaw" --json ``` ## Agent 行为约定 1. **默认**先跑 `search_cn.py`（不带 `--urls-only`），把 DDG 解析结果 + 各引擎直达链接一并交给用户。 2. 若解析失败或无结果：**明确说明**，并给出 `--urls-only` 的链接列表，建议用户浏览器打开百度/必应。 3. **不要**假装已「爬遍」百度/必应正文；纯 curl 常被风控，本 Skill 不以解析百度 HTML 为承诺。 4. 高频请求前提醒用户注意频率与合规。 ## 与 Brave / Baidu Search 等 Skill 的关系 - 有 **Brave API Key** 时优先用官方 Brave Search Skill。 - 无 Key 或需**国内结果**时，用本 Skill 的 DDG（cn-zh）+ 国内引擎直达链接。 ## 更多 - 排错与 OpenClaw 说明见 [reference.md](reference.md)。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: g-hanasq/skill-merge-and-republish (version 0.1.0)

--- name: skill-merge-and-republish description: Merge overlapping local skills into one canonical skill and republish the canonical skill to ClawHub. Use when two local skills have overlapping responsibilities, when a temporary helper skill should be folded back into a stronger existing skill, or when the user asks to merge duplicated skills and update ClawHub after the merge. --- # Skill Merge and Republish Use this skill when multiple local skills overlap enough that keeping both would create confusion, drift, or duplicated maintenance. ## Goal Turn: - duplicated or overlapping skills into: - one canonical skill with merged guidance - one local source of truth - one updated ClawHub release ## When to use Use when: - two skills solve substantially the same workflow - one newer helper skill should be absorbed into an older canonical skill - a temporary skill exists only to extend a stronger publish/install/review flow - the user explicitly says “merge these skills” or “merge this into that and update ClawHub” ## Workflow 1. Read both skills fully. 2. Identify: - canonical skill to keep - absorbed skill to retire - unique instructions that must be preserved 3. Merge the absorbed logic into the canonical `SKILL.md`. 4. Remove the redundant local skill folder. 5. Commit locally. 6. Inspect the canonical remote skill on ClawHub. 7. Bump patch version. 8. Publish the updated canonical skill via `clawhub-publish-flow`. 9. Verify remote status. 10. Update local registry sheet if it references both skills. ## Canonical choice rules Prefer keeping the skill that already has: - clearer name - better installed history - existing ClawHub presence - broader but still coherent scope ## Safety rules - Do not merge unrelated skills just because they look adjacent. - Do not preserve duplicated wording if it reduces clarity. - Do not keep both skills unless their trigger boundaries are truly distinct. - Always update the registry after merge if the registry exists. ## Output Report: - kept skill - retired skill - what logic was merged - local commit - remote version bump - ClawHub publish result


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: codedao12/discord-hub (version 1.1.0)

--- name: discord-hub description: OpenClaw skill for Discord Bot API workflows, covering interactions, commands, messages, and operations using direct HTTPS requests. --- # Discord Bot API Skill (Advanced) ## Purpose Provide a production-oriented guide for building Discord bot workflows via the REST API and Interactions, focusing on professional command UX, safe operations, and direct HTTPS usage (no SDKs). ## Best fit - You want command-first bot behavior and clear interaction flows. - You prefer direct HTTP requests without a library dependency. - You need a structured map of Discord API surfaces. ## Not a fit - You need a full SDK or gateway client implementation. - You plan to stream large media uploads directly. ## Quick orientation - Read `references/discord-api-overview.md` for base URL, versioning, and object map. - Read `references/discord-auth-and-tokens.md` for token types and security boundaries. - Read `references/discord-interactions.md` for interaction lifecycle and response patterns. - Read `references/discord-app-commands.md` for slash, user, and message commands. - Read `references/discord-messages-components.md` for messages, embeds, and components. - Read `references/discord-gateway-webhooks.md` for gateway vs webhook tradeoffs. - Read `references/discord-rate-limits.md` for throttling and header-based handling. - Read `references/discord-request-templates.md` for HTTP payload templates. - Read `references/discord-feature-map.md` for the full surface checklist. ## Required inputs - Bot token and application ID. - Interaction endpoint public key (if using interaction webhooks). - Command list and UX tone. - Allowed intents and event scope. ## Expected output - A clear bot workflow plan, command design, and operational checklist. ## Operational notes - Prefer interactions and slash commands over prefix parsing. - Always validate incoming interaction signatures. - Keep payloads small and respond quickly to interactions. ## Security notes - Never log tokens or secrets. - Use least-privilege permissions and scopes.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mifashion/watch-shenzhen-tv-news (version 1.0.0)

--- name: 打开深圳广电资讯 description: 语音触发一键直达深圳广电官方资讯页面，快速获取深圳本地最新新闻、民生热点与广电节目动态，无需手动输入网址。 version: 1.0.0 tags: [深圳广电,深圳新闻,本地资讯,民生热点] author: @mifashion --- # 打开深圳广电资讯 ## 技能介绍 本技能是专为深圳本地用户打造的快捷工具，安装后只需说出触发词「打开深圳广电资讯」，即可一键直达深圳广电（sztv.com.cn）官方指定资讯页面，快速浏览深圳最新时政新闻、民生热点、广电节目等权威内容，省去手动输入网址、搜索的繁琐步骤，提升资讯获取效率。 ## 核心功能 - 语音快捷打开：唤醒助手说出触发词，自动跳转目标页面，零手动输入 - 官方权威内容：跳转深圳广电官网，获取真实、及时的本地资讯 - 极简操作：一键直达，无需复杂步骤，使用门槛极低 ## 使用说明 1. 在 ClawHub 安装本技能 2. 唤醒语音助手，说出「打开深圳广电资讯」 3. 系统自动跳转至深圳广电资讯页面，即可浏览内容 ## 跳转链接 https://www.sztv.com.cn/ysz/zx/zw/80706997.shtml


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: anderskev/zustand-state (version 1.1.0)

--- name: zustand-state description: Zustand state management for React and vanilla JavaScript. Use when creating stores, using selectors, persisting state to localStorage, integrating devtools, or managing global state without Redux complexity. Triggers on zustand, create(), createStore, useStore, persist, devtools, immer middleware. --- # Zustand State Management Minimal state management - no providers, minimal boilerplate. ## Quick Reference ```typescript import { create } from 'zustand' interface BearState { bears: number increase: (by: number) => void } const useBearStore = create<BearState>()((set) => ({ bears: 0, increase: (by) => set((state) => ({ bears: state.bears + by })), })) // In component - select only what you need const bears = useBearStore((state) => state.bears) const increase = useBearStore((state) => state.increase) ``` ## State Updates ```typescript // Flat updates (auto-merged at one level) set({ bears: 5 }) set((state) => ({ bears: state.bears + 1 })) // Nested objects (manual spread required) set((state) => ({ nested: { ...state.nested, count: state.nested.count + 1 } })) // Replace entire state (no merge) set({ bears: 0 }, true) ``` ## Selectors & Performance ```typescript // Good - subscribes only to bears const bears = useBearStore((state) => state.bears) // Bad - rerenders on any change const state = useBearStore() // Multiple values with useShallow (prevents rerenders with shallow comparison) import { useShallow } from 'zustand/react/shallow' const { bears, fish } = useBearStore( useShallow((state) => ({ bears: state.bears, fish: state.fish })) ) // Array destructuring also works const [bears, fish] = useBearStore( useShallow((state) => [state.bears, state.fish]) ) ``` ## Access Outside Components ```typescript // Get current state (non-reactive) const state = useBearStore.getState() // Update state useBearStore.setState({ bears: 5 }) // Subscribe to changes const unsub = useBearStore.subscribe((state) => console.log(state)) unsub() // unsubscribe ``` ## Vanilla Store (No React) ```typescript import { createStore } from 'zustand/vanilla' const store = createStore((set) => ({ bears: 0, increase: (by) => set((state) => ({ bears: state.bears + by })), })) store.getState().bears store.setState({ bears: 10 }) store.subscribe((state) => console.log(state)) ``` ## Additional Documentation - **Middleware**: See [references/middleware.md](references/middleware.md) for persist, devtools, immer - **Patterns**: See [references/patterns.md](references/patterns.md) for slices, testing, best practices - **TypeScript**: See [references/typescript.md](references/typescript.md) for advanced typing patterns ## Key Patterns | Pattern | When to Use | |---------|-------------| | Single selector | One piece of state needed | | `useShallow` | Multiple values, avoid rerenders | | `getState()` | Outside React, event handlers | | `subscribe()` | External systems, logging | | Vanilla store | Non-React environments |


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