Qwen Code skills

Install PopNow skills in Qwen 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 Qwen 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

  • Swimlane Process VideoVideo

    An actor-by-actor handoff film with waiting time and ownership checks.

  • Interactive Architecture DiagramWeb

    An offline, clickable system diagram built from a checked JSON model, with the evidence behind each box.

  • Supply Chain ExplainerVideo

    A material-flow film with lead time, yield and exception notes.

  • Process Cycle AnimationVideo

    A closed operating cycle with owners, handoff criteria and a failure exit.

  • Org Chart AnimationVideo

    A validated reporting tree with role scope and vacant positions clearly marked.

  • Mind Map AnimationVideo

    A verified concept tree with bounded depth and explicit relationship labels.

Explain a process clearly with Qwen Code

Choose the right level of process detail

Qwen Code users can use a skill to turn an operational process into a visual explanation that a reader can follow. Swimlane Process Video is worth inspecting when responsibilities move between groups. Supply Chain Explainer offers a related narrative direction for a chain of activities, while Interactive Architecture Diagram serves a navigable web artifact. The choice is about the explanation's structure: a film guides a viewer through a sequence, whereas an interactive diagram lets a reader inspect relationships. Select the format after identifying where the current documentation leaves people confused.

Keep the Qwen skills path distinct

The personal location listed for Qwen Code is ~/.qwen/skills and the project location is .qwen/skills. Install the complete popnow-prefixed directory, including SKILL.md and any supporting scripts or references. Request the workflow by its plain skill name. Gemini CLI's folders instead use .gemini, even though its listed invocation also uses the plain-name pattern. When moving an explanation task between those assistants, compare the destination paths as well as the brief. Correctly naming the package in a conversation does not compensate for putting it in another host's project folder.

Review responsibility, sequence and exceptions

For a first Qwen Code assignment, describe the process start and end, the actors involved, the handoffs and the cases that do not follow the normal route. Ask for a source-backed outline before choosing animation details. Keep a diagram's connections meaningful and label whether they indicate sequence, dependency or information flow. Review a small example with someone who understands the process before expanding it. If the artifact oversimplifies exceptions, improve the source brief. If rendering cannot begin, inspect the package requirements and local files. A workflow should make the process easier to understand without silently converting uncertain relationships into authoritative-looking arrows.

Three ways to install

Install guides by agent

Same skills everywhere; only the folder changes.

Frequently asked questions

How do I call a process skill in Qwen Code?

Use the plain popnow-prefixed name shown in the installation pattern and follow it with the process brief. Include the source material, reader and intended output. Ask Qwen Code to confirm the instructions it found before it plans scenes or builds an interactive artifact.

Should I use swimlanes or an architecture diagram?

Swimlane Process Video is a useful candidate when responsibilities and handoffs shape the story. Interactive Architecture Diagram is a candidate when readers need to explore relationships. Compare their examples with the audience's question and the evidence you can provide, rather than choosing solely by visual style.

What information should a process brief include?

Define the starting event, completion condition, actors, normal transitions and important exceptions. Explain what each connection means. The assistant needs those distinctions to avoid drawing a sequence that looks plausible but misrepresents ownership or the conditions under which the process changes direction.

Why might a supply-chain explanation feel incomplete?

The brief may omit delays, dependencies or exception paths that matter to the audience. Supply Chain Explainer can provide a visual workflow, but it cannot verify missing operational facts. Review the outline with a knowledgeable stakeholder and resolve gaps before polishing the animation.

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.