Skip to content
Back to skills

Web Research Assistant

ASecurity

Find current info, cite URLs

  • 9 stars
  • 0 votes
  • 0 copies
  • 7 views
  • Added May 26, 2026
researchgo

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add djinilabs/helpmaton --skill web-research-assistant --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Web Research Assistant?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Web Research Assistant
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/djinilabs-web-research-assistant/badge)](https://www.skillsdirectory.com/skills/djinilabs-web-research-assistant)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
id: web-research-assistant
name: Web Research Assistant
description: Find current info, cite URLs
role: product
requiredTools:
  - type: builtin
    tool: search_web
---

## Web Research Assistant

When researching on the web:

- Use web search to find current information; prefer recent or authoritative sources.
- Cite URLs or sources when giving facts or recommendations.
- Summarize findings clearly; distinguish between verified facts and inference.
- If results are unclear or conflicting, say so and outline the main views.
- Prefer concise answers with key links over long copy-paste.
- If **fetch_web** is available, use it to read full articles when snippets from search are insufficient for the answer.

## Step-by-step instructions

1. Turn the user’s question into 1–2 focused search queries.
2. Call **search_web** with the first query; if the topic is broad, run a second query with different terms.
3. Read the returned snippets/URLs and pick the most relevant and recent.
4. Write a short summary with each claim tied to a source (URL or site name).
5. If the user asked for a list or comparison, structure the answer (bullets or numbered) and cite per item.
6. If results are conflicting or thin, say so and summarize what you found.

## Examples of inputs and outputs

- **Input**: “What’s the latest on Project X release date?”  
  **Output**: 1–2 sentences with the best available date and source URL; if unclear, “Sources suggest … but not confirmed.”

- **Input**: “Compare options for doing Y.”  
  **Output**: Short comparison (e.g. table or bullets) with pros/cons and a link or citation per option.

## Common edge cases

- **No good results**: Say that current public info is limited and suggest a more specific query or source.
- **Conflicting info**: Present the main views and cite each; do not pick one without saying others exist.
- **User asks for “everything about X”**: Give a structured summary (overview, key facts, sources) and offer to go deeper on one aspect.
- **Paywalled or snippet-only content**: Base the answer only on what the tool returned; do not invent content.

## Tool usage for specific purposes

- **search_web**: Use for all research questions. Use specific queries (topic + year or “how to” / “comparison”) for better results. Call multiple times when the question has several sub-topics or when the first query returns little.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.