Skip to content
Skills Library
Documents & office · Analysis

deck

/deck

Use when outlining, reviewing, or rehearsing a Guochuang pitch deck, project-book presentation, slide narrative, or visual evidence sequence.

Licence
MIT
Last repository change
13.08.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when outlining, reviewing, or rehearsing a Guochuang pitch deck, project-book presentation, slide narrative, or visual evidence sequence.

Original author description

Use when outlining, reviewing, or rehearsing a Guochuang pitch deck, project-book presentation, slide narrative, or visual evidence sequence.

How it works

  1. Build the sequence
  2. Slide contract
  3. Time cuts
  4. Final QA
Original SKILL.md headings · 37 lines, 307 words
SKILL.md preview
---
name: deck
description: Use when outlining, reviewing, or rehearsing a Guochuang pitch deck, project-book presentation, slide narrative, or visual evidence sequence.
---

# Deck

Apply the shared policies in `gps-common`. When saving a Markdown report, use the common project-name rule with topic `PPT`.

Design the deck as a sequence of reviewer decisions. Each slide needs one conclusion, one visual job and one evidence pointer.

## Build the sequence

A common technical or venture spine is:

value in one sentence -> real problem -> field finding -> intervention -> mechanism -> baseline and metric -> validation -> user or scene -> alternatives -> IP and student work -> customer and economics -> growth -> social value -> ask.

Change the order when the track demands it. For an industry project, make the chain visible: enterprise question -> response -> demonstrator -> expert questions. For red-tour, show participation and beneficiary change early.

## Slide contract

For each page fill: no, purpose, headline, visual, evidence_ids, speaker cue, risk and cut priority.

The headline should state the conclusion, not the topic. Put units, sample size, date and source beside a number. Keep project-book, slide and spoken figures identical. Label image-only pages visual review required; missing extracted text is not proof that a page is empty.

## Time cuts

Prepare three versions:

- Full: the complete argument and supporting proof.
- Review: remove decorative pages and keep one proof page per major claim.
- Rescue: keep value, problem, mechanism, strongest result, user evidence, team ownership and the next step.

Never cut the only baseline, limitation or student-contribution evidence. Timing, page count, font and effects are local rules until the 2026 evaluation notice or a school or provincial notice confirms them.

## Final QA

Check headline clarity, legibility, source and date, units, number consistency, ownership, privacy, transitions, screen readability and unsupported superlatives. End with the two claims the team wants the reviewer to remember and the evidence that supports each.

See references/slide-patterns.md for historical patterns.
Files in this package (2)
  • SKILL.md 2 KB
  • references/slide-patterns.md 1 KB

Versions

RepositoryScoreLicence
This page · leewayworks/guochuang-gps90MIT
zauberzeug/game-of-cards100MIT
zauberzeug/game-of-cards100MIT
zauberzeug/game-of-cards100MIT
octavehq/lfgtm100MIT
ramonk2o/storymaker100MIT
wookiya1364/scv-claude-code100MIT
roaldnefs/deckfile100MIT
MBGrao/deck-skill100MIT

Database snapshot: 13.11.2026 · package version 210ca3d8f8a7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100presentation-blueprint
    Use when the user needs to create a presentation, pitch deck, slide deck, or visual summary about a project, codebase, website, or topic. Triggers on requests like 'build a deck', 'create a presentation', 'make slides about', or 'pitch deck for'.
  • 100form-deck
    Use when asked to design a pitch deck, presentation, or slide set. Examples: "design a pitch deck", "create a sales deck", "make a conference presentation", "build an investor deck", "help me present this to the board", "create slides for X".
  • 90glaw-pitch-deck
    Designs polished pitch deck slides and presentation layouts. Use when the user asks for a slide deck, investor pitch, presentation, or multi-slide narrative. Enforces slide structure, whitespace discipline, and one-claim-per-slide rule.
  • 100pitch-deck-creation
    Create professional investor pitch decks with structured content and visual design. Use when users need help with pitch deck, investor deck, fundraising deck, startup pitch, deck design, slide design, pitch presentation, pitch deck visuals, investor presentation, Series A deck,…
  • 100frontend-slides
    Build a self-contained HTML slide deck that runs in the browser. Use when the user wants a presentation, slides for a talk or a pitch, a PPT/PPTX converted to web, or an existing HTML deck improved.
  • 100pitch-deck-builder
    Build investor-ready pitch decks and sales presentations — 10-11 slide structure, persona-customized per role, storytelling frameworks, speaker notes, and visual direction. Use when creating pitch decks, sales decks, investor decks, board presentations, or any slide-based…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.