Kimi Code skills

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

  1. 1Copy the install prompt

    Paste it into Kimi Code. 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

  • Research Paper PresentationSlides

    Figure-first pages on warm paper, forest-green ink, amber section tabs and a source line under every chart.

  • Data Storytelling PresentationSlides

    Editable data storytelling presentation with checked inputs, evidence and speaker notes.

  • Research Graphical AbstractImage

    Turn a research brief into editable question–method–result artwork with source-linked measurements.

  • Research Presentation SlidesSlides

    Projection-ready research talk slides with one message per frame, equations, results and speaker notes.

  • Thesis Defense SlidesSlides

    Defense slides with claim titles, each result beside its limits, and backup pages for questions.

  • Experiment Comparison ChartWeb

    Compare conversion variants with sample sizes, percentage-point lift and honest uncertainty intervals.

Make Kimi Code presentation work traceable to the source

Choose a presentation by the decision it supports

A Kimi Code skill request can turn research notes into a reviewable presentation when the audience and evidence are explicit. Research Paper Presentation is a catalog choice for a research-centered talk. Data Storytelling Deck is useful to compare when a numerical narrative drives the discussion. Research Graphical Abstract offers a separate image-oriented route for communicating the central idea visually. Decide whether the reader needs a full argument, a chart-led story or a compact graphical explanation. An appealing illustration should support the source material rather than stand in for the evidence behind it.

Shared directories do not imply shared invocation

Kimi Code's listed locations are ~/.agents/skills for personal use and .agents/skills for a repository. Preserve the downloaded popnow-prefixed directory, with SKILL.md and supporting assets together. Use the plain skill name in the request, followed by the task and relevant files. Codex shares those directory locations in PopNow's table, but its invocation pattern begins with a dollar sign. This comparison matters when passing a brief between assistants: the package location may be familiar while the way you explicitly name it changes. Confirm the active package rather than relying on a copied command.

Build the argument before the visual system

For a first Kimi Code research task, supply the original paper or notes, identify claims that are settled, and list limitations that must remain visible. Ask for a slide outline with source references before making the deck. Keep chart units and denominators consistent, and distinguish observations from interpretation. Review the result with the intended speaking time and audience knowledge in mind. If rendering stops, consult the package's local requirements; if the narrative overstates a finding, revise the evidence mapping. Re-running generation without that distinction can reproduce the same misleading conclusion in a more polished form.

Three ways to install

Install guides by agent

Same skills everywhere; only the folder changes.

Frequently asked questions

Can I reuse my Codex skills directory with Kimi Code?

The directory names recorded for both agents are ~/.agents/skills and .agents/skills. Check the actual package and active project before relying on it. The listed invocation patterns differ: Kimi Code uses a plain skill name, while Codex uses a dollar-prefixed form.

What should I include in a research presentation brief?

Supply the source paper, intended audience, central question and limitations. Identify which figures may be reused and which claims need careful qualification. Ask for an outline that traces the argument back to the material before investing effort in visual styling or additional illustration.

When should I use a graphical abstract instead of a deck?

Research Graphical Abstract is worth inspecting when the main task is a compact visual account of the research idea. A full presentation is better suited to explaining methods, evidence and limitations over several stages. Choose based on the communication setting and inspect the package outputs first.

How do I review a chart-led presentation?

Compare every displayed value, unit and label with the supplied dataset. Check that the narrative does not confuse correlation with an established mechanism. Data Storytelling Deck can structure a numerical explanation, but the underlying source checks still belong in the review of the finished artifact.

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.