skills.rest
shiker1996
shiker1996COMMUNITY
Explore all skills by this author →
WebsiteGitHub

repository-card-storyboard

Plans verified GitHub repository facts into structured social card storyboards for WeChat and Xiaohongshu.

5|1|Updated Jul 31, 2026
Search Tags:#content planning#social media#github#json#wechat#storyboard#xiaohongshu
One-click install
npx skills add https://github.com/shiker1996/wechat-editroom --skill repository-card-storyboard-shiker1996
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repository-card-storyboard
Source: https://github.com/shiker1996/wechat-editroom/tree/main/skills/repository-card-storyboard
Command: npx skills add https://github.com/shiker1996/wechat-editroom --skill repository-card-storyboard-shiker1996

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a verified GitHub repository or tool fact base into a coherent multi-page social media graphic story is hard: facts get repeated across pages, unverified claims slip in, and page structure drifts. This Skill converts a verified repository fact base into a strict JSON storyboard with defined page roles, evidence references, and visual intent. ## Core Features & Use Cases - Structured Storyboard Generation: Produces a social_card_storyboard JSON contract with pages typed as cover, problem, capability, quickstart, scenario, limitation, and ending, each with kind, role, and per-block source_refs. - Fact Discipline & Evidence Boundaries: Enforces fact allocation so each verified fact appears on exactly one page, forbids fabricated commands, performance claims, or Star/Trending-based value judgments, and defines degradation rules when evidence is thin. - Repository Archetype Storylines: Selects page sequences based on repository type (awesome list, library/SDK, CLI/app, template, dataset) with merge and anti-merge rules. - Use Case: Given a verified fact base for an open-source CLI tool, generate a 5-page Xiaohongshu card plan covering the reader's task, core capabilities, real install commands, permission limits, and a selection conclusion. ## Quick Start Provide a verified repository fact base and ask the AI to plan a tool card storyboard for the social-tool entry point.

Frequently Asked Questions about repository-card-storyboard

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

FAQPage Schema
How do I turn a GitHub repository into a social media card storyboard?▼

Provide a verified fact base containing the repository metadata, README, source URLs, and any real run records. The Skill outputs a strict JSON storyboard with typed pages such as cover, capability, quickstart, limitation, and ending, each block carrying source references.

What input does the repository card storyboard require?▼

It requires a `social_card_fact_base` input contract with content type `repository`, containing only verified facts: repository metadata, README content, license info, version records, actual run logs if available, and explicitly marked unknowns.

Can the storyboard include install commands not found in the README?▼

No. The Skill forbids fabricating commands, parameters, or verification steps. When no real commands exist in the fact base, the quickstart page degrades to an operation-path description instead of invented instructions.

How many pages should a tool card storyboard have?▼

The recommended range is 4 to 7 pages depending on the repository archetype and available evidence. If facts are insufficient for standalone scenario pages, they merge into limitation or ending pages rather than being padded with generic audience labels.

What output format does the storyboard use?▼

It returns strict JSON following the `social_card_storyboard` contract. Every page includes `kind` and `role`, every content block includes `source_refs`, and visual intent is expressed semantically through emphasis, tone, icons, and badges without any CSS, HTML, or color values.

When should a repository not become a tool card storyboard?▼

When the fact base lacks verified positioning and capability facts, or only contains README claims without evidence. In those cases the content should be shortened to 4 pages, moved to a candidate pool, or not upgraded into trend or deep-dive article formats.

Related Skills

Explore More Content & Communication Skills→
dmccrearydmccreary
90

readme-generator

Generate validated GitHub README.md files with badges and site metrics.

Community
Intermediate
solar-lunasolar-luna
66

xiaohongshu-publisher

Convert WeChat HTML content into Xiaohongshu posts and publish via MCP.

Community
Advanced
fgrehmfgrehm

blog-fact-checking

Verify blog claims against official documentation using web_fetch.

Community
Basic
Knoka1Knoka1

content-repurposing

Repurpose existing content into platform-native formats for different audiences.

Community
Advanced