first commit
This commit is contained in:
150
文档润色流和知识库构建流/claude-scholar/skills/post-acceptance/SKILL.md
Normal file
150
文档润色流和知识库构建流/claude-scholar/skills/post-acceptance/SKILL.md
Normal file
@@ -0,0 +1,150 @@
|
||||
---
|
||||
name: post-acceptance
|
||||
description: This skill should be used when the user asks to "prepare conference presentation", "create presentation slides", "design poster", "make academic poster", "write promotion content", "create Twitter thread", or mentions post-acceptance conference preparation. Provides comprehensive workflow for presentation, poster, and promotion content creation.
|
||||
version: 0.1.0
|
||||
---
|
||||
|
||||
# Post-Acceptance Conference Preparation
|
||||
|
||||
A post-acceptance conference preparation workflow that helps researchers efficiently complete presentations, posters, and promotional content.
|
||||
|
||||
## Core Features
|
||||
|
||||
### 1. Presentation Slide Creation
|
||||
|
||||
Guidance for creating conference presentation slides:
|
||||
|
||||
**Time Control**
|
||||
- 15-minute talk: 10-15 slides
|
||||
- 20-minute talk: 15-20 slides
|
||||
- 30-minute talk: 20-30 slides
|
||||
- Average 1-1.5 minutes per slide
|
||||
|
||||
**Content Structure**
|
||||
- Title slide (1)
|
||||
- Motivation/Problem (2-3)
|
||||
- Method overview (3-5)
|
||||
- Key results (3-5)
|
||||
- Conclusion (1-2)
|
||||
- Q&A/Thank you (1)
|
||||
|
||||
**Visual Design Principles**
|
||||
- One key message per slide
|
||||
- Use figures and diagrams over text
|
||||
- Consistent color scheme and fonts
|
||||
- Minimum font size: 24pt for body, 32pt for titles
|
||||
- High-contrast colors for readability
|
||||
|
||||
**Presentation Tips**
|
||||
- Practice timing with a stopwatch
|
||||
- Prepare backup slides for anticipated questions
|
||||
- Use animations sparingly and purposefully
|
||||
- Include slide numbers for Q&A reference
|
||||
|
||||
### 2. Academic Poster Design
|
||||
|
||||
Guidance for creating conference posters:
|
||||
|
||||
**Standard Sizes**
|
||||
- Portrait: 24x36 inches or A0 (841x1189mm)
|
||||
- Landscape: 36x24 inches or A0 landscape
|
||||
- Check conference requirements for specific size
|
||||
|
||||
**Layout Structure**
|
||||
- Title bar (top): Title, authors, affiliations, logos
|
||||
- Introduction (left): Problem statement, motivation
|
||||
- Method (center): Key approach, architecture diagram
|
||||
- Results (right): Main findings, tables, figures
|
||||
- Conclusion (bottom): Summary, future work, QR code
|
||||
|
||||
**Design Guidelines**
|
||||
- Readable from 4-6 feet distance
|
||||
- Title font: 72-96pt
|
||||
- Section headers: 36-48pt
|
||||
- Body text: 24-32pt
|
||||
- Use bullet points, not paragraphs
|
||||
- Include QR code linking to paper/code
|
||||
|
||||
### 3. Promotion Content Creation
|
||||
|
||||
Guidance for creating promotional content after paper acceptance:
|
||||
|
||||
**Twitter/X Thread**
|
||||
- Thread structure: Hook -> Problem -> Method -> Key Result -> Link
|
||||
- First tweet: Attention-grabbing summary with emoji
|
||||
- Include 1-2 key figures
|
||||
- End with paper link and relevant hashtags
|
||||
- Tag co-authors and relevant accounts
|
||||
|
||||
**LinkedIn Post**
|
||||
- Professional tone, 3-5 paragraphs
|
||||
- Highlight practical implications
|
||||
- Include key figure or diagram
|
||||
- Add relevant hashtags
|
||||
|
||||
**Blog Post**
|
||||
- 800-1500 words
|
||||
- Non-technical summary for broader audience
|
||||
- Include figures with explanations
|
||||
- Link to paper, code, and demo
|
||||
|
||||
## When to Use
|
||||
|
||||
Use this skill in the following scenarios:
|
||||
|
||||
- **After paper acceptance** - Prepare presentation materials for the conference
|
||||
- **Poster session preparation** - Design and create academic poster
|
||||
- **Research promotion** - Create social media and blog content
|
||||
- **Conference talk preparation** - Structure and practice presentation
|
||||
|
||||
## Workflow
|
||||
|
||||
### Presentation Workflow
|
||||
```
|
||||
Paper accepted -> Identify key messages -> Create slide outline -> Design slides -> Practice timing -> Prepare Q&A backup slides
|
||||
```
|
||||
|
||||
### Poster Workflow
|
||||
```
|
||||
Paper accepted -> Choose layout template -> Extract key content -> Design poster -> Print test at reduced size -> Final print
|
||||
```
|
||||
|
||||
### Promotion Workflow
|
||||
```
|
||||
Paper accepted -> Write Twitter thread -> Create LinkedIn post -> Draft blog post -> Schedule posts around conference dates
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
### Presentation
|
||||
- Start with the "so what" - why should the audience care
|
||||
- Tell a story: problem -> insight -> solution -> impact
|
||||
- Use concrete examples and demos when possible
|
||||
- Anticipate questions and prepare answers
|
||||
- Arrive early to test equipment
|
||||
|
||||
### Poster
|
||||
- Design for scanning, not reading
|
||||
- Use visual hierarchy to guide the eye
|
||||
- Include a "elevator pitch" summary
|
||||
- Bring business cards or QR codes
|
||||
- Practice a 2-minute and 5-minute explanation
|
||||
|
||||
### Promotion
|
||||
- Post within 1-2 weeks of acceptance notification
|
||||
- Coordinate timing with co-authors
|
||||
- Engage with comments and questions
|
||||
- Share across multiple platforms
|
||||
- Include accessible descriptions for figures
|
||||
|
||||
## Summary
|
||||
|
||||
This skill provides a comprehensive post-acceptance workflow covering three key areas: presentation slides, academic posters, and promotional content. Following these guidelines helps researchers effectively communicate their work at conferences and to the broader community.
|
||||
|
||||
|
||||
## Reference Files
|
||||
|
||||
Load only what is needed:
|
||||
- `references/design-guidelines.md` - visual design guidance
|
||||
- `references/deliverable-checklists.md` - slide/poster/promo-specific checklists
|
||||
- `examples/post-acceptance-plan.md` - compact delivery plan example
|
||||
@@ -0,0 +1,11 @@
|
||||
# Post-Acceptance Plan
|
||||
|
||||
## Week 1
|
||||
- draft slide outline
|
||||
- choose poster layout
|
||||
- write short social post draft
|
||||
|
||||
## Week 2
|
||||
- polish slides
|
||||
- finalize poster
|
||||
- schedule promotion around conference timeline
|
||||
@@ -0,0 +1,16 @@
|
||||
# Deliverable Checklists
|
||||
|
||||
## Slides
|
||||
- one key message per slide
|
||||
- readable from the back of the room
|
||||
- backup slides for likely questions
|
||||
|
||||
## Poster
|
||||
- readable from 4-6 feet
|
||||
- visual hierarchy clear
|
||||
- QR code or artifact link present
|
||||
|
||||
## Promotion
|
||||
- one-sentence hook
|
||||
- one clear figure or graphic
|
||||
- platform-specific tone and length respected
|
||||
@@ -0,0 +1,85 @@
|
||||
# Design Guidelines for Conference Materials
|
||||
|
||||
会议材料设计的详细指南和最佳实践。
|
||||
|
||||
## Presentation Design Guidelines
|
||||
|
||||
### Slide Layout
|
||||
- 使用16:9宽屏比例(现代投影仪标准)
|
||||
- 保持一致的页边距(建议:上下左右各1英寸)
|
||||
- 标题区域占slide高度的15-20%
|
||||
|
||||
### Typography
|
||||
- 标题字体:Sans-serif(Arial, Helvetica, Calibri)
|
||||
- 正文字体:与标题保持一致
|
||||
- 最小字号:24pt(确保后排观众可见)
|
||||
- 行距:1.2-1.5倍
|
||||
|
||||
|
||||
### Color Scheme
|
||||
- 使用高对比度配色(深色背景+浅色文字,或反之)
|
||||
- 主色调:选择1-2种主色
|
||||
- 强调色:用于突出关键信息
|
||||
- 避免使用纯红色和纯绿色(色盲友好)
|
||||
- 推荐配色方案:
|
||||
- 学术蓝:#003366 + #FFFFFF
|
||||
- 专业灰:#333333 + #F5F5F5
|
||||
- 现代绿:#2E7D32 + #FFFFFF
|
||||
|
||||
### Visual Elements
|
||||
- 图表:使用矢量图(SVG, PDF)
|
||||
- 照片:高分辨率(至少300 DPI)
|
||||
- 图标:统一风格,简洁明了
|
||||
- 动画:谨慎使用,不超过3个
|
||||
|
||||
|
||||
## Poster Design Guidelines
|
||||
|
||||
### Layout Structure
|
||||
- 标题栏:占海报高度的15-20%
|
||||
- 内容区:分3-4列,每列宽度相等
|
||||
- 结论区:占海报高度的15-20%
|
||||
- 页边距:至少2英寸(便于打印和装裱)
|
||||
|
||||
### Content Organization
|
||||
- 从左到右、从上到下的阅读顺序
|
||||
- 每个部分有清晰的标题
|
||||
- 使用编号或箭头引导阅读流程
|
||||
- 核心内容放在视觉中心(黄金分割点)
|
||||
|
||||
|
||||
### Typography for Posters
|
||||
- 标题:72-96pt,粗体
|
||||
- 作者和机构:36-48pt
|
||||
- 章节标题:48-60pt
|
||||
- 正文:24-32pt
|
||||
- 图表标注:20-24pt
|
||||
|
||||
### Printing Guidelines
|
||||
- 分辨率:至少150 DPI(推荐300 DPI)
|
||||
- 颜色模式:CMYK(打印)或RGB(屏幕显示)
|
||||
- 文件格式:PDF(推荐)或高质量PNG
|
||||
- 打印前检查:颜色校准、文字清晰度、图表质量
|
||||
|
||||
|
||||
## Promotion Content Guidelines
|
||||
|
||||
### Social Media Design
|
||||
- 配图尺寸:
|
||||
- Twitter: 1200×675px
|
||||
- LinkedIn: 1200×627px
|
||||
- 通用: 1080×1080px (正方形)
|
||||
- 文字叠加:使用高对比度,确保可读性
|
||||
- Logo/水印:放在不显眼的位置
|
||||
|
||||
### Visual Consistency
|
||||
- 使用统一的配色方案
|
||||
- 保持字体风格一致
|
||||
- 图表风格统一
|
||||
- 品牌元素(Logo、颜色)保持一致
|
||||
|
||||
### Best Practices
|
||||
- 简洁明了:避免信息过载
|
||||
- 视觉层次:突出关键信息
|
||||
- 可访问性:考虑色盲和视力障碍用户
|
||||
- 跨平台适配:确保在不同设备上显示良好
|
||||
@@ -0,0 +1,30 @@
|
||||
# Basic Poster Template
|
||||
|
||||
基础学术海报模板结构
|
||||
|
||||
## Top Section (20%)
|
||||
- 论文标题(大号粗体)
|
||||
- 作者和机构
|
||||
- 会议Logo
|
||||
|
||||
## Main Content (60%)
|
||||
|
||||
### Column 1: Introduction & Method
|
||||
- 研究背景
|
||||
- 问题陈述
|
||||
- 方法概述
|
||||
|
||||
### Column 2: Results
|
||||
- 主要实验结果
|
||||
- 关键图表
|
||||
- 数据可视化
|
||||
|
||||
### Column 3: Discussion & Conclusion
|
||||
- 结果分析
|
||||
- 主要贡献
|
||||
- 未来工作
|
||||
|
||||
## Bottom Section (20%)
|
||||
- 主要结论
|
||||
- 联系方式
|
||||
- QR码(论文/代码链接)
|
||||
@@ -0,0 +1,28 @@
|
||||
# Basic Presentation Template
|
||||
|
||||
基础演讲模板结构示例
|
||||
|
||||
## Slide 1: Title
|
||||
- 论文标题
|
||||
- 作者姓名和机构
|
||||
- 会议名称和日期
|
||||
|
||||
## Slide 2-3: Motivation
|
||||
- 研究背景
|
||||
- 现有问题
|
||||
- 研究动机
|
||||
|
||||
## Slide 4-6: Method
|
||||
- 方法概述
|
||||
- 关键技术
|
||||
- 创新点
|
||||
|
||||
## Slide 7-9: Results
|
||||
- 主要实验结果
|
||||
- 对比分析
|
||||
- 可视化展示
|
||||
|
||||
## Slide 10: Conclusion
|
||||
- 主要贡献
|
||||
- 未来工作
|
||||
- 致谢
|
||||
@@ -0,0 +1,36 @@
|
||||
# Twitter/X Promotion Example
|
||||
|
||||
学术推文示例
|
||||
|
||||
## Example 1: Thread Format
|
||||
|
||||
**Tweet 1 (Hook)**
|
||||
🎉 Excited to share our paper accepted at #NeurIPS2024!
|
||||
|
||||
We tackle the challenge of [problem] in [domain].
|
||||
|
||||
Thread 👇
|
||||
|
||||
**Tweet 2 (Problem)**
|
||||
Current methods struggle with [specific issue], leading to [consequence].
|
||||
|
||||
Our key insight: [novel perspective]
|
||||
|
||||
**Tweet 3 (Method)**
|
||||
We propose [method name], which:
|
||||
✅ [Key feature 1]
|
||||
✅ [Key feature 2]
|
||||
✅ [Key feature 3]
|
||||
|
||||
**Tweet 4 (Results)**
|
||||
Results on [benchmark]:
|
||||
📊 [Metric 1]: X% improvement
|
||||
📊 [Metric 2]: Y% faster
|
||||
📊 [Metric 3]: Z% better
|
||||
|
||||
**Tweet 5 (CTA)**
|
||||
📄 Paper: [link]
|
||||
💻 Code: [link]
|
||||
🎯 Demo: [link]
|
||||
|
||||
#MachineLearning #AI #Research
|
||||
Reference in New Issue
Block a user