Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

talk-stage4-position谈话阶段 4 位置

Agent Skill

talk-stage4-position 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

582

周安装

25

GitHub Stars

4,026

下载量

204
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:talk-stage4-position(谈话阶段 4 位置)
来源仓库:https://github.com/florianbruniaux/claude-code-ultimate-guide
仓库路径:skills/talk-stage4-position
安装命令:
npx skills add https://github.com/florianbruniaux/claude-code-ultimate-guide --skill talk-stage4-position
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/florianbruniaux/claude-code-ultimate-guide --skill talk-stage4-position

简介

talk-stage4-position 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 安装前需确认权限范围和维护状态,注意可能触发联网、命令执行或文件读写操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Talk Stage 4: Position + CHECKPOINT

Generates strategic angles, titles, descriptions, and a peer-feedback draft. Then stops and waits for your angle + title choice before Stage 5 can proceed.

When to Use This Skill

  • After Stage 3 (Concepts) — needs the concept catalogue
  • When deciding how to frame the talk
  • Before sending the CFP (uses the generated descriptions directly)

What This Skill Does

  1. Reads inputs — summary + concepts + event constraints
  2. Generates angles — 3-4 distinct angles with force/weakness analysis
  3. Recommends — one clear choice with structured justification
  4. Generates titles — 3-5 options per angle
  5. Generates descriptions — short abstract + long CFP description
  6. Generates feedback draft — ready-to-send message (3 formats)
  7. CHECKPOINT — displays choice request and waits for user response
  8. Saves 4 files

Input

  • talks/{YYYY}-{slug}-summary.md (required)
  • talks/{YYYY}-{slug}-concepts.md (required)
  • Event constraints: duration, audience, CFP format if applicable

Output

  • talks/{YYYY}-{slug}-angles.md
  • talks/{YYYY}-{slug}-titre.md
  • talks/{YYYY}-{slug}-descriptions.md
  • talks/{YYYY}-{slug}-feedback-draft.md

angles.md Format

# Talk Angles — {provisional title}

**Goal**: Choose the angle that maximizes impact for {audience}.
**Audience**: {audience description}

---

## Angle 1: {Angle name}

**Pitch**: {2-3 sentences describing the talk from this angle}

**Strengths**:
- {strength 1}
- {strength 2}

**Weaknesses**:
- {weakness 1}
- {weakness 2}

**Audience fit**: Strong / Medium / Weak — {short justification}

**Verdict**: ⭐⭐⭐⭐⭐ (out of 5)

---

[Angle 2, Angle 3, (optional Angle 4) — same structure]

---

## Recommendation: Angle {X}, enriched by the others

**Angle {X} is the right choice.** Here's why:

### 1. It's the only angle that integrates the others
[Structure showing how other angles feed into the main one]

### 2. The narrative arc is natural and compelling
[Why the story holds better with this angle]

### 3. The metrics lend credibility throughout
[Which metrics support this angle most]

### 4. The final message emerges naturally
[How the conclusion flows from this angle]

---

## Recommended structure with sub-angles

| Act | Duration | Main angle | Integrated sub-angle |
|-----|----------|-----------|---------------------|
| 1. {name} | {n} min | {main angle} | {sub-angle} |
...

titre.md Format

# Titles — Talk {slug}

**Selected angle**: Angle {X} — {name}
**Constraints**: {duration} min | {audience}

---

## Titles for the recommended angle

### Option 1 (recommended)
**{Main title}**
*Optional subtitle: {subtitle}*

Strengths: {why this title works}
Audience appeal: {who it hooks}

### Option 2
**{Title}**
Strengths: {strengths}

[Options 3-5]

---

## Titles for alternative angles (backup)

### If Angle 2 chosen
- **{title}**
- **{title}**

[If Angle 3 chosen — same]

---

## Verdict

**Recommendation**: Option 1 — "{title}"
**Why**: {short justification}

descriptions.md Format

# Descriptions — Talk {slug}

---

## Short description (abstract, ~100 words)

{Full text — direct, engaging, starts with the impact or concrete promise.
Not "In this talk, we will..."}

---

## Long description (CFP, ~250 words)

{Full text — context, what the audience will learn, who it's for.
Includes key metrics if available.
Direct and factual tone.}

---

## Speaker pitch (bio-ready, ~50 words)

{Speaker introduction in 1-2 sentences, their relationship to the topic}

---

## Tags / Keywords

{5-10 relevant tags for CFP or search}

CHECKPOINT (mandatory — Step 7)

After generating and saving the 4 files, display:

---
CHECKPOINT: Angle + Title choice

I've generated 4 files:
- talks/{YYYY}-{slug}-angles.md    → {n} angles analyzed
- talks/{YYYY}-{slug}-titre.md     → {n} title options
- talks/{YYYY}-{slug}-descriptions.md
- talks/{YYYY}-{slug}-feedback-draft.md

Before starting the script (Stage 5), I need your choice:

1. Which angle do you choose? (recommended: Angle {X} — {name})
2. Which title do you prefer? (recommended: "{title}")

You can also modify, combine, or propose something different.
Reply to start the script.
---

Do not invoke Stage 5 without explicit user confirmation.

Angle Generation Rules

  • Minimum 3 angles, maximum 4 (beyond that it's noise)
  • Each angle must be genuinely distinct (not variations of the same)
  • The recommendation must be clear and argued — not "your choice"
  • Always test: "can this angle sustain the full duration without repeating?"

Anti-patterns

  • Click-bait titles ("What nobody tells you about AI")
  • Recommending the last angle listed by default (recency bias)
  • Descriptions that read like slide summaries
  • Skipping the CHECKPOINT — it's the pipeline's most important control point
  • Marketing language in descriptions (revolutionary, game-changer)

Validation Checklist

  • 3-4 angles with force/weakness/audience-fit analysis
  • Clear recommendation with structured justification
  • 3-5 titles for the recommended angle
  • Short description (~100 words) and long description (~250 words)
  • Feedback draft generated from template
  • CHECKPOINT displayed clearly
  • 4 files saved

Tips

  • Send feedback-draft.md to a peer before the checkpoint — 10 minutes of external feedback can save hours of rework on the script
  • The recommendation is a starting point, not an order — your audience knowledge overrides any algorithmic suggestion
  • Weak titles are usually too abstract: test each title by asking "would someone in the hallway stop walking to read this?"

Templates

Related

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.19%
按下载量换算74

Claude

31.7%
按下载量换算65

Cursor

16.42%
按下载量换算33

Gemini CLI

9.96%
按下载量换算20

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills