defense-prep
Skill6 starsChanged 6 months agoMITView on GitHub
Prepare for PhD or Master's thesis defense. Use when preparing defense presentation, anticipating committee questions, practicing oral defense, or structuring defense slides.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- MsNan/bishe-doc-skillstheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- MsNan/bishe-doc-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository75 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- agent-desktopSkill
- agent-expertise-protocolSkill
- ai-figure-generationSkill
- api-securitySkill
- architecture-decision-recordsSkill
- architecture-reviewSkill
- art-of-war-software-engineeringSkill
- browser-automationSkill
- business-product-leadershipSkill
- c4-level1-contextSkill
- c4-level2-containerSkill
- c4-level3-componentSkill
- c4-level4-codeSkill
- c4-modelSkill
- clean-architectureSkill
- cloud-securitySkill
- code-quality-gateSkill
- collaborative-engineering-agentSkill
- conference-paperSkill
- container-securitySkill
- database-designSkill
- ddd-coreSkill
- ddd-patternsSkill
- ddd-tacticalSkill
- dependency-managementSkill
- diffusion-release-trackingSkill
- docker-containerizationSkill
- dora-coreSkill
- evolutionary-architectureSkill
- exam-rubricSkill
- experiment-trackingSkill
- federated-learning-dqnSkill
- git-workflowSkill
- golang-developmentSkill
- internal-critiqueSkill
- javascript-typescriptSkill
- journal-q1-polishSkill
- kinhluan-routerSkill
- kubernetes-orchestrationSkill
- merge-request-reviewSkill
- milestone-trackerSkill
- paper-auditSkill
- paper-writingSkill
- pastureSkill
- payment-systemsSkill
- penetration-testingSkill
- phd-proposalSkill
- problem-discoverySkill
- product-analyticsSkill
- product-ux-researchSkill
- progress-reportSkill
- proposal-defenseSkill
- publication-strategySkill
- python-developmentSkill
- research-designSkill
- research-questionSkill
- research-watchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 102
Use this when practicing with peers/advisor:
- Distinctive: line 121
Never say "I don't know" alone — say "I don't know, but here's how I would think about it."
- Distinctive: line 125
Every slide: estimate seconds.
- Distinctive: line 126
Don't rush Q&A by running over.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Defense Preparation
Prepare a confident, rigorous oral defense of your thesis work.
Defense Timeline
T-8 weeks: Draft complete slides, share with advisor
T-6 weeks: Practice talk #1 with advisor (full run)
T-4 weeks: Incorporate feedback, practice with lab group
T-2 weeks: Practice with mock committee (optional but recommended)
T-1 week: Final slide polish, print backup PDF, know venue
T-1 day: Rest. Eat well. Check AV setup.
T-0: Arrive 30min early. Water bottle. Backup on USB.Slide Structure (60-min defense = ~40 slides)
Cover slide (1) — title, your name, advisor, date
Outline (1) — roadmap of talk
Motivation (2-3) — why this problem matters
Research Questions (1) — what you set out to answer
Background (3-4) — what audience needs to know
Related Work (2-3) — where you fit in literature
Methodology (8-10) — your main contribution
Results (6-8) — experiments + key findings
Discussion (2-3) — implications, limitations
Conclusion (2) — answer your RQs, contributions
Future Work (1-2)
Thank You + Q&A (1)
Backup slides (5-10) — for expected hard questionsSlide Design Principles
- 1 idea per slide — title is the takeaway, body is the evidence
- Figures over text — if explainable with a diagram, use one
- Build animations sparingly — only to guide attention, not show off
- Results: always compare — isolated numbers mean nothing
- Font ≥ 24pt — smallest text readable from back of room
Anticipated Question Categories
Category 1 — Methodology Deep Dives
"Why did you choose [method X] over [method Y]?" → Prepare: justification from research-design + comparison data
"What happens if assumption [A] doesn't hold?" → Prepare: robustness experiment or honest limitation statement
"How does your method scale to [larger/different] setting?" → Prepare: complexity analysis + any scaling experiments
Category 2 — Experimental Validity
"Why didn't you compare to [paper Z]?" → Prepare: why it's not a fair baseline OR add it
"Could your results be explained by [confound]?" → Prepare: controlled experiment that rules it out
"Is the improvement statistically significant?" → Prepare: p-values, effect sizes, number of seeds
Category 3 — Contribution Scope
"How is this different from [prior work X]?" → Prepare: explicit differentiation table
"What is your key insight / novelty?" → One crisp sentence. Practice this until fluent.
"What would you do differently if starting over?" → Honest answer. Shows maturity. Not a trap.
Category 4 — Future Directions
"What are the next steps?" → Have 2-3 concrete, specific directions (not vague "more datasets")
Category 5 — Basics (common in Master's)
"Explain [fundamental concept] in your work" → Never assume they know your domain. Prepare Feynman-style explanation.
Practice Scoring Rubric
Use this when practicing with peers/advisor:
| Dimension | 1-Poor | 3-OK | 5-Excellent |
| Motivation clarity | Unclear why | Somewhat clear | Crystal clear, real stakes |
| Technical depth | Skips details | Some details | Rigorous but accessible |
| Results explanation | Just shows numbers | Explains trends | Insights + implications |
| Question handling | Defensive | Addresses question | Engages, builds on question |
| Time management | Over/under by >5min | ±3min | Hits target exactly |
| Confidence | Nervous, hesitant | Competent | Authoritative |
On the Day
Opening (memorize this):
"Good [morning/afternoon]. Thank you for coming. My thesis is titled [X]. The central question I've been investigating is [RQ in plain language]. Today I'll walk you through what I found and why I believe it matters."
Handling unknown questions:
"That's a great question. I haven't specifically tested for that, but based on [reasoning], I would expect [answer]. This is actually a good direction for future work."
Never say "I don't know" alone — say "I don't know, but here's how I would think about it."
Time control:
- Practice 3 times minimum. Know your pace.
- Every slide: estimate seconds. Cut if needed.
- Don't rush Q&A by running over.
Backup Slide Topics (prepare these)
- Detailed algorithm pseudocode
- Full hyperparameter tables
- Additional ablation results
- Proofs or derivations referenced but not shown
- Failure cases / limitations in detail
- Comparison with [most likely missing baseline]
Links to Other Skills
- Requires →
paper-writing(thesis must be written first) - Requires →
milestone-tracker(defense date in timeline) - Pairs with →
internal-critique(critique your slides like a reviewer)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

