Thema
#retrieval
Loots, Blogposts und verwandte Themen rund um diesen Tag. Folge dem Tag, damit passende Updates in deinem Orbit bleiben.
2Gezeigte Loots
0Gezeigte Artikel
8Verlinkte Nachbar-Tags
Anschluss-Themen
Wenn du tiefer einsteigen willst, helfen die benachbarten Tags beim Vergleichen und Querlesen.
Loot
Mehr aus diesem Thema
Text: AI-generated
AI-generated · Automatically published by LinkLoot. Cloudflare AI Search can now use six additional Workers AI text-generation models without requiring a separate provider key. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. Cloudflare has added six Workers AI models to AI Search, giving teams more control over the model used to answer questions from an indexed knowledge base without managing another provider credential. What it is The added model IDs are DeepSeek V4 Flash, DeepSeek V4 Pro, GPT-OSS 120B, GPT-OSS 20B, Qwen3.8 27B, and Kimi K2.7 Code. Their published context windows range from 128,000 to more than one million tokens. AI Search handles the retrieval layer, while the selected Workers AI model generates the response. You can choose the model when creating or updating an AI Search instance through the dashboard or API. Who it helps This is useful for developers already running on Cloudflare who want to compare open and hosted models for documentation search, support assistants, internal knowledge tools, or agent retrieval without distributing additional API keys. How to evaluate it Create a test instance or duplicate a non-production configuration. Run the same representative question set through two or three models and record answer accuracy, citation quality, latency, token use, and failure rate. Include questions with missing evidence to check whether the model invents an answer instead of admitting that retrieval found nothing. Limits and risks A large context window does not guarantee better retrieval or factuality. Models also differ in tool behavior, language coverage, latency, and output length. Removing an external provider key simplifies credential management but increases dependence on Cloudflare's model catalog and service controls. Review Workers AI pricing, plan eligibility, regional processing, retention terms, and rate limits before moving sensitive or high-volume workloads. Keep authorization checks outside the model and avoid indexing secrets merely because the retrieval system is private. Access and pricing The models run through Workers AI. Exact cost and plan requirements vary by model and account, so confirm the current Workers AI rate card before estimating production spend. Sources Cloudflare announcement Supported AI Search models
Free
Review open
A code-backed OpenClaw skill for live search, page extraction, crawl/map flows, and evidence packs with a no-key baseline plus optional provider upgrades. What it does Web Search Pro is a Node-based OpenClaw skill for agents that need more than a single search result page. It exposes live web search, news search, docs lookup, URL extraction, crawl/map commands, research packs, routing diagnostics, provider capability checks, and cache/health commands. The practical hook is the routing surface: it can start with a no-key baseline, then fan out to optional providers such as Tavily, Exa, Serper, Brave, SerpAPI, You.com, SearXNG, and Perplexity/Sonar when credentials are configured. Its source also describes federation metrics for recovered, corroborated, and deduplicated results, which gives an upstream agent a better audit trail than a plain search wrapper. Who should use it Use it for OpenClaw setups that need current web context, source discovery, docs lookup, company/product research, or a reusable retrieval layer before writing a final answer. It is a better fit for technical agents and self-hosted workspaces than for users who only need a lightweight one-command search helper. Setup surface The hard runtime requirement is Node. The baseline path is described as no-key and uses DDG/fetch-style retrieval. Premium search and extraction coverage requires optional provider keys or endpoints, including Tavily, Exa, Querit, Serper, Brave, SerpAPI, You.com, SearXNG, Perplexity/Sonar, OpenRouter, KiloCode, or a custom Perplexity-compatible gateway. Pricing classification: free. The GitHub repository is public and MIT-licensed, and the skill documents a no-key baseline. Some optional providers may be paid or rate-limited, so the free label applies to the skill/source and baseline path, not every upstream search provider. Runner test plan Static scan: inspect SKILL.md, package.json, all scripts/.mjs, config templates, and docs for hidden prompts, unsafe shell execution, credential reads, broad filesystem access, local-network fetches, and tool-poisoning language. Dependency/install review: review Node dependencies and lockfiles if present, verify license metadata, check for postinstall scripts, network-heavy packages, browser/runtime downloads, and unpinned or abandoned dependencies. Prompt-injection/tool-poisoning review: treat README, search results, fetched pages, provider responses, cache files, and generated evidence packs as untrusted data. Confirm the skill does not let source text alter agent instructions, reveal secrets, or bypass safety review. Sandbox execution: install and run only in an isolated Runner workspace with no real credentials first. Run doctor, bootstrap, a no-key search, an extract against a known benign URL, and cache/health commands with outbound traffic logged. Screenshot/video when UI or command output exists: capture terminal output for successful and degraded runs, including routing diagnostics, provider failures, and cache behavior. Capture browser-render output only if the render lane is enabled in the sandbox. Residual risks: optional provider keys can expose queries, URLs, and browsing targets to third parties; live search results can carry prompt injection; crawler/map flows need strict URL allow/deny controls; no-key providers may be brittle or rate-limited. Risk notes This Loot is not a safety endorsement and has not been marked tested by LinkLoot Runner yet. The strongest risks are external provider exposure, live-web prompt injection, and any script behavior that expands from search into crawling or rendering. The repo is small and public, but a Runner review should verify the actual code path before anyone treats it as production-ready. Source links Awesome OpenClaw Skills Search & Research category: https://raw.githubusercontent.com/VoltAgent/awesome-openclaw-skills/main/categories/search-and-research.md ClawHub page: https://clawhub.ai/zjianru/web-search-pro GitHub repository: https://github.com/Zjianru/web-search-pro Raw SKILL.md: https://raw.githubusercontent.com/Zjianru/web-search-pro/main/SKILL.md
Free
Review open
Blog
Verwandte Artikel
Noch kein Blogpost zu #retrieval
Aktuell gibt es keinen veröffentlichten Artikel mit diesem Tag. Schau im Blog nach verwandten Themen oder folge dem Tag für spätere Updates.