data-research

Automates recurring web/data research workflows with configurable pipelines and tracked output.

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/weiping/gbrain-cn --skill data-research-weiping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-research
Source: https://github.com/weiping/gbrain-cn/tree/main/skills/data-research
Command: npx skills add https://github.com/weiping/gbrain-cn --skill data-research-weiping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual, error-prone work of finding sources, extracting structured fields from emails or documents, and keeping a single canonical tracker up to date without double-counting.

Core Features & Use Cases

  • Recipe-driven research pipeline: Reuses the same 7-phase workflow while changing only the queries, classification rules, extraction schema, and tracker page format.
  • Deterministic-first extraction with integrity safeguards: Saves raw sources immediately, applies deterministic extraction first, uses LLM only as a fallback, and re-reads saved files when summarizing to prevent batch hallucination errors.
  • Archival + deduplication + backlinking: Archives raw sources, deduplicates entries (exact and fuzzy), updates canonical tracker tables, and backlinks entities (people and companies) to their knowledge pages.

Quick Start

Use the skill to build a recurring tracker from investor update emails by running a research and tracking job configured with the investor-updates recipe.

Frequently Asked Questions about data-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract structured data from emails and update a tracker without duplicates?

Extracting structured data from emails without duplicates requires a pipeline that parses fields, applies exact and fuzzy deduplication logic, and updates a canonical tracker while archiving raw inputs with backlinks. This eliminates manual matching errors.

What is deterministic-first extraction and when do I need it for data research?

Deterministic-first extraction is a method that applies strict parsing rules to emails and documents before using an LLM as a fallback. You need it for recurring data research pipelines to prevent batch hallucination errors and ensure structured field accuracy.

How do I automate an investor update tracker from email sources?

Automating an investor update tracker involves running a recipe-driven research job that searches sources, extracts schema fields from emails or attachments, deduplicates entries, and updates the tracker page while archiving raw emails with backlinks to the canonical record.

Can I build a recurring tracking pipeline for expenses and donations from emails?

Yes, you can build a recurring tracking pipeline for expenses and donations by configuring recipe-defined queries and extraction schemas. The pipeline processes emails, web sources, and APIs together, deduplicates entries, and updates the canonical tracker automatically.

Does this structured data research approach support knowledge graph backlinking?

Yes, structured data research supports knowledge graph backlinking by archiving raw sources immediately and linking extracted entities like people and companies back to their respective knowledge pages within the updated canonical tracker.

What are the limitations of using LLM fallbacks for email-to-data extraction?

LLM fallback limitations in email-to-data extraction include potential batch hallucination errors, which require integrity safeguards like re-reading saved raw files when summarizing to ensure extraction accuracy and prevent double-counting in the canonical tracker.