Quick research

Skill Razaib-khan/ForgeWeave/src/forgeweave/templates/qwen/.qwen/skills/quick-research

Lightweight single-pass search for fast answers when context is missing. Use this skill whenever the agent needs to: look up an API signature, verify a library version, check a CLI flag, find a code example, research an error message, or confirm a configuration option. Triggers automatically when you are about to write code with an unfamiliar library or encounter a gap in context. NOT for comprehensive research — use deep-research for that.From its SKILL.md

Install

npx -y skills add Razaib-khan/ForgeWeave --skill quick-research

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.6 KB, 706 tokens by cl100k_base, as published. Nobody here has run it

Single Search

Purpose

Get fast, focused answers by crawling a small set of authoritative URLs and extracting the relevant information. No multi-agent pipeline, no planning phase, no validation stage. This is the default research mode — use it whenever you lack context about any technology.

When to Use (Auto-Detect)

Always call websearch or load this skill when:

You are about to write code using an API/library you're not 100% confident about
You encounter an unfamiliar function signature, parameter, or return type
You need to verify a library version, feature availability, or deprecation status
You need a quick code example for a specific API method
You encounter an error and need to look up the error message or fix
You need to confirm a configuration option, CLI flag, or environment variable
The question can be answered from 1-3 sources
You are short on context for any technology usage — stop and search before coding

When NOT to Use

The topic requires comparing multiple sources or perspectives — use deep-research
You need to understand a new framework from scratch (3+ subtopics) — use deep-research
The question is about code in the current project — answer directly from the codebase
The user explicitly asked for "deep research" or "comprehensive report"
The project will need this knowledge repeatedly — research and convert to skill

Inputs

Input	Type	Required	Description
`query`	string	Yes	The specific question to answer
`seed_urls`	array of string	No	Suggested URLs to check (auto-discovered if omitted)

Expected Outputs

A concise answer with:

Direct answer to the question
1-3 code examples if applicable
Source URLs for each claim

Exact Workflow Steps

Determine 1-3 authoritative URLs (official docs, API refs)
Fetch them using webfetch
For JS-rendered pages or incomplete responses, use Playwright MCP tools:
- browser_navigate to load the page
- browser_snapshot to extract structured content via element refs
Extract the specific information requested
Return a concise answer with sources

Required Checks

Every claim has a source URL
Answer directly addresses the question

Failure Modes

Failure Condition	Response
URL returns 404	Try Playwright MCP as fallback
Information not found at any URL	Report "not found in searched sources"

Examples

Example: "What's the cacheLife default profile in Next.js 16?"

Crawl nextjs.org/docs/app/api-reference/functions/cacheLife
Extract: default is stale=5min, revalidate=15min, expire=never
Return answer with source URL

Example: "Fix: ModuleNotFoundError: No module named 'aiohttp'"

This is a context gap — stop and search
websearch("python install aiohttp package")
Extract: pip install aiohttp
Proceed with the fix

References

Reference	Path
Web Scraper skill	`../web-scraper/SKILL.md`

What ships with it: 2 files

2.5 KB alongside SKILL.md, 1 of them executable

references/

source-reliability.md704 B

scripts/

fetch_and_extract.pyruns1.9 KB

Gives 0 of the 12 instructions most quality gates skills give in 706 tokens

Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-07

Read the output and check the exit codein 54 of 1195, across 14 files
Verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
Identify the verification command proving the claimin 51 of 1195, across 12 files
Run the full verification commandin 50 of 1195, across 11 files
Verify output confirms the claimin 49 of 1195, across 12 files
Check version control diff after agent delegationin 46 of 1195, across 6 files
State claim with evidencein 44 of 1195, across 4 files
Run the test suitein 33 of 1195, across 26 files
Keep state in memory by defaultin 27 of 1195, across 6 files
Make prototype runnable with one commandin 26 of 1195, across 5 files
Produce a verification reportin 25 of 1195, across 14 files
Detect the package manager from lockfilesin 24 of 1195, across 5 files

Said here and by no other author read

stop and search before coding
determine authoritative URLs
use Playwright for JS-rendered pages
extract requested information
return concise answer with sources
try Playwright as fallback on 404

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.