figure-results-review
Figure Results Review
Purpose
Help the user present experimental results clearly and scientifically. This skill follows the handbook's result presentation and figure standards: explain setup before results, define variables and hypotheses, label axes with units, use captions and legends, include uncertainty when appropriate, and point out key trends.
The output is a figure/result review note and a corrected presentation plan.
When to Use
- User has plots, tables, or result slides to show
- User wants feedback on a figure
- User is preparing experimental results for a paper or talk
- User is unsure how to explain a result
- User wants to check whether a plot is publication-ready
Workflow
Stage 1: Establish the Result Context
Ask:
- What claim is this result meant to support?
- What is the experimental setup?
- What are the baselines?
- What metrics are used?
- What should the audience notice first?
Do not review aesthetics before the scientific claim is clear.
Stage 2: Figure Checklist
For each figure, check:
- Descriptive title
- X-axis label with units
- Y-axis label with units
- Legend for all symbols/colors
- Readable font size
- Accessible color scheme
- Error bars or confidence intervals where appropriate
- Caption explains what is shown and what to conclude
- Scale/range does not distort the comparison
- Consistent model colors and ordering across subplots
Stage 3: Results Interpretation
Ask the user to state:
- Main trend
- Quantitative effect size
- Comparison to baseline
- Whether it confirms or contradicts the hypothesis
- Plausible confounders
- Negative or surprising findings
If the user says "it improves performance," push for exact metric deltas and conditions.
Stage 4: Presentation Sequence
Create a speaking order:
- Experimental setting
- Variables and metrics
- Hypothesis
- Figure caption in plain language
- Axes and legend
- Main trend
- Takeaway and limitation
This prevents the common mistake of jumping straight to a plot and forcing the audience to decode it.
Stage 5: Produce the Artifact
Save to ~/phd-log/results/YYYY-MM-DD-[short-topic].md.
# Figure / Results Review — [Short Topic]
## Claim
[What this result is meant to support]
## Experimental setup
- Dataset:
- Baselines:
- Metrics:
- Variables:
- Hypothesis:
## Figure checklist
| Figure | Issue | Fix | Priority |
|---|---|---|---|
## Interpretation
- Main trend:
- Effect size:
- Baseline comparison:
- Confounders:
- Negative/surprising results:
- Takeaway:
## Presentation script
1. Setup:
2. Metric:
3. Hypothesis:
4. Figure explanation:
5. Trend:
6. Limitation:
7. Next step:
## Fix list
- [ ] [figure/result fix]
Tone
Be exacting. A beautiful figure that does not explain the setup or claim is not ready.
What Not to Do
- Do not accept unlabeled axes.
- Do not let the user present a result without the experimental setting.
- Do not infer a causal claim from a weak comparison.
- Do not hide negative results when they clarify the research direction.
More from a-green-hand-jack/phd-skills
advisor-meeting-prep
Help a PhD student prepare for a meeting with their advisor so that both sides get maximum value from the limited time. Use this skill whenever the user has an upcoming advisor meeting, lab meeting presentation, or committee meeting, and needs help structuring what to bring. Trigger on phrases like "meeting with my advisor", "advisor meeting tomorrow", "what do I show my PI", "prepare for lab meeting", "committee meeting prep", "I meet my advisor in", or whenever the user expresses anxiety about an upcoming research check-in. Also trigger when the user is unsure how to communicate a research problem or a setback to their advisor.
2phd-mode-switcher
Help a PhD student intentionally choose which cognitive mode to enter right now (deep production, wide reading, or collaborative engagement) and plan their day around these modes to minimize context-switching costs. Use this skill whenever the user is at the start of a day or work block and unsure what to focus on, feels scattered across too many activities, asks "what should I do right now", wants to plan their day, or feels frustrated by constant context-switching. Trigger on phrases like "plan my day", "what should I work on now", "I feel scattered", "context switching", "deep work", "can't focus", "I have X hours", or whenever the user is trying to decide between substantively different kinds of work (writing vs reading vs meetings).
2phd-quarterly-planner
Help a PhD student set and revise a realistic 3-month research plan that connects to their longer-term goals. Use this skill whenever the user wants to plan a new quarter, review how the last quarter went, set research goals for the next few months, think about what papers to aim for, or reorient after things drift off course. Trigger on phrases like "quarterly plan", "next 3 months", "plan my quarter", "what should I work on this quarter", "review last quarter", "my research goals", or whenever the user talks about mid-range planning (longer than a week, shorter than a year). Also trigger if the user is feeling directionless about what to focus on next.
2research-mental-check
Offer a structured but non-clinical space for a PhD student or researcher to check in on their mental and emotional state, especially around imposter syndrome, guilt about rest, chronic over-promising, and burnout signals. Use this skill when the user expresses feelings of inadequacy, constant comparison to peers, fear of disappointing their advisor, guilt about taking time off, or exhaustion that isn't just physical. Trigger on phrases like "I feel behind", "everyone is smarter than me", "I can't rest", "I'm burned out", "imposter syndrome", "I'm not good enough", "I'm afraid of disappointing", "I should be working", or whenever the tone of the user's message suggests emotional strain rather than a technical question. Also trigger gently if these signals appear incidentally in a task-focused conversation.
2phd-weekly-review
Guide a PhD student through a structured weekly review of their research progress. Use this skill whenever the user wants to do a weekly check-in, prepare a progress update for their advisor, reflect on the past week's research, or plan the upcoming week. Trigger on phrases like "weekly review", "this week's progress", "advisor update", "reflect on my week", "plan next week", "how did my week go", or whenever the user mentions wanting to take stock of their recent research work. Also trigger when the user seems to be venting about the week without structure — help them channel it into a productive review.
2literature-review-sprint
Guide a CS or AI PhD student through a focused literature review sprint that produces a ranked paper map, notes, gaps, and next actions. Use this skill whenever the user needs to survey a topic, prepare related work, check whether an idea is novel, catch up on a field, read papers before a meeting, or turn a pile of papers into an organized research direction.
2