PopNowAPI
Get API key

Gemini CLI skills for design work

Install PopNow skills in Gemini CLI. Download a skill, unzip it into the skills folder, and call it by name in your next chat.

Browse 6 skills Gemini CLI documentation
  1. 1Copy the install prompt

    Paste it into Gemini CLI. It downloads the skill with your API key and unzips it into the right folder.

  2. 2Ask for the result

    Call the skill and say what you need in plain words: the topic, the audience, the length.

  3. 3Review and refine

    Open the file it made, ask for changes in the chat, and ship when it looks right.

All skills

  • Whiteboard Animation VideoVideo

    A marker pen draws the whole lesson on one board, erases the myth, then pulls back to the finished board.

  • Article to SlidesSlides

    Turn a long article or report into a short, sourced briefing deck with discussion prompts.

  • Watercolor Concept DiagramImage

    A watercolor illustration of how something works, with fine ink lines, clean label lanes and exact callouts.

  • Narrated Explainer VideoVideo

    A 45-120 second explainer with voiceover and word-synced captions, in collage, whiteboard or data style.

  • Terminology Explainer VideoVideo

    A sourced definition with a misconception, example, counterexample and scope.

  • Sketchnote Presentation DeckSlides

    A bold black and yellow presentation with giant headlines and hand-drawn ink scenes.

Brief Gemini CLI for evidence-led explainers

Turn a source document into a visual explanation

Gemini CLI users can use a design skill to give a terminal-based assignment a clear creative structure. An effective first exercise is explaining a documented process: supply the original notes, define the audience and identify the terms that readers misunderstand. Whiteboard Animation is a catalog option for an explanatory film, while Article to Slides serves a presentation handoff. The choice depends on how the audience will consume the explanation. A meeting deck should invite discussion; a self-contained video needs a sequence that remains understandable without a presenter filling gaps.

Follow Gemini CLI's own installation locations

The agent table lists ~/.gemini/skills for personal skills and .gemini/skills for project skills. Install the package as a directory containing SKILL.md and the resources it references. Use its plain popnow-prefixed name in your request; the table does not prescribe Claude Code's slash form here. Antigravity has a related-looking personal path, ~/.gemini/antigravity/skills, but a different project path, .agents/skills. Those distinctions matter when a package appears correctly extracted yet cannot be found in the active project. Check the directory before rewriting the explanation brief.

Approve the story before rendering it

Ask Gemini CLI to map each explanatory beat to a source passage and flag missing facts. Start with a short outline, decide where a diagram is necessary, and remove decorative scenes that do not clarify the process. Watercolor Concept Diagram can be explored when a standalone conceptual illustration is a more suitable deliverable than a full film. Keep labels and definitions consistent across outputs. For troubleshooting, separate content uncertainty from execution errors: an ambiguous source needs clarification, while a missing renderer needs a local dependency check. Optional media generation should remain an explicit step with a reviewed quote, rather than an assumption hidden inside the brief.

Three ways to install

Install guides by agent

Same skills everywhere; only the folder changes.

Frequently asked questions

How do I name a skill in Gemini CLI?

Use the plain skill-name pattern listed on this page and follow it with the explanation task. Include the source document and the audience's level of familiarity. Ask the assistant to confirm the package instructions it is using before it builds an outline or starts rendering.

Is Antigravity's skills folder interchangeable with Gemini CLI's?

The listed folders differ. Gemini CLI uses .gemini/skills inside a project, whereas Antigravity uses .agents/skills. Their personal locations also differ. Preserve the same skill package if appropriate, but place it according to the assistant you are actually running rather than the similarity of their names.

What source material makes an explainer easier to review?

Provide definitions, a verified sequence of events or steps, and examples the audience can recognize. Mark unresolved questions before asking for visuals. A reviewer should be able to trace a claim in the resulting storyboard back to a document rather than infer its origin from attractive graphics.

When should I choose slides instead of animation?

Choose Article to Slides when a presenter will pause, answer questions and adjust the pace. Consider Whiteboard Animation when the sequence should play on its own. Inspect the relevant skill detail page to compare required inputs and outputs before committing to either production workflow.

Start building in minutes

One key for every model, a USD balance you top up when you need to, and an exact price before every run.

Get API key Try in Playground