Install the "apricot-ritual-pptx" agent skill from https://github.com/happycapy-ai/Happycapy-skills/tree/main/skills/apricot-ritual into .claude/skills/apricot-ritual-pptx/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apricot-ritual-pptx", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add happycapy-ai/Happycapy-skills --skill apricot-ritual-pptx -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "apricot-ritual-pptx" agent skill from https://github.com/happycapy-ai/Happycapy-skills/tree/main/skills/apricot-ritual into .agents/skills/apricot-ritual-pptx/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apricot-ritual-pptx", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add happycapy-ai/Happycapy-skills --skill apricot-ritual-pptx -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "apricot-ritual-pptx" agent skill from https://github.com/happycapy-ai/Happycapy-skills/tree/main/skills/apricot-ritual into .cursor/skills/apricot-ritual-pptx/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apricot-ritual-pptx", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add happycapy-ai/Happycapy-skills --skill apricot-ritual-pptx -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "apricot-ritual-pptx" agent skill from https://github.com/happycapy-ai/Happycapy-skills/tree/main/skills/apricot-ritual into .gemini/skills/apricot-ritual-pptx/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apricot-ritual-pptx", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add happycapy-ai/Happycapy-skills --skill apricot-ritual-pptx -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "apricot-ritual-pptx" agent skill from https://github.com/happycapy-ai/Happycapy-skills/tree/main/skills/apricot-ritual into .github/skills/apricot-ritual-pptx/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apricot-ritual-pptx", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add happycapy-ai/Happycapy-skills --skill apricot-ritual-pptx -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "apricot-ritual-pptx" agent skill from https://github.com/happycapy-ai/Happycapy-skills/tree/main/skills/apricot-ritual into .opencode/skills/apricot-ritual-pptx/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apricot-ritual-pptx", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
apricot-ritual-pptx
GitHub stars
137
Token cost
~4.2k tokens
SKILL.md length
1,532 words
Files
2
Skills in repo
28
Repo updated
First seen
Licence
MIT
At a glance
Reusable fixed-style PPTX generation skill for the Apricot Ritual Index visual brand — warm apricot background (FDDEB6), cocoa-brown typography (6C4832), refined minimalist editorial poster…
Works in 6 steps: Gather Inputs (Ask First — Max 3… → Translate the Topic into Apricot Ritual… → Generate Images (if requested) → …
The user mentions Apricot Ritual Index
SKILL.md covers Step 1: Gather Inputs (Ask…, Step 2: Translate the Topic…, Step 3: Generate Images (if… and Step 4: Build the PPTX, plus 6 more sections
Calls python and pdftoppm
What it does
Apricot Ritual PPTX is an agent skill from happycapy-ai/Happycapy-skills. Reusable fixed-style PPTX generation skill for the Apricot Ritual Index visual brand — warm apricot background (FDDEB6), cocoa-brown typography (6C4832), refined minimalist editorial poster aesthetic, elegant serif titles, narrow-sans labels, centered word stacks, thin horizontal rules, sparse image placement, widescreen 16:9 editable .pptx output. Use this skill whenever the user mentions Apricot Ritual Index, asks for a warm apricot minimalist presentation, wants a refined product-poster or ritual-index style…
Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
It sits in Documents & Office, covering PowerPoint presentations, Slides and decks and Typography. It works with Microsoft PowerPoint. The repository describes itself as: A curated collection of high-quality Claude Code skills to enhance your development workflow. The licence is MIT.
When your agent uses it
The user mentions Apricot Ritual Index
Asks for a warm apricot minimalist presentation
Wants a refined product-poster
Ritual-index style deck
Example prompts
“apricot ritual”
“ritual index deck”
“apricot minimalist slides”
“/apricot-ritual-pptx”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 9ff72fe. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python
pdftoppm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Apricot Ritual PPTX loads about 4.2k tokens when it runs. Until then it costs about 218 tokens; SKILL.md has 1,532 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~218
When it runs· the whole SKILL.md, loaded when a task matches
~4.2k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/apricot-ritual-pptx/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
apricot-ritual-pptx
description
Reusable fixed-style PPTX generation skill for the Apricot Ritual Index visual brand — warm apricot background (#FDDEB6), cocoa-brown typography (#6C4832), refined minimalist editorial poster aesthetic, elegant serif titles, narrow-sans labels, centered word stacks, thin horizontal rules, sparse image placement, widescreen 16:9 editable .pptx output. Use this skill whenever the user mentions Apricot Ritual Index, asks for a warm apricot minimalist presentation, wants a refined product-poster or ritual-index style deck, or requests a presentation using the Apricot Ritual Index visual system. Also trigger when the user says 'apricot ritual', 'ritual index deck', 'apricot minimalist slides', 'product poster presentation', 'ritual index pptx', 'editorial poster deck', 'typographic poster presentation', or 'warm apricot slides' in any context.
Apricot Ritual Index PPTX Skill
A reusable fixed-style PowerPoint generation skill. It builds on the pptx skill's technical capabilities while locking in the Apricot Ritual Index visual identity: calm, editorial, typographic, premium, sparse — like a refined product introduction combined with a typographic brand-poster system.
Core principle — style fidelity over content volume. When the user's topic contains more information than the poster format can hold, compress and reinterpret. The deck must feel calm, premium, and intentional — not a generic report template, not a text-heavy catalog, not a business slide deck. Every slide is an editorial poster plate.
Step 1: Gather Inputs (Ask First — Max 3 Questions)
Do not start generating immediately. Use the AskUserQuestion tool to present all questions in a single call. Only ask about what the user hasn't already provided.
Question 1 — Topic (skip if already provided):
header: "Topic"
question: "What is the presentation topic or title?"
options: 2–3 relevant examples plus allow Other
Question 2 — Slide count (skip if already specified):
header: "Slides"
question: "How many slides should the deck include? (9 recommended)"
Generate with gpt-image-2 — AI creates warm apricot editorial imagery
Combine both — Mix uploaded and AI-generated images
Infer the audience, narrative structure, section labels, and supporting details from the topic and available context. Do not ask additional questions unless essential information is missing and the presentation cannot be completed without it.
Once you have the three answers, proceed directly to generation.
Step 2: Translate the Topic into Apricot Ritual Index Language
Before writing any slide copy, translate the user's topic into the Apricot Ritual Index frame. The visual language originates in premium product introductions and ritual sequences, but it works for any subject — every topic can be reinterpreted as principles, components, stages, layers, chapters, rituals, index entries, sequences, or key objects/concepts.
User provides
Apricot Ritual Index treatment
Product or brand
Ritual introduction — ingredients, sequences, layers, collection index
Reframe as a refined index, ritual sequence, or brand poster series
Decide the poster title, the one-line premise, and the index or sequence structure before writing any slides. These anchor the cover and define the visual rhythm of the whole deck.
Preserve factual accuracy and the user's intended meaning. Do not invent product claims, brand names, statistics, people, or factual details.
Step 3: Generate Images (if requested)
Read the generate-image skill at /home/node/.claude/skills/generate-image/SKILL.md for the exact API call pattern. Use openai/gpt-image-2 with response_format: "b64_json".
How many images to generate
9-slide deck → 4–5 images
12–15 slide deck → 5–6 images
6 slides → 3–4 images
Cover image rule
The cover must contain one strong topic-relevant image as its primary visual. Generate or use an uploaded image for the cover first, before building the rest of the deck.
Apricot Ritual Index image prompt formula
Generated images are minimal premium editorial assets — not slide screenshots and never images with embedded text.
Base formula:
Minimal premium editorial still-life photograph. [Scene descriptor: matte ceramic container / abstract organic form / textured surface detail / sparse ingredient arrangement / clean studio object / polished artifact]. Warm apricot (#FDDEB6) surface, soft cocoa-brown (#6C4832) shadow accents, subtle beige highlights, clean studio lighting, sparse high-end composition, adequate negative space. No readable text, no logos, no brand marks, no watermarks, no people, no hands, no busy environments. Clearly visible primary silhouette. Warm tonal palette, calm and restrained.
For non-product topics, adapt the scene to abstracted forms relevant to the user's subject:
Minimal premium editorial still-life. [Abstract form relevant to topic: layered paper / architectural model fragment / scientific instrument / tool arrangement / geometric object]. Warm apricot surface, cocoa-brown accents. Same lighting and composition rules as above.
Save each image to /tmp/apricot-ritual-img-N.png.
Step 4: Build the PPTX
Read the pptx skill at /home/node/.claude/skills/pptx/SKILL.md and its pptxgenjs.md reference for the full API. Build using PptxGenJS.
If Georgia is unavailable, substitute Palatino Linotype or Times New Roman.
Layout — LAYOUT_16x9 always (10" × 5.625")
All slides use LAYOUT_16x9. Background is APRICOT on every slide. The cocoa-brown color applies to all text, rules, and dividers. Beige is used sparingly for depth or image integration only.
Typography sizing
Role
Font
Size
Color
Cover hero title
SERIF
72–120pt
COCOA
Slide headline / category word
SERIF
40–68pt
COCOA
Supporting statement
SERIF or SANS
22–30pt
COCOA
Index entries / step labels
SANS
16–20pt
COCOA
Small metadata / captions
SANS
12–16pt
COCOA
Typography must remain spacious and restrained. Never shrink text aggressively to fit excess copy — reduce the copy instead.
Apricot Ritual Index Visual System Rules
The most common failure mode is a text-heavy report placed on an apricot background. These rules prevent that.
Rule 1: Style fidelity over content volume
The poster system takes priority over including every detail. Summarise. Compress. Choose the one most important idea for each slide and let everything else recede. A calm empty apricot field is a design choice, not a mistake.
Rule 2: One idea per slide. Under 30 words.
Count visible words before finalising each slide. Most slides must be under 30 words total — title, body, labels, metadata combined. Body copy should be one short statement, a compact label sequence, or a brief step name. No paragraphs, no dense bullet lists.
Wrong: "This section explores the fundamental principles underlying our approach to sustainable product design, focusing on material selection, lifecycle analysis, and end-user experience throughout the development process."
Right:
MATERIAL
HONESTY
Sourced with intention.
Designed to last.
Rule 3: Varied layouts within the same system
The Apricot Ritual Index style uses multiple layout types — centered poster, typographic index, image plate, split composition — but all within the same apricot/cocoa palette and serif/sans hierarchy. Vary the layout across slides so the deck feels composed, not repetitive.
Layout vocabulary:
Centered title plate: Large SERIF title centered, thin COCOA rule above/below, sparse SANS metadata
Typographic index: Numbered or labeled entries, SANS compact rows, thin rules between groups
Image plate: One dominant image, single SANS caption, generous negative space
Split composition: Left text field (SERIF headline + SANS detail), right image panel
Category word: One oversized SERIF word centered, thin rule, 1–2 compact SANS lines
Closing poster: Full APRICOT field, large centered SERIF statement, SANS credit/date
Show full SKILL.md (563 more words)Show less
Rule 4: Thin rules as section dividers only
Thin horizontal COCOA rules (LINE shapes, h: 0, line.width: 1–1.5pt) may separate typographic sections. They must sit in clean whitespace — never passing through or touching any text box, image, or caption. Before adding a rule, verify there is at least 0.3" of clear space above and below it.
Rule 5: Safe layout zones — no collisions
Before placing elements, define these non-overlapping zones:
TITLE ZONE: y: 0.7"–2.4", adequate left/right margin
SUPPORTING-TEXT ZONE: at least 0.35" below title bottom edge
IMAGE ZONE: defined rectangle — text must never enter it
DIVIDER ZONE: dedicated whitespace only — never within 0.3" of any text
CAPTION/METADATA ZONE: y: 4.8"–5.3" bottom strip, or compact block near image
FOOTER ZONE: y: ~5.2"–5.5", minimal SANS credit if needed
Rule 6: Images as editorial plates, never backgrounds
Images sit in clean rectangular windows or cover one half of the slide. They must not float over text or have text placed across them (except for a compact caption in a separate APRICOT block). Full-bleed images should have minimal text — maximum 10 words — placed in a calm area with adequate contrast.
Suggested Slide Structure
Use this when the user provides no outline. Adapt freely when they do.
#
Slide type
Words target
Layout
1
Cover — topic title + poster image
≤ 15
Large SERIF title + image, centered or split
2
Central premise or thesis
≤ 20
Centered title plate or category word
3
Overview or index
≤ 30
Typographic index — labeled rows
4
Key component or concept A
≤ 25
Split or image plate
5
Key component or concept B
≤ 25
Split or image plate
6
Focus detail or focal sequence
≤ 25
Category word + thin rule + compact detail
7
Process, ritual, or ordered sequence
≤ 30
Step-based composition, numbered SANS rows
8
Summary or collection view
≤ 25
Centered plate or compact index
9
Closing poster
≤ 15
Full APRICOT field, large centered SERIF statement
Layout Patterns
Cover (poster image + centered title)
Background: APRICOT full slide
Optional: image panel (right half or upper portion)
Image: clean editorial still-life, x:5.5, y:0, w:4.5, h:5.625 (right half)
— OR —
Image: centered plate, x:3.5, y:0.8, w:3, h:3 (centered upper block)
Left/lower field:
Small SANS category tag, 13pt, COCOA, uppercase, y: 0.5", x: 0.6"
Hero SERIF title (stacked), 80–110pt, COCOA, y: 1.2"–2.8"
Thin COCOA rule (LINE), w: 3", y: below title + 0.4" gap
SANS metadata, 13pt, COCOA, near bottom
Use a subagent for visual inspection with this prompt:
Visually inspect these Apricot Ritual Index slides. Assume there are issues — find them.
Look for:
- Any rule, line, or divider crossing or touching title text, body text, captions, labels, step numbers, or images
- Text overflow or clipping at box boundaries or slide edges
- Images that are distorted, stretched, or badly cropped
- Text colliding with image edges
- Agenda rows or metadata blocks overlapping titles
- Slides with more than 30 words total
- Slides lacking a clear dominant headline
- Low-contrast text (e.g., cream or light text on apricot background — all text should be cocoa-brown)
- Any slide that feels like a generic report or webinar deck rather than a calm editorial poster
- Inconsistent use of serif (titles) vs narrow-sans (labels/metadata)
For each slide, list issues. Report ALL issues, including minor ones.
Images:
1. /path/to/slide-01.jpg
2. /path/to/slide-02.jpg ...
Ritual Index QA checklist — check every slide
Under 30 words on most slides (count them)
No rule, line, or divider passes through or touches any text
No text collides with images or image edges
No content exceeds slide boundaries
Title/headline is clearly the dominant element
Body is compact — editorial language, not paragraphs
Serif font for titles/category words, narrow-sans for labels/metadata
Apricot (#FDDEB6) background on all slides
Cocoa-brown (#6C4832) on all text, rules, and dividers
Varied layouts across slides — not every slide identical
Cover has one strong poster image
Generated images contain no embedded text, logos, or marks
Deck feels calm, premium, sparse, and intentional
If any slide fails: fix, re-render, verify. If fixing requires removing copy, remove the copy. Deliver only after a clean pass.
Step 6: Deliver
Save to ./outputs/[topic-slug].pptx. Confirm: slide count, image approach, QA passed.
Do not show internal labels — no skill instructions, no source filenames, no implementation notes, no QA checklist text — on any visible slide.
Apricot Ritual PPTX next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Apricot Ritual PPTX compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Apricot Ritual PPTX this skillhappycapy-ai/Happycapy-skills
Create or redesign PowerPoint decks in a high-end Japanese hand-drawn editorial style: warm off-white paper texture, delicate pencil or ink line illustration, thin uneven strokes, mostly monochrome…
Rebuild slide images, scanned or image-based PPT/PPTX files, and PDF decks into object-level editable PowerPoint (.pptx), preserving speaker notes when supplied.
Reusable fixed-style PPTX generation skill for the Apricot Ritual Index visual brand — warm apricot background (FDDEB6), cocoa-brown typography (6C4832), refined minimalist editorial poster…. Apricot Ritual PPTX is an agent skill from happycapy-ai/Happycapy-skills.pptx output.
When should I use Apricot Ritual PPTX?
Apricot Ritual PPTX fits situations like: the user mentions Apricot Ritual Index; asks for a warm apricot minimalist presentation; wants a refined product-poster; ritual-index style deck.
How do I install Apricot Ritual PPTX in Claude Code?
Run `npx skills add happycapy-ai/Happycapy-skills --skill apricot-ritual-pptx -a claude-code`. Or copy the skill folder (skills/apricot-ritual in happycapy-ai/Happycapy-skills) into .claude/skills/apricot-ritual-pptx in your project. Claude Code loads it when a task matches its description.
How do I install Apricot Ritual PPTX in Codex?
Run `npx skills add happycapy-ai/Happycapy-skills --skill apricot-ritual-pptx -a codex`. Or copy the skill folder (skills/apricot-ritual in happycapy-ai/Happycapy-skills) into .agents/skills/apricot-ritual-pptx in your project. Codex loads it when a task matches its description.
Can I use Apricot Ritual PPTX in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add happycapy-ai/Happycapy-skills --skill apricot-ritual-pptx -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/apricot-ritual-pptx, .gemini/skills/apricot-ritual-pptx, .github/skills/apricot-ritual-pptx and .opencode/skills/apricot-ritual-pptx in your project.
What does Apricot Ritual PPTX need to run?
Going by SKILL.md and its folder, Apricot Ritual PPTX needs the command-line tools its instructions call (python and pdftoppm).
Does Apricot Ritual PPTX access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Apricot Ritual PPTX safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Apricot Ritual PPTX use?
Apricot Ritual PPTX is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Apricot Ritual PPTX use?
About 4.2k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Apricot Ritual PPTX?
Skills that share tags, products or a category with Apricot Ritual PPTX: Futuristic Tech Editorial Ppt Skill (software-ai-life/Awesome-PPT-Design-Skills, 120 stars), Japanese Hand Drawn Editorial Ppt Skill (software-ai-life/Awesome-PPT-Design-Skills, 120 stars), Minimalist Luxury Branding Ppt Skill (software-ai-life/Awesome-PPT-Design-Skills, 120 stars) and Ppt Orchestra Skill (haojing8312/WorkClaw, 141 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Apricot Ritual PPTX?
happycapy-ai (a GitHub user) maintains it in happycapy-ai/Happycapy-skills, which has 137 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on September 3, 2026.
Source: happycapy-ai/Happycapy-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.