Source profileQuality 98/100

travisjneuman/.claude/skills/research-presenter/SKILL.md

research-presenter

Turn research findings into presentation outlines with narrative arc, data visualization suggestions, audience adaptation, and slide design guidance. Use when creating research presentations, conference talks, or findings briefings.

Source repository stars
95
Declared platforms
0
Static risk flags
0
Last source update
2026-08-13
Source checked
2026-08-28

Decision brief

What it does: where it fits

Structured frameworks for transforming research findings into compelling presentations across academic, industry, and executive contexts.

Best for

  • Use when creating research presentations, conference talks, or findings briefings.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/travisjneuman/.claude --skill "skills/research-presenter"
Safe inspection promptEditorial

Inspect the Agent Skill "research-presenter" from https://github.com/travisjneuman/.claude/blob/b8b4dd55d61b9f25d33e3b5427870641a1c8c39c/skills/research-presenter/SKILL.md at commit b8b4dd55d61b9f25d33e3b5427870641a1c8c39c. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Audience Assessment Checklist

    Review the “Audience Assessment Checklist” section in the pinned source before continuing.

    Review and apply the “Audience Assessment Checklist” source section.
  2. 02

    Presentation Structure Template

    Review the “Presentation Structure Template” section in the pinned source before continuing.

    Review and apply the “Presentation Structure Template” source section.
  3. 03

    Standard Research Presentation (15-20 minutes)

    Review the “Standard Research Presentation (15-20 minutes)” section in the pinned source before continuing.

    Review and apply the “Standard Research Presentation (15-20 minutes)” source section.
  4. 04

    Short Talk Structure (5-7 minutes)

    Review the “Short Talk Structure (5-7 minutes)” section in the pinned source before continuing.

    Review and apply the “Short Talk Structure (5-7 minutes)” source section.
  5. 05

    Narrative Arc Framework

    Review the “Narrative Arc Framework” section in the pinned source before continuing.

    Review and apply the “Narrative Arc Framework” source section.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score98/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars95SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
travisjneuman/.claude
Skill path
skills/research-presenter/SKILL.md
Commit
b8b4dd55d61b9f25d33e3b5427870641a1c8c39c
License
MIT
Collected
2026-08-28
Default branch
master
View the original SKILL.md

Research Presenter

Structured frameworks for transforming research findings into compelling presentations across academic, industry, and executive contexts.

Presentation Structure Template

Standard Research Presentation (15-20 minutes)

PRESENTATION OUTLINE:

1. TITLE SLIDE (30 seconds)
   - Clear, specific title (not clever, not vague)
   - Author(s) and affiliation
   - Date and venue
   - Funding acknowledgment (if applicable)

2. OPENING HOOK (1-2 minutes)
   - Start with a problem, question, or surprising fact
   - Make the audience care before explaining the method
   - Connect to their world (industry relevance, real impact)

3. BACKGROUND AND CONTEXT (2-3 minutes)
   - What is known (brief literature positioning)
   - What is NOT known (the gap)
   - Why this gap matters (so what?)
   - Your research question (single, clear statement)

4. METHODS (2-3 minutes)
   - Study design overview (visual diagram preferred)
   - Key methodological decisions and rationale
   - Sample / data description
   - Analysis approach (high-level, not every step)

5. RESULTS (5-7 minutes — the core)
   - Lead with the main finding (not chronological)
   - One key finding per slide
   - Visualize data rather than tables of numbers
   - Build complexity gradually
   - Highlight what is new or surprising

6. DISCUSSION (2-3 minutes)
   - What does this mean? (interpretation)
   - How does it fit with existing knowledge?
   - Limitations (honest, but don't dwell)
   - Implications (practical, theoretical, policy)

7. CONCLUSION (1-2 minutes)
   - 2-3 key takeaways (memorable statements)
   - Future directions (what comes next)
   - Call to action (if applicable)

8. ACKNOWLEDGMENTS AND Q&A (remaining time)
   - Thank collaborators and funders
   - Display contact information
   - Open for questions

Short Talk Structure (5-7 minutes)

LIGHTNING TALK FORMAT:

Slide 1: Title + one-sentence summary of finding
Slide 2: The problem (why should anyone care?)
Slide 3: What we did (one visual of method)
Slide 4: Main result (one chart, one takeaway)
Slide 5: Supporting result (optional, only if critical)
Slide 6: So what? (implications + next steps)
Slide 7: Contact info + key reference

RULE: One idea per slide. No more than 7 slides.
If you cannot explain it in 7 slides, you do not
understand it well enough yet.

Narrative Arc Framework

Story Structure for Research

NARRATIVE ARC:

                    CLIMAX (Main Finding)
                   /                      \
                  /                        \
    RISING ACTION                    FALLING ACTION
    (Methods, Build-up)              (Discussion, Context)
   /                                          \
  /                                            \
HOOK ─────────────────────────────────────── RESOLUTION
(Problem/Question)                        (Takeaways/Future)

IMPLEMENTATION:

ACT 1 — SETUP (25% of time)
  "Here is a problem that matters to you..."
  "Previous attempts have tried X, Y, Z but..."
  "The question we asked was..."

ACT 2 — CONFRONTATION (50% of time)
  "We approached this by..."
  "What we found was..." [build tension with supporting data]
  "The surprising part was..." [climax — main finding]

ACT 3 — RESOLUTION (25% of time)
  "This means that..."
  "The limitation is..."
  "Going forward, we plan to..."
  "What you can do with this is..."

Narrative Transitions

FromToTransition Phrase
HookBackground"To understand why this matters, let me give you some context..."
BackgroundResearch question"This brings us to the question we set out to answer..."
Research questionMethods"Here is how we investigated this..."
MethodsResults"So what did we find?"
Result 1Result 2"Building on this, we also discovered..."
ResultsDiscussion"What does this tell us?"
DiscussionLimitations"Before we get too excited, there are important caveats..."
LimitationsConclusion"Despite these limitations, the evidence suggests..."
ConclusionCall to action"Here is what I hope you take away from this..."

Audience Adaptation Matrix

Tailoring Content by Audience

ElementAcademic ConferenceIndustry/PractitionerExecutive BriefingGeneral Public
OpeningLiterature gapBusiness problemBottom-line impactHuman story
Methods depthDetailed, justify choicesHigh-level summarySkip or one slideAvoid jargon
Results focusStatistical rigorPractical applicationsROI / impact numbersWhat changed
VisualizationsDetailed charts, tablesClean charts, dashboardsSummary metrics onlyInfographics
Jargon levelField-specific terms OKIndustry terms OKPlain language requiredEveryday language
Slides per minute1-1.51-22-3 (fast pacing)1-1.5
Takeaway formatFuture researchAction itemsRecommendationMemorable insight
Q&A depthMethodological debate"How do I apply this?""What should we do?""What does this mean?"

Audience Assessment Checklist

BEFORE DESIGNING YOUR PRESENTATION:

1. WHO is in the audience?
   - Expertise level: [ ] Expert  [ ] Knowledgeable  [ ] General
   - Role: [ ] Researchers  [ ] Practitioners  [ ] Decision-makers  [ ] Mixed
   - Size: [ ] Small (<20)  [ ] Medium (20-100)  [ ] Large (100+)

2. WHAT do they already know?
   - Background in your field: [ ] Deep  [ ] Some  [ ] None
   - Familiarity with your methods: [ ] High  [ ] Low  [ ] None
   - Prior exposure to your topic: [ ] Extensive  [ ] Limited  [ ] First time

3. WHY are they here?
   - [ ] Required (conference, class, meeting)
   - [ ] Voluntary (interested in topic)
   - [ ] Decision-making (evaluating your work)

4. WHAT do they need from you?
   - [ ] Rigorous evidence and methodology
   - [ ] Practical recommendations
   - [ ] Strategic implications
   - [ ] Inspiration or awareness

5. WHAT is their attention span?
   - [ ] High focus (small seminar, engaged group)
   - [ ] Moderate (conference session, last day)
   - [ ] Low (after lunch, end of long day, virtual)
   Adjust: pacing, interactivity, slide density

Slide Design Guidelines

Content Rules

SLIDE DESIGN PRINCIPLES:

1. ONE IDEA PER SLIDE
   If a slide requires more than 6 seconds to understand,
   it has too much content. Split it.

2. ASSERTION-EVIDENCE STRUCTURE
   Title: A complete sentence stating the slide's message
   Body: Visual evidence supporting that assertion
   Example title: "Treatment group showed 40% faster recovery"
   NOT: "Results" or "Figure 3"

3. TEXT LIMITS
   - Title: 1 line, max 10 words
   - Bullet points: max 3-4 per slide, max 8 words each
   - Body text: avoid entirely (speak it, do not display it)
   - Font size: never below 24pt (28-36pt recommended)

4. VISUAL HIERARCHY
   - Most important element is largest
   - Use contrast (color, size, weight) to direct attention
   - White space is not wasted space — it aids comprehension
   - Consistent alignment (left-align text, center figures)

5. COLOR USAGE
   - Maximum 3-4 colors total
   - One accent color for emphasis
   - Sufficient contrast (check for colorblind accessibility)
   - Dark text on light background (or vice versa consistently)

Slide Type Templates

Slide TypeLayoutWhen to Use
TitleLarge title, subtitle, author, affiliationOpening slide
Section dividerSingle word or phrase, full-bleedTransition between major sections
Assertion + chartSentence title + single chartPresenting a finding
Assertion + imageSentence title + photo/diagramContext, methods, examples
ComparisonSide-by-side panels or split screenBefore/after, two conditions
Build slideProgressive reveal (animation)Complex concepts, step-by-step
QuoteLarge text, attributionExpert opinion, participant voice
Summary3 key points, numberedRecap and transition
ContactName, email, QR code, key referenceFinal slide

Slide Count Guidelines

Presentation LengthSlide CountPace
5 minutes5-7 slides45-60 sec/slide
10 minutes8-12 slides50-75 sec/slide
15 minutes12-18 slides50-75 sec/slide
20 minutes15-25 slides50-80 sec/slide
45 minutes30-45 slides60-90 sec/slide
60 minutes (with Q&A)35-50 slides60-90 sec/slide

Data Visualization Selection

Chart Selection Guide

CHOOSING THE RIGHT CHART:

COMPARISON (between items):
  Few items (2-5)    → Bar chart (horizontal or vertical)
  Many items (5-15)  → Horizontal bar chart (sorted)
  Over time          → Line chart
  Two variables      → Scatter plot

COMPOSITION (parts of a whole):
  At a point in time   → Stacked bar or pie (max 5 slices)
  Over time            → Stacked area chart
  Hierarchical         → Treemap

DISTRIBUTION:
  Single variable      → Histogram or density plot
  Compare groups       → Box plot or violin plot
  Two variables        → Scatter plot with density

RELATIONSHIP:
  Two variables        → Scatter plot
  Three variables      → Bubble chart
  Correlation matrix   → Heat map

CHANGE OVER TIME:
  Single series        → Line chart
  Multiple series      → Small multiples (not spaghetti lines)
  Cumulative           → Area chart

Visualization Do's and Don'ts

DoDon't
Label axes clearly with unitsAssume the audience knows the units
Start bar chart y-axis at zeroTruncate axis to exaggerate differences
Use color meaningfullyUse color decoratively
Annotate key data pointsLet the audience search for the insight
Simplify to the essential messageShow all the data you collected
Use consistent scales across comparisonsChange scales between related charts
Provide a descriptive chart title (assertion)Use generic titles ("Figure 1")
Test for colorblind accessibilityRely on red/green distinction

Speaking Notes Template

Per-Slide Notes Structure

SPEAKING NOTES FORMAT:

SLIDE [N]: [Title]
Duration: [XX] seconds

KEY POINT:
[The one thing the audience must understand from this slide]

SCRIPT (conversational, not read verbatim):
"[Opening line for this slide]...
 [Supporting detail or transition]...
 [Bridge to next slide]."

AUDIENCE CUE:
[Pause here / Ask question / Point to specific data]

FALLBACK:
[If running behind: skip this detail]
[If ahead of schedule: add this anecdote or example]

Timing and Pacing Guide

PACING STRATEGY:

OPENING (first 2 minutes):
  - Speak slightly slower than natural pace
  - Establish eye contact with different sections
  - Pause after your opening hook for impact

MIDDLE (core content):
  - Natural conversational pace
  - Pause before and after key findings (2-3 seconds)
  - Vary pace: slow for important points, normal for transitions

CLOSING (final 2 minutes):
  - Slightly slower, more deliberate
  - Pause before final takeaway
  - End with a strong, definitive statement (not "that's it")

TIME CHECKPOINTS:
  25% mark: Should be finishing Background/Context
  50% mark: Should be in the middle of Results
  75% mark: Should be starting Discussion
  90% mark: Should be on Conclusion slide

RECOVERY IF BEHIND SCHEDULE:
  - Skip one supporting result (keep main finding)
  - Shorten methods to "we used X approach"
  - Condense discussion to 2 sentences
  - Never skip the conclusion or takeaways

Q&A Preparation

Anticipated Questions Framework

Q&A PREPARATION TEMPLATE:

CATEGORY 1: METHODOLOGY QUESTIONS
Q: "Why did you choose [method X] instead of [method Y]?"
A: [Prepared response with rationale]
Backup slide: [slide number]

Q: "What about [potential confound]?"
A: [How you addressed or acknowledged it]

CATEGORY 2: RESULTS INTERPRETATION
Q: "How do you explain [unexpected finding]?"
A: [Your interpretation + alternative explanations]

Q: "Is this statistically significant?"
A: [Specific numbers: p-value, CI, effect size]

CATEGORY 3: PRACTICAL IMPLICATIONS
Q: "How would this apply to [specific context]?"
A: [Concrete application with caveats]

CATEGORY 4: LIMITATIONS AND FUTURE WORK
Q: "What are the biggest limitations?"
A: [Top 2-3 limitations, framed constructively]

Q: "What would you do differently?"
A: [Honest reflection + next steps]

CATEGORY 5: HOSTILE OR CHALLENGING QUESTIONS
Q: "This contradicts [other researcher's] findings..."
A: [Acknowledge, explain differences, avoid defensiveness]

STRATEGY FOR UNKNOWN QUESTIONS:
"That is a great question. I do not have data on that
specifically, but based on what we observed, I would
hypothesize that... I am happy to follow up after the
session with more detail."

Q&A Best Practices

SituationResponse Strategy
Question you know the answer toConcise answer + one supporting detail
Question you partially knowAnswer what you can, acknowledge the gap
Question you don't know"I don't know, but here's what I think..."
Hostile or loaded questionReframe neutrally, answer the valid part
Overly long question"If I understand correctly, you're asking..."
Question outside scope"That's interesting — it's outside this study, but..."
No questions from audienceHave a self-asked question prepared to break silence

Poster Presentation Layout

Standard Research Poster (48" x 36")

POSTER LAYOUT:

┌─────────────────────────────────────────────────┐
│                   TITLE                          │
│            Authors, Affiliations                 │
├──────────┬──────────┬──────────┬────────────────┤
│          │          │          │                │
│ INTRO    │ METHODS  │ RESULTS  │  RESULTS       │
│          │          │ (Chart 1)│  (Chart 2)     │
│ Research │ Design   │          │                │
│ Question │ diagram  │          │                │
│          │          │          │                │
├──────────┴──────────┼──────────┴────────────────┤
│                     │                            │
│  KEY FINDINGS       │  CONCLUSION + REFERENCES   │
│  (3 bullet points)  │  + QR code to full paper   │
│                     │                            │
└─────────────────────┴────────────────────────────┘

POSTER RULES:
  - Readable from 4 feet away (title: 72pt, body: 28-32pt)
  - Maximum 800 words total
  - Figures > text (60/40 ratio minimum)
  - Flow: top-left → bottom-right (Z-pattern)
  - Include QR code linking to paper, data, or slides
  - White space between sections aids navigation

Conference Abstract Template

Structured Abstract (250-300 words)

ABSTRACT FORMAT:

TITLE: [Specific, descriptive — avoid question format]

BACKGROUND: [2-3 sentences]
[What is known + what gap exists + why it matters]

OBJECTIVE: [1 sentence]
[Clear statement of what this study aimed to do]

METHODS: [3-4 sentences]
[Study design, participants/data, key measures, analysis]

RESULTS: [3-4 sentences]
[Main finding with numbers: effect sizes, p-values, CIs]
[Secondary findings if space permits]

CONCLUSIONS: [2-3 sentences]
[Interpretation of findings + practical significance]
[One sentence on limitations or future directions]

KEYWORDS: [3-5 terms, separated by semicolons]

Abstract Quality Checklist

ElementCheckStatus
Title is specific and informativeNot a question, not vague[ ]
Background establishes the gapWhy this study was needed[ ]
Objective is a clear single statementOne research question[ ]
Methods include design and sampleEnough to assess validity[ ]
Results include actual numbersEffect sizes, not just p-values[ ]
Conclusions match the resultsNo overclaiming[ ]
Within word limitUsually 250-300 words[ ]
Keywords are searchable termsStandard terminology[ ]

Presentation Rehearsal Protocol

REHEARSAL STAGES:

STAGE 1 — SOLO RUN-THROUGH (day -7)
  - Read through slides and notes
  - Time yourself
  - Identify awkward transitions and fix them
  - Mark slides that need simplification

STAGE 2 — RECORDED PRACTICE (day -5)
  - Record audio or video of full presentation
  - Watch/listen for: filler words, pacing, clarity
  - Check: are you reading slides or speaking naturally?
  - Adjust timing for problem sections

STAGE 3 — PRACTICE AUDIENCE (day -3)
  - Present to 1-3 colleagues or friends
  - Ask them: "What was the main takeaway?"
  - If they cannot answer clearly, revise that section
  - Practice answering their questions

STAGE 4 — FINAL POLISH (day -1)
  - One final timed run-through
  - Verify all technology works (projector, pointer, backup)
  - Prepare backup: USB drive + cloud link + printed notes
  - Get adequate sleep

See Also

Frequently asked questions

What to verify before installation and use

What does the research-presenter source document cover?

Structured frameworks for transforming research findings into compelling presentations across academic, industry, and executive contexts.

How do I install research-presenter?

The source record exposes this install command: npx skills add https://github.com/travisjneuman/.claude --skill "skills/research-presenter". Inspect the command and pinned source before running it.

Alternatives

Compare before choosing

Computed 10045,960

coreyhaines31/marketingskills

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

Computed 10045,960

coreyhaines31/marketingskills

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

Computed 10014,706

prowler-cloud/prowler

postgresql-indexing

PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance

Computed 1008

narrative-io/narrative-skills-marketplace

design-analysis

Translate a fuzzy analytical question into a rigorous investigation plan. Interrogates the ask, grounds the plan in the available data dictionary, applies analytical best practices, and produces a structured brief of query specifications for a downstream query-writing skill. Plans, does not write SQL. Use when: "why did X drop", "is there a relationship between A and B", "who are our highest-value customers", "what's driving the change in Y", "investigate this trend", "design an analysis for", "