原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

visual-style-ppt-skill Skill

代码仓库 ↗

作者:irenerachel★ 3981 个 skill

安装

What it does

【Skill】视觉风格 PPT 生成工作流

  • Connects Instruction files the AI reads
  • Account or key Not confirmed yet (README not read yet)
  • Category 设计与网页
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/irenerachel-visual-style-ppt-skill.svg)](https://mcp.popnx.com/en/skills/irenerachel-visual-style-ppt-skill)

可搭配使用

在同一工作中把 AI 连到服务的 MCP

Next AI Draw.io

draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand

作者:DayuanJiang广泛使用↓ 2.2万/周★ 3.7万 整个仓库的星标4天前更新

MCP · 连接服务在你的电脑上运行

Pascal 3D Editor

Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.

作者:pascalorg广泛使用↓ 1037/周★ 2.6万 整个仓库的星标今天更新

MCP · 连接服务电脑或云端✓ 服务方 · pascal.app

Semiotic

Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.

作者:nteract广泛使用↓ 8456/周★ 271719天前更新

MCP · 连接服务电脑或云端

相似的 Skill

同类工作,排序与 Skill 列表相同

与相似项目对比
本项
visual-style-ppt-skill
impeccablediagram-designfrontend-slidesguizang-ppt-skill
作者irenerachelpbakauscathrynlaveryzarazhangruiop7418
Skill 数11111
GitHub 星标398112,54468,06932,51430,030
最近代码更新2026年10月25日2026年11月18日2026年11月13日2026年6月24日2026年10月30日
许可证–Apache-2.0MITMITAGPL-3.0

irenerachel 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server

Skill 和 MCP 有什么不同

MCP = 手

把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。

Skill = 手册

教 AI 怎么做某项工作的文本文件,不连接任何服务。

有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。

适用的应用

Codex

依据开发者 README 和 repo 中的文件夹

安装

Is it safe?

  • Who made it

    GitHub account irenerachel (person), 3 years old

  • Use and upkeep

    ★ 398 stars, few users so far · code last changed 2026年10月25日

  • Any scripts?

    No, plain text files the AI reads and follows

  • Uses the internet?

    No scripts, so it does not go online by itself

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit 7122461 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself

第一步:你用哪个 AI?

选择你用的应用,本页只显示该应用的安装方法

Option 1Upload to claude.ai (web and app)

  1. Download from GitHub

    This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier

    Download from GitHub (whole repo) ↗

    Unzip it, then zip only the visual-style-ppt-skill folder again. The ZIP must have a visual-style-ppt folder with SKILL.md at the top level, no loose files

  2. Open Skills on claude.ai and upload

    +Create skillUpload a skillpick visual-style-ppt.zip

    Open claude.ai/customize/skills ↗

  3. No Upload button? Turn on file creation first

    SettingsCapabilitiesCode execution and file creation

    Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free

Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)

Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)

Checked against official docs 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com

Option 1让 Claude Code 帮你安装

复制这句话,粘贴到 Claude Code 的对话中

Where to install

正在检查命令 · 通过后才会显示复制按钮

正在检查命令 · 通过后才会显示复制按钮

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

重新打开 Claude Code,输入 /visual-style-ppt-skill,或直接提出相关任务,Claude 会自动选用

Checked against official docs 2026年11月12日 · Source: code.claude.com

For Terminal users

Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。

  1. 打开终端

    Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”

  2. 把 skill 文件夹复制到 ~/.claude/skills

    这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹

    正在检查命令 · 通过后才会显示复制按钮

  3. 重新打开 Claude Code,输入 /visual-style-ppt-skill,或直接提出相关任务,Claude 会自动选用

自己安装的 Skill 可用于 ChatGPT 桌面应用、Codex CLI 和 IDE 中的 Codex 扩展 · 网页版和手机版 ChatGPT 不能使用自己安装的 Skill,只能使用目录中插件自带的 Skill

ChatGPT 桌面应用

ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill

Option 1让 ChatGPT 帮你安装

在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中

Where to install

正在检查命令 · 通过后才会显示复制按钮

正在检查命令 · 通过后才会显示复制按钮

The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Option 2自己放入文件夹

把 visual-style-ppt 文件夹放到 ~/.agents/skills/visual-style-ppt

~ 是你的主文件夹($HOME)

For Terminal users

Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。

  1. 打开终端

    Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”

  2. 把 skill 文件夹复制到 ~/.agents/skills

    这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹

    正在检查命令 · 通过后才会显示复制按钮

安装之后

  • ChatGPT 桌面应用:打开侧边栏中的 Skills,确认 Skill 已出现
  • 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
  • Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex

Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com

网页版和手机版 ChatGPT

不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill

想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用

Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com

Option 1让 Codex 帮你安装

复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展

Where to install

正在检查命令 · 通过后才会显示复制按钮

正在检查命令 · 通过后才会显示复制按钮

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称

Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com

For Terminal users

Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。

  1. 打开终端

    Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”

  2. 把 skill 文件夹复制到 ~/.agents/skills

    这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹

    正在检查命令 · 通过后才会显示复制按钮

  3. 重新打开 Codex 并提出相关任务,Codex 会列出这个 skill

Option 1让 Cursor 帮你安装

复制这句话,粘贴到 Cursor 的对话中

Where to install

正在检查命令 · 通过后才会显示复制按钮

正在检查命令 · 通过后才会显示复制按钮

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

在 Cursor 的 Agent 聊天中输入 / 并选择 visual-style-ppt-skill

Checked against official docs 2026年11月12日 · Source: cursor.com

For Terminal users

Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。

  1. 打开终端

    Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”

  2. 把 skill 文件夹复制到 ~/.cursor/skills

    这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹

    正在检查命令 · 通过后才会显示复制按钮

  3. 在 Cursor 的 Agent 聊天中输入 / 并选择 visual-style-ppt-skill

Option 1Let the AI install it

适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat

Where to install

正在检查命令 · 通过后才会显示复制按钮

正在检查命令 · 通过后才会显示复制按钮

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。

在 GitHub 上查看 ↗

已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹

查看原始 SKILL.md

以下文字来自开发者的 repo,不是 PopNx MCP 的指令

显示前 8,000 个字符 · 在 GitHub 打开完整文件

---
name: visual-style-ppt
description: Create style-driven slide images strictly with the Image 2.5 model, assemble those images into image-only PPTX decks, and manage reusable visual style libraries from documents or visual references. Use when the user asks for a "PPT Skill", "风格驱动 PPT", "提炼风格做 PPT", "调用某个风格做 PPT", "图片版 PPT", "保存 PPT 风格", "列出 PPT 风格", "文档生成 PPT", "文章生成 PPT", "把文档做成演示文稿", or wants to extract, save, reuse, and apply visual style keywords specifically for visual slide/image deck creation.
---

# Visual Style PPT

## Highest Priority Rule: Image 2.5 Only

This skill must use the Image 2.5 model to generate every final slide image, thumbnail board, visual page, infographic, article illustration, or PPT page image.

HTML output is strictly forbidden for image generation. Do not create HTML/CSS pages, browser screenshots, SVG/HTML mockups, canvas renders, or local-script visual reproductions as final or intermediate image outputs. Do not use HTML as a fallback when Image 2.5 is unavailable; stop and state that Image 2.5 access is required.

This rule has the highest priority in this skill and overrides every workflow, reference file, style file, packaging rule, user shortcut, or implementation convenience that might imply another image-production route. PPTX files may only be assembled after Image 2.5 has generated the approved page images; PPTX is a container, not an image-generation method.

## Core Idea

Turn visual style into a reusable asset, then apply that asset to documents, outlines, image-only PPT decks, slide images, Xiaohongshu information graphics, and article illustrations.

Use this skill as an Image 2.5-only visual slide workflow. The default deliverable is full-slide images generated by Image 2.5; when the user wants a PPT, place the generated images into a PPTX as full-slide image pages. Do not implement or optimize editable PPTX content unless the user explicitly overrides this skill direction.

## Required References

- For the full operating workflow, read `references/workflow.md`.
- For PPTX vs image output rules, read `references/output-package.md`.
- For page type selection, read `references/page-types.md`.
- For post-generation revisions, read `references/revision-workflow.md`.
- For style extraction interviews, read `references/style-interview.md`.
- For the default terminal-tech magazine visual style, read `styles/terminal-tech-magazine.md`.
- When the user asks for a style library, list or read files in `styles/`.

## Default Behavior

- Default output type: Image 2.5-generated slide images. If the user says "PPT", assemble those images into an image-only PPTX.
- Default aspect ratio: 16:9.
- Default image quality: Image 2.5, 16:9, high-resolution, sharp text, clean edges.
- Default language: Chinese-first. Use Chinese for slide titles, section titles, module labels, captions, explanatory copy, and all generated support documents unless the user explicitly asks for another language. Keep proper nouns, product names, model names, code terms, and unavoidable domain terms in their original language when that is clearer.
- Default style: `styles/terminal-tech-magazine.md` when the user says "终端风格", "CodeBuddy 风格", "科技杂志风格", or does not specify another saved style.
- Default text density: low information by default, especially for PPT inner slides. Never create dense slides unless the user explicitly asks for a leave-behind, report page, or infographic. A normal inner slide should have one title, one short subtitle or takeaway, and at most 2-3 short information points.
- Default layout direction: cover pages may be visually expressive; inner slides must be information-first, calm, readable, and spacious, with imagery/backgrounds kept subordinate.
- Default style isolation: each deck must use exactly one selected style source and one `Style Lock`. Do not blend visual DNA from earlier tasks, previous reference images, or unrelated saved styles unless the user explicitly requests a hybrid.
- Default component consistency: across one deck, borders, cards, containers, dividers, arrows, footer metadata, corner radius, and line weights must use one repeated system. Variation may come from layout and emphasis, not from changing the frame/container style on every slide.
- Default slide header consistency: if a style uses small top titles with numbers, treat them as repeated content-section headers, not necessarily absolute slide/page numbers. Keep the same placement, size, spacing, and format across all applicable slides. If the style defines exceptions such as cover, contents, divider, or thank-you pages, preserve those exceptions deliberately; those exception pages do not consume a content-section number. The first applicable inner/content slide should usually start at `01` or `PART 1`.
- Default logo behavior: do not ask Image2.5 to generate logos, brand wordmarks, reusable deck marks, watermarks, or repeated English identity labels by default. If the user needs a logo, keep it out of generated slide images and add it later as a fixed post-production asset/layer, or let the user add it after delivery. A reference logo image may guide visual shape but is not reliable enough for cross-page text/logo consistency inside Image2.5 output.
- Default time/date behavior: do not add dates, times, timestamps, "today", export time, generated time, or current date to slides, prompts, metadata, footers, or visual elements by default. Include date/time only when the source article explicitly requires it, the user explicitly asks for it, or the slide topic itself is a timeline/schedule/date-sensitive report. A source document having a file timestamp, export timestamp, or local system date does not by itself justify visible date/time in the deck.
- Default page count: ask the user how many pages/slides they want unless they already provided a count or explicitly asked the skill to decide.
- Multiple outputs: keep one visual DNA while varying composition, page type, visual anchor, or emphasis.
- No outer border rule: generated slide images and thumbnail boards must not have black borders, dark strokes, or frame lines on the outer canvas edge. Internal grid lines, dividers, and module borders are allowed, but keep them inset from the image edge or let imagery/white space bleed naturally. Never create a full-page rectangular outline around the slide.
- Per-slide image rule: PPT pages must be generated and saved as separate single-slide image files, one image per slide. Do not request or deliver a multi-slide contact sheet, storyboard, PDF page, or collage as the final slide image output. Each final slide image must be independently usable as one full-bleed PPT page.
- Thumbnail-first option: for multi-page decks, prefer a two-pass visual workflow when style consistency matters: first generate one small "thumbnail board / contact sheet" that shows the whole deck as tiny slide thumbnails to lock visual rhythm, grid, palette, and page-to-page variation; then generate each approved slide as an individual full-size image using that thumbnail board as the visual continuity reference plus the page-specific prompt. The thumbnail board is a planning/reference artifact, not a final slide.
- Thumbnail grid rule: thumbnail board counts are flexible, but prefer stable grids with 4, 6, 9, or 16 slots. Choose the smallest preferred grid that can contain all planned slides, leaving any extra slot as a style/system/reference tile. Each thumbnail tile must use the same aspect ratio as the requested final slide output. For example, if the final deck is 16:9, every tiny slide in the thumbnail board should be composed as 16:9; if the user requests 3:4 vertical slides, every tiny slide in the thumbnail board should be composed as 3:4.
- Generation gate: before calling Image2.5 for a multi-page deck, always produce `outline.md` and `prompts.md` first, then ask the user to confirm or revise. `prompts.md` must include the selected style's full `Style Lock`.
- Fin

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

来自 GitHub

GitHub 星标
398
开发者
irenerachel
许可证
未注明许可证 此 repo 未注明许可证,默认作者保留所有权利;转发或商用前请先询问作者。
最近代码更新
2026年10月25日
repo 中的 SKILL.md 文件(含译本和模板)
1
主题
claude-skill, skill