Devin skills

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

  • Searchable Records TableWeb

    Turn a flat CSV into a searchable, sortable table with pagination and safe filtered export.

  • Editable Budget GridWeb

    Edit quantities and unit costs, track actual spending and export a reconciled budget.

  • Operations Dashboard KitWeb

    Triage work by priority, owner and overdue status, with clear state transitions and an exportable queue.

  • KPI Dashboard TemplateWeb

    Four KPI tiles with change chips over a glowing line chart, a breakdown table and target bars on warm paper.

  • Cashflow DashboardWeb

    Reconcile opening cash, signed transactions and closing balance with a traceable running ledger.

  • Financial Report PortalWeb

    A financial report directory with year and type filters, source-linked metric comparisons and explicit missing-data handling.

Define a Devin handoff around a bounded interface task

Choose a small internal-tool artifact

A Devin skill assignment can focus on one reviewable interface rather than an undefined application. Searchable Records Table is a candidate when the user needs to find and inspect rows. Editable Budget Grid offers a different catalog direction for working with structured amounts, while Operations Dashboard Kit is worth inspecting for a broader operational overview. Select the initial artifact from a specific user action. A table, editable grid and dashboard are different interaction patterns; combining them before understanding the data can make the handoff harder to review and integrate.

Verify the CLI-oriented installation record

PopNow lists ~/.config/devin/skills for personal skills and .devin/skills for project skills, with a plain-name invocation pattern and a CLI documentation link. Preserve the complete popnow-prefixed package so SKILL.md can find its supporting files. This page does not prescribe a separate import command for other environments. OpenHands uses .openhands/skills for project scope, so moving a package between those assistants calls for checking the destination explicitly. Confirm the active environment can read the package before asking it to build the tool from the brief.

Describe interaction and data together

For a first Devin interface task, provide a small representative dataset, field definitions and the action the user should take. Explain which values can change, what should be read-only and how missing information should appear. Request a small working artifact and review it with normal, empty and invalid input before expanding its scope. Identify integration requirements separately from the generated design so the next developer knows what remains to connect. If a task stalls, distinguish missing dependencies from an ambiguous data model. If the result looks complete but behaves poorly, review the interaction contract instead of adding more visual decoration or more sample rows.

Three ways to install

Install guides by agent

Same skills everywhere; only the folder changes.

Frequently asked questions

Do these Devin instructions describe every possible environment?

The locations recorded here accompany the CLI documentation link in PopNow's agent table. They do not establish an additional import process for every environment. Check the documentation for your setup, retain the package resources, and confirm the assistant can read the intended SKILL.md before executing the task.

What should I provide for a records-table brief?

Supply representative rows, field meanings, the reader's task and any constraints on what may be displayed. Explain empty and unavailable states. Searchable Records Table is worth inspecting when finding records is central, but the brief still needs a clear interaction and data contract.

When is an editable grid a better starting point?

Inspect Editable Budget Grid when changing structured amounts is part of the intended task. A read-oriented records table serves a different purpose. Describe which values may change and how they should be checked, then review the artifact with representative input before expanding the interface.

What should the handoff say about application integration?

Identify the generated artifact, its source data assumptions and any behavior that still needs connection to the real application. Ask Devin to distinguish demonstrated interactions from production integration. This makes the result easier for another developer to review without inferring capabilities from its finished appearance.

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.