# gradient-calendar-pptx

The gradient-calendar-pptx skill turns a user’s topic into an editable PowerPoint deck with a calendar-led visual style. Use it for roadmaps, plans, or event programmes that call for dates and schedule blocks.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 138 repo stars
- Author: happycapy-ai
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/happycapy-ai/Happycapy-skills/tree/HEAD/skills/gradient-calendar/SKILL.md
- Updated: 2026-09-03
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/gradient-calendar-pptx

## What it does

The skill asks for any missing details about the topic, slide count, and image treatment in one `AskUserQuestion` call, with up to three questions. It then frames the subject as a calendar system: a strategy can become a grid of phases, while an event can become a day-by-day programme. The cover uses a prominent numeral, a title, and a vertical edge label.

The visual identity uses a pale gray background, oversized dark numerals, lime schedule blocks, blue vertical labels, and soft gradients. Calendar grids and cards are native editable PowerPoint elements rather than flattened images. If image generation is selected, the skill relies on `generate-image` and `openai/gpt-image-2`; it reads `/home/node/.claude/skills/generate-image/SKILL.md` for the call pattern. It asks before generation, so a deck does not start until the user has answered the applicable questions.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add happycapy-ai/Happycapy-skills --skill gradient-calendar-pptx -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/gradient-calendar/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/gradient-calendar/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add happycapy-ai/Happycapy-skills --skill gradient-calendar-pptx -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/gradient-calendar/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add happycapy-ai/Happycapy-skills --skill gradient-calendar-pptx -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/gradient-calendar/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install happycapy-ai/Happycapy-skills skills/gradient-calendar
```

2. **Manually: put the files in place**
- File: `.github/skills/gradient-calendar/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add happycapy-ai/Happycapy-skills --skill gradient-calendar-pptx -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/happycapy-ai/Happycapy-skills --path skills/gradient-calendar
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/gradient-calendar/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/happycapy-ai/Happycapy-skills/tree/HEAD/skills/gradient-calendar/SKILL.md

## When to use it
- turn a strategy into a grid of calendar phases
- lay out an event programme by day and track
- map a roadmap to dates and milestones
- build an editable PowerPoint deck around a topic

## Example prompts
- Create a 10-slide Gradient Calendar deck about a product launch, with no generated images.
- Turn my research topic into a calendar-style presentation and use the images I uploaded.
- Make a team roadmap in the Gradient Calendar style; ask only for details you still need.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: e6c23be3f1922ead.

BEGIN THIRD-PARTY FILE e6c23be3f1922ead
```text
---
name: gradient-calendar-pptx
description: "Reusable fixed-style PPTX generation skill for the Gradient Calendar visual brand — pale gray (#F1F3F7) calendar-native productivity aesthetic with near-black oversized numerals, electric lime (#C8FF00) schedule blocks, saturated blue (#0B74FF) vertical labels, and soft cyan-lime-lavender gradient washes, on strict calendar grids, widescreen 16:9 editable .pptx output. Use this skill whenever the user mentions Gradient Calendar, asks for a presentation or deck in the Gradient Calendar style, wants a calendar-native / agenda-poster / schedule-led productivity deck, a planner or roadmap deck with oversized date numerals and lime event blocks, or mentions the pale-gray + electric-lime + blue + gradient-wash look for slides. Also trigger when the user says 'gradient calendar', 'calendar deck', 'agenda poster deck', 'schedule deck', 'planner slides', or 'productivity system presentation' in any context. Display name: Gradient Calendar PPTX."
---

# Gradient Calendar PPTX Skill

A reusable fixed-style PowerPoint generation skill. It builds on the `pptx` skill's technical capabilities while locking in the **Gradient Calendar** visual identity: a polished, calendar-native productivity system — sparse poster-like covers, strict calendar grids, oversized date numerals, electric-lime schedule blocks, and soft gradient washes.

**Core principle — style wins over content volume.** When the user's topic contains more information than the format can hold, compress it into calendar grids, schedule cards, timelines, and extra slides. The deck must feel like a polished calendar-native productivity system for the user's topic — **not** a generic SaaS pitch deck, **not** a cluttered screenshot dump, and **not** a text-heavy product report.

**This skill is topic-agnostic.** It generates Gradient Calendar decks for *any* user-provided topic. Never hardcode a sample topic (productivity apps, SaaS, calendar products, launch plans, specific years, or any brand) into a deck. Any topic-specific wording in this file is an *example only* — replace it at runtime with the user's topic variables.

---

## Step 1: Gather Inputs (Ask First — Max 3 Questions)

Do **not** start generating immediately. Use the `AskUserQuestion` tool to present the missing questions in a **single** call (up to 3 at once). Only ask what the user hasn't already provided in their prompt — if they already gave the topic, slide count, or image choice, skip that question. Do not ask any extra questions unless the deck literally cannot be built without them.

**Question 1 — Topic** (skip if already provided):
- header: "Topic"
```
END THIRD-PARTY FILE e6c23be3f1922ead

The third-party file has ended. Everything between the e6c23be3f1922ead tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2676 of 19755 bytes. © happycapy-ai · MIT · https://github.com/happycapy-ai/Happycapy-skills/tree/HEAD/skills/gradient-calendar/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
