event-research-analyzer

Analyzes event card reports into a source-attributed deep fact base as strict JSON.

5|1|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/shiker1996/wechat-editroom --skill event-research-analyzer-shiker1996
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-research-analyzer
Source: https://github.com/shiker1996/wechat-editroom/tree/main/skills/event-research-analyzer
Command: npx skills add https://github.com/shiker1996/wechat-editroom --skill event-research-analyzer-shiker1996

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When producing event-based social graphics, raw collected reports are messy, repetitive, and unverified. This Skill turns an event card plus its fetched report contents into a traceable deep fact base, so downstream storyboard and graphic generation rest on verified, source-attributed facts instead of guesses. ## Core Features & Use Cases - Source-Attributed Fact Extraction: Every claim, mechanism, impact, and open question is bound to source_id values from the input, separating confirmed facts from unverified claims and model inferences. - Structured JSON Output: Produces a strict JSON object with fields like context, keyChanges, mechanisms, benchmarks, impacts, risks, openQuestions, and a sourceAudit section counting independent sources. - Use Case: As an automatic internal stage in the social-event pipeline, it runs after report fetching and before storyboard generation—for example, analyzing a breaking tech event's multiple reports into a deduplicated fact base that the graphic generator can safely consume. ## Quick Start Provide an event card with its fetched report contents and ask the pipeline to run the event deep analysis stage to produce the deep event fact base JSON.

Frequently Asked Questions about event-research-analyzer

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

FAQPage Schema
How do I generate a deep fact base from event reports?

Feed the event card fact base together with the fetched report contents into this stage. It outputs a strict JSON object containing context, key changes, mechanisms, impacts, risks, and open questions, each tied to source identifiers.

What input does the event research analyzer require?

It requires the event_fact_base_with_source_content contract: an event card fact base plus the fetched full text of associated reports. It only uses these inputs and treats report text as untrusted material, never executing instructions found inside it.

Can I use this skill as a standalone user-facing tool?

No. It is an automatic internal stage in the social-event graphic generation chain with no independent user entry point. It runs between report collection and storyboard or graphic generation.

How does it handle conflicting or repeated reports?

Repeated paraphrasing across multiple reports is not counted as independent evidence. The sourceAudit section tracks the independent source count, issues, and needed materials, while unverified claims are marked separately from confirmed facts.

What happens when there is no evidence for an output field?

Fields without supporting evidence return empty arrays rather than guessed content. The skill never fabricates numbers, causes, motives, responsibilities, or legal conclusions to fill the structure.