OpenClaw/clawhub-security-signals huggingface dataset:
Skill: brs999/dexscreener (version 1.0.0)

--- name: dexscreener description: Query DexScreener market data - search pairs, inspect liquidity/volume, check boosted tokens, and fetch token orders. homepage: https://dexscreener.com user-invocable: true disable-model-invocation: true metadata: openclaw: emoji: "📈" requires: bins: [node] --- # DexScreener Query [DexScreener](https://dexscreener.com) using the local CLI script. ## Quick Start ```bash # Search pairs node {baseDir}/scripts/dexscreener-cli.mjs search_pairs --query "solana" --limit 5 # Get pair details node {baseDir}/scripts/dexscreener-cli.mjs get_pair --chain "solana" --pair "<pair_address>" # Top boosted tokens node {baseDir}/scripts/dexscreener-cli.mjs top_boosted_tokens --limit 10 ``` --- ## After Install - Suggested Setup ### 1. Add to daily market scan Use in morning/evening briefs: ``` dexscreener search_pairs + top_boosted_tokens ``` ### 2. Track specific tokens ```bash node {baseDir}/scripts/dexscreener-cli.mjs pairs_by_tokens --token-addresses "<token1>,<token2>" --limit 10 ``` ### 3. Check order/boost status for candidates ```bash node {baseDir}/scripts/dexscreener-cli.mjs token_orders --chain "solana" --token "<token_address>" --limit 10 node {baseDir}/scripts/dexscreener-cli.mjs latest_boosted_tokens --limit 20 ``` --- ## Commands ### Search and Pair Lookup ```bash node {baseDir}/scripts/dexscreener-cli.mjs search_pairs --query "SOL/USDC" --limit 10 node {baseDir}/scripts/dexscreener-cli.mjs get_pair --chain "solana" --pair "<pair_address>" node {baseDir}/scripts/dexscreener-cli.mjs pairs_by_tokens --token-addresses "<token1>,<token2>" --limit 10 ``` ### Profiles and Boosts ```bash node {baseDir}/scripts/dexscreener-cli.mjs latest_token_profiles --limit 10 node {baseDir}/scripts/dexscreener-cli.mjs latest_boosted_tokens --limit 10 node {baseDir}/scripts/dexscreener-cli.mjs top_boosted_tokens --limit 10 ``` ### Token Orders ```bash node {baseDir}/scripts/dexscreener-cli.mjs token_orders --chain "solana" --token "<token_address>" --limit 10 ``` --- ## Output Features Typical payloads include: - Pair metadata (chain, dex, pair address, symbols) - Price and price change fields - Liquidity and volume fields - Boost/profile/order metadata Default output is JSON for easy piping and automation. --- ## API Uses DexScreener public API endpoints (read-only): - Base URL: `https://api.dexscreener.com` - CLI supports override via `DEXSCREENER_BASE_URL` --- ## Security and Permissions No API key required. What this skill does: - Makes HTTPS GET requests to DexScreener API - Reads public market/pair/profile/boost/order data What this skill does not do: - No wallet connections - No transactions or trading - No credential handling - No autonomous invocation (`disable-model-invocation: true`)


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: xammarie/subreddit-scout (version 1.0.0)

--- name: subreddit-scout description: Find high-fit subreddits for a product, summarize rules, and suggest value-first posting angles. --- # Subreddit Scout Use this skill when launching a product via Reddit. ## Steps 1. Identify niche keywords and adjacent problem keywords. 2. Collect 15-30 candidate subreddits. 3. Summarize each subreddit rule/profile: - self-promo policy - preferred content style - allowed post frequency 4. Rank by fit score (audience match + promo tolerance + activity). 5. Output top 5 with tailored post angles.


Security scan verdicts — ClawScan: clean | static analysis:  | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: fuzzyb33s/sales-crypto-sentiment (version 1.0.0)

--- name: sales-crypto-sentiment description: Crypto market sentiment analysis and trading signal agent. Monitors on-chain data, social sentiment, and price action to deliver actionable trading insights. Trigger phrases: "crypto signal", "analyze bitcoin", "trading alert", "bullish or bearish", "defi analytics" metadata: { openclaw: { requires: { bins: ["curl"] }, install: [ { id: "node", kind: "node", package: "clawhub", bins: ["clawhub"] } ] } } --- # Sales Crypto Sentiment Agent ## Overview You are a **crypto market intelligence agent** that analyzes sentiment, on-chain data, and price action to deliver actionable trading insights. You help traders and investors make informed decisions without hallucinating — you only surface signals you can verify. ## Your Capabilities ### Sentiment Analysis - **Social monitoring** — track Twitter/X, Reddit, Telegram, Discord crypto chatter - **News sentiment** — parse crypto news and rate market bias (bullish/bearish/neutral) - **Funding rate analysis** — identify leverage extremes on Binance, Bybit, Deribit - **Google Trends** — measure search interest as a contrarian indicator - **On-chain metrics** — exchange flows, whale transactions, validator activity ### Technical Analysis - Trend identification (higher highs/lows vs. lower highs/lows) - Support/resistance zones with volume confirmation - Moving average crossovers (MA20, MA50, MA200) - RSI overbought/oversold signals - MACD momentum shifts ### Market Intelligence - **Exchange flows** — deposit/withdrawal patterns indicate accumulation/distribution - **Whale alerts** — large wallet movements that may signal market direction - **Options market** — put/call ratios and max pain analysis - **Stablecoin supply** — USDT/USDC supply changes as liquidity signal ### Trading Signal Generation When requested, provide structured signals: ``` ASSET: BTC/USDT DIRECTION: Bullish / Bearish / Neutral CONFIDENCE: 60-95% TIMEFRAME: 4H / 1D / 1W ENTRY ZONE: $XXX - $XXX STOP LOSS: $XXX (-X%) TAKE PROFIT: $XXX (+X%) KEY CATALYST: [news/event/on-chain signal] RISK/REWARD: 1:X ``` ## What You DON'T Do - NEVER give financial advice — always frame as "signal/market analysis" - NEVER guarantee returns — always include confidence level and risk factors - NEVER trade on your behalf — you are an information tool only - NEVER ignore high volatility conditions as risk factors ## Pricing Reference (USD) | Service | Price Range | |---------|-------------| | Single asset analysis | $25–$75 | | Portfolio review (5 assets) | $75–$200 | | Weekly market report | $50–$150/mo | | Daily signals (30-day sub) | $150–$500/mo | | Custom alert dashboard | $200–$500 setup | | Full trading strategy design | $500–$2000 | ## Interaction Style Start with: - "Which asset(s) do you want analyzed?" - "What timeframe are you trading on?" - "What's your risk tolerance?" Be direct with signals. When bearish, say so. No fluff.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: komako-workshop/kokochat-search (version 0.2.0)

--- name: kokochat-search version: 0.2.0 description: "Web search via KokoChat's hosted Brave-backed search proxy. No API key required on the user's machine — credentials live on KokoChat's server (deeply.plus). Use this skill when you need quick web search results inside an OpenClaw agent without configuring Tavily / Serper / Brave keys locally." author: komako-workshop license: Apache-2.0 tags: [latest, search, web, web-search, kokochat, brave, no-key] triggers: - search the web - 搜一下 - 联网查 - hosted search - kokochat search metadata: openclaw: emoji: "🔎" requires: capabilities: - network platforms: - linux - darwin - windows --- # kokochat-search `kokochat-search` is a thin local OpenClaw exec wrapper around KokoChat's hosted search API. The user's OpenClaw does **not** store Brave (or any other search) API credentials; it only runs `bin/search.mjs`, which POSTs `{ query, count }` to the KokoChat search endpoint (default `https://deeply.plus/deeply/search`, override via `KOKO_SEARCH_API_BASE`). Originally written for KokoChat's Deeply mini-app, but the wrapper itself is generic — any agent that just wants "give me web search with no per-user key" can install and call it. ## Install ```bash openclaw skills install kokochat-search --agent <your-agent> ``` After install, add it to the agent's exec allowlist so the agent is allowed to invoke `bin/search.mjs`. KokoChat's own installer does this automatically; standalone users can do it via `openclaw approvals` (see OpenClaw docs). ## Tool command ```bash ~/.openclaw/agents/<your-agent>/workspace/skills/kokochat-search/bin/search.mjs '{"query":"EN keywords","count":5}' ``` (Inside KokoChat's `deeply` agent, the host prompt rewrites this to the real absolute path automatically.) Input: - `query` (string, required): concise English keywords. - `count` (number, optional): 1-10, default 5. Output: ```json { "ok": true, "provider": "brave", "query": "...", "requestedCount": 5, "count": 5, "results": [ { "title": "...", "url": "https://...", "snippet": "..." } ] } ``` If `ok` is false, be honest in the visible narration and do not invent URLs. Common failure modes: `search_not_configured` (server has no Brave key configured), `rate_limited` (hosted endpoint is throttling). ## Optional env - `KOKO_SEARCH_API_BASE` — override search endpoint, e.g. `http://127.0.0.1:8788` when running a local KokoChat Deeply server. - `KOKO_SEARCH_TOKEN` — bearer token if the hosted endpoint requires one (default deployment is unauthenticated with per-IP rate limit). - Legacy aliases `KOKO_DEEPLY_SEARCH_BASE` / `KOKO_DEEPLY_SEARCH_TOKEN` are still honoured. ## Source <https://github.com/komako-workshop/koko-chat/tree/main/openclaw/skills/kokochat-search>


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mtsatryan/ah-technical-writer (version 1.0.0)

--- name: technical-writer description: 'You are a technical writer specialist with expertise in creating clear, comprehensive documentation, user guides, API documentation, and. Use when: technical documentation and writing, user manuals and guides, api and developer documentation, tutorial and how-to content, release notes and changelogs.' --- # Technical Writer You are a technical writer specialist with expertise in creating clear, comprehensive documentation, user guides, API documentation, and technical tutorials. ## Core Expertise - Technical documentation and writing - User manuals and guides - API and developer documentation - Tutorial and how-to content - Release notes and changelogs - Knowledge base articles - Style guide development - Documentation strategy and governance ## Technical Stack - **Documentation Tools**: Markdown, AsciiDoc, reStructuredText, LaTeX - **Static Generators**: Docusaurus, MkDocs, Sphinx, Hugo, Jekyll - **API Documentation**: OpenAPI/Swagger, Postman, Redoc, Slate - **Collaboration**: Git, GitHub/GitLab, Confluence, SharePoint - **Diagrams**: Mermaid, PlantUML, Draw.io, Lucidchart - **Publishing**: Read the Docs, GitHub Pages, GitBook, Netlify - **Style Checkers**: Vale, write-good, alex, textlint ## Technical Documentation Framework > 📎 **Code example 1** (typescript) — see [references/examples.md](references/examples.md) ## Best Practices 1. **Know Your Audience**: Write for your specific audience level 2. **Be Clear and Concise**: Use simple, direct language 3. **Use Examples**: Include practical, working examples 4. **Visual Aids**: Use diagrams and screenshots effectively 5. **Consistency**: Maintain consistent style and terminology 6. **Organization**: Use logical structure and navigation 7. **Testing**: Test all code examples and procedures ## Documentation Strategies - Start with user goals and tasks - Use progressive disclosure for complex topics - Provide multiple learning paths - Include troubleshooting and FAQs - Keep documentation updated with code - Use version control for documentation - Gather and incorporate user feedback ## Approach - Understand the subject matter thoroughly - Identify target audience and their needs - Plan documentation structure - Write clear, concise content - Add examples and visuals - Review and edit for clarity - Test all procedures and examples ## Output Format - Provide complete documentation frameworks - Include various document templates - Add style guide implementation - Include examples and code snippets - Provide validation tools - Generate multiple output formats --- ## Reference Materials For detailed code examples and implementation patterns, see [references/examples.md](references/examples.md).


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: rmarji/scannable-reports (version 1.0.0)

--- name: scannable-reports description: Format agent outputs for mobile chat apps. Unicode progress bars, sparklines, and status indicators that render perfectly in Telegram, Discord, Slack, WhatsApp — no images needed. Use when creating status updates, dashboards, metrics reports, or any structured information for chat-based delivery. Triggers on status reports, dashboards, metrics, progress updates, or when output needs to be mobile-scannable. --- # Scannable Reports Mobile-first formatting for chat apps. Make agent outputs professional and easy to scan. ## Why This Exists Chat apps render plain text. No charts, no images inline. This skill uses Unicode characters to create visual data that works everywhere. ## Core Patterns ### 1. Progress Bars ``` CPU ███████░░░ 70% MEM ████░░░░░░ 40% Tasks ████████░░ 80% ``` **Blocks:** `░` (empty) `▒` (light) `▓` (medium) `█` (full) **10-char bar formula:** `█` × (value/10), `░` × (10 - filled) ### 2. Sparklines (Trends) ``` 24h: ▁▂▃▅▇█▇▅▃▂ Revenue: ▂▃▃▅▆▇█ (up) Errors: █▅▃▂▁▁▁ (down) ``` **Chars (low→high):** `▁ ▂ ▃ ▄ ▅ ▆ ▇ █` ### 3. Status Indicators | Emoji | Meaning | |-------|---------| | 🟢 | Good / Done / Healthy | | 🟡 | Warning / In Progress | | 🔴 | Critical / Blocked / Error | | 🔥 | Hot / Urgent / Trending | | ⚡ | Fast / Quick win | ### 4. Monospace Tables Use triple backticks for alignment: ``` Project Status Owner ───────────────────────────── VIRAL 🟡 WIP PM Hackathon 🟢 Ready PM Matrix 🔴 Block Sales ``` ### 5. Lead with Signal Most important first. Assume mobile scanning. **Bad:** > I've reviewed the project status and found several items that need attention including... **Good:** > 🔴 Matrix blocked > 🟢 Hackathon ready > 🟡 VIRAL 75% ## Example Report ``` 📊 Daily Status — Feb 27 🔴 Blocked • Matrix client (awaiting scope) 🟡 In Progress • Hackathon ████████░░ 80% • VIRAL ██████░░░░ 60% 🟢 Shipped • Demo script ✓ • Offer doc ✓ 📈 Momentum: ▃▅▆▇█ ``` ## Platform Compatibility | Platform | Progress | Sparklines | Emoji | Monospace | |----------|----------|------------|-------|-----------| | Telegram | ✅ | ✅ | ✅ | ✅ | | Discord | ✅ | ✅ | ✅ | ✅ | | Slack | ✅ | ✅ | ✅ | ✅ | | WhatsApp | ✅ | ✅ | ✅ | ⚠️ Limited | | iMessage | ✅ | ✅ | ✅ | ❌ | ## Quick Reference ``` Progress: ░▒▓█ Sparkline: ▁▂▃▄▅▆▇█ Divider: ───────── Status: 🟢🟡🔴🔥⚡ ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: dagangtj/github-pr-automation-pro (version 1.0.0)

--- name: github-pr-automation description: Automate GitHub pull request workflows including creation, review, merging, and monitoring. Handles PR templates, auto-labeling, CI/CD integration, and review automation. Use when users need to create PRs with proper formatting and templates, automate PR reviews and approvals, monitor PR status and CI checks, auto-merge PRs based on conditions, batch process multiple PRs, or track PR metrics and performance. --- # GitHub PR Automation Streamline GitHub pull request workflows with intelligent automation for creation, review, and merging. ## Features - Automated PR creation with templates - Smart labeling and assignment - CI/CD status monitoring - Auto-review and approval workflows - Conditional auto-merge - Batch PR operations - PR analytics and reporting ## Quick Start ### Create PR with Template ```bash node scripts/create_pr.js --branch feature/new-api --title "Add new API endpoint" --template feature ``` ### Monitor PR Status ```bash node scripts/monitor_pr.js --pr 123 ``` Returns CI status, review status, and merge readiness. ### Auto-merge Ready PRs ```bash node scripts/auto_merge.js --repo owner/repo --conditions "ci_passed,reviews_approved" ``` ### Batch Review PRs ```bash node scripts/batch_review.js --repo owner/repo --label "ready-for-review" --action approve ``` ## Configuration PR automation rules are defined in `references/automation_rules.json`: ```json { "auto_label": { "bug": ["fix", "bugfix"], "feature": ["feat", "feature"], "docs": ["docs", "documentation"] }, "auto_merge": { "enabled": true, "conditions": ["ci_passed", "reviews_approved", "no_conflicts"] }, "reviewers": { "backend": ["@backend-team"], "frontend": ["@frontend-team"] } } ``` ## PR Templates Store templates in `references/pr_templates/`: - `feature.md` - Feature PRs - `bugfix.md` - Bug fixes - `hotfix.md` - Urgent fixes - `docs.md` - Documentation updates ## GitHub CLI Integration This skill uses `gh` CLI for GitHub operations. Ensure it's installed and authenticated: ```bash gh auth status ``` ## Pricing - **Free**: Basic PR automation, 1 repository, manual triggers - **Pro ($14.99/month)**: Unlimited repos, auto-triggers, advanced rules - **Team ($49.99/month)**: Multi-team support, custom workflows, analytics


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: steipete/ordercli (version 1.0.0)

--- name: ordercli description: Foodora-only CLI for checking past orders and active order status (Deliveroo WIP). homepage: https://ordercli.sh metadata: {"clawdbot":{"emoji":"🛵","requires":{"bins":["ordercli"]},"install":[{"id":"brew","kind":"brew","formula":"steipete/tap/ordercli","bins":["ordercli"],"label":"Install ordercli (brew)"},{"id":"go","kind":"go","module":"github.com/steipete/ordercli/cmd/ordercli@latest","bins":["ordercli"],"label":"Install ordercli (go)"}]}} --- # ordercli Use `ordercli` to check past orders and track active order status (Foodora only right now). Quick start (Foodora) - `ordercli foodora countries` - `ordercli foodora config set --country AT` - `ordercli foodora login --email [REDACTED_SECRET] --password-stdin` - `ordercli foodora orders` - `ordercli foodora history --limit 20` - `ordercli foodora history show <orderCode>` Orders - Active list (arrival/status): `ordercli foodora orders` - Watch: `ordercli foodora orders --watch` - Active order detail: `ordercli foodora order <orderCode>` - History detail JSON: `ordercli foodora history show <orderCode> --json` Reorder (adds to cart) - Preview: `ordercli foodora reorder <orderCode>` - Confirm: `ordercli foodora reorder <orderCode> --confirm` - Address: `ordercli foodora reorder <orderCode> --confirm --address-id <id>` Cloudflare / bot protection - Browser login: `ordercli foodora login --email [REDACTED_SECRET] --password-stdin --browser` - Reuse profile: `--browser-profile "$HOME/Library/Application Support/ordercli/browser-profile"` - Import Chrome cookies: `ordercli foodora cookies chrome --profile "Default"` Session import (no password) - `ordercli foodora session chrome --url https://www.foodora.at/ --profile "Default"` - `ordercli foodora session refresh --client-id android` Deliveroo (WIP, not working yet) - Requires `DELIVEROO_BEARER_TOKEN` (optional `DELIVEROO_COOKIE`). - `ordercli deliveroo config set --market uk` - `ordercli deliveroo history` Notes - Use `--config /tmp/ordercli.json` for testing. - Confirm before any reorder or cart-changing action.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: dagangtj/crypto-price-alerts (version 1.0.0)

# Crypto Price Alerts Skill Set price alerts for cryptocurrencies and get instant notifications. ## Capabilities - Set price alerts for any crypto pair - Monitor multiple alerts simultaneously - Get notified via message when price hits target - Manage alerts (list, add, remove) ## Commands - "Alert me when BTC hits $100k" - "Notify me if ETH drops below $3000" - "Show my active alerts" - "Remove BTC alert" ## Setup Alerts are stored locally in `~/.openclaw/workspace/data/price_alerts.json` ## Tools ### set_price_alert Create a new price alert. ### list_alerts Show all active alerts. ### remove_alert Delete an alert. ### check_alerts Check if any alerts have been triggered (runs automatically). ## Pricing $3/month subscription ## Author AI Trading Tools


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: leo-zzl/mood-logger (version 1.0.0)

--- name: mood-logger version: 1.0.0 description: 记录每日心情并保存到 Obsidian 库。当用户要求记录心情、情绪日记、心情追踪或类似的情绪记录任务时使用。使用 scripts/log_mood.py 脚本确保格式固定一致。支持心情评分(1-10)、标签和备注。 --- # 心情日记 用于记录每日心情和情绪状态，保存到 Obsidian 库中，格式完全固定。 ## 使用方法 使用 Python 脚本记录心情： ```bash python3 ~/.openclaw/workspace/skills/mood-logger/scripts/log_mood.py \ --date 2026-03-27 \ --score 8 \ --tags "开心,充实" \ --note "今天完成了重要任务" ``` ### 参数说明 - `--date`: 日期 (YYYY-MM-DD)，默认为今天 - `--score`: 心情评分 (1-10)，必需 - `--tags`: 心情标签，逗号分隔，必需 - `--note`: 备注/原因 (可选) ### 评分与表情对照 | 评分 | 表情 | 说明 | |------|------|------| | 9-10 | 😄 | 非常开心 | | 7-8 | 😊 | 开心/不错 | | 5-6 | 😐 | 平静/一般 | | 3-4 | 😔 | 低落/疲惫 | | 1-2 | 😢 | 很难过 | ### 示例 ```bash # 简单记录 python3 ~/.openclaw/workspace/skills/mood-logger/scripts/log_mood.py \ --score 8 --tags "开心" # 带备注 python3 ~/.openclaw/workspace/skills/mood-logger/scripts/log_mood.py \ --score 6 --tags "平静,普通" --note "今天没什么特别的事" # 多条记录（支持一天多次记录） python3 ~/.openclaw/workspace/skills/mood-logger/scripts/log_mood.py \ --score 4 --tags "疲惫,焦虑" --note "工作压力有点大" # 指定日期 python3 ~/.openclaw/workspace/skills/mood-logger/scripts/log_mood.py \ --date 2026-03-26 --score 9 --tags "兴奋,成就感" ``` ## 文件格式 生成的文件格式固定如下： ```markdown # YYYY-MM-DD 心情日记 ## 今日心情 ### 😊 评分: 8/10 **标签**: `开心` `充实` **备注**: 今天完成了重要任务 ### 😔 评分: 4/10 **标签**: `疲惫` `焦虑` **备注**: 工作压力有点大 --- *记录时间: YYYY-MM-DD HH:MM* ``` ## 配置信息 **保存路径**: `/mnt/c/Users/loong/iCloudDrive/iCloud~md~obsidian/HomeMo.Art/05-Daily/` **文件名格式**: `心情日记-YYYY-MM-DD.md` **脚本位置**: `scripts/log_mood.py` ## 周报功能 ### 生成周报 ```bash # 生成本周周报（打印到控制台） python3 ~/.openclaw/workspace/skills/mood-logger/scripts/weekly_mood_report.py # 生成指定周的周报 python3 ~/.openclaw/workspace/skills/mood-logger/scripts/weekly_mood_report.py --date 2026-03-27 # 保存到文件 python3 ~/.openclaw/workspace/skills/mood-logger/scripts/weekly_mood_report.py --output /tmp/mood_report.md ``` ### 周报内容 - 本周心情平均分 - 最高/最低心情 - 心情标签统计 TOP5 - 每日心情走势 - 备注摘录 ### 定时发送 每周日早上 9:00 自动生成并发送周报。 设置命令： ```bash openclaw cron create --name "mood-weekly-report" \ --schedule "0 9 * * 0" \ --command "python3 ~/.openclaw/workspace/skills/mood-logger/scripts/send_weekly_report.py" \ --channel openclaw-weixin \ --to "[REDACTED_SECRET]" ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: azzazhang/bing-search-free (version 1.0.0)

--- name: bing-search description: "免费网页搜索，使用 Bing + Jina.ai 提取内容摘要。无需 API Key，直接可用。适用于快速获取搜索结果和网页内容。" --- # Bing Search Skill 免费网页搜索方案，基于 Bing 搜索 + Jina.ai 内容提取。 ## 特性 - ✅ **完全免费** — 无需 API Key - 🌐 **Bing 搜索** — 全球搜索结果 - 📄 **内容摘要** — Jina.ai 自动提取页面核心内容 - ⚡ **快速响应** — 通常 1 秒内完成 ## 使用方法 ### 命令行 ```bash ./scripts/bing_search.sh '<json>' ``` **示例：** ```bash # 基本搜索 ./scripts/bing_search.sh '{"query": "Python 教程"}' # 指定结果数量 ./scripts/bing_search.sh '{"query": "AI news", "max_results": 5}' # 中文搜索 ./scripts/bing_search.sh '{"query": "人工智能 最新消息", "max_results": 3}' ``` ### 参数说明 | 参数 | 类型 | 默认值 | 说明 | |------|------|--------|------| | `query` | string | 必填 | 搜索关键词 | | `max_results` | number | 5 | 返回结果数量 (1-10) | ## 输出格式 ```json { "query": "搜索关键词", "results": [ { "url": "https://example.com", "title": "页面标题", "content": "页面内容摘要...", "score": 0.95 } ], "response_time": 0.75 } ``` ## 技术原理 1. **Bing 搜索** — 获取搜索结果列表 2. **Jina.ai 提取** — `https://r.jina.ai/http://bing.com/search?q=关键词` 3. **结果解析** — 提取标题、URL、内容摘要 ## 限制 - 免费服务，有请求频率限制 - 不适合大规模自动化搜索 - 结果质量依赖 Bing 和 Jina.ai ## 故障排除 **问题：** 返回空结果 **解决：** 检查网络连接，稍后重试 **问题：** 请求频繁被拒 **解决：** 等待几秒后再试，或减少请求频率 --- **来源：** agents-skills-personal → openclaw-workspace


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