菜单
Use when writing persuasive content (sales pitches, blog posts, speeches, marketing copy) or structuring an argument. Applies the NASA method (Need → Acceptance → Solution → Acceptance) to make sure context is loaded into the listener's attention before the solution is proposed.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/aukilabs/org-auki --skill nasa-persuasion命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Generates a combined community-facing presentation that aggregates all internal weekly updates into a single master document. Run once per week after individual updates have been committed. Reads all presentations from the target week in aukilabs/presentations, synthesises them by project, applies NDA redaction, and commits a community-update page to community/week-{NN}.html. Always community audience — this is the outward-facing digest.
Sub-skill called by /presentation and /presentation-external (the router skills). Auto-populates presentation context from a contributor's work in the current ISO week — reads CHANGELOG entries, merged PRs, closed issues, and skill diffs since the most recent past Friday. Returns a structured digest that the router passes down to /slides or /page. Reduces user-prompting burden by pre-filling "what shipped, what's in progress, what's next".
Post-processing skill that audits a generated presentation for NDA and sensitive material, then rewrites flagged content with appropriate public-facing language. Called automatically by /presentation when audience is community — the only public audience. Never invoked for internal, investor, or client presentations.
基于 SOC 职业分类
正在显示 SKILL.md
| name | nasa-persuasion |
| description | Use when writing persuasive content (sales pitches, blog posts, speeches, marketing copy) or structuring an argument. Applies the NASA method (Need → Acceptance → Solution → Acceptance) to make sure context is loaded into the listener's attention before the solution is proposed. |
People sell to themselves. Equip the listener with the information they need to reach the conclusion on their own. Never assume context is "in their RAM" just because it's in their long-term memory.
Only after the loop can you sell the concrete thing. In the example above, the listener's need was "get home earlier." The abstract solution was "a tool that saves time." What you actually sold them in the end was bookkeeping software.
Structure the content so the reader always has the necessary scaffolding in RAM. Don't assume.
story-why-how-what maps closely: Need ≈ Why, Solution ≈ How. Use NASA for dialogue, WHW for one-directional narrative.
