Add Gemini CLI Agent Skill support (one-command install)

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Andrei Wong
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -1,58 +1,62 @@
-# Academic Presentations Skill for Claude
+# Academic Presentations Skill for Gemini CLI
 
-A Claude Skill for creating high-quality academic presentations: conference talks, seminar slides, thesis defenses, and grant briefings.
+A Gemini skill for creating high-quality academic presentations: conference talks, seminar slides, thesis defenses, and grant briefings.
 
-## What It Does
+## Quick Install
 
-This skill overrides Claude's default design-forward presentation style and replaces it with communication-first standards appropriate for academic and analytical contexts. When active, Claude will:
+To install this skill for Gemini CLI:
 
-- Write every slide title as a **complete sentence stating the takeaway** ("action title"), not a topic label
-- Structure the deck as a **logical argument** (situation → complication → resolution), not a collection of independent slides
-- Apply the **ghost deck test**: the action titles alone, read in sequence, should tell the full story
-- Place **one exhibit per results slide** and annotate the key finding directly on the chart
-- Apply **citation standards**: in-text citations on every borrowed figure, a References slide at the end
-- End on a **Conclusions slide** that stays on screen during Q&A — never on "Thank You" or a blank
-- Apply minimal, communication-first design: white backgrounds, single sans-serif font, three colours maximum, no decorative icons
+```bash
+gemini skills install https://github.com/Andrei-WongE/academic-pptx-skill
+```
+
+## Features
+
+This skill overrides default design-forward presentation styles and replaces them with communication-first standards appropriate for academic and analytical contexts:
+
+- **Action Titles**: Every slide title is a complete sentence stating the takeaway.
+- **Logical Argument**: Deck structure follows a proven narrative spine (Situation → Complication → Resolution).
+- **Ghost Deck Test**: The argument must hold together when reading only the slide titles.
+- **Exhibit Discipline**: One exhibit per results slide with "so what" annotations.
+- **Academic Citations**: In-slide citations and a full References slide at the end.
+- **Strategic Conclusions**: The deck ends on a Conclusions slide that stays visible during Q&A.
 
-## Installation
+## Platform Compatibility
 
-1. Download this repository as a zip file (click **Code → Download ZIP** above)
-2. In [claude.ai](https://claude.ai), go to **Customize → Skills**
-3. Upload the zip file
-4. Confirm the skill appears in your skills list and is toggled on
+This repository is optimized for dual-platform use:
 
-> **Requirement:** Code execution and file creation must be enabled in **Settings → Capabilities**.
+### Gemini CLI (Recommended)
+Follow the installation command above. The `gemini/SKILL.md` and `gemini/references/` folder provide immediate, native compatibility with Gemini CLI's skill system.
+
+### Claude Code
+The original structure is preserved in the `claude/` directory (flat structure with `SKILL.md` and supporting files) for users who prefer the legacy layout.
 
 ## Usage
 
-Just ask naturally:
+Once installed, the skill is automatically discovered. You can trigger it naturally:
 
 - *"Make slides for my conference paper on X"*
 - *"Build a deck for my thesis defense"*
 - *"Create a seminar presentation about my research on Y"*
 
-Claude will detect the academic context, load this skill automatically, and apply all guidelines before generating any slides. You do not need to give any special instructions.
-
-This skill works alongside Anthropic's built-in PPTX skill, which handles the technical file generation. This skill handles content, argument structure, and design standards.
+Gemini will detect the academic context, load this skill, and apply all guidelines.
 
-## File Structure
+## Development & Structure
 
 ```
 academic-pptx-skill/
-├── SKILL.md                  # Entry point: routing logic and design standards
-├── content_guidelines.md     # Argument structure, action titles, citations, deck architecture
-├── slide_patterns.md         # Per-slide-type implementation patterns with PptxGenJS code
-└── README.md                 # This file
+├── README.md
+├── gemini/
+│   ├── SKILL.md             # Core methodology + metadata
+│   └── references/          # Supporting guidelines and patterns
+│       ├── content_guidelines.md
+│       └── slide_patterns.md
+└── claude/                  # Original Claude Code version (flat)
+    ├── SKILL.md
+    ├── content_guidelines.md
+    └── slide_patterns.md
 ```
 
-## Background
-
-The guidelines in this skill draw on:
-- Barbara Minto's *Pyramid Principle* (structured argument, action titles)
-- Naegle (2021), "Ten simple rules for effective presentation slides," *PLOS Computational Biology*
-- Standard consulting and academic presentation practice (McKinsey, conference norms)
-- Community feedback on Claude's default presentation behaviour in professional contexts
-
 ## License
 
 MIT — free to use, adapt, and share.

SKILL.md → claude/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: academic-pptx
 description: "Use this skill whenever the user wants to create or improve a presentation for an academic context — conference papers, seminar talks, thesis defenses, grant briefings, lab meetings, invited lectures, or any presentation where the audience will evaluate reasoning and evidence. Triggers include: 'conference talk', 'seminar slides', 'thesis defense', 'research presentation', 'academic deck', 'academic presentation'. Also triggers when the user asks to 'make slides' in combination with academic content (e.g., 'make slides for my paper on X', 'create a presentation for my dissertation defense', 'build a deck for my grant proposal'). This skill governs CONTENT and STRUCTURE decisions. For the technical work of creating or editing the .pptx file itself, also read the pptx SKILL.md."
-license: Proprietary. LICENSE.txt has complete terms
+license: MIT
 ---
 
 # Academic Presentations Skill

gemini/SKILL.md

@@ -0,0 +1,152 @@
+---
+name: academic-pptx
+description: "Use this skill whenever the user wants to create or improve a presentation for an academic context — conference papers, seminar talks, thesis defenses, grant briefings, lab meetings, invited lectures, or any presentation where the audience will evaluate reasoning and evidence. Triggers include: 'conference talk', 'seminar slides', 'thesis defense', 'research presentation', 'academic deck', 'academic presentation'. Also triggers when the user asks to 'make slides' in combination with academic content (e.g., 'make slides for my paper on X', 'create a presentation for my dissertation defense', 'build a deck for my grant proposal'). This skill governs CONTENT and STRUCTURE decisions. For the technical work of creating or editing the .pptx file itself, also read the pptx SKILL.md."
+license: MIT
+---
+
+# Academic Presentations Skill
+
+## How This Skill Works
+
+This skill has two layers:
+
+1. **This file** — governs content, argument structure, and design standards for academic presentations. Read it fully before planning any slides.
+2. **PPTX skill** — governs the technical implementation (creating, editing, and QA-ing the .pptx file). Read it too.
+
+**Always read both before writing any code or creating any files.**
+
+---
+
+## Quick Reference
+
+| Task | Guide |
+|------|-------|
+| Content planning, argument structure, slide-by-slide rules | [references/content_guidelines.md](references/content_guidelines.md) |
+| Per-slide-type patterns (title, methods, results, etc.) | [references/slide_patterns.md](references/slide_patterns.md) |
+| Technical creation from scratch | PPTX skill → `pptxgenjs.md` |
+| Technical editing of an existing file | PPTX skill → `editing.md` |
+
+---
+
+## Step 1: Identify Presentation Type
+
+Before planning a single slide, determine which mode applies.
+
+### Structured Argument (default for academic work)
+
+Use for: conference papers, seminar talks, thesis defenses, dissertation chapters, grant briefings, internal lab presentations, policy briefings, consulting-style research deliverables.
+
+**Priority order: argument structure → data → layout → aesthetics.**
+
+Follow [references/content_guidelines.md](references/content_guidelines.md) in full.
+
+### Visual / Narrative
+
+Use for: public engagement talks, science communication to non-specialist audiences, funding pitches to lay panels, event keynotes.
+
+Follow the PPTX skill's design-forward guidelines. Argument structure still matters, but visual storytelling and emotional engagement take priority.
+
+### When in doubt
+
+Default to **Structured Argument**. If the user mentions a paper, a study, a dataset, a thesis, a grant, or a conference, they almost certainly want structured argument mode.
+
+---
+
+## Step 2: Plan the Deck Before Creating Any Slides
+
+Produce a slide-by-slide outline (title, action title, exhibit type) and confirm with the user if the deck is more than 10 slides or if the content is complex. Do not start building until the outline is agreed.
+
+Use the ghost deck test during planning: read only the proposed action titles in sequence. They must tell the complete argument. If they don't, fix the outline before building.
+
+---
+
+## Step 3: Apply Design Standards
+
+Academic presentations use **communication-first design**. These rules override the PPTX skill's design-forward defaults.
+
+### Color
+
+- White background for all content slides.
+- One sans-serif font throughout (Arial, Calibri, or Helvetica — confirm with user or match their institution's template if provided).
+- Maximum three colors: one primary, one accent, one for emphasis or alerts. Default: dark navy primary (`1F4E79`), mid-blue accent (`2E75B6`), white or off-white background.
+- No decorative color gradients, no themed color palettes unless the user explicitly requests them.
+- Use color to **direct attention** — highlight the key finding on a chart, mark a callout box — not for decoration.
+
+### Typography
+
+| Element | Size | Weight |
+|---------|------|--------|
+| Action title | 24–28 pt | Bold |
+| Section header | 20–22 pt | Bold |
+| Body bullets | 20 pt | Regular |
+| Chart labels / annotations | 16–18 pt | Regular |
+| Source citations on slides | 12–14 pt | Regular, muted color |
+
+Single font face. Use size and weight for hierarchy — never multiple typefaces.
+
+### Layout
+
+- Left-align all body text. Center only slide titles and axis labels.
+- Consistent grid: all text boxes and figures align to the same margins (minimum 0.5" from slide edges).
+- For result slides: figure on the left, interpretive bullets on the right. This matches natural left-to-right reading.
+- White space is a signal of analytical clarity — do not fill every inch.
+- 16:9 widescreen is the default. Confirm with the user if they know the venue's aspect ratio.
+
+### Avoid (Academic-Specific)
+
+- **No decorative icons** — icons in colored circles, stock images, clip art are inappropriate for analytical academic presentations.
+- **No accent lines under titles** — use whitespace instead.
+- **No color palettes chosen for aesthetic interest** — use institution colors or the minimal defaults above.
+- **No full-bleed background images on content slides** — reserve for title/section dividers only if desired.
+- **No text-heavy slides** — if the audience is reading, they are not listening. Maximum ~40 words of body text per content slide.
+
+---
+
+## Step 4: Build and QA
+
+Follow the PPTX skill's QA procedure in full, including:
+- Content QA via `markitdown`
+- Visual QA via slide images (subagents if available)
+- Fix-and-verify loop until a full pass reveals no new issues
+
+**Additionally, run the academic-specific checks:**
+
+```
+Academic QA checklist:
+□ Every content slide has an action title (complete sentence stating the takeaway)
+□ Ghost deck test passes (action titles alone tell the full argument)
+□ One exhibit per results slide; each exhibit has a "so what" annotation
+□ Every borrowed figure or data point has an in-slide citation
+□ A References slide exists at the end
+□ Conclusions slide is the last non-appendix slide (not "Thank You" or a blank)
+□ Contact information and/or QR code/link on the final slide
+□ Font sizes are readable from the back of a room (≥ 20 pt body text)
+□ No decorative elements that don't carry content
+□ Section dividers or breadcrumb bar present for decks > 15 slides
+```
+
+---
+
+## Key Principles (Summary)
+
+**Action titles, not topic labels.** Every slide title is a complete sentence stating the takeaway. Reading titles alone should tell the whole argument (ghost deck test).
+
+**One argument, made well.** Don't present your whole paper. Pick the claim that can be made convincingly in the allotted time. Everything else goes in the appendix.
+
+**One insight per slide.** One exhibit per results slide. Highlight the key finding directly on the chart — don't make the audience hunt for it.
+
+**Slides support speech; they don't replace it.** Body text is for orientation, not information transfer. The presenter carries the argument; the slide carries the evidence.
+
+**Cite everything borrowed.** Academic integrity applies to slides. In-text citations on the slide, full references on the References slide.
+
+**End on conclusions.** The conclusions slide stays on screen during Q&A. Never end on "Thank You" or a blank slide.
+
+---
+
+## Dependencies
+
+Same as PPTX skill:
+- `pip install "markitdown[pptx]"` — text extraction
+- `npm install -g pptxgenjs` — creating from scratch
+- LibreOffice (`soffice`) — PDF conversion
+- Poppler (`pdftoppm`) — PDF to images