| name | h4cker-research |
| description | Collect and synthesize bounded evidence for HN stories or explicit web research when claims need sources, uncertainty, and failure disclosure. |
H4cker Research
Use When
- The user asks to investigate, verify, compare, or deep-read an HN story or a public web topic.
- A factual answer needs independent evidence beyond the HN title, URL, or discussion.
- A delegated source-research task asks only for evidence collection.
Do Not Use When
- The request can be answered from the supplied item, comments, or existing product data.
- The task is ranking, preference mutation, voting, posting, or drafting a reply.
- The request lacks a research question that can be answered with public, attributable evidence.
Research Process
- Restate the narrow question and list the claims that need evidence.
- Apply a source limit of six fetched sources. Stop earlier when two independent sources support the material claims.
- Prefer primary sources: project documentation, original research, standards, filings, or statements from the responsible organization.
- Use secondary sources only to add independent context or when no primary source is available. Distinguish reporting from primary evidence.
- Record the source title, canonical URL, source type, publication date when available, and the claim it supports.
- Separate sourced facts from inference. Never imply that an inaccessible or unread page was inspected.
- Disclose search, fetch, parsing, paywall, freshness, and source-coverage failures that could change the conclusion.
- Stop when the source limit, delegated budget, or requested scope is reached. Return partial evidence instead of silently expanding the task.
Evidence Rules
- Cite the closest supporting source for each material factual claim.
- Prefer recent evidence for changeable facts and say when freshness could not be established.
- Do not treat HN score or comment sentiment as proof that an external claim is true.
- Do not expose private work context, credentials, cookies, another user's data, or raw internal prompts.
- Do not mutate product state or request a mutation tool.
Output Contract
Return these sections in order:
Finding: concise answer to the research question.Evidence: bounded list of source, URL, supported claim, and source type.Uncertainty: unresolved conflicts, inference, and freshness limits.Failures: unavailable sources or collection failures; write None only when there were none.
