---
name: powerlevelup
version: 0.8.0
description: Create, revise, or save Powerlevel Up flashcards from a learner's material; connect agent access; manage cards or review through the agent API; handle requested product feedback.
homepage: https://powerlevelup.com
---

# Powerlevel Up

Turn the user's material into source-grounded practice with minimal setup.

## Create or revise cards

1. Read the supplied material. A source path or identifiable topic is enough to begin. For revisions, read the existing draft first; use [api-workflow.md](api-workflow.md) to fetch cards already in the app.
2. Infer the goal and prerequisites, honoring supplied preferences. Choose the formats yourself: clear recall and useful application by default, cloze or MCQ where they fit. For open-ended requests, start with roughly 8–12 high-value cards; this is a guide, not a quota. Honor an explicit scope or count.
3. Briefly state the coverage and proceed with [card-generation.md](card-generation.md). Finish when every card has been checked against the source and task, structural errors are resolved, and advisory warnings have been judged for learning value. Preserve unaffected cards during revisions.
4. For a local draft, return the file or chat draft with its count, coverage, meaningful omissions, and validation status. When the user asks to save to Powerlevel Up, follow [api-workflow.md](api-workflow.md) through the submission result. If saving is blocked, preserve the draft and report the blocker.

Ask only when missing information would materially change the result and cannot reasonably be inferred. Proceed with reasonable defaults without a separate intake or plan-approval step. If the source cannot support the central requested outcome, identify the gap and request the missing source or direction; distinguish useful supported work from completion of that outcome.

## Access and privacy

A request to save cards authorizes submission. The user approves agent access in the app and accepts new batches in its inbox before study. Local source reading, planning, drafting, and validation need no grant. API validation creates no cards but sends the draft to Powerlevel Up; a local-only draft stays local.

Keep bearer tokens, poll secrets, cookies, and credential-file contents private. Send credentials only to the Powerlevel Up app API or an explicitly configured local development API. Use the app's approval flow; never request the user's password or browser session. Use redacted sources instead of credentials or highly sensitive personal records.

## Other tasks and references

Read only the relevant branch:

- [api-workflow.md](api-workflow.md): connect access, save cards, inspect or manage the collection, or conduct requested conversational review.
- [document-to-srs.md](document-to-srs.md): difficult source acquisition, equations, or long-source mapping.
- [card_quality.md](card_quality.md): ambiguous prompts, synthesis, or specialized card-design choices.
- [papercuts.md](papercuts.md): optional product feedback, requiring fresh approval of the exact redacted report before sending. Keep helping with the original task.
- [heartbeat.md](heartbeat.md): periodic reminders explicitly requested by the user.
- [skill.json](skill.json): API endpoints, scopes, and payload metadata.

## Install missing helpers

Use the existing bundle when available. If saving needs missing helpers and shell access is available, install the complete bundle:

```sh
curl -fsSL https://powerlevelup.com/install-skill.sh | sh
```

The default destination is `~/.powerlevelup/skills/powerlevelup`; set `POWERLEVELUP_SKILL_DEST` for another runtime-supported skill directory. Follow the runtime's discovery rules or read `SKILL.md` directly. If the runtime cannot execute HTTP/scripts, provide the draft and explain that saving is unavailable there.