agentleFS
robzolkosrobzolkos/LazyPi/.agents/skills/add-package/SKILL.md

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

  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 6

    1. remix-run/remix★ 33ksame name
    2. nrjdalal/zerostarter★ 65same name
    3. elastic/esql-js★ 14same name
    4. debuffjp/debuff★ 12same name
    5. nrjdalal/inscope★ 3same name
    6. 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.

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
  1. Distinctive:

    Use this skill for this repository only.

    line 8
  2. Very specific:

    Add a new package to LazyPi in a way that matches the repository's existing structure and conventions.

    line 20
  3. Distinctive:

    Always read these files first:

    line 32
  4. Distinctive:

    Do not invent pins unless there is a good reason.

    line 63
  5. Very specific:

    Use the repository's current naming style, not the upstream project's exact wording, if that wording is inconsistent with LazyPi.

    line 78
  6. Distinctive:

    Before editing, inspect the upstream package enough to understand:

    line 96
  7. Distinctive:

    Use the package's docs, README, package metadata, and install instructions as needed.

    line 104
  8. Very specific:

    Add the package to PACKAGES in bin/lazypi.mjs.

    line 108
  9. Distinctive:

    keep object formatting consistent

    line 113
  10. Very specific:

    write a concise description

    line 114
  11. Very specific:

    write a practical hint

    line 115
  12. Distinctive:

    If the new package needs special handling, place it near the relevant existing install/settings logic and explain it briefly in code …

    line 125
  13. Distinctive:

    If the package does not need special logic, do not add any.

    line 127
  14. Distinctive:

    When creating a dedicated package page, match the structure of existing pages:

    line 139
  15. Distinctive:

    If the new docs page is user-facing, update all places that should link to it.

    line 152
  16. Distinctive:

    Check and update as needed:

    line 158
  17. Distinctive:

    search for outdated package counts or stale navigation

    line 172
  18. Distinctive:

    verify the new slug/path is linked correctly

    line 173
  19. Very specific:

    verify formatting in bin/lazypi.mjs matches surrounding entries

    line 174
  20. Very specific:

    verify .github/workflows/test.yml still reflects the default installed catalog when applicable

    line 175
  21. Distinctive:

    verify the package category and source are defensible

    line 176
  22. Distinctive:

    call out any uncertainty about pins, categories, or whether a package should have a dedicated page

    line 177
  23. Distinctive:

    Prefer small, precise edits.

    line 181
  24. Distinctive:

    Do not rewrite unrelated docs.

    line 183
  25. Distinctive:

    Do not remove existing packages unless explicitly asked.

    line 184
  26. Distinctive:

    If the package is ambiguous, ask a clarifying question before making risky assumptions.

    line 185

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.mjs
  • README.md
  • .github/workflows/test.yml
  • docs/docs/index.html
  • docs/docs/packages/index.html
  • docs/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:foo or git: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:

  • id
  • category
  • source
  • 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:

  • core
  • ui
  • research
  • frameworks
  • themes

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.yml
  • docs/docs/packages/index.html
  • sidebars in docs pages that list package pages
  • docs/docs/index.html
  • README.md
  • docs/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.mjs matches surrounding entries
  • verify .github/workflows/test.yml still 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.