add-package
Skill488 starsChanged 6 months agoMITView on GitHub
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.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- debuffjp/debufftheir own version, first seen Nov 1, 2026
- nrjdalal/inscopetheir own version, first seen Oct 13, 2026
- elastic/esql-jstheir own version, first seen Oct 9, 2026
- nrjdalal/zerostartertheir own version, first seen Oct 8, 2026
- remix-run/remixtheir own version, first seen Oct 8, 2026
- robmclarty/trailheadtheir own version, first seen Apr 18, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- remix-run/remix★ 33ksame name
- nrjdalal/zerostarter★ 65same name
- elastic/esql-js★ 14same name
- debuffjp/debuff★ 12same name
- nrjdalal/inscope★ 3same name
- robmclarty/trailhead★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-videoSkill
- find-videosSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
26 rules. 0 are common, 19 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
19
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill for this repository only.
- Very specific: line 20
Add a new package to LazyPi in a way that matches the repository's existing structure and conventions.
- Distinctive: line 32
Always read these files first:
- Distinctive: line 63
Do not invent pins unless there is a good reason.
- Very specific: line 78
Use the repository's current naming style, not the upstream project's exact wording, if that wording is inconsistent with LazyPi.
- Distinctive: line 96
Before editing, inspect the upstream package enough to understand:
- Distinctive: line 104
Use the package's docs, README, package metadata, and install instructions as needed.
- Very specific: line 108
Add the package to PACKAGES in bin/lazypi.mjs.
- Distinctive: line 113
keep object formatting consistent
- Very specific: line 114
write a concise description
- Very specific: line 115
write a practical hint
- Distinctive: line 125
If the new package needs special handling, place it near the relevant existing install/settings logic and explain it briefly in code …
- Distinctive: line 127
If the package does not need special logic, do not add any.
- Distinctive: line 139
When creating a dedicated package page, match the structure of existing pages:
- Distinctive: line 152
If the new docs page is user-facing, update all places that should link to it.
- Distinctive: line 158
Check and update as needed:
- Distinctive: line 172
search for outdated package counts or stale navigation
- Distinctive: line 173
verify the new slug/path is linked correctly
- Very specific: line 174
verify formatting in bin/lazypi.mjs matches surrounding entries
- Very specific: line 175
verify .github/workflows/test.yml still reflects the default installed catalog when applicable
- Distinctive: line 176
verify the package category and source are defensible
- Distinctive: line 177
call out any uncertainty about pins, categories, or whether a package should have a dedicated page
- Distinctive: line 181
Prefer small, precise edits.
- Distinctive: line 183
Do not rewrite unrelated docs.
- Distinctive: line 184
Do not remove existing packages unless explicitly asked.
- Distinctive: line 185
If the package is ambiguous, ask a clarifying question before making risky assumptions.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add Package to LazyPi
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>.
Goal
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:
- stores package metadata for installation
- categorizes packages
- handles package-specific install quirks
- presents package documentation
- maintains navigation, counts, and summaries
First: inspect the repository before editing
Always read these files first:
bin/lazypi.mjsREADME.md.github/workflows/test.ymldocs/docs/index.htmldocs/docs/packages/index.htmldocs/themes.html
Then read the repository map:
- references/repo-map.md
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.
Input normalization
The user may give you:
- an npm package name or npm URL
- a GitHub URL
- a git install source
- a raw Pi install source such as
npm:fooorgit:github.com/org/repo
Normalize that into the LazyPi catalog source format used in bin/lazypi.mjs.
Examples:
- npm package →
npm:<name>or pinned form if this repo clearly uses a pin for that package - GitHub repo →
git:github.com/<owner>/<repo>or a pinned ref if the repo's existing conventions suggest it
Do not invent pins unless there is a good reason.
Determine the package metadata
Work out the following before editing:
idcategorysource- short
description - short
hint - docs title
- docs slug / filename
- whether the package needs a dedicated docs page, a themes-page update, or both
Use the repository's current naming style, not the upstream project's exact wording, if that wording is inconsistent with LazyPi.
Category rules
LazyPi currently uses these categories in bin/lazypi.mjs:
coreuiresearchframeworksthemes
Choose the single best fit.
Required implementation steps
1) Inspect upstream package details
Before editing, inspect the upstream package enough to understand:
- what it actually does
- how users access it inside Pi
- whether it is user-facing or just a support dependency
- whether it needs auth, environment variables, setup, or repair logic
- whether it is a theme package
Use the package's docs, README, package metadata, and install instructions as needed.
2) Update the installer catalog
Add the package to PACKAGES in bin/lazypi.mjs.
Follow existing conventions:
- preserve category grouping and nearby ordering
- keep object formatting consistent
- write a concise
description - write a practical
hint
3) Add special-case install logic only if justified
Inspect whether the package needs special handling.
Examples already present in this repo include:
- subagent settings overrides
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.
4) Update documentation
Work out the right documentation surface based on how this repo is already organized.
Typical cases:
- user-facing non-theme package → add
docs/docs/packages/<slug>.html - theme package → update
docs/themes.html, and add package docs only if the existing docs structure suggests it belongs there - support/auxiliary package → decide whether it deserves its own page or should be documented indirectly through a related page
When creating a dedicated package page, match the structure of existing pages:
- title
- one-line page description
- "What it does"
- "Why it's included"
- commands or usage notes if relevant
- "Learn more" link to upstream project
- previous/next nav
- footer and sidebar structure matching the existing docs pages
5) Update navigation, docs, and CI expectations
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.html- sidebars in docs pages that list package pages
docs/docs/index.htmlREADME.mddocs/themes.html- any package-count text such as "23 packages" or theme counts
6) Validate before finishing
At minimum:
- search for outdated package counts or stale navigation
- verify the new slug/path is linked correctly
- verify formatting in
bin/lazypi.mjsmatches surrounding entries - verify
.github/workflows/test.ymlstill reflects the default installed catalog when applicable - verify the package category and source are defensible
- call out any uncertainty about pins, categories, or whether a package should have a dedicated page
Editing principles
- Prefer small, precise edits.
- Preserve the tone and formatting already used in this repo.
- Do not rewrite unrelated docs.
- Do not remove existing packages unless explicitly asked.
- If the package is ambiguous, ask a clarifying question before making risky assumptions.
Final response
When done, summarize:
- chosen
id - chosen
category - chosen
source - files changed
- any special install logic added
- any assumptions or follow-up review items
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

