Warp skills
Install PopNow skills in Warp. Download a skill, unzip it into the skills folder, and call it by name in your next chat.
- Where skills go
For every project
~/.agents/skillsFor this project only
.agents/skills - How to call a skill
Mention the skill by name, or just describe the job and let Warp 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 Warp. 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
- Service Status DashboardWeb
Publish an honest service snapshot with stale checks, component health and incident history.
- Incident Postmortem VideoVideo
A blameless incident narrative with impact, evidence and owned follow-ups.
- Capacity Planning VideoVideo
A demand-versus-capacity film with utilization and bottleneck calculations.
- Operations Dashboard KitWeb
Triage work by priority, owner and overdue status, with clear state transitions and an exportable queue.
- Meeting Agenda VideoVideo
A timeboxed meeting brief with owners, decisions and an overflow check.
- Project Retrospective PresentationSlides
Editable project retrospective presentation with checked inputs, evidence and speaker notes.
Keep a Warp status-report workflow grounded in timestamps
Start from an operational snapshot
A Warp skill assignment can turn a bounded set of operational records into a clear report. Service Status Dashboard is a useful candidate for component health and incident history. Incident Postmortem Video offers a guided narrative after an event, and Capacity Planning Video is another option when the discussion concerns future resource needs. These outputs answer different questions: current state, explanation of a past event and planning under assumptions. Choose one review question first. Do not let the visual format blur the distinction between an observed condition and a proposed future scenario.
Use the listed shared-directory convention
The personal skills location for Warp is ~/.agents/skills and the project location is .agents/skills. Preserve the whole popnow-prefixed folder so SKILL.md and supporting resources remain together, then use the plain skill name in your request. Zed shares those locations in the PopNow table. That makes the directory convention familiar, but the current task should still identify which package is being used. When a workflow cannot be found, verify the active project and extraction structure before changing commands or assuming an operational data problem.
Make freshness part of the artifact
For a first Warp status page, supply service identifiers, check times, statuses and incident updates with timezone-aware timestamps. Service Status Dashboard's documented input includes an as-of time and stale threshold, so explain how the report should communicate outdated evidence. For a postmortem, keep event order and follow-up ownership traceable to records. Review the output as a snapshot and avoid implying ongoing monitoring unless another system provides it. If values are wrong, inspect the source data and transformation rules. If the task fails before rendering, check its local dependencies. Separating those checks helps preserve an honest operational story while the presentation is refined.
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
What should a Warp status-page request include?
Provide the service list, observed states, check timestamps and incident updates. State the point in time the snapshot represents and when records should be considered stale. The chosen workflow can present that evidence, but it cannot make an outdated dataset current by changing the design.
Where should the skill package be placed for Warp?
Use the listed .agents/skills repository folder or ~/.agents/skills personal folder. Keep the package resources beside SKILL.md and use the plain popnow-prefixed name in the request. Confirm the active project before diagnosing an absent workflow, especially if the same directory convention is used elsewhere.
How does a postmortem video differ from a status page?
Incident Postmortem Video is a narrative format for impact, evidence and follow-ups after an event. Service Status Dashboard presents a snapshot of component health and incidents. Compare the audience's question and source records before selecting one; a historical explanation should not masquerade as a live status feed.
When is a capacity-planning video appropriate?
Inspect Capacity Planning Video when the audience needs to understand a planning scenario and you can supply the assumptions behind it. Keep forecasts distinct from observed measurements. Review the proposed story against source material before spending effort on motion polish or optional generated 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.