OpenClaw/clawhub-security-signals huggingface dataset:
Skill: miniade/miniade-agent-lifecycle-manager (version 0.1.2)

--- name: agent-lifecycle-manager description: "Manage full OpenClaw agent lifecycle operations on a node: create/register agents, configure channel bindings, optionally inherit credentials with explicit consent, approve pairing, archive and delete agents, refresh status dashboards, and write lifecycle change logs. Use when a user asks to onboard a new agent, reconfigure an existing agent, retire/archive/delete agents, or maintain agent status boards and lifecycle audit records." metadata: { "openclaw": { "emoji": "🛠️", "requires": { "bins": ["openclaw", "jq"] } } } --- # Agent Lifecycle Manager Use this skill to execute repeatable, low-error lifecycle operations for OpenClaw agents. ## Workflow 1. Collect required inputs 2. Run lifecycle action (create/configure/archive/delete/status) 3. Verify runtime status (`openclaw status`, `openclaw agents list`) 4. Refresh dashboard files 5. Append lifecycle log entry If deleting an agent, always archive first and require explicit confirmation. ## Required inputs by action - Create + Telegram bind: - `AGENT_ID` - `TELEGRAM_TOKEN` - optional `WORKSPACE` (default: `~/.openclaw/workspace-<AGENT_ID>`) - optional credential inheritance flag (`--inherit-auth` or `INHERIT_AUTH=1`) only with explicit user consent - Pairing approval (separate step): - `AGENT_ID` - `PAIRING_CODE` (obtained only after user sends `/start` to the bot) - Reconfigure: - `AGENT_ID` - changed fields (model/routes/channel token/etc.) - Archive/Delete: - `AGENT_ID` - archive destination (default under `state/archive/<AGENT_ID>/`) ## Command playbook Read `references/openclaw-agent-lifecycle-playbook.md` before running uncommon operations. For deterministic execution, use scripts in this skill: - `scripts/create-telegram-agent.sh` - `scripts/approve-telegram-pairing.sh` - `scripts/archive-agent.sh` - `scripts/delete-agent-safe.sh` - `scripts/refresh-dashboard.sh` - `scripts/lifecycle-log.sh` ## Execution rules - Prefer `openclaw` CLI over ad-hoc file edits. - Configure bindings via `openclaw config get/set` (append entry; do not overwrite blindly). - Do not restart gateway by default after binding/config changes. - Use pairing command with explicit channel flag: `openclaw pairing approve <PAIRING_CODE> --channel telegram`. - Credential inheritance is optional and must be explicitly approved before copying `auth-profiles.json` from another agent workspace. - Never hard-delete before successful archive. - For deletion, prefer `scripts/delete-agent-safe.sh` (archive verification + explicit confirmation + cleanup + logging). - After every lifecycle change, run dashboard refresh + lifecycle logging. ## Minimal post-change verification Run: ```bash openclaw agents list --json openclaw status --json openclaw gateway status --json ``` Confirm: - target agent exists (or is absent after deletion) - expected bindings/routes are present - gateway runtime is healthy and RPC probe is ok


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 1970168137/aftersale-sop (version 1.0.0)

# aftersale-sop ## Name After-Sales Service SOP ## Description Comprehensive after-sales service standard operating procedures including退换货流程 (return/exchange processes), complaint escalation, service recovery, and compensation frameworks. Covers policy documentation, workflow design, quality standards, response timeframes, and customer satisfaction measurement for consistent, efficient post-purchase support operations. ## Input | Name | Type | Required | Description | |------|------|----------|-------------| | business_type | text | Yes | Type of products/services sold | | return_policy | text | Yes | Current return and exchange policy | | team_structure | text | Yes | Customer service team organization | | common_issues | text | Yes | Frequent after-sales scenarios | | service_standards | text | Yes | Target response and resolution times | | escalation_matrix | text | No | Current escalation procedures | ## Output | Name | Type | Description | |------|------|-------------| | return_process | text | Step-by-step return/exchange workflow | | complaint_sop | text | Complaint handling procedures | | escalation_procedures | text | Clear escalation paths and criteria | | service_recovery | text | Service failure recovery protocols | | compensation_matrix | text | Compensation guidelines by scenario | | quality_standards | text | Service quality metrics and monitoring | | training_materials | text | CS team training content | ## Example ### Input ```json { "business_type": "Consumer electronics, 30-day return policy", "return_policy": "30 days unused, 14 days defective exchange", "team_structure": "Tier 1: 10 agents, Tier 2: 3 specialists, Manager", "common_issues": "Defective products, wrong items, buyer's remorse", "service_standards": "First response 2 hours, resolution 24 hours" } ``` ### Output ```json { "return_process": "1. Verify eligibility, 2. Issue RMA, 3. Receive item, 4. Process refund", "complaint_sop": "Acknowledge in 1hr, investigate in 4hrs, resolve in 24hrs", "escalation_procedures": "Tier 2: >$500 value, Manager: legal threat, repeat complaint", "service_recovery": "Empower agents to offer up to $50 credit without approval", "compensation_matrix": "Shipping error: $10 credit, Defective: Full refund + $20 credit", "quality_standards": "CSAT >85%, First contact resolution >70%, Response time <2hrs", "training_materials": "Product knowledge, empathy scripts, de-escalation techniques" } ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jini92/clawhub-publish-mai (version 1.0.0)

--- name: clawhub-publish description: Publish OpenClaw skills to ClawHub marketplace (clawhub.ai). Use when deploying a skill to ClawHub for the first time, updating an existing published skill, or when user says "스킬 배포", "ClawHub에 올려줘", "publish skill", "스킬 퍼블리시", "ClawHub publish". Handles language check (Korean → English), personal info sanitization, versioning, and clawhub CLI publish. --- # ClawHub Publish ## Prerequisites - clawhub CLI installed: `npm i -g clawhub` - Logged in: `clawhub whoami` (if not: `clawhub login` via PTY + browser) - Target skill folder exists under `C:\MAIBOT\skills\<skill-name>\` ## Workflow ### 1. Pre-publish Checklist Run against each skill before publishing. See `references/checklist.md` for full criteria. **Quick scan:** ```powershell Get-Content "C:\MAIBOT\skills\<skill-name>\SKILL.md" -Encoding UTF8 | Select-Object -First 40 ``` Must verify: - [ ] `description:` field is in **English** (this is what ClawHub users see first) - [ ] No Korean text in SKILL.md body - [ ] No personal paths (`C:\Users\jini9`, `JINI_SYNC`, etc.) - [ ] No internal account names or credentials - [ ] Generic placeholders used where personal config appeared ### 2. Language & Sanitization Fix If Korean or personal info is found: 1. Rewrite SKILL.md fully in English 2. Replace personal paths with generic placeholders (`$VAULT_PATH`, `~/vault`, `your-username`) 3. Move any `references/*.md` content to English as well 4. Write with UTF-8: `[System.IO.File]::WriteAllText($path, $content, [System.Text.Encoding]::UTF8)` ### 3. Determine Version | Scenario | Version bump | |----------|-------------| | First publish | `1.0.0` | | Content fix / translation | `1.1.0` (minor) | | New section / major rewrite | `2.0.0` (major) | | Typo / small fix | `1.0.1` (patch) | ### 4. Publish ```powershell cd C:\MAIBOT clawhub publish ./skills/<skill-name> ` --slug <slug> ` --name "<Display Name>" ` --version <X.Y.Z> ` --changelog "<one-line summary of changes>" ``` **Slug rules:** - Lowercase, hyphens only - Must be globally unique on ClawHub - If slug taken: append `-mai` suffix (e.g., `obsidian-daily-mai`) ### 5. Verify ```powershell clawhub whoami # confirm still authenticated # Then check: https://clawhub.ai/u/jini92 ``` ### 6. Update Records After successful publish, update both: - `C:\MAIBOT\memory\marketplace-strategy.md` — add row to ClawHub table - Obsidian `_DASHBOARD.md` — add to Current Sprint as Done ## Batch Publish To publish multiple skills at once, run steps 1–4 for each in sequence. Check `references/checklist.md` for the full quality bar before each. ## Common Errors | Error | Fix | |-------|-----| | `Not logged in` | Run `clawhub login` in PTY mode; open browser URL when shown | | `Only the owner can publish updates` | Slug taken by another user; add `-mai` suffix | | `Login session timeout (code 1)` | Rerun `clawhub login` — PTY must stay alive until browser auth completes |


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: lars147/tmx-cli (version 0.1.0)

--- name: cookidoo description: Manage Thermomix/Cookidoo meal planning via tmx-cli. Use for recipe search, weekly meal plan management, shopping list generation, favorites, and recipe details. Trigger when the user mentions Cookidoo, Thermomix, Wochenplan, meal plan, Rezept, recipe, or Einkaufsliste for cooking. --- # Cookidoo / tmx-cli Skill Manage Cookidoo® (Thermomix) meal plans, recipes, and shopping lists using `tmx-cli` — a pure-Python CLI bundled in this skill at `{baseDir}/tmx_cli.py`. ## Setup 1. **Python 3.9+** required (no external dependencies) 2. **Login**: `python3 {baseDir}/tmx_cli.py login` (OAuth flow with Cookidoo account) 3. **Setup** (optional): `python3 {baseDir}/tmx_cli.py setup` — configure TM version, diet preferences, max cooking time ## Critical Rules 1. **Confirm before destructive actions** (shopping clear, plan remove). 2. **Use `--json`** when parsing output programmatically. 3. **Respect user preferences** — setup config auto-applies to searches. ## CLI Usage ``` python3 {baseDir}/../tmx-cli/tmx_cli.py <resource> <action> [options] ``` ## Core Workflows ### Search Recipes ```bash tmx search "Pasta" --json tmx search "Kuchen" -n 20 --json # more results tmx search "Suppe" -t 30 --json # max 30 min prep time tmx search "Salat" -d easy -c vegetarisch --json # easy + vegetarian ``` Filters: `-t <minutes>`, `-d easy|medium|advanced`, `--tm TM5|TM6|TM7`, `-c <category>` Categories: vorspeisen, suppen, pasta, fleisch, fisch, vegetarisch, beilagen, desserts, herzhaft-backen, kuchen, brot, getraenke, grundrezepte, saucen, snacks ### Recipe Details ```bash tmx recipe show <recipe_id> --json # ingredients, steps, nutrition ``` ### Meal Plan ```bash tmx plan show --json # current week plan tmx plan sync # sync from Cookidoo tmx plan add <recipe_id> <day> # add recipe (day: mon/tue/wed/thu/fri/sat/sun) tmx plan remove <recipe_id> <day> # remove from plan tmx plan move <recipe_id> <from> <to> # move between days ``` ### Shopping List ```bash tmx shopping show --json # current list tmx shopping from-plan # generate from meal plan tmx shopping add <recipe_id> # add recipe ingredients tmx shopping add-item "Milch" "1L" # add custom item tmx shopping remove <recipe_id> # remove recipe ingredients tmx shopping clear # clear entire list ⚠️ tmx shopping export # export as markdown tmx shopping export --format json # export as JSON ``` ### Today's Recipes ```bash tmx today --json # what's on the plan today ``` ### Favorites ```bash tmx favorites show --json tmx favorites add <recipe_id> tmx favorites remove <recipe_id> ``` ## Full Command Reference For all commands, options, and flags see `{baseDir}/references/commands.md`.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: ayhanagirgol/yasal-defterler-tr (version 1.0.0)

--- name: yasal-defterler-tr description: Türkiye'de şirketlerin tutması zorunlu yasal defterler, e-defter uygulaması, defter tasdik tarihleri, belge arşivleme kuralları, personel özlük dosyaları, çalışan türleri ve zorunlu dokümanlar. Use when asked about Turkish company legal books, e-defter, yasal defterler, document archiving, or employee documentation requirements in Turkey. version: "1.0" author: Tech Consulting (techsmmm.com) tags: [turkey, defter, e-defter, arsiv, ozluk, calisanlar, belge, tasdik] --- # Yasal Defterler, Arşivleme ve Çalışan Belgeleri Bu skill, Türkiye'de şirketlerin tutmak zorunda olduğu yasal defterleri, defter tasdik takvimini, e-defter uygulamasını, belge arşivleme kurallarını ve personel özlük dosyası gerekliliklerini kapsar. ## Bu Skill Ne Zaman Tetiklenir? - "Hangi defterleri tutmak zorundayım?" - "Defter tasdiki ne zamana kadar yapılmalı?" - "E-defter nedir, zorunlu mu?" - "Personel özlük dosyasında neler olmalı?" - "Belgeleri kaç yıl saklamam gerekiyor?" - "Stajyer veya freelancer çalıştırırken ne yapmalıyım?" - Türkiye'de yasal defterler, belge arşivleme veya çalışan dokümanlarıyla ilgili sorular ## Nasıl Kullanılır? 1. `references/defter_listesi.md` → 8 yasal defter ve hangi şirketler için zorunlu olduğu 2. `references/tasdik_ve_arsiv.md` → Tasdik tarihleri, e-defter, fiziksel ve dijital arşiv kuralları 3. `references/calisanlar_dokumanlari.md` → Çalışan türleri ve zorunlu dokümanlar tablosu ## Temel Kural > "Defter tasdik tarihi geçerse, defterdeki işlemler geçersiz sayılır!" > "Yasal defterler, şirketin geriye dönük ispat güvencesidir." --- > **Kaynak:** Şirket 101 — Tech Consulting (techsmmm.com) > © 2025 Her hakkı saklıdır. Kaynak gösterilmeden çoğaltılamaz.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kingofzhao/habit-loop-architect (version 1.0.0)

# Habit Loop Architect > 习惯回路建筑师 — 基于 Charles Duhigg 的习惯回路理论和 BJ Fogg 的行为模型，设计和拆解习惯。 ## Description 将习惯科学的核心研究转化为可执行的习惯设计框架。不靠意志力，靠系统设计。每个习惯 = 触发 → 行为 → 奖励，修改任一环节即可改变习惯。 ## Usage 当用户需要： - 建立新习惯 - 戒除坏习惯 - 设计习惯叠加链 - 克服习惯中断后的恢复 - 理解为什么习惯总是失败 ## Key Concepts ### 1. Fogg行为模型：B=MAP - **B**ehavior = **M**otivation × **A**bility × **P**rompt - 习惯失败 = 三者之一不足 - 解决方案不是"更有意志力"，而是"降低难度"或"加强提示" ### 2. 习惯叠加公式 ``` 在 [已有习惯] 之后，我将 [新习惯] ``` - 利用已有神经通路作为触发器 - 例：在"泡咖啡"之后 → "写3件感恩的事" ### 3. 两分钟法则 - 新习惯必须能在2分钟内完成 - "每天读30页" → "每天翻开书"（先建立身份认同） - 习惯固化后再逐步扩展 ### 4. 习惯中断恢复协议 - 中断 ≠ 失败，中断后24h内恢复 = 成功 - "永不连续错过两次"原则 - 中断原因分析 > 自责 ## Instructions 1. 识别目标习惯或要戒除的习惯 2. 分析当前的习惯回路（触发→行为→奖励） 3. 设计新回路（保持触发和奖励，替换行为） 4. 降低执行门槛到2分钟版本 5. 建立追踪机制（无需复杂，日历打勾即可） 6. 规划中断恢复方案 ## Examples **输入**: "想养成每天运动的习惯但总坚持不了" **输出**: 2分钟版本(穿上运动鞋) + 叠加到晨间刷牙后 + 完成打勾→多巴胺奖励 + 中断恢复：任何运动算数 ## Boundaries - 不处理成瘾级别问题（需专业帮助） - 尊重用户节奏，不催促 - 习惯改变是月级别的过程


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: zack-dev-cm/skool-challenge-launcher (version 0.1.0)

--- name: skool-challenge-launcher description: Design a public-safe 7-day Skool challenge. Use when the user wants to invite member action, collect comments, produce visible proof, test demand, or turn repeated tasks into free templates, course modules, and proof reviews without promising results. --- # Skool Challenge Launcher Use this skill to launch a simple Skool challenge that invites visible participation and product signals without relying on private member data. ## Inputs Collect or infer: - audience, - challenge promise, - first member action, - available public-safe example, - proof members can post without exposing private data, - operator capacity for daily replies, - topics, claims, or tools to avoid. ## Challenge Shape Prefer challenges that ask members to post a small real artifact: - repeated task audit, - before/after workflow, - template request, - redacted proof screenshot or text summary, - self-reported time-saved estimate framed as a baseline, not a promise, - blocker report. ## Workflow 1. Pick one audience and one outcome. 2. Define a 7-day sequence: - Day 1: introduce the task. - Day 2: show a simple example. - Day 3: ask for member submissions. - Day 4: review common blockers. - Day 5: publish a reusable template. - Day 6: collect wins and proof. - Day 7: publish the trust recap and next free-course module vote. 3. Write the launch post. 4. Write 3 reminder comments. 5. Define the free-course trust CTA. 6. Define success thresholds. ## Output Return: - challenge title, - launch post, - daily prompts, - reminder comments, - free-course trust CTA, - success metrics, - follow-up product idea. Keep it simple enough for non-technical members. Use Codex, OpenClaw, or ClawHub only as optional advanced implementation paths. ## Examples Good public-safe inputs: - "Help solo operators turn one repeated task into a reusable checklist." - "Ask members to post a redacted before/after workflow, not client data." Avoid inputs that require member DMs, hidden posts, paid lessons, private exports, credentials, or screenshots with personal/account details. Use synthetic samples or member-owned redacted examples instead. ## Guardrails - Do not scrape private communities, member lists, DMs, paid lessons, or hidden pages. - Do not request, store, transform, or paste credentials, API keys, session cookies, payment data, private exports, or account recovery data. - Do not promise income, growth, conversion, rank, time saved, health, financial, legal, or education outcomes. - Treat screenshots as unsafe until names, handles, emails, phone numbers, private URLs, order IDs, account IDs, and sensitive UI are removed. - Keep outreach consent-first and based on visible member posts or explicit replies.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: willoscar/citation-anchoring (version 1.0.0)

--- name: citation-anchoring description: 'Regression-check citation anchoring (citations stay in the same subsection) to prevent “polish drift” that breaks claim→evidence alignment. **Trigger**: citation anchoring, citation drift, regression, cite stability, 引用锚定, 引用漂移. **Use when**: after editing/polishing, you want to confirm citations did not migrate across `###` subsections. **Skip if**: you do not have a baseline anchor file yet. **Network**: none. **Guardrail**: analysis-only; do not edit content.' version: 0.1.0 metadata: openclaw: requires: anyBins: - python3 - python --- # Citation Anchoring (regression) Purpose: prevent a common failure mode: polishing rewrites text and accidentally moves citation markers into a different `###` subsection, breaking claim→evidence alignment. ## Inputs - `output/DRAFT.md` - `output/citation_anchors.prepolish.jsonl` (baseline; created by `draft-polisher` on first run) ## Outputs - `output/CITATION_ANCHORING_REPORT.md` (PASS/FAIL + drift examples) ## Baseline policy - `draft-polisher` captures a baseline once per run: `output/citation_anchors.prepolish.jsonl`. - Subsequent polish runs should keep per-H3 citation sets stable. ## Workflow (analysis-only) Role: - **Auditor**: only checks and reports; does not edit. Steps: 1) Load the baseline anchors. 2) Parse the current `output/DRAFT.md` into `###` subsections and extract citation keys per subsection. 3) Compare current sets to baseline sets: - keys added/removed within a subsection - keys that migrated across subsections 4) Write `output/CITATION_ANCHORING_REPORT.md`: - `- Status: PASS` only if no drift is detected - otherwise, `- Status: FAIL` with a short diff table + examples ## Notes If you intentionally restructure across subsections: - delete `output/citation_anchors.prepolish.jsonl` and regenerate a new baseline (then treat that as the new regression anchor). ## Troubleshooting ### Issue: baseline anchor file is missing Fix: - Run `draft-polisher` once to generate `output/citation_anchors.prepolish.jsonl`, then rerun the anchoring check. ### Issue: citations intentionally moved across subsections Fix: - Delete `output/citation_anchors.prepolish.jsonl` and regenerate a new baseline (then treat that as the new regression anchor).


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: renoblabs/dev-glue (version 1.0.0)

--- name: dev-glue description: JSON transformation, schema validation, text diffing, document conversion. Four developer utility micro-services. Use for data transformation, validation, and format conversion. --- # Dev Glue Four utility services for data transformation and validation. ## Services ### /transform-json — JSON Transformation Apply expressions to transform JSON data. ``` POST /x402s/transform-json Body: {"input": {"users": [...]}, "expression": "users[0].name"} Response: {"output": "Alice", "expression": "users[0].name"} Price: $0.001 USDC ``` ### /validate-json — Schema Validation Validate JSON against schema with human-readable errors. ``` POST /x402s/validate-json Body: {"input": {...}, "schema": {...}} Response: {"valid": false, "errors": [{"path": ["name"], "message": "required", "rule": "required"}]} Price: $0.001 USDC ``` ### /compare-text — Text Diff Semantic diff between two texts with similarity score. ``` POST /x402s/compare-text Body: {"text1": "Hello world", "text2": "Hello there world"} Response: {"similarity": 0.647, "additions": 6, "deletions": 0, "diffs": [...]} Price: $0.001 USDC ``` ### /convert-doc — Format Conversion Markdown to HTML to plain text. ``` POST /x402s/convert-doc Body: {"input": "# Hello\n**bold**", "from_format": "markdown", "to_format": "html"} Response: {"output": "<h1>Hello</h1><p><strong>bold</strong></p>"} Price: $0.002 USDC ``` ## Payment x402 protocol — USDC on Base.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: nickliang/ssh-remote-sanitized (version 1.0.0)

--- name: ssh-remote-skill description: SSH 远程服务器管理工具。支持多服务器连接管理、命令执行、文件传输、系统监控、服务管理、日志分析、安全检查等功能，适用于 Linux/Unix 服务器运维。 --- # SSH 远程服务器管理 > SSH 远程服务器管理工具，支持多服务器连接管理、命令执行、文件传输、系统监控、服务管理、日志分析、安全检查等功能，适用于 Linux/Unix 服务器运维。 ## 功能特性 | 功能模块 | 描述 | |----------|------| | 🔌 **连接管理** | 多服务器配置、连接测试、连接池管理 | | 💻 **命令执行** | 远程命令执行、脚本运行、批量操作 | | 📤 **文件上传** | 单文件/目录上传、进度显示 | | 📥 **文件下载** | 单文件/目录下载、文件列表 | | 📊 **系统监控** | CPU/内存/磁盘/网络/进程监控 | | ⚙️ **服务管理** | systemctl 服务管理、日志查看 | | 📋 **日志分析** | 系统/应用日志查看、搜索、分析 | | 🔒 **安全检查** | 安全扫描、漏洞检查、加固建议 | ## 安装 ```bash npm install ``` ## 配置 创建配置文件 `configs/servers.json`: ```json { "servers": [ { "name": "production", "host": "YOUR_SERVER_IP", "port": 22, "username": "YOUR_USERNAME", "privateKeyPath": "~/.ssh/id_rsa" } ] } ``` ## 使用示例 ### 连接测试 ``` 用户：ssh 连接测试 AI: 🔌 服务器连接状态： ✅ production - 延迟 25ms ``` ### 执行命令 ``` 用户：ssh 执行 production uptime AI: 📋 执行结果： 12:30:00 up 15 days, load average: 0.50 ``` ### 文件传输 ``` 用户：ssh 上传 production ./app.js /var/www/ AI: ✅ 文件上传成功！ ``` ### 系统监控 ``` 用户：ssh 监控 production AI: 📊 CPU: 25% | 内存: 50% | 磁盘: 40% ``` ## 触发词 - `ssh 连接` - 连接管理 - `ssh 执行` - 执行远程命令 - `ssh 上传` - 上传文件 - `ssh 下载` - 下载文件 - `ssh 监控` - 系统监控 - `ssh 服务` - 服务管理 - `ssh 日志` - 日志查看 - `ssh 安全` - 安全检查 ## 依赖 - Node.js >= 18.0.0 - ssh2 ^1.15.0 ## License MIT


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