OpenClaw/clawhub-security-signals huggingface dataset:
Skill: codenova58/tmall (version 0.1.0)

--- name: tmall-hot-trend description: 注册“天猫”热门技能；当需要访问或自动化天猫相关内容时调用。 homepage: `https://www.tmall.com/` metadata: {"clawdbot":{"emoji":"🔥"}} --- # 天猫 用途与边界 - 面向品牌旗舰店与商品页的价格/评价摘要与对比 - 不提供下单、接口逆向或突破风控能力 - 仅用于公开页面的轻量分析与提醒 关键入口 - 主页：https://www.tmall.com/ - 商品搜索：https://list.tmall.com/ - 品牌旗舰店：通过商品页店铺链接进入 常见任务 - 指定品牌的旗舰店商品列表摘要（价格、销量、评价） - 商品详情核心指标整理（价格、促销、规格、评价亮点） - 同类商品对比（品牌、规格、价格/促销） 数据字段 - 商品标题、链接、主图URL、价格/促销价、月销量、评价数 - 店铺名称、店铺链接、品牌、规格/属性 - 评价亮点关键词（可基于文本提取） 自动化要点 - 动态渲染与人机校验，建议人工打开后触发解析 - 价格/促销随时间变动，需标注采集时间 - 频率控制，避免触发风控；不进行批量抓取 示例流程 - 品牌清单：输入品牌 → 搜索 → 分页解析 → 输出价格/销量摘要 - 商品摘要：访问详情页 → 提取价格/规格/评价 → 生成对比卡片 - 同类对比：收集候选 → 按规格分组 → 输出差异点 合规提示 - 遵守平台规则，不进行接口调用或批量采集 - 结果仅用于内部分析与提醒


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: grey0758/knowledge-to-clawhub-skill-publisher (version 1.0.1)

--- name: knowledge-to-clawhub-skill-publisher description: Turn a solved workflow into canonical knowledge docs and a self-contained ClawHub-publishable skill. 把一个已验证流程沉淀成规范知识文档，并打包成可发布到 ClawHub 的自包含 skill。 homepage: https://docs.openclaw.ai/tools/clawhub --- # Knowledge to ClawHub Skill Publisher Use this skill when a workflow has already been proven in practice and should now be captured as durable docs plus a reusable skill. 当一个流程已经在实战中验证过，并且现在需要沉淀成长期文档与可复用 skill 时，使用这个 skill。 ## Read First | 先读这些 Review these files before doing any packaging work: 在做打包工作之前，先看这些文件： - `{baseDir}/README.md` - `{baseDir}/WORKFLOW.md` - `{baseDir}/FAQ.md` - `{baseDir}/CHANGELOG.md` ## Primary Rule | 核心原则 Do not publish a skill from a raw chat transcript. First extract a stable workflow and write canonical docs. 不要直接把原始聊天记录发布成 skill。先提炼稳定流程，再写成规范知识文档。 ## Workflow | 执行流程 1. Identify the stable workflow and remove one-off chat noise. 识别稳定流程，去掉一次性聊天噪音。 2. Write canonical docs under `knowledge/runbooks/` if working inside a shared knowledge repository. 如果在共享知识仓库中工作，先把规范文档写到 `knowledge/runbooks/`。 3. Create a self-contained skill folder under `skills/shared/<skill-name>/`. 在 `skills/shared/<skill-name>/` 下创建自包含 skill 目录。 4. Add: 补齐以下文件： - `SKILL.md` - `README.md` - `WORKFLOW.md` - `FAQ.md` - `CHANGELOG.md` 5. Keep package references self-contained via `{baseDir}`. 使用 `{baseDir}` 保持包内引用自包含。 6. Publish only after the docs and package are aligned. 只在文档和包内容一致后再发布。 7. Verify the remote package after publish. 发布后验证远端包内容。 ## Strong Heuristics | 强判断规则 - if the process is not proven yet, document it as a draft instead of publishing a skill - if the workflow depends on hidden workspace files, make the package self-contained first - if `CHANGELOG.md` is missing, add it before the first stable release - if the audience is mixed, prefer bilingual docs 中文解释： - 流程还没验证过，就先记成草稿，不要急着发布 skill。 - 如果流程依赖工作区外部文件，先把包改成自包含。 - 如果缺 `CHANGELOG.md`，最好在第一个稳定版本前补上。 - 面向中英文混合用户时，优先双语。 ## Safe Commands | 安全命令 ```bash make sync clawhub publish /absolute/path/to/skill-folder --slug your-skill --name "Your Skill" --version 1.0.0 clawhub inspect your-skill --version 1.0.0 --files ``` ## Response Format | 输出格式 Always return: 始终返回： 1. current workflow status 2. missing artifacts 3. next single best action 4. verification after that ## Constraints | 约束 - do not treat ClawHub as the source of truth - do not publish secrets, machine-specific tokens, or raw transcripts - keep skill bundles self-contained when possible - prefer `knowledge/` as the canonical Markdown source 中文约束： - 不要把 ClawHub 当成事实源。 - 不要发布密钥、机器专属 token，或原始聊天记录。 - 尽量保持 skill 包自包含。 - 优先把 `knowledge/` 作为规范 Markdown 来源。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: athola/nm-parseltongue-python-async (version 1.0.2)

--- name: python-async description: | Async Python patterns and concurrency: async APIs, I/O-bound apps, rate limiting, context managers version: 1.9.5 triggers: - python - async - asyncio - concurrency - await - coroutines metadata: {"openclaw": {"homepage": "https://github.com/athola/claude-night-market/tree/master/plugins/parseltongue", "emoji": "\ud83e\udd9e"}} source: claude-night-market source_plugin: parseltongue --- > **Night Market Skill** — ported from [claude-night-market/parseltongue](https://github.com/athola/claude-night-market/tree/master/plugins/parseltongue). For the full experience with agents, hooks, and commands, install the Claude Code plugin. # Async Python Patterns asyncio and async/await patterns for Python applications. ## Quick Start ```python import asyncio async def main(): print("Hello") await asyncio.sleep(1) print("World") asyncio.run(main()) ``` ## When To Use - Building async web APIs (FastAPI, aiohttp) - Implementing concurrent I/O operations - Creating web scrapers with concurrent requests - Developing real-time applications (WebSockets) - Processing multiple independent tasks simultaneously - Building microservices with async communication ## When NOT To Use - CPU-bound optimization - use python-performance instead - Testing async code - use python-testing async module ## Modules This skill uses progressive loading. Content is organized into focused modules: - See `modules/basic-patterns.md` - Core async/await, gather(), and task management - See `modules/concurrency-control.md` - Semaphores and locks for rate limiting - See `modules/error-handling-timeouts.md` - Error handling, timeouts, and cancellation - See `modules/advanced-patterns.md` - Context managers, iterators, producer-consumer - See `modules/testing-async.md` - Testing with pytest-asyncio - See `modules/real-world-applications.md` - Web scraping and database operations - See `modules/pitfalls-best-practices.md` - Common mistakes and best practices Load specific modules based on your needs, or reference all for detailed guidance. ## Exit Criteria - Async patterns applied correctly - No blocking operations in async code - Proper error handling implemented - Rate limiting configured where needed - Tests pass with pytest-asyncio ## Troubleshooting ### Common Issues **RuntimeError: no current event loop** Use `asyncio.run()` as the entry point. Avoid `get_event_loop()` in Python 3.10+. **Blocking call in async context** Move sync I/O to `asyncio.to_thread()` or `loop.run_in_executor()`. **Tests hang indefinitely** Ensure pytest-asyncio is installed and test functions are decorated with `@pytest.mark.asyncio`.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: terrycarter1985/gog-stale-game-cleanup (version 1.0.0)

--- name: gog-stale-game-cleanup description: > Find installed GOG games not played in 30+ days, email a report, and add reminders to Apple Reminders Gaming list. Use when user wants to clean up unused GOG games, review stale game library, get uninstall reminders, or run a periodic game cleanup sweep. Triggers on stale games, game cleanup, unused games, GOG cleanup, game purge review. --- # GOG Stale Game Cleanup Automated workflow to identify installed GOG games that haven't been played recently, notify via email, and create Apple Reminders for each stale game. ## Prerequisites - GOG library JSON file (see `gog_library.json` in config) - `himalaya` CLI configured for email sending - `remindctl` CLI for Apple Reminders (macOS) - `python3` for JSON parsing ## Workflow 1. Run `scripts/stale_games.sh` with required environment variables 2. Script identifies installed games with `last_played` older than 30 days (or never played) 3. Sends an email report to the configured address 4. Adds a "Consider uninstalling: <game>" reminder to the Gaming list ## Usage ```bash GOG_LIBRARY=/path/to/gog_library.json \ EMAIL_TO=[REDACTED_SECRET] \ EMAIL_ACCOUNT=personal \ REMINDERS_LIST=Gaming \ bash scripts/stale_games.sh ``` ### Environment Variables | Variable | Required | Default | Description | |---|---|---|---| | `GOG_LIBRARY` | Yes | — | Path to GOG library JSON | | `EMAIL_TO` | Yes | — | Recipient email address | | `EMAIL_ACCOUNT` | No | `personal` | Himalaya account name | | `REMINDERS_LIST` | No | `Gaming` | Apple Reminders list name | | `STALE_DAYS` | No | `30` | Days threshold for stale | | `DRY_RUN` | No | `false` | Preview without sending | ### Scheduling To run weekly via cron: ```bash # Add to crontab or use OpenClaw cron 0 10 * * 1 GOG_LIBRARY=... EMAIL_TO=... bash /path/to/scripts/stale_games.sh ``` ## Output - **Email**: Formatted report listing each stale game with last-played date and install path - **Reminders**: One reminder per stale game titled "Consider uninstalling: <game name>" in the Gaming list - **Console**: Summary of findings and action confirmations


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: alvisdunlop/alvis-gh-cli (version 1.0.5)

--- name: gh description: "Use the GitHub CLI (gh) to perform core GitHub operations: auth status, repo create/clone/fork, issues, pull requests, releases, and basic repo management. Trigger for requests to use gh, manage GitHub repos, PRs, or issues from the CLI." --- > ?? **Complete setup guide**: https://SkillBoss.co/skill.md # GitHub CLI (gh) ## Overview Use `gh` for authenticated GitHub operations from the terminal. Prefer explicit, idempotent commands and report URLs back to the user. ## Quick checks - Auth status: ```bash gh auth status ``` - Current repo context: ```bash gh repo view --json nameWithOwner,url,defaultBranchRef ``` ## Core workflows ### Repo create (private by default) ```bash gh repo create OWNER/NAME --private --confirm --description "..." ``` If running inside a local repo, use `--source . --remote origin --push`. ### Clone / fork ```bash gh repo clone OWNER/NAME ``` ```bash gh repo fork OWNER/NAME --clone ``` ### Issues - List: ```bash gh issue list --limit 20 ``` - Create: ```bash gh issue create --title "..." --body "..." ``` - Comment: ```bash gh issue comment <num> --body "..." ``` ### Pull requests - Create from current branch: ```bash gh pr create --title "..." --body "..." ``` - List: ```bash gh pr list --limit 20 ``` - View: ```bash gh pr view <num> --web ``` - Merge (use explicit method): ```bash gh pr merge <num> --merge ``` ### Releases ```bash gh release create vX.Y.Z --title "vX.Y.Z" --notes "..." ``` ## Safety notes - Confirm the target repo/owner before destructive actions (delete, force push). - For private repos, ensure `--private` is set on create. - Prefer `--confirm` to avoid interactive prompts in automation.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: sky-lv/skylv-doc-generator (version 1.0.0)

--- name: skylv-readme-generator slug: skylv-readme-generator version: 1.0.0 description: "Auto-generates professional README.md from code structure, package.json, and directory analysis. Triggers: generate readme, create readme, readme from code, project documentation, scaffold readme." author: SKY-lv license: MIT tags: [readme, documentation, generator, github] keywords: [readme, documentation, github, markdown, generator] triggers: readme generator, generate readme, create readme --- # README Generator ## Overview Automatically analyzes a codebase and generates a comprehensive, professional README.md. ## When to Use - User asks to "generate a README", "create documentation", or "document this project" - New project needs a README but none exists - Existing README is outdated or incomplete ## How It Works ### Step 1: Analyze project structure Run: dir /b /s /a:d (Windows) or find . -maxdepth 2 -type d (macOS/Linux) ### Step 2: Detect project type Check for: package.json (JS), setup.py/pyproject.toml (Python), Cargo.toml (Rust), go.mod (Go), pom.xml (Java) ### Step 3: Generate README sections 1. Project Title - from package.json name or directory name 2. Badges - CI status, version, license, downloads 3. One-liner Description 4. Features - auto-detect from exports and main functions 5. Installation - standard install for detected type 6. Usage - realistic examples from source code 7. API Reference - parse function signatures 8. Contributing + License ## Output Format Write a complete README.md with all sections. Keep descriptions under 80 chars per line. Include real badges (shields.io) and actual code examples from the source.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: feiyang2007/academic-research-conflict (version 1.0.0)

--- name: academic-research version: 1.0.0 description: Search academic papers and conduct literature reviews using OpenAlex API (free, no key needed). Use when the user needs to find scholarly papers by topic/author/DOI, explore citation chains, get structured paper metadata (title, authors, abstract, citations, DOI, open access URL), fetch full text of open access papers, or conduct automated literature reviews with theme identification and synthesis. Triggers on requests involving academic search, paper lookup, citation analysis, literature review, research synthesis, or scholarly reference gathering. --- # Academic Research Search 250M+ academic works via OpenAlex. No API key required. Built by [Topanga](https://topanga.ludwitt.com) — AI Research Consultant ## Quick Start ### Search papers by topic ```bash python3 scripts/scholar-search.py search "transformer architectures" --limit 10 ``` ### Search by author ```bash python3 scripts/scholar-search.py author "Yann LeCun" --limit 5 ``` ### Look up by DOI ```bash python3 scripts/scholar-search.py doi "10.1038/s41586-021-03819-2" ``` ### Get citation chain (papers that cite a work) ```bash python3 scripts/scholar-search.py citations "10.1038/s41586-021-03819-2" --direction both ``` ### Deep read (fetch abstract + full text when available) ```bash python3 scripts/scholar-search.py deep "10.1038/s41586-021-03819-2" ``` ### JSON output for programmatic use ```bash python3 scripts/scholar-search.py search "CRISPR" --json ``` ## Literature Review Workflow Automated multi-step literature review: ```bash python3 scripts/literature-review.py "algorithmic literacy in education" --papers 30 --output review.md ``` This will: 1. Search for papers across multiple query variations 2. Deduplicate and rank by relevance + citations 3. Identify thematic clusters 4. Generate a structured synthesis in markdown Options: - `--papers N` — Target number of papers (default: 20) - `--output FILE` — Write review to file (default: stdout) - `--years 2020-2025` — Restrict publication year range - `--json` — Output structured JSON instead of markdown ## Output Format All search commands return structured data per paper: - **Title** and publication year - **Authors** (up to 5) - **Abstract** (when available) - **Citation count** - **DOI** - **Open access URL** (when available) - **Source journal/venue** ## Tips - OpenAlex sorts by relevance by default; use `--sort citations` for most-cited - Combine `search` + `deep` for quick triage: search first, deep-read promising hits - The literature review script caches results in `/tmp/litreview_cache/` to avoid re-fetching - For full-text PDFs, pipe DOIs to your PDF extraction tool

path: _meta.json
content: ownerId: kn7d70nbbqsbc4y76x7a6stq3s80e98c
slug: academic-research
version: 1.0.0
publishedAt: 1771467688891

Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: evezart/agent-safety-monitor (version 1.0.0)

--- name: agent-safety-monitor description: Real-time AI agent safety monitoring, anomaly detection, and constraint enforcement. Use when building agent guardrails, detecting unsafe behaviors, enforcing action limits, or creating safety dashboards for autonomous AI systems. Covers behavior logging, rule engines, alert systems, and compliance tracking. --- # Agent Safety Monitor Monitor AI agent behavior in real-time, detect anomalies, and enforce safety constraints. ## Quick Start Run the monitor against an agent log stream: ```bash python3 scripts/monitor.py --config safety_rules.yaml --input agent_logs/ ``` ## Architecture ``` Agent Actions → Event Stream → Rule Engine → Alerts → Dashboard ↓ Anomaly Detector ↓ Auto-Pause/Kill ``` ## Safety Rule Types 1. **Rate limits**: Max N actions per minute/hour 2. **Action allowlists**: Only permit specific tool calls 3. **Content filters**: Block PII exfiltration, harmful outputs 4. **Budget caps**: Stop when cost exceeds threshold 5. **Scope limits**: Restrict file/API/network access 6. **Behavioral anomalies**: Flag unusual patterns (tool call frequency spikes, repetitive loops) ## Rule Configuration See `references/rules-reference.md` for the YAML schema. ## Alert Channels - Console (default) - Webhook (Slack, Discord) - File log - Dashboard (HTTP server) ## Dashboard Launch the monitoring dashboard: ```bash python3 scripts/dashboard.py --port 8080 ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: yangzhe1991/binance-crypto-price (version 1.0.3)

--- name: cryptoprice description: Query real-time cryptocurrency prices using the Binance API. Get latest prices for Bitcoin, Ethereum, and all BN listed cryptocurrencies. No API key required. --- # CryptoPrice - Cryptocurrency Price Query Query real-time cryptocurrency prices using the official Binance API. ## Quick Start ### Query Popular Coin Prices ```bash uv run ~/.openclaw/skills/cryptoprice/scripts/cryptoprice.py ``` ### Query Specific Coin ```bash # Query Bitcoin uv run ~/.openclaw/skills/cryptoprice/scripts/cryptoprice.py BTCUSDT # Query Ethereum uv run ~/.openclaw/skills/cryptoprice/scripts/cryptoprice.py ETHUSDT # Shorthand (auto-completes USDT) uv run ~/.openclaw/skills/cryptoprice/scripts/cryptoprice.py BTC ``` ### JSON Format Output ```bash uv run ~/.openclaw/skills/cryptoprice/scripts/cryptoprice.py --json uv run ~/.openclaw/skills/cryptoprice/scripts/cryptoprice.py BTC --json ``` ### List All Trading Pairs ```bash uv run ~/.openclaw/skills/cryptoprice/scripts/cryptoprice.py --list ``` ## Supported Coins Popular coins displayed by default: - **BTC** - Bitcoin - **ETH** - Ethereum - **BNB** - Binance Coin - **SOL** - Solana - **XRP** - Ripple - **DOGE** - Dogecoin - **ADA** - Cardano - **AVAX** - Avalanche - **DOT** - Polkadot - **LINK** - Chainlink ## API Data Source - **Binance Spot API**: `https://api.binance.com/api/v3/ticker/price` - No API Key required - Real-time data with low latency


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: wudi488/liuyao (version 2.1.1)

--- name: liuyao description: 六爻铜钱卦占卜技能。核心理念："解一卦就是传一道，说一言就是传一智"。支持真实/虚拟起卦，集成儒道哲学。 version: 2.1.1 author: imagor tags: [六爻, 易经, 占卜, 命理] --- # 🔮 六爻占卜技能 ## 📜 贫道人设 贫道乃修道之人，通《易经》六爻，精儒道哲学。自称"贫道"，称用户"居士"。 **开场**：善。居士坐，贫道为汝细细道来。 **结尾**：解一卦就是传一道，说一言就是传一智。 --- ## ⚠️ 解卦流程（不可跳过） ### 第一步：启动确认 "居士，贫道来为居士解这一卦。请问居士所问何事？" ### 第二步：起卦（参考 references/divination_method.md） - 虚拟起卦：直接调用 `scripts/liuyao.py` 生成六次掷币结果 - 真实起卦：指导用户用三枚硬币掷六次，从下往上记录 ### 第三步：按需读取 references/ - **必读**：`references/64gua.md`（查卦辞）、当前卦象对应的 references - **按需**：根据所问之事，读取对应引用（见下表） | 所问之事 | 必读文件 | |----------|----------| | 事业/工作 | `references/history_wisdom.md` | | 财运/投资 | `references/confucian.md` | | 人际/感情 | `references/taoist.md` | | 逆境/困难 | `references/five_elements.md` | | 决策/选择 | `references/history_wisdom.md` | | 健康/疾病 | `references/five_elements.md` | ### 第四步：六章解卦（每章必须融入文化引用） | 章 | 内容 | 引用来源 | |----|------|----------| | 一 | 卦象确认（原卦辞、彖传、主卦+变卦） | 64gua.md | | 二 | 历史定位（典故对照） | history_wisdom.md | | 三 | 核心内容（儒道哲学） | confucian.md, taoist.md | | 四 | 针对分析（用神旺衰、动变生克） | five_elements.md, history_wisdom.md | | 五 | 现代启示 | 成语俗语 | | 六 | 贫道赠言 | 诗词经典 | 引用规则：至少3条古语（《易经》《论语》《道德经》《孙子兵法》），引后必解释。 --- ## 🎲 起卦速查 ### 符号对照 | 结果 | 符号 | 含义 | |------|------|------| | 三正 | O 老阳 | 变阴 | | 三背 | X 老阴 | 变阳 | | 两正一背 | — 少阳 | 不变 | | 两背一正 | - - 少阴 | 不变 | ### 快速解卦口诀 ``` ① 列卦象 → ② 找用神 → ③ 看旺衰 → ④ 看动爻 → ⑤ 判吉凶 → ⑥ 参应期 ``` ### 用神口诀 ``` 问财妻财问官鬼，问事父母问文书， 问病官鬼问出行，五行六亲各归位。 ``` --- ## 🎭 解卦输出风格 - 以"贫道"自称，称用户"居士" - 通俗有古韵，不堆砌文言 - 解卦+传道并重，不止于吉凶判断 - 避免：爹味说教、过于煽情、纯理论无温度 --- ## ⚠️ 禁忌 | 禁忌 | 原因 | |------|------| | 不诚不占 | 心不诚信息不聚 | | 不疑不占 | 无疑惑则无意义 | | 一事一占 | 多事同占信息混乱 | | 不再三占 | 结果可能矛盾 | | 酒后/激动/疲惫不占 | 影响判断 | --- ## 📦 技能结构 ``` liuyao/ ├── SKILL.md # 主文件 ├── references/ # 按需加载 │ ├── 64gua.md # 六十四卦 │ ├── bagua.md # 八卦六亲 │ ├── zengshanbuyiyi.md # 增删卜易 │ ├── confucian.md # 论语 │ ├── taoist.md # 道德经 │ ├── history_wisdom.md # 历史典故+孙子兵法 │ ├── five_elements.md # 五行详解 │ ├── divination_method.md # 起卦详细方法 │ └── cases.md # 卦例 ├── scripts/ │ ├── liuyao.py # 命令行起卦工具 │ └── weekly_evolution.py # 每周手动检查脚本（需手动运行，非定时任务） └── logs/ └── evolution_log.md # weekly_evolution.py 运行时写入 ``` --- ## 📚 学习入口 - "教我学六爻" → 入门教程（见 references/tutorial.md） - "帮我起一卦" → 直接起卦解卦 - "推荐六爻书籍" → 见 references/zengshanbuyiyi.md 末尾书单 --- 本技能仅供学习娱乐参考，不构成专业命理建议。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: liverock/openclaw-skill-vibe-to-code-theme-gen (version 1.0.0)

--- name: VibeTheme description: Generates a color palette and CSS variables based on a descriptive atmosphere version: 1.0.0-openclaw-skill-vibe-to-code-theme-gen commands: - name: generate_theme description: Generates a color palette and CSS variables based on a descriptive atmosphere parameters: - name: vibe type: string required: true description: A descriptive atmosphere to base the color palette on (e.g. "cozy autumn evening", "neon cyberpunk city") - name: format type: string required: false description: "Output format: css (default), tailwind, or vscode" --- # VibeTheme VibeTheme generates a color palette and CSS variables based on a descriptive atmosphere. ## Usage ``` /vibe_theme generate_theme --vibe "<atmosphere>" [--format css|tailwind|vscode] ``` ### Parameters | Parameter | Required | Description | |-----------|----------|-------------| | `vibe` | Yes | A descriptive atmosphere to base the color palette on (e.g. "cozy autumn evening", "neon cyberpunk city") | | `format` | No | Output format: `css` (default), `tailwind`, or `vscode` | ## What It Does 1. Takes a descriptive vibe string as input. 2. Generates a harmonious color palette inspired by the atmosphere. 3. Outputs in the chosen format: - **css** — A `:root { ... }` block of CSS custom properties. - **tailwind** — A `colors: { ... }` object for `tailwind.config.js`. - **vscode** — A `.json` structure for VS Code's `workbench.colorCustomizations`.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: senknight/sqlite-reader (version 1.0.0)

--- name: sqlite-reader description: Read and query SQLite database files. Use when user wants to inspect or extract data from .sqlite files, especially OpenClaw's main.sqlite memory database. Supports basic SELECT queries, table listing, and schema inspection. --- # SQLite Reader Skill ## Quick Start To read a SQLite file: 1. Use `read_sqlite` tool (not yet implemented - need to create script first) 2. Or use the provided Python script in scripts/read_sqlite.py ## Available Tools Currently no direct tool exists, but I'll create a Python script that can: - List all tables in the database - Show table schema - Execute SELECT queries - Export data to CSV/JSON ## Usage Examples ### List all tables ```python python scripts/read_sqlite.py --list-tables C:\path\to\database.sqlite ``` ### Show table schema ```python python scripts/read_sqlite.py --schema C:\path\to\database.sqlite users ``` ### Execute SELECT query ```python python scripts/read_sqlite.py --query "SELECT * FROM sessions LIMIT 5" C:\path\to\database.sqlite ``` ## Implementation Plan I need to create: 1. `scripts/read_sqlite.py` - Python script for SQLite operations 2. `references/schema.md` - SQLite schema reference


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