// Add a new package to the LazyPi repository. Use when asked to add a Pi package URL or install source to LazyPi, update the installer catalog, and create or update the matching documentation.
Search YouTube for new Pi coding agent videos using agent-browser, list candidates, ask which ones to add, then add selected videos on a new branch using the add-video skill workflow.
Add a new YouTube video to the LazyPi videos page. Use when given a YouTube URL to add to the site. Fetches title, channel, duration, and publish date automatically via agent-browser; Shorts are placed in Short Pi automatically, while regular videos ask for a category.
| name | add-package |
| description | Add a new package to the LazyPi repository. Use when asked to add a Pi package URL or install source to LazyPi, update the installer catalog, and create or update the matching documentation. |
Use this skill for this repository only.
Invoke it with:
/skill:add-package <url-or-pi-source>
Pi appends the command arguments to this skill as User: <args>.
Add a new package to LazyPi in a way that matches the repository's existing structure and conventions.
That means you must do more than just append a package object. You need to inspect how this repo currently:
Always read these files first:
bin/lazypi.mjsREADME.md.github/workflows/test.ymldocs/docs/index.htmldocs/docs/packages/index.htmldocs/themes.htmlThen read the repository map:
Then read at least two existing package docs pages that are closest to the new package in category and style. Prefer pages from docs/docs/packages/ that resemble the new package.
The user may give you:
npm:foo or git:github.com/org/repoNormalize that into the LazyPi catalog source format used in bin/lazypi.mjs.
Examples:
npm:<name> or pinned form if this repo clearly uses a pin for that packagegit:github.com/<owner>/<repo> or a pinned ref if the repo's existing conventions suggest itDo not invent pins unless there is a good reason.
Work out the following before editing:
idcategorysourcedescriptionhintUse the repository's current naming style, not the upstream project's exact wording, if that wording is inconsistent with LazyPi.
LazyPi currently uses these categories in bin/lazypi.mjs:
coreuiresearchframeworksthemesChoose the single best fit.
Before editing, inspect the upstream package enough to understand:
Use the package's docs, README, package metadata, and install instructions as needed.
Add the package to PACKAGES in bin/lazypi.mjs.
Follow existing conventions:
descriptionhintInspect whether the package needs special handling.
Examples already present in this repo include:
If the new package needs special handling, place it near the relevant existing install/settings logic and explain it briefly in code comments only when necessary.
If the package does not need special logic, do not add any.
Work out the right documentation surface based on how this repo is already organized.
Typical cases:
docs/docs/packages/<slug>.htmldocs/themes.html, and add package docs only if the existing docs structure suggests it belongs thereWhen creating a dedicated package page, match the structure of existing pages:
If the new docs page is user-facing, update all places that should link to it.
This repo uses hand-authored static HTML, so navigation is duplicated across files. Do not assume there is a generator.
Also inspect CI. The GitHub Actions workflow may assert that specific default package sources are installed, so adding a package to the default LazyPi catalog may require updating workflow expectations.
Check and update as needed:
.github/workflows/test.ymldocs/docs/packages/index.htmldocs/docs/index.htmlREADME.mddocs/themes.htmlAt minimum:
bin/lazypi.mjs matches surrounding entries.github/workflows/test.yml still reflects the default installed catalog when applicableWhen done, summarize:
idcategorysource