/post-acceptance
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
$ npx -y skills add Galaxy-Dawn/claude-scholar --skill post-acceptance --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/post-acceptance
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
post-acceptance.SKILL.mdname: 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
Read more
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
Semi-automated research assistant for academic research and software development. Supports Claude Code, Codex CLI, Kimi Code CLI, and OpenCode across ideation, coding, experiments, writing, and publication.
Repo: Galaxy-Dawn/claude-scholar
Other skills on claude-scholar.
- /agent-identifier
Use when creating or configuring Claude Code agents and their frontmatter.
Open skill - /architecture-design
Use only when creating new registrable ML components that require Factory or Registry patterns.
Open skill - /bug-detective
This skill should be used when the user asks to "debug this", "fix this error", "investigate this bug", "troubleshoot this issue", "find the problem", "something is broken", "this isn't working", "why is this failing", or reports errors/exceptions/bugs. Provides systematic
Open skill - /citation-verification
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports
Open skill - /code-review-excellence
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.
Open skill - /command-development
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in
Open skill

