OpenClaw/clawhub-security-signals huggingface dataset:
Skill: gigshow/decker-hyperliquid (version 1.1.0)

--- name: decker-hyperliquid description: "Use when user asks about Hyperliquid DEX trading via Decker. Triggers: HL, 하이퍼리퀴드, DEX, 영구선물, HL 매수, HL 포지션, Hyperliquid 시세. Includes Safety Guidelines (position sizing, slippage)." user-invocable: true metadata: version: 1.1.0 extends: decker --- # Decker + Hyperliquid (DEX) 스킬 ## Goal Decker를 통해 **Hyperliquid DEX**에서 시세 조회·주문 실행. 메인 decker 스킬을 확장. ## Quick Reference | 사용자 말 | 액션 | 비고 | |-----------|------|------| | "HL BTC 0.01 매수해줘", "Hyperliquid에서 이더 매수" | order-request **exchange_id=hyperliquid** | 승인 플로우 | | "HL 시세", "Hyperliquid BTC 가격" | Assistant API 또는 시세 조회 | | | "HL 포지션", "Hyperliquid 포지션" | Assistant API | JWT 필요 | ## DECKER_API_URL https://api.decker-ai.com ## 주문 (Hyperliquid) **order-request에 exchange_id=hyperliquid 추가**: ``` GET {DECKER_API_URL}/api/v1/link/slack/order-request?slack_user_id={sender_id}&symbol=BTC&side=buy&quantity=0.01&exchange_id=hyperliquid&openclaw_secret={OPENCLAW_SECRET} ``` - **exchange_id=hyperliquid** 필수 (Hyperliquid DEX 실행) - symbol: BTC, ETH 등 (USDT 선물 자동) - quantity: 계약 수량 ## 전제 조건 - Decker 가입 + Slack 연동 - user_settings.exchange_preference = hyperliquid 또는 order 시 exchange_id 지정 - **Hyperliquid 키 연동** (Decker 설정 → 거래소 API 설정) ## Hyperliquid 키 설정 (에이전트 안내용) 1. **API 전용 지갑 생성**: https://app.hyperliquid.xyz/API 접속 → "Create API Wallet" 2. **개인키 백업**: 생성 시 표시되는 개인키(0x로 시작)를 안전하게 저장 (한 번만 표시) 3. **Decker 설정**: 로그인 → 설정 → 거래소 API 설정 → Hyperliquid - API Key: 지갑 주소(0x..., 42자) — 선택 - Secret Key: 개인키(0x..., 64자 이상) — **필수** 4. **거래소 선택**: exchange_preference를 "Hyperliquid"로 설정 후 저장 5. **주문**: "HL BTC 0.01 매수해줘" (Slack/Telegram) ⚠️ API Wallet은 출금 불가, 거래 전용. 메인 지갑과 분리 권장. ## Safety Guidelines (ClawHub hyperliquid-trading 흡수) **주문 실행 전:** 1. 사용자에게 거래 파라미터 확인 (코인, 수량, 방향, 가격) 2. 현재 시세·기존 포지션을 함께 표시 3. 예상 비용/수익 계산 후 안내 **Position sizing:** - 계정 자산의 20% 초과 주문 시 경고 - 잔고 기준 적정 수량 제안 **가격·슬리피지:** - Limit 주문 시 지정가와 현재가 비교 - 지정가가 시장가 대비 5% 이상 이탈 시 오타 가능성 경고 - 시장가 주문 시 슬리피지(5% 등) 안내 ## Error Handling - "Address required" / "Private key required" → Decker 설정에서 Hyperliquid 키 연동 확인 - "Unknown coin" → BTC, ETH 등 지원 심볼 확인 - 네트워크 오류 → API 상태·연결 확인 - **자동 재시도 금지** — 실패 시 사용자 확인 후 재요청 ## 참고 - 메인 decker 스킬: `docs/openclaw_skills/decker/SKILL.md` - Hyperliquid: 탈중앙 영구선물 DEX


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: calvinxhk/botlearn-transtlor (version 1.0.0)

--- name: translator role: Translation Specialist version: 1.0.0 triggers: - "translate" - "translation" - "翻译" - "convert to [language]" - "say this in" - "how do you say" - "localize" --- # Role You are a Translation Specialist. When activated, you produce context-aware, human-level translations that preserve meaning, tone, register, and cultural nuance across language pairs. You maintain terminology consistency throughout documents and adapt content for the target audience while respecting the intent and style of the source material. # Capabilities 1. Translate text between any major language pair with awareness of formal/dynamic equivalence tradeoffs, selecting the appropriate strategy based on text type and purpose 2. Identify and preserve register (formal, informal, technical, literary) across source and target languages, adapting stylistic conventions to target-language norms 3. Build and maintain per-session terminology glossaries to ensure consistent translation of domain-specific terms, brand names, and recurring phrases across long documents 4. Detect culturally bound expressions, idioms, metaphors, and humor, then localize them using target-culture equivalents rather than word-for-word rendering 5. Handle specialized domains (legal, medical, technical, financial, literary) by applying domain-appropriate terminology and conventions 6. Provide translator notes when ambiguity exists in the source, offering alternative renderings with rationale for the chosen translation # Constraints 1. Never produce a literal word-for-word translation when it would result in unnatural or misleading target-language text 2. Never change the factual content, meaning, or intent of the source material during translation 3. Never omit or add information that is not present in or implied by the source text without explicit annotation 4. Never ignore register or formality level — a formal legal document must not read as casual conversation 5. Always flag uncertain translations or ambiguous source passages with translator notes rather than silently guessing 6. Always maintain terminology consistency within a single translation session — the same source term must map to the same target term unless context requires otherwise # Activation WHEN the user requests a translation or language conversion: 1. Analyze the source text to identify language, register, domain, and communicative purpose 2. Establish context and build a terminology base following strategies/main.md 3. Apply translation theory principles from knowledge/domain.md 4. Follow quality practices from knowledge/best-practices.md 5. Verify against knowledge/anti-patterns.md to avoid common translation errors 6. Output the translation with terminology notes and confidence indicators where appropriate


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: hazy2go/agent-defibrillator (version 1.0.1)

--- name: agent-defibrillator description: Watchdog that monitors your AI agent gateway and restarts it when it crashes. Triggers on "install defibrillator", "agent watchdog", "gateway monitor", "auto-restart agent", or "keep agent alive". macOS launchd service with optional Discord notifications. --- # Agent Defibrillator Watchdog service that monitors your AI agent gateway and restarts it when it crashes. ## What It Does - Checks gateway health every 10 minutes - Detects crashes and stale processes - Auto-restarts with cooldown protection - Optional Discord notifications on restart - Detects version mismatches after updates ## Install **Recommended (review code first):** ```bash git clone https://github.com/hazy2go/agent-defibrillator.git cd agent-defibrillator ./install.sh ``` ## Verify ```bash launchctl list | grep defib ``` ## Configure Edit `~/.openclaw/scripts/defibrillator.sh`: | Variable | Default | Description | |----------|---------|-------------| | `DEFIB_GATEWAY_LABEL` | `ai.openclaw.gateway` | launchd service label | | `DEFIB_RETRY_DELAY` | `10` | Seconds between retries | | `DEFIB_MAX_RETRIES` | `3` | Retries before restart | | `DEFIB_COOLDOWN` | `300` | Seconds between restarts | | `DISCORD_CHANNEL` | (empty) | Your channel ID for notifications | ## Commands ```bash # View logs tail -f ~/.openclaw/logs/defibrillator.log # Manual check ~/.openclaw/scripts/defibrillator.sh # Stop watchdog launchctl bootout gui/$(id -u)/com.openclaw.defibrillator # Restart watchdog launchctl kickstart -k gui/$(id -u)/com.openclaw.defibrillator ``` ## Uninstall ```bash launchctl bootout gui/$(id -u)/com.openclaw.defibrillator rm ~/Library/LaunchAgents/com.openclaw.defibrillator.plist rm ~/.openclaw/scripts/defibrillator.sh ``` ## Requirements - macOS (uses launchd) - AI agent running via launchd (OpenClaw, etc.)


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (HIGH)
Skill: spyfree/destiny-fusion-pro (version 1.0.3)

--- name: destiny-fusion-pro description: Premium destiny consultation skill combining Ziwei Doushu and Bazi in one offline workflow. Use when the user wants a flagship, consultation-style report from birth date and time with unified calculation rules, dual-system cross-checking, optional chart images, and polished markdown or JSON deliverables for yearly outlook, decade luck cycles, relationships, career, wealth, and risk themes. --- # Destiny Fusion Pro Generate a **consultation-grade destiny report** by combining **Ziwei Doushu + Bazi** under one consistent calculation standard. Core appeal: - One input, two systems, one unified report - Offline-first and reproducible - Text report is the primary deliverable; chart image is optional enhancement - Suitable for both human-readable consultation and structured automation output ## Recommended Command ```bash python scripts/fortune_fusion.py \ --date 1990-10-21 \ --time 15:30 \ --gender female \ --year 2026 \ --from-year 2026 \ --years 10 \ --template pro \ --format markdown ``` ## Default Standard - Timezone: `Asia/Shanghai` - Longitude: `120.0` (Beijing standard) - Ziwei engine: `py` - Report priority: text-first; chart export may be attempted when enabled ## Deliverables A strong output should include: 1. Calculation standard (timezone, longitude, unified calculation time) 2. Ziwei full-plate facts (命宫 / 身宫 / 十二宫 / annual transformations) 3. Bazi facts (四柱 / 日主 / 十神 / 藏干 / 大运 / 流年) 4. Cross-system synthesis - personality baseline - career / money / relationship / health themes - current-cycle opportunity and risk boundaries 5. Caution notes about time ambiguity or interpretation limits ## Common Parameters - `--engine py|js|dual`: primary / fallback / dual-engine cross-check - `--template lite|pro|executive`: lighter / standard / premium consulting density - `--chart none|svg|jpg`: chart export mode - `--chart-quality 1-100`: JPG quality, default `92` - `--chart-backend auto|cairosvg`: offline image backend - `--format markdown|json`: final output format ## Output Style Guardrails - Write **fact first, interpretation second, advice last**. - Prefer trend language and probability language; avoid absolute prophecy. - Make cross-system consistency visible: note where Ziwei and Bazi reinforce each other vs diverge. - If chart rendering fails, continue with the text report instead of failing the whole workflow. - If birth time is near a boundary, explicitly recommend dual-plate comparison. ## Scope Boundary - Fully offline; use no web search or headless browser. - Produce analysis only; not medical, legal, or investment advice. - Optional chart export should never block the report. ## References - `references/ziwei-methodology.md` - `references/positioning.md`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: tmstudio667-commits/openclaw-mcp-debugger (version 1.0.0)

--- name: openclaw-mcp-debugger description: "Universal adapter diagnostics for Model Context Protocol (MCP). It automatically detects connection issues between agents and external tools, providing deep-trace debugging for the 2026 Agentic Economy." metadata: { "openclaw": { "emoji": "🛠️" }, "author": "System Architect Zero", "category": "Developer Tools" } --- # OpenClaw MCP Debugger The definitive toolkit for managing complex MCP environments. As AI Agents transition from toys to infrastructure, protocol stability is paramount. This skill provides real-time health checks, latency audits, and automated repair paths for your local MCP servers. ## Features - **Protocol Audit**: Deep inspection of MCP handshakes and binary streams. - **Latency Tracker**: Measures the round-trip time between your LLM and its tools. - **Auto-Fixer**: Automatically restarts crashed MCP servers (e.g., SQLite, Google Search, custom adapters). ## Usage ```bash npx openclaw skill run openclaw-mcp-debugger --all ``` ## Architect's Note Operational excellence is the invisible foundation of successful AI Agents. Built for the Sovereign Protocol.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: happybigmtn/botcoin-miner (version 6.0.2)

# rBitcoin Agent Skill Bitcoin Core fork from genesis, upstream-pinned to official release tags. The only delta is a scope-limited immutable patch for chain identity. ## Quickstart ```bash ./install.sh v30.2 ``` This verifies the upstream release (GPG + checksums), builds with the immutable patch, starts the node, and optionally starts a CPU miner. Override defaults: ```bash MINER_CPU_PERCENT=25 MINER_MAX_THREADS=2 ./install.sh v30.2 ``` ## Environment Variables | Variable | Default | Description | |---|---|---| | `MINER_CPU_PERCENT` | `25` | Max CPU percentage for mining | | `MINER_MAX_THREADS` | `2` | Max miner threads | | `MINER_THREADS` | (auto) | Explicit thread count | | `MINER_BACKGROUND` | `0` | Run miner in background | | `START_MINER` | `1` | Set to `0` to skip miner startup | | `AUTO_ACCEPT_NETWORK_PATCH_HASH` | `1` | Set to `0` for strict patch-hash pinning | | `RPC_ALLOWIP` | `127.0.0.1` | RPC access control | | `RPC_BIND` | `127.0.0.1` | RPC bind address | ## Verify Audit the upstream release and local binary without running a node: ```bash ./scripts/agent_verify.sh v30.2 ``` Outputs a machine-readable report to `reports/agent-verify-v30.2.json`. Verify patch scope stays within the allowed file set: ```bash ./scripts/enforce_patch_scope.sh ./patch/immutable.patch ``` Verify binary provenance against a manifest: ```bash ./scripts/verify_local_binary.sh ./build/bitcoind ./manifests/manifest.json ``` ## Build ```bash ./scripts/build_from_tag.sh v30.2 ``` Fetches the upstream tag, applies the immutable patch, and compiles. The binary lands in `./build/bitcoind`. Generate the update manifest after building: ```bash ./scripts/make_update_manifest.sh v30.2 ``` ## Run ```bash ./scripts/run_node.sh --datadir ~/.rbitcoin --network main ``` RPC defaults to port `19332`, P2P to `19333`. Connect to seed nodes by adding `addnode=<ip>:19333` entries to `~/.rbitcoin/bitcoin.conf`. ## Mine Solo CPU mining with `cpuminer` (sha256d): ```bash ./scripts/start_cpu_miner.sh --datadir ~/.rbitcoin --network main ``` For single-block mining (regtest/dev): ```bash ./scripts/mine_solo.sh --address <ADDRESS> --network regtest ``` ## Update Atomic update to a new upstream tag: ```bash ./scripts/updater.sh v30.3 ``` This builds and verifies the new version, then atomically swaps the `runtime/current` symlink. The previous version is preserved for rollback. Check for the latest upstream release: ```bash ./scripts/fetch_upstream_release.sh ```


Security scan verdicts — ClawScan: clean | static analysis:  | VirusTotal: malicious | SkillSpector: clean (LOW)
Skill: droba07/ms365-mail-calendar (version 1.2.0)

--- name: ms365 description: Microsoft 365 Email & Calendar CLI via Microsoft Graph API. Supports multiple accounts. metadata: {"openclaw":{"emoji":"🟦","requires":{"bins":["node"],"env":["MICROSOFT_CLIENT_ID"]}}} --- # ms365 Microsoft 365 CLI for Email & Calendar via Graph API. Multi-account support. ## Setup (once per account) 1. Register app in Azure Portal → App registrations → New → Public client (mobile & desktop) 2. Enable "Allow public client flows" (Device Code Flow) 3. API permissions: `Mail.Read`, `Mail.Send`, `Calendars.ReadWrite`, `User.Read` 4. Set env: `MICROSOFT_CLIENT_ID=<your-app-id>` and optionally `MICROSOFT_TENANT_ID` 5. Run: `node skills/ms365/index.js --account work login` ## Commands - Login: `node index.js --account work login` - Who am I: `node index.js --account work whoami` - Inbox: `node index.js --account work mail inbox --top 10` - Unread: `node index.js --account work mail unread` - Read: `node index.js --account work mail read <id>` - Send: `node index.js --account work mail send --to [REDACTED_SECRET] --subject "Hi" --body "Hello"` - Search: `node index.js --account work mail search "invoice"` - Calendar: `node index.js --account work calendar --from 2026-04-14T00:00:00Z --to 2026-04-14T23:59:59Z` - Create event: `node index.js --account work calendar-create --subject "Meeting" --start 2026-04-15T10:00 --end 2026-04-15T11:00` ## Multi-account Use `--account <name>` to switch. Each account has separate tokens stored in `~/.openclaw/credentials/`. ## Notes - Device Code Flow — authenticate in browser, no secrets stored - Tokens auto-refresh - Confirm before sending emails


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: lightcastlepro/realtime-interact-overlay (version 1.0.0)

--- name: realtime-interact description: | 实时交互浮窗技能。在需要用户确认、输入或交互的场景中，通过浮窗方式在当前操作界面旁边进行交互， 而不是回到OpenClaw聊天窗口。适用于：(1) 评论内容需要用户确认后执行，(2) 删除文件前需要用户确认， (3) 购物付款时需要输入密码，(4) 任何需要即时交互的场景。支持系统级浮窗和浏览器内浮窗。 metadata: version: "1.0.0" author: "liuyong74" --- # Realtime Interact - 实时交互浮窗 在用户当前操作界面旁边弹出浮窗进行交互，提供流畅的确认/输入体验。 ## 快速开始 ### 浮窗类型 | 场景 | 使用方式 | |------|---------| | 确认框（是/否） | `interact.confirm(title, message)` | | 输入框 | `interact.input(title, message, default)` | | 选择框 | `interact.select(title, options)` | | 自定义HTML | `interact.html(title, html_content)` | ### 基础示例 **1. 评论前确认** ``` 用户：帮我评论这条朋友圈 AI：准备评论内容后，调用浮窗确认 → 浮窗弹出：显示"写的评论内容" → 用户点击"确认" → AI执行评论 ``` **2. 删除文件确认** ``` 用户：帮我删除这个文件 AI：准备删除操作后，调用浮窗确认 → 系统浮窗弹出："确定删除 xxx 吗？" → 用户点击"确认删除" → AI执行删除 ``` **3. 密码输入** ``` 用户：帮我完成支付 AI：准备支付后，调用输入框 → 浮窗弹出：密码输入框 → 用户输入密码 → AI执行支付 ``` ## 技术实现 ### 方式一：macOS 系统浮窗（本地操作） 适用于：删除文件、执行命令等本地操作 ```bash python3 ~/.openclaw/skills/realtime-interact-1.0.0/scripts/macos_dialog.py \ --type confirm \ --title "确认删除" \ --message "确定要删除文件 /path/to/file 吗？" ``` **参数：** - `--type`: confirm | input | select - `--title`: 浮窗标题 - `--message`: 浮窗内容 - `--default`: 默认值（input类型需要） - `--options`: 选项（select类型需要，用逗号分隔） ### 方式二：浏览器内浮窗（网页操作） 适用于：网页评论、购物等浏览器内操作 ```bash # 在当前浏览器页面注入浮窗 python3 ~/.openclaw/skills/realtime-interact-1.0.0/scripts/browser_modal.py \ --action show \ --type confirm \ --title "评论确认" \ --message "确认发送这条评论吗？" ``` ### 方式三：Canvas 覆盖层（通用） 使用 OpenClaw canvas 绘制覆盖层： ```javascript // 通过 JavaScript 注入创建浮窗 // 见 scripts/inject_modal.js ``` ## 浮窗样式 浮窗采用现代美观设计： - 🎨 毛玻璃效果背景 - 📐 居中弹出，带阴影 - 🔘 圆角按钮 - ✨ 流畅动画过渡 ## 交互流程 ``` 1. 用户发起请求（如：评论朋友圈） 2. AI 准备交互内容（评论文案、操作指令等） 3. 判断场景类型： - 本地操作 → macOS 浮窗 - 浏览器操作 → 浏览器内浮窗 - 不确定 → 优先浏览器浮窗 4. 弹出浮窗展示内容 5. 用户确认/输入 6. 返回结果给 AI 7. AI 执行实际操作 8. 反馈结果给用户 ``` ## 错误处理 - 用户取消：返回 `{"result": "cancel"}` - 超时（默认60秒）：返回 `{"result": "timeout"}` - 执行失败：返回 `{"result": "error", "message": "..."}` ## 扩展功能 ### 语音交互（未来） 计划支持： - 语音输入 - 语音确认（"好的"、"确认"） - 语音播报结果 --- **注意**：首次使用需要授权 macOS 辅助功能权限（系统偏好设置 → 安全性与隐私 → 辅助功能）


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (MEDIUM)
Skill: hongjiaping2010-coder/akshare-wrapper (version 1.0.0)

--- name: akshare-wrapper description: A股分析技能包装器，基于akshare数据源。支持实时行情、个股分析、板块轮动、资金流向等A股分析功能。使用自然语言查询A股市场数据。 metadata: openclaw: emoji: "📈" requires: python_modules: ["akshare", "pandas", "numpy"] --- # A股分析技能 (akshare-wrapper) ## 功能特性 - **实时大盘行情**：上证、深证、创业板、沪深300等主要指数 - **个股K线分析**：历史K线数据，支持日线、周线、月线 - **资金流向监控**：个股、板块、市场资金流向分析 - **板块轮动分析**：行业板块、概念板块涨跌排行 - **涨跌停统计**：涨停池、跌停池、连板梯队 - **基本面分析**：财务指标、财报数据、融资融券 - **港股/美股**：跨市场行情数据 - **新闻研报**：财经新闻、机构研报 ## 使用示例 ### 大盘行情 - "A股大盘" - 查看实时指数行情 - "上证指数" - 上证指数实时数据 - "创业板指" - 创业板指数行情 ### 个股分析 - "贵州茅台近30日K线" - 查看个股历史走势 - "茅台资金流向" - 查看个股资金流向 - "茅台怎么样" - 个股综合信息 - "600519周线" - 使用股票代码查询 ### 板块分析 - "行业板块涨跌" - 行业板块表现排行 - "概念板块涨跌" - 概念板块表现排行 - "板块资金流向" - 板块资金净流入排行 ### 市场统计 - "今日涨停" - 涨停跌停统计 - "连板梯队" - 连板股统计 - "炸板率" - 涨停炸板情况 ### 其他功能 - "港股行情" - 港股市场行情 - "美股行情" - 美股市场行情 - "财经新闻" - 最新财经新闻 - "推荐股票" - 股票推荐 ## 技术依赖 ### Python包 ```bash pip install akshare pandas numpy ``` ### 版本要求 - akshare>=1.18.0 - pandas>=3.0.0 - numpy>=2.4.0 ## 快速开始 ### 命令行使用 ```bash cd /root/.openclaw/workspace/skills/akshare-wrapper python3 main.py "A股大盘" ``` ### OpenClaw集成 技能安装后，可在OpenClaw中直接使用自然语言查询： - "帮我看看A股大盘" - "茅台最近走势怎么样" - "今天哪个板块最强" ## 输出格式 技能输出针对聊天平台优化： - 使用emoji增强可读性 - 关键数据突出显示 - 分段清晰，避免信息过载 - 包含数据更新时间戳 ## 性能特点 - **快速响应**：大部分查询2-3秒内返回 - **智能缓存**：重复查询使用缓存提高速度 - **错误处理**：网络异常友好提示 - **超时控制**：长查询自动超时保护 ## 注意事项 ### 数据源 - 数据来自akshare，最终源为新浪财经、东方财富等 - 数据有延迟，非实时Level2数据 - 港股/美股查询可能较慢 ### 使用限制 - 避免短时间内高频查询 - 复杂查询可能需要更长时间 - 非交易时间数据可能不更新 ### 故障处理 1. **查询无响应**：检查网络连接，确认akshare安装 2. **导入错误**：确认python依赖已安装 3. **数据不更新**：检查数据源状态，确认交易时间 ## 高级功能 ### 持仓管理 支持简单的持仓管理功能： - "我的持仓" - 显示当前持仓 - "添加持仓 600519 --cost 10.5 --qty 1000" - 添加持仓 - "持仓分析" - 分析持仓盈亏 ### 股票筛选 基于当前市场情况的股票推荐： - "推荐股票" - 综合推荐 - "半导体股票推荐" - 板块内推荐 ## 更新日志 ### v1.0 (2026-03-11) - 初始版本发布 - 基于akshare-stock技能包装 - 修复导入问题 - 添加统一错误处理 - 优化输出格式 ## 技术支持 ### 问题反馈 如遇问题，请提供： 1. 查询的具体内容 2. 错误信息（如有） 3. 期望的输出 ### 功能建议 欢迎提出新功能建议，包括： 1. 需要新增的数据类型 2. 输出格式改进 3. 性能优化建议 ## 许可证 基于akshare-stock技能，遵循原技能许可证。 --- **技能状态**: ✅ 可用 **最后测试**: 2026-03-11 **维护团队**: 小富AI助手 **推荐用途**: A股市场分析、投资研究、团队协作


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: eveiljuice/claw-guardirails-skill (version 0.1.0)

--- name: guardrails-safe-tools description: Enforces guarded execution with safe_exec, safe_send, and safe_action. Use when a task may run shell commands, send channel messages, or call external APIs/actions that can mutate data or state. --- # Guardrails Safe Tools ## When to Use Apply this skill whenever a request can: - execute shell/system commands; - send outbound messages/posts to channels; - trigger external actions (email, DB, gateways, automation). ## Hard Rules 1. Use `safe_exec` instead of raw `exec`. 2. Use `safe_send` instead of direct channel-post tools. 3. Use `safe_action` for generic external/API side effects. 4. Never bypass the guardrails resolver with direct destructive tools. 5. If decision is `require_approval`, stop and wait for explicit approval flow. ## Input Hygiene - Always provide the narrowest `cwd` for `safe_exec`. - Include sender/channel/agent context when available. - Keep command args explicit; do not hide risky flags in shell expansions. - For `safe_action`, include explicit `resources` where possible. ## Tool Contracts ### `safe_exec` Use for shell commands only after permission resolution. Expected input shape: ```json { "command": "git", "args": ["status"], "cwd": "/workspace/project" } ``` ### `safe_send` Use for outbound channel messages. Expected input shape: ```json { "channel": "telegram:ops-room", "message": "Deployment done", "channelType": "telegram" } ``` ### `safe_action` Use for side-effect actions that are not plain shell or plain chat send. Expected input shape: ```json { "action": "gmail.delete_message", "payload": { "messageId": "..." }, "resources": [ { "kind": "unknown", "value": "email-api", "operation": "delete" } ] } ``` ## Decision Handling - `allow`: continue and return runtime result. - `deny`: return denial with reason code; do not retry with alternate dangerous tools. - `require_approval`: surface approval id/reason and wait for `/approve <id>` or RPC approval. ## Good Defaults - Prefer read-only commands (`git status`, `rg`, `ls`) before mutable ones. - Propose reversible operations first. - Ask for confirmation before destructive intent, even if technically allowed.


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