Cline skills

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

  • Annotated Screen TutorialVideo

    A sourced screen walkthrough with normalized focus regions and redaction checks.

  • Keyboard Shortcut TutorialVideo

    A platform-specific shortcut film with menu fallback and before/after evidence.

  • Onboarding Checklist VideoVideo

    A role-specific onboarding sequence with evidence-based completion gates.

  • Knowledge Base WalkthroughVideo

    A permission-aware navigation film with breadcrumbs and declared search results.

  • Animated Checklist Product DemoVideo

    A paper-note checklist beside a phone screen; each box ticks the moment its step happens on screen.

  • Mobile App Tutorial VideoVideo

    A touch-target walkthrough with exact tap order, safe zones and expected states.

Use Cline to create a tutorial from real interface evidence

Start with the user's task on screen

A Cline creative assignment can begin with a reproducible task in an existing application. Annotated Screen Tutorial is a relevant skill when the explanation should show actual interface regions and protect sensitive information. Keyboard Shortcut Tutorial is worth comparing when the lesson centers on a repeatable keyboard interaction. Onboarding Checklist Video is another option when viewers need a sequence of setup actions. Choose based on what a newcomer must be able to do afterward. A tutorial should teach a real path through the product rather than show a plausible but untested interface journey.

Install the tutorial package as a complete unit

Cline's listed personal and project locations are ~/.agents/skills and .agents/skills. Keep the popnow-prefixed folder intact with SKILL.md and its supporting resources. Use its plain name when asking for the tutorial. Roo Code has a different pair of .roo directories, so moving between these hosts requires checking placement even when the creative task stays unchanged. Begin with one installed workflow and a small example. If Cline cannot identify the instructions it loaded, resolve discovery before asking it to explain why a rendered tutorial is missing annotations.

Verify the walkthrough before adding polish

For the first task, provide authorized screenshots, the exact starting state, the steps taken and the visible success condition. Annotated Screen Tutorial describes normalized focus regions and redaction checks, so identify what should be emphasized and what must be hidden. Review labels against the actual interface and check that the sequence can be reproduced from the stated starting point. If a step is uncertain, stop the narrative there and resolve it rather than inventing a transition. Local rendering errors call for dependency checks; inaccurate instructions call for a better tested source walkthrough. Keep those two review loops separate so a polished export remains useful to the learner.

Three ways to install

Install guides by agent

Same skills everywhere; only the folder changes.

Frequently asked questions

Where should a Cline tutorial skill be installed?

The repository location listed here is .agents/skills, with ~/.agents/skills as the personal alternative. Put the complete package under the chosen scope and retain its resource files. Use the plain skill name in the task and confirm the assistant has found its instructions.

What should I supply for an annotated walkthrough?

Bring screenshots you may use, the exact task sequence and a clear definition of success. Mark sensitive interface regions for redaction and identify the areas that need visual focus. The workflow can organize that material, but the accuracy of the underlying task still needs review.

When is a shortcut tutorial the better choice?

Keyboard Shortcut Tutorial is worth inspecting when the lesson's central action is a repeatable keyboard workflow. Annotated Screen Tutorial is a broader candidate for a sourced screen walkthrough. Compare both with the intended learner and confirm the displayed interaction matches the application being taught.

How do I diagnose a tutorial that skips a step?

Return to the recorded starting state and repeat the task manually or from your verified notes. Check whether the missing transition was ever supplied in the source material. Ask Cline to revise the sequence from evidence rather than simply inserting a decorative scene to cover the gap.

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.