跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
演示文稿

magazine-web-ppt

For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query "annual-marketing-plan", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion.

nexu-io · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add nexu-io/open-design --skill magazine-web-ppt

技能说明


name: magazine-web-ppt en_name: "Write a Brand-to-Revenue Story like a Growth Strategy Lead" zh_name: "像增长策略负责人一样写品牌到收入故事" description: | For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query "annual-marketing-plan", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion. en_description: | For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query "annual-marketing-plan", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion. zh_description: | 市场/增长/GTM场景:围绕 core query「annual-marketing-plan」把粗糙材料整理成“像增长策略负责人一样写品牌到收入故事”这类可购买、可复用的专业 Deck;突出受众、决策目标、证据链、风险取舍和评审标准。 tags:

  • "marketing-gtm"
  • "annual-marketing-plan"
  • "launch"
  • "campaign"
  • "pipeline"
  • "marketing"
  • "decision-deck"
  • "commercial-slide-agent"
  • "guizang-ppt" triggers:
  • "annual-marketing-plan"
  • "marketing-gtm"
  • "Write a Brand-to-Revenue Story like a Growth Strategy Lead"
  • "像增长策略负责人一样写品牌到收入故事"
  • "launch"
  • "campaign"
  • "pipeline"
  • "html deck"
  • "html slides" od: mode: deck default_for: deck upstream: "https://github.com/op7418/guizang-ppt-skill" preview: type: html entry: index.html design_system: requires: false scenario: "marketing" example_prompt: "Create "Write a Brand-to-Revenue Story like a Growth Strategy Lead" as a Marketing and GTM deck in the Guizang Ppt visual system. Scene: annual-marketing-plan. First ask only for missing essentials: audience, decision target, source-of-truth materials, deadline, and must-keep numbers. Then produce a commercial-grade slide plan, written slides, visual direction, speaker-ready structure, and critic pass against this rubric: can the plan connect creative choices to measurable growth."

Magazine Web Ppt

What this skill does

Generates a single-file HTML horizontal-swipe deck with a visual tone of:

  • A electronic magazine + electronic ink hybrid style
  • A WebGL fluid / contour / dispersion background (visible on hero pages)
  • Serif headlines (Noto Serif SC + Playfair Display) + sans-serif body (Noto Sans SC + Inter) + monospace metadata (IBM Plex Mono)
  • Lucide line icons (no emoji)
  • Horizontal left/right paging (keyboard ← →, scroll wheel, touch swipe, bottom dots, ESC index)
  • Smooth theme interpolation: when you flip to a hero page, the colors and shader transition softly

This skill's aesthetic is not "corporate PPT," nor "consumer-internet UI": it looks like Monocle magazine after code was stitched onto it.

When to use

Suitable scenarios:

  • Offline talks / internal industry talks / private salons
  • AI new-product launches / demo day
  • Talks with a strong personal style
  • A web version of slides that you "make once, with no paging tool needed"

Unsuitable scenarios:

  • Long stretches of tabular data, stacked charts (use a regular PPT)
  • Training courseware (information density too low)
  • Multi-person collaborative editing (this is static HTML)

Workflow

Step 0 · Infer a direction; ask only when comparison is requested

Infer one of the 5 magazine directions from the brief, audience, content, and known context. Each direction packages its theme color, recommended layouts, chrome style, and slide count. Use the closest fit and continue without asking.

Only when the user explicitly asks to see or compare direction options, open references/styles.md and present the 1-line summaries in one direction-cards question form:

1. Monocle Editorial · International magazine style ✦ default
2. WIRED Tech · Data + engineering
3. Kinfolk Slow · Slow living / humanist
4. Domus Architectural · Architecture / sense of space
5. Lab / Reference · Academic + craft manual

If the user says "I don't know, you recommend" or provides no direction cue: default to Monocle Editorial without asking, because it has the lowest failure probability. If the user mentions "AI / benchmark / technical launch": choose WIRED; "reading / private / social circle": choose Kinfolk; "design / architecture / portfolio": choose Domus; "research / academic / methodology": choose Lab.

After picking a direction, create or update 项目记录.md (Project Record) in the project folder, with the first line clearly stating direction + theme color + audience + duration (see the template at the end of styles.md). Do not change direction at any point: switching midway = everything before is wasted.

Step 1 · Resolve intent

If the user has already given a complete outline + images, you can skip straight to Step 2.

Infer the checklist below from the brief, project metadata, supplied content, and conversation. If a missing answer would materially change the deck and no safe default exists, ask only those unresolved fields in one consolidated question form. Do not ask the checklist one by one.

6-question clarifying checklist

Direction and theme color are inferred in Step 0 unless the user explicitly asks to compare options.

#QuestionWhy ask it
1Who is the audience? Sharing scenario? (internal industry / commercial launch / demo day / private salon)determines the language style and depth
2Talk duration?15 min ≈ 10 pages, 30 min ≈ 20 pages, 45 min ≈ 25-30 pages (see each direction's recommended range in styles.md)
3Any source material? (documents / data / old PPT / article links)with material, build on it; without, help them build
4Any images? Where are they?see the "Image convention" below
5Which theme color do you want?✓ already decided by the direction in Step 0
6Any hard constraints? (must include XX data / must not show YY)avoids rework

Ou

阅读完整来源 ↗