Roo Code skills
Install PopNow skills in Roo Code. Download a skill, unzip it into the skills folder, and call it by name in your next chat.
- Where skills go
For every project
~/.roo/skillsFor this project only
.roo/skills - How to call a skill
Mention the skill by name, or just describe the job and let Roo Code pick it.
popnow-<skill> - Connect PopNow
Skills are free. To generate images, video or sound, set your PopNow API key in POPNOW_API_KEY. Calls using this key draw from your separate API balance in USD. Each paid generation is quoted first and waits for your approval.
POPNOW_API_KEY
- 1Copy the install prompt
Paste it into Roo Code. It downloads the skill with your API key and unzips it into the right folder.
- 2Ask for the result
Call the skill and say what you need in plain words: the topic, the audience, the length.
- 3Review and refine
Open the file it made, ask for changes in the chat, and ship when it looks right.
All skills
- Changelog Explainer VideoVideo
Turn a real pull request into a 30-second film for people who will never read the diff.
- Feature Comparison VideoVideo
A dated feature matrix with evidence, unknown states and audience tradeoffs.
- Before-and-After Comparison Launch VideoVideo
Near-black canvas, mono file names, one electric accent: your content as a still page, then as a film.
- Complaint-to-Feature Launch VideoVideo
Open on the complaint your users keep posting, then prove the new feature makes it false.
- Roadmap Update VideoVideo
A change-focused roadmap with dependencies and confidence labels.
- Product Demo PresentationSlides
Editable product demo presentation with checked inputs, evidence and speaker notes.
Turn a completed change into a Roo Code release story
Choose the release format from the audience
A Roo Code skill request can help explain a shipped change without burying the reader in implementation details. Changelog Video is a catalog option for communicating an update. Feature Comparison Video is worth reviewing when the audience needs to understand a distinction between capabilities, and Before and After Comparison Video serves a visible change in state. These formats need different evidence. A change log needs confirmed changes, a comparison needs fair criteria, and a before-and-after sequence needs representative source material. Start with the viewer's question rather than selecting the most dramatic transition.
Use Roo Code's own skills scope
PopNow lists ~/.roo/skills for a personal collection and .roo/skills for the project location. Extract the full skill folder with SKILL.md and supporting files, then name the skill plainly in the request. Cline's listed locations use .agents/skills instead. That comparison is helpful for a developer switching between tools on the same repository: shared source code does not guarantee shared instruction discovery. Ask Roo Code to identify the selected package before it plans the release story, especially when more than one related comparison skill has been installed.
Make the comparison honest and reproducible
For a first release video, provide the approved change list, representative screenshots and any limitations that users need to understand. Describe the previous and current state using the same conditions so the comparison remains meaningful. Ask for a short outline with each claim mapped to evidence. Review small labels and timing before approving optional generated media or sound. If the result feels exaggerated, remove unsupported conclusions and tighten the comparison criteria. If the project fails to render, inspect its local requirements independently of the copy. A successful export is a delivery milestone, while a fair explanation still depends on the underlying facts.
Three ways to install
- Ask your agent
Copy a skill's install prompt into your agent. It reads the install guide, downloads the package with your key and unzips it into the right folder.
https://popnow.ai/api/skills/install.md - Use the CLI
popnow skills finds and installs skills from your terminal.
npm install -g @popnow/cli && popnow skills - Over MCP
With the developer MCP connected, ask for a style: find_skills suggests packages and install_skill hands over the playbook and the install commands.
find_skills → install_skill - Generation uses your API key
Skills are free. The images, video, music and voice they make through PopNow are charged in USD to the API balance behind POPNOW_API_KEY, after a quote you approve.
POPNOW_API_KEY
Install guides by agent
Same skills everywhere; only the folder changes.
Frequently asked questions
How do I request a release workflow in Roo Code?
Use the plain installed skill name, such as popnow-changelog-video, and provide the approved release material. State the audience and the behavior that changed. Ask the assistant to confirm the package instructions so a general request for a video does not drift into an unrelated format.
What is the difference between the comparison options?
Feature Comparison Video is worth inspecting for a comparison organized around capabilities. Before and After Comparison Video is worth inspecting for a visible change between states. The source evidence and comparison criteria should determine the selection, rather than using whichever title sounds more persuasive.
Can I reuse a Cline installation unchanged?
The listed project directories differ: Roo Code uses .roo/skills, while Cline uses .agents/skills. Keep the package contents together, but follow the folder guidance for the host you are using. Confirm discovery again before attributing a missing workflow to the creative brief.
How can I avoid an overstated before-and-after story?
Use comparable source material and describe the conditions under which each result was obtained. Include relevant limitations and avoid presenting an exceptional example as universal. Review the storyboard against the release evidence before investing in final motion, sound or additional illustrative assets.
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.