event-card-storyboard

Plans traceable event storyboards from verified fact bases for WeChat and Xiaohongshu cards.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a breaking-news fact base into a coherent multi-page social card story is hard: facts get duplicated across pages, unverified claims leak in as conclusions, and disclaimers replace real discussion. This Skill converts a structured event fact base into a page-by-page storyboard with a fixed narrative arc and strict evidence boundaries. ## Core Features & Use Cases - Structured narrative planning: Organizes pages as cover, what-happened, timeline, controversy-and-discussion, and ending, with conditional rules for when a timeline page is warranted. - Evidence traceability: Every content block carries source references, unverified claims keep speaker attribution and uncertainty markers, and each core fact is assigned to exactly one primary page. - Semantic visual intent: Outputs visual hints (emphasis, tone, icons, badges) for key facts, comparisons, and timelines without emitting HTML, CSS, or layout coordinates. - Use Case: Given a fact base about a corporate event with confirmed facts, party responses, and a timeline, produce a strict JSON storyboard of 4-10 pages ready for downstream card rendering on WeChat or Xiaohongshu. ## Quick Start Given this event fact base, plan a traceable social card storyboard covering what happened, key changes, controversies, and what to watch next.

Frequently Asked Questions about event-card-storyboard

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

FAQPage Schema
How do I turn a news event fact base into a social media storyboard?

Provide a social_card_fact_base containing confirmed facts, sourced claims, party responses, and timeline nodes. The Skill plans pages in a what-happened, key-changes, discussion, and follow-up arc, returning strict JSON with per-block source references.

What input format does the event storyboard planner require?

It requires the social_card_fact_base contract with content type event. Fact bases upgraded to open_source_technology or open_source_trend are rejected, since those belong to different storyboard skills.

When is a timeline page generated in the storyboard?

A standalone timeline page is created only when the fact base contains at least two meaningful, ordered time nodes. A single time point is folded into the what-happened or current-status page instead.

Does the storyboard output HTML or CSS for card rendering?

No. The output is strict JSON with semantic visual intent such as emphasis, tone, icons, and badges. Font sizes, color values, HTML, CSS, and layout coordinates are explicitly forbidden and handled by downstream renderers.

How are unverified claims handled in event storyboards?

Unverified claims must retain the speaker and uncertainty wording such as allegedly or not independently confirmed. The Skill never infers motive, legality, liability, or causation, and never presents speculation as conclusion.

What happens when the fact base has insufficient evidence?

The storyboard is shortened or deferred rather than padded. With only one confirmed fact, a compact cover, what-happened, boundary, and ending structure is used, and no fabricated controversy pages are generated.