agentleFS
JacobinwweyJacobinwwey/notemdpro/skills/web-researcher/SKILL.md

web-researcher

Skill2 starsChanged 39 days agoMITView on GitHub

Use when gathering web research context via Tavily or DuckDuckGo before content generation or topic summarization

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Fact-checking: Verify information from web sources

    line 16

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

NoteMD Pro - Web Research

Overview

This feature researches topics using web search providers and provides summarized context. It supports both Tavily (API-based) and DuckDuckGo (scraper-based) providers.

When to Use

  • Research before writing: Gather context for content generation
  • Summarize topics: Get overview of any subject
  • Fact-checking: Verify information from web sources
  • Literature review: Collect information from multiple sources

Function Call Chain

_performResearch (searchUtils.ts)
├── SearchManager.getProvider(settings)
│   ├── TavilyProvider (if searchProvider='tavily')
│   └── DuckDuckGoProvider (if searchProvider='duckduckgo')
├── provider.search(query, settings)
│   └── Returns SearchResult[]
├── fetchContentFromUrl(url)  [For DuckDuckGo only]
│   └── requestUrl({url, method: 'GET'})
│   └── Extract text from HTML
├── Combine research context
└── Return combined context string

Search Providers

Tavily Provider

  • API-based search (requires API key)
  • Returns snippets/summaries
  • Faster, more reliable
  • Configuration: tavilyApiKey, tavilyMaxResults, tavilySearchDepth

DuckDuckGo Provider

  • Web scraping (no API key needed)
  • Returns URLs, fetches full content
  • More results, slower
  • Configuration: ddgMaxResults, ddgFetchTimeout

Key Functions (from searchUtils.ts)

_performResearch

Performs web research for a topic and returns combined context.

export async function _performResearch(
  settings: NotemdSettings,
  topic: string,
  progressReporter: ProgressReporter,
): Promise<string | null>;

fetchContentFromUrl

Fetches content from a URL and extracts text.

export async function fetchContentFromUrl(
  url: string,
  progressReporter: ProgressReporter,
  debugMode?: boolean,
): Promise<string>;
// Returns extracted text or error message

SearchManager (search/SearchManager.ts)

Factory for getting search provider.

export class SearchManager {
  static getProvider(settings: NotemdSettings): SearchProvider;
  // Returns TavilyProvider or DuckDuckGoProvider
}

Settings

Provider Settings

SettingDescription
searchProvider'tavily' or 'duckduckgo'
tavilyApiKeyAPI key for Tavily

Tavily Settings

SettingDescription
tavilyMaxResultsNumber of results (default: 5)
tavilySearchDepth'basic' or 'advanced'

DuckDuckGo Settings

SettingDescription
ddgMaxResultsNumber of results (default: 5)
ddgFetchTimeoutTimeout in seconds (default: 10)

Contextual Context (Macro Settings)

SettingDescription
enableFocusedLearningInject macro user domain preferences globally
focusedLearningDomainThe specific domain context (e.g., "Physics", "History")

Research Limits

SettingDescription
maxResearchContentTokensMax tokens for research context
enableApiErrorDebugModeEnable detailed error logging

Prompt Template (researchSummarize)

From promptUtils.ts:

Summarize the following search results for the topic "{TOPIC}".
Provide a concise yet comprehensive overview.
Focus on key findings, data, and important conclusions.
Format the summary in Markdown.
The output language should be {LANGUAGE}.

Search Results:
{SEARCH_RESULTS_CONTEXT}

Output Format

Research context is formatted as:

Research context for "{query}" (via {provider}):

Result 1:
Title: {title}
URL: {url}
Content: {content}

Result 2:
Title: {title}
...

Error Handling

Common Errors

  1. No API key for Tavily
    • Error: "Tavily API key not configured"
    • Solution: Add API key in settings or switch to DuckDuckGo
  2. Network timeout
    • Error: "Timeout fetching {url}"
    • Solution: Increase ddgFetchTimeout
  3. No search results
    • Warning: "Search returned no results"
    • Solution: Try different search query

Debug Mode

Enable enableApiErrorDebugMode for detailed error information including:

  • Full API request/response
  • HTTP status codes
  • Error stack traces

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.