web search

Other Community

Skill notes

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.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
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
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview web-search.preview
# 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.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.