open-source-trend-storyboard

Plans multi-source open-source trend facts into traceable social card storyboards.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning scattered open-source trend signals (multiple projects, sources, and timelines) into a coherent, evidence-backed social media card storyboard is hard: single releases get overhyped as industry trends, facts get duplicated across pages, and sources get lost. This Skill structures verified trend facts into a page-by-page storyboard where every claim stays traceable to its source. ## Core Features & Use Cases - Trend narrative planning: Organizes facts into a fixed narrative arc (trend signal → driving actors → timeline/ecosystem signals → comparison → open questions) before deciding page count and layout. - Evidence gating and degradation: Requires at least two of cross-source, cross-actor, or cross-time signals; otherwise downgrades the content to a single-event or tech card instead of fabricating a trend. - Strict structured output: Emits strict JSON conforming to the social_card_storyboard contract, with per-block source_refs and semantic visual intent, and no HTML, CSS, or invented metrics. - Use Case: Given a fact base covering several organizations adopting a new open-source protocol over two years, produce a 4–6 page WeChat/Xiaohongshu card plan with a cover, trend judgment, actor actions, comparison table, and observation boundaries. ## Quick Start Classify the collected open-source trend event facts and generate a traceable multi-page social card storyboard from them.

Frequently Asked Questions about open-source-trend-storyboard

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

FAQPage Schema
How do I turn open-source trend research into social media cards?

Provide a fact base of confirmed facts, actors, timelines, and change signals classified as open_source_trend. The Skill plans a 4-6 page storyboard with cover, trend judgment, actors, comparison, and ending pages, each block carrying source references.

What input format does the trend storyboard planning require?

It requires the social_card_fact_base contract: event content classified as open_source_trend containing confirmed facts, subjects, timelines, change signals, and explicit unknowns. Single-project introductions or one-off releases are downgraded instead of treated as trends.

When is content not eligible for a trend storyboard?

Content lacking at least two of cross-source, cross-actor, or cross-time change signals is downgraded to a regular event or tech card. Star counts, trending rankings, or a single release cannot alone support an industry trend claim.

Does the storyboard output include HTML or visual styling?

No. The output is strict JSON with page kind, role, content blocks, source_refs, and semantic visual intent such as emphasis, tone, icons, and badges. Font sizes, color values, HTML, and CSS are explicitly forbidden.

How does the storyboard prevent duplicated or fabricated facts?

Each fact is assigned to exactly one page for full narration, and every content block must cite source_refs from the fact base. The Skill forbids inventing growth curves, market share, adoption rates, or actor motivations.