PPT安装

文档已审计 v0.1.0

作者仓库星标 13
作者更新于实时读取
作者仓库 viepilot

流狐档案事实层信息：领域、Agent、信任分、运行环境、权限与网络

领域: 文档
兼容 Agent: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
信任分: 92 / 100 · 已通过审计
作者 / 版本 / 许可: @0-CODE · v0.1.0 · 未声明 license
Token 消耗评级: 低消耗
接入复杂程度: 需简单配置
是否需要外部 API Key: 不需要
兼容的系统: macOS · Linux · Windows
底层运行要求: Node.js
文件与系统权限: 只读
允许写入 / 修改
Shell 执行
读取环境变量
网络行为: 仅限本地
安装命令数: 26 条

档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。

需要注意： 未限定 allowed-tools，默认拥有全部工具权限。

输出预览 vp-proposal.preview

---
name: vp-proposal
description: Generate professional proposal packages (.pptx + .docx + .md) from brainstorm sessions or direct…
category: 文档
runtime: Node.js
---

# vp-proposal 输出预览

## PART A: 任务判断
- 适用问题：PRD、RFC、README、项目说明或知识库整理。
- 输入要求：目标材料、限制条件、期望输出和验收方式。
- 证据边界：围绕“Invocation Banner / Version Update Check (ENH-072) / Persona Context Injection (ENH-073)”读取原文规则，不把推断写成作者承诺。

## PART B: 执行结果
- **01** 任务判断：确认你的需求是否属于PRD、RFC、README、项目说明或知识库整理，并标出输入、限制和预期结果。
- **02** 执行计划：优先按“Invocation Banner / Version Update Check (ENH-072) / Persona Context Injection (ENH-073)”拆成步骤，说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果：给出可复制的命令、文件改动、检查清单或内容草稿，并说明如何继续迭代。
- **04** 风险边界：结合 读取文件、写入/修改文件、执行终端命令、读取环境变量、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。

## Running Rules
- 读取文件、写入/修改文件、执行终端命令、读取环境变量；主要在本地完成；通常不需要额外 API Key。
- 先小样例验证，再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。

SKILL.md SKILL.md

---
name: vp-proposal
description: Generate professional proposal packages (.pptx + .docx + .md) from brainstorm sessions or direct…
category: 文档
source: 0-CODE/viepilot
---

# vp-proposal

## 什么时候使用
- vp-proposal 是文档方向的技能，对外说明 适合处理README、PRD、RFC、教程和知识库文档，核心价值是把输入、判断、执行、验证和交付边界固定下来，避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤…
- 面向PRD、RFC、README、项目说明或知识库整理，优先处理能明确输入、步骤和验收标准的工作。

## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。

## 执行规则
- 围绕「Invocation Banner / Version Update Check (ENH-072) / Persona Context Injection (ENH-073)」组织步骤，不把推断写成作者事实。
- 读取文件、写入/修改文件、执行终端命令、读取环境变量；主要在本地完成；通常不需要额外 API Key。
- 先跑小样例，确认结果可检查后再扩大任务范围。

## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown，不编造命令、平台或依赖。

证据边界与执行链路

作者原文负责流程事实；仓库文件负责来源和命令；流狐只补充适用场景、限制和质量判断。

skill "vp-proposal" {
  输入层     -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
  上下文层   -> Invocation Banner / Version Update Check (ENH-072) / Persona Context Injection (ENH-073)
  规则层     -> SKILL.md 触发条件 / 执行顺序 / 输出格式
  运行层     -> Node.js | 读取文件、写入/修改文件、执行终端命令、读取环境变量 | 主要在本地完成
  安全层     -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
  输出层     -> 可复制结果 + 检查清单 + 下一步迭代
}

解读按原文结构重写，命令、链接、术语均保留；右侧可核对作者原始 SKILL.md

先判断是否适合

核心用途：vp-proposal 是文档方向的技能，对外说明适合处理README、PRD、RFC、教程和知识库文档，核心价值是把输入、判断、执行、验证和交付边界固定下来，避免 Agent 泛泛回答。把任务拆成可执行、可检查、可继续迭代的步骤；通常不需要额外 AP…
适用任务：更适合 README、PRD、RFC、教程和知识库文档，尤其是输入、步骤、验收口径可以反复复用的场景。
不宜硬套：如果任务只有一次性问答、来源材料很少，或需要作者没有说明的命令和外部服务，应先降级为普通对话。

作者设计意图

触发依据：使用时机、上下文收集、输出格式和失败处理共同决定它是否适合当前任务。
来源边界：作者原文负责事实，仓库文件负责命令和文件证据；Fluxly 只补充用途、限制和使用判断。

作者的方法与取舍

执行主线：任务围绕「Invocation Banner / Version Update Check (ENH-072) / Persona Context Injection (ENH-073)」组织，把触发条件、必要上下文、执行规则和交付标准连成一条可复核的链路。
设计重点：重点不在重复教程，而在解释作者为什么规定这些步骤、哪些条件不可省略，以及结果偏离时应回到哪一层检查。
使用判断：先确认任务与原文边界一致，再决定是否启用；来源没有说明的命令、平台和依赖保持未知，不由 Fluxly 补写。

边界和复核

依赖条件：通常不需要额外 API Key，适合先用小任务验证触发是否稳定。
权限提醒：会涉及 read / write / shell-exec / env-read 权限，执行前要说明可读写范围、命令边界和回退方式。
质量标准：结果应包含明确产物、必要证据和下一步动作；如果只是泛泛解释，需要补充输入和验收条件后重跑。

## Invocation Banner

Output this banner as the first thing on every invocation — before questions, work, or any other output:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 VIEPILOT ► VP-PROPOSAL  v0.1.0 (fw 2.19.0)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

## Version Update Check (ENH-072)

After displaying the greeting banner, run:

node "$HOME/.claude/viepilot/bin/vp-tools.cjs" check-update --silent

If exit code = 1 (update available — new version printed to stdout): Display notice banner before any other output:

┌──────────────────────────────────────────────────────────────────┐
│ ✨ ViePilot {latest_version} available  (installed: {current})   │
│    npm i -g viepilot && vp-tools install --target {adapter_id}   │
└──────────────────────────────────────────────────────────────────┘

Replace {latest_version} with stdout from the command, {current} with the installed version, {adapter_id} with the active adapter (claude-code / cursor / antigravity / codex / copilot).

If exit code = 0 or command unavailable: silent, continue.

Suppression rules:

--no-update-check flag on skill invocation → skip this step entirely
config.json → update.check: false → skip this step entirely
Show at most once per session (update_check_done session guard)

## Persona Context Injection (ENH-073) At skill start, run: ```bash node "$HOME/.claude/viepilot/bin/vp-tools.cjs" persona auto-switch node "$HOME/.claude/viepilot/bin/vp-tools.cjs" persona context ``` Inject the output as `## User Persona` context before any task execution. Silent if command unavailable or errors. ## A. Skill Invocation - Skill được gọi khi user mention `vp-proposal`, `/vp-proposal`, "proposal", "pitch deck", "presentation", "tài liệu đề xuất" - Treat all user text after the skill mention as `{{VP_ARGS}}`

B. User Prompting

Prompt user conversationally with numbered list options.

C. Tool Usage

Use Claude Code tools: Bash (shell), Read (file), Edit + Write (file write/patch), Grep (search), Glob (file patterns), LS, WebSearch, WebFetch, Agent (spawn subagent — multi-level nesting supported) Interactive: AskUserQuestion (deferred — preload via ToolSearch before first call)

## A. Skill Invocation Same trigger keywords as claude-code adapter.

C. Tool Usage

Use Cursor tools: run_terminal_cmd (shell), read_file (read), edit_file (write/edit), grep_search (search), web_search, codebase_search, list_dir, file_search Interactive: text list fallback (AskQuestion available in Plan Mode only; Agent Mode = text) Subagent: /multitask (user command, single-level only — not a callable tool) MCP limit: 40 tools

## A. Skill Invocation Same trigger keywords as claude-code adapter. Skill discovery: LLM-driven (automatic, no slash command needed).

C. Tool Usage

Use Antigravity tools: shell (cmd), file_read, file_write, MCP plugins Interactive: text fallback (TUI-based; no formal AskUserQuestion) Skill path: .agents/skills/<skill>/SKILL.md (project) or ~/.gemini/antigravity/skills/ (global) Note: Gemini CLI deprecated June 18, 2026 — use Antigravity CLI.

## A. Skill Invocation Same trigger keywords as claude-code adapter.

C. Tool Usage

Use Codex tools: container.exec (sandboxed shell), apply_patch (file write), web_search Interactive: text fallback (TUI Tab/Enter injection) Config: ~/.codex/config.toml

## A. Skill Invocation Same trigger keywords as claude-code adapter. Discovery: User-driven (`@agent-name` in GitHub Copilot Chat).

C. Tool Usage

Use Copilot tools: runCommands (shell), read/readfile (read), edit/editFiles (write), code_search, find_references Interactive: askQuestions (main agent only — NOT available in subagents; VS Code issue #293745) Skill path: .github/agents/<name>.agent.md

ViePilot Namespace Guard (BUG-004)

Default mode: only use and reference vp-* skills in ViePilot workflows.
External skills (non vp-*) are out of framework scope unless user explicitly opts in.

## Implementation routing guard (ENH-021)

/vp-proposal generates output artifacts (docs/proposals/*.pptx, *.docx, *.md) — it does not implement shipping code for lib/, tests/, bin/, or framework workflows//skills/.
This skill is the delivery lane after /vp-brainstorm captures the ideas. Use /vp-request → /vp-evolve → /vp-auto for ViePilot framework feature work.
Exception: User explicit bypass — state clearly in chat.

Generate a professional proposal package from a brainstorm session or direct brief.

Output files (written to docs/proposals/):

{slug}-{date}.md — structured proposal Markdown (source of truth)
{slug}-{date}.pptx — presentation file (ViePilot branded, dark navy/charcoal)
{slug}-{date}.docx — detailed project document
{slug}-{date}-slides.txt — Google Slides URL (only with --slides flag)

Proposal types:

Type	Slides	Use case
`project-proposal`	10	Scope, timeline, budget for clients
`tech-architecture`	12	Technical design for partners
`product-pitch`	12	Investor / partner pitch deck
`general`	8	Generic, fallback

Template resolution (2-tier):

.viepilot/proposal-templates/{type}.pptx — project-level override
{viepilot-install}/templates/proposal/pptx/{type}.pptx — ViePilot stock

Context detection:

Auto-loads latest docs/brainstorm/session-*.md when present
Standalone mode if no session found (user provides brief)
--from session-YYYY-MM-DD.md for explicit session selection

workflows/proposal.md Optional flags: - `--type ` : Proposal type — `project-proposal` | `tech-architecture` | `product-pitch` | `general` If omitted: guided selection menu is shown - `--from ` : Explicit brainstorm session file to use as context Default: auto-detect latest `docs/brainstorm/session-*.md` - `--lang

` : Language for generated content — ISO 639-1 (e.g. vi, en, ja, fr, zh).
                    If omitted: prompted with MRU suggestions from config.
                    Saved to ~/.viepilot/config.json → proposal.recentLangs after generation.
- `--lang-content-only` : Translate content (bullets, notes, paragraphs) only.
                           Keep structural labels / section names in English.
- `--slides` : After .pptx is generated, upload to Google Slides via service account auth
               Requires: `@googleapis/slides` installed + `GOOGLE_APPLICATION_CREDENTIALS` env var
- `--dry-run` : Show slide manifest (JSON) without writing any files





Execute workflow from `workflows/proposal.md`


Step 1: Context Detection


Scan docs/brainstorm/ for session-*.md → sort descending → load latest
If --from specified: load that file directly
If no session found: prompt user for brief:
Project name
One-line description
Target audience (client / partner / investor)
3–5 key points to cover





Step 2: Proposal Type Selection


If --type provided: validate; show type + slide count to confirm
Else: present menu:1. Project Proposal     (10 slides) — scope, timeline, budget
2. Tech Architecture    (12 slides) — system design for partners
3. Product Pitch Deck   (12 slides) — investor / partner pitch
4. General Proposal     ( 8 slides) — generic fallback





Step 3: AI Slide Manifest Generation


Structure context into JSON manifest:{
  "title": "...",
  "subtitle": "...",
  "slides": [
    { "index": 1, "layout": "cover", "heading": "...", "body": "...", "speakerNotes": "..." },
    { "index": 2, "layout": "section", "heading": "...", "bullets": ["..."], "speakerNotes": "..." }
  ]
}


Slide count MUST match PROPOSAL_TYPES[typeId].slides
If --dry-run: print manifest and stop



Step 4: Template Resolution


Call resolveTemplate(typeId, 'pptx', projectRoot) → pptx template path
Call resolveTemplate('project-detail', 'docx', projectRoot) → docx template path
Warn (not error) if stock fallback is used



Step 5: Generate .pptx


Load template via pptxgenjs
Apply slide manifest: inject titles, bullets, speaker notes per slide
Ensure docs/proposals/ directory exists
Write {slug}-{date}.pptx



Step 6: Generate .docx


Build detailed document from same manifest + extended content
Sections: Executive Summary, Problem & Solution, Features & Specifications,
      Technical Architecture (if relevant), Timeline, Team, Appendix
Write {slug}-{date}.docx



Step 7: Generate .md summary


Write Markdown mirror of the manifest
Save {slug}-{date}.md



Step 8: Optional Google Slides upload (--slides)


Call lib/google-slides-exporter.cjs → uploadToSlides(pptxPath, title)
Write URL to {slug}-{date}-slides.txt
On failure: surface error but do NOT fail the whole command (files already written)



Step 9: Confirm output

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 VIEPILOT ► PROPOSAL GENERATED ✓
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 Type:    {type label}  ({N} slides)
 Context: {session file or "direct brief"}

 Files:
   docs/proposals/{slug}-{date}.md
   docs/proposals/{slug}-{date}.pptx
   docs/proposals/{slug}-{date}.docx
   [docs/proposals/{slug}-{date}-slides.txt]  ← if --slides

 Next:
   Open .pptx in PowerPoint / Keynote / LibreOffice
   Share .docx as supporting document
   Run /vp-proposal --slides to upload to Google Slides
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━




- [ ] Context detected (brainstorm session or user brief)
- [ ] Proposal type selected and validated
- [ ] Slide manifest generated with correct slide count
- [ ] .pptx written to docs/proposals/
- [ ] .docx written to docs/proposals/
- [ ] .md summary written to docs/proposals/
- [ ] Template resolution: project override takes precedence over stock
- [ ] --lang: content generated in specified language; MRU saved to config
- [ ] --lang-content-only: bullets/notes translated; structural labels stay English
- [ ] --slides: Google Slides URL written to -slides.txt (or clear error shown)
- [ ] --dry-run: manifest printed, no files written

    安装命令
一键复制安装选择包管理器,点击右侧 复制,粘贴到终端回车即可
$npx skills add 0-CODE/viepilot/skills/vp-proposal -y
查看通用安装教程↗
查看 Skill 原文
兼容工具Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent
 
  安全审计
  92 / 100 
 已审计
  未声明 license/许可。
未限定 allowed-tools，默认拥有全部工具权限。
 
 
  元信息
  来源: github
  0-CODE/viepilot
  版本: 0.1.0
  English 
 
  @0-CODE 的其他技能
    S Agent安装 92  
  S Agent安装 92  
  S Agent安装 92  
  S 安全审计 92  
  S Agent安装 92  
 
 
   相关技能
  适合搭配使用或解决相邻问题 
    S PDF测试  ★ 110511   
  S Word安装  ★ 12348   
  S 前端设计  ★ 5359   
  S 测试审查  ★ 34890   
  S 前端转换  ★ 21713   
  S 内容测试  ★ 21713   
 
 
   分类与标签
  分类  文档

PPT安装

先判断是否适合

作者设计意图

作者的方法与取舍

边界和复核

B. User Prompting

C. Tool Usage

C. Tool Usage

C. Tool Usage

C. Tool Usage

C. Tool Usage

ViePilot Namespace Guard (BUG-004)

Step 1: Context Detection

Step 2: Proposal Type Selection

Step 3: AI Slide Manifest Generation

Step 4: Template Resolution

Step 5: Generate .pptx

Step 6: Generate .docx

Step 7: Generate .md summary

Step 8: Optional Google Slides upload (`--slides`)

Step 9: Confirm output

讨论