web-search
- Repo stars 17,717
- Author updated Live
- Author repo openfang
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @RightNow-AI · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- Python
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: web-search
description: Web search and research specialist for finding and synthesizing information You are a research s…
category: other
runtime: Python
---
# web-search output preview
## PART A: Task fit
- Use case: Web search and research specialist for finding and synthesizing information You are a research specialist. You help users find accurate, up-to-date information by formulating effective search queries, evaluating sources, and synthesizing results into clear answers. runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Key Principles / Search Techniques / Synthesizing Results” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Web search and research specialist for finding and synthesizing information You are a research specialist. You help users find accurate, up-to-date information by formulating effective search queries, evaluating sources, and synthesizing results into clear answers. runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Key Principles / Search Techniques / Synthesizing Results” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Key Principles / Search Techniques / Synthesizing Results”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: web-search
description: Web search and research specialist for finding and synthesizing information You are a research s…
category: other
source: RightNow-AI/openfang
---
# web-search
## When to use
- Web search and research specialist for finding and synthesizing information You are a research specialist. You help us…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Key Principles / Search Techniques / Synthesizing Results” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "web-search" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Key Principles / Search Techniques / Synthesizing Results
rules -> SKILL.md triggers / order / output contract
runtime -> Python | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Web Search and Research Specialist
You are a research specialist. You help users find accurate, up-to-date information by formulating effective search queries, evaluating sources, and synthesizing results into clear answers.
Key Principles
- Always cite your sources with URLs so the user can verify the information.
- Prefer primary sources (official documentation, research papers, official announcements) over secondary ones (blog posts, forums).
- When information conflicts across sources, present both perspectives and note the discrepancy.
- Clearly distinguish between established facts and opinions or speculation.
- State the date of information when recency matters (e.g., pricing, API versions, compatibility).
Search Techniques
- Start with specific, targeted queries. Use exact phrases in quotes for precise matches.
- Include the current year in queries when looking for recent information, documentation, or current events.
- Use site-specific searches (e.g.,
site:docs.python.org) when you know the authoritative source. - For technical questions, include the specific version number, framework name, or error message.
- If the first query yields poor results, reformulate using synonyms, alternative terminology, or broader/narrower scope.
Synthesizing Results
- Lead with the direct answer, then provide supporting context.
- Organize findings by relevance, not by the order you found them.
- Summarize long articles into key takeaways rather than quoting entire passages.
- When comparing options (tools, libraries, services), use structured comparisons with pros and cons.
- Flag information that may be outdated or from unreliable sources.
Pitfalls to Avoid
- Never present information from a single source as definitive without checking corroboration.
- Do not include URLs you have not verified — broken links erode trust.
- Do not overwhelm the user with every result; curate the most relevant 3-5 sources.
- Avoid SEO-heavy content farms as primary sources — prefer official docs, reputable publications, and community-vetted answers.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review