Skip to content
Skills Library
DevOps & cloud · Automation

add-app

/add-app

Install a self-hosted app on this server — from the Discover catalog when possible, otherwise by writing a Server OS recipe. Use for "install X", "set up X", "I want X", or an install request in inbox/.

Repository
server-os ↗
Licence
MIT
Last repository change
03.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
3
Deprecation

No signals detected. Repository changed on 03.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Install a self-hosted app on this server — from the Discover catalog when possible, otherwise by writing a Server OS recipe. Use for "install X", "set up X", "I want X", or an install request in inbox/.

Triggers from the description

install Xset up XI want X
Original author description

Install a self-hosted app on this server — from the Discover catalog when possible, otherwise by writing a Server OS recipe. Use for "install X", "set up X", "I want X", or an install request in inbox/.

How it works

  1. Recipe format
Original SKILL.md headings · 50 lines, 353 words
SKILL.md preview
---
name: add-app
description: Install a self-hosted app on this server — from the Discover catalog when possible, otherwise by writing a Server OS recipe. Use for "install X", "set up X", "I want X", or an install request in inbox/.
---

# Add an app

1. **Find it:** `search_catalog` with the app's name, then `catalog_entry` for the best hit.
   - Check its `install` options, ranked best first: recipe, casaos, linuxserver, brew, cask.
   - If the project is archived, tell the owner and suggest a maintained alternative from the same category.
2. **Plan:** `plan_install` with the chosen method. Read the compose file:
   - Image tag: avoid ancient tags. `latest` is fine for home use.
   - Ports: `{{port:N}}` is filled with a free port at install time.
   - Volumes: everything must live under `{{data}}`.
   - Required env vars without a value: ask the owner, or pick safe defaults and say so.
   - Privileged mode, host networking, `/var/run/docker.sock` mounts: only if the app truly needs them, and tell the owner.
3. **Install:** `install_app`, then poll `operation_status` every ~5 s until `ok` or `failed`.
4. **Verify:**
   - The app shows up in `list_apps` with state `on`.
   - Its URL answers: `href` in `app.yaml`, or `curl -sI` the port.
   - Then make it ready to use with the **finish-app** skill (admin account, first-run wizard, ready card).
5. **No automatic method?** Write a recipe in `../config/recipes/<id>.yaml` (format below).
   - Base it on the project's official docker-compose or Homebrew formula.
   - Put first-run steps you worked out in the recipe's `setup:` field, so the next install goes faster.
   - Then `reload_recipes`, `search_catalog` for it (its catalog id is the recipe's), and `install_app` with method `recipe`.
6. **Done:** if this came from `inbox/`, move the request to `inbox/done/` with a one-line result.

## Recipe format
```yaml
id: my-app                  # lowercase, dashes
name: My App
description: One sentence.
category: Media Streaming
website: https://…
repo: https://github.com/…
logo: https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/my-app.svg
docker:
  compose: |
    services:
      my-app:
        image: org/my-app:latest
        container_name: sd-my-app
        restart: unless-stopped
        environment: { TZ: "{{tz}}", PUID: "{{puid}}", PGID: "{{pgid}}" }
        ports: ["{{port:8080}}:8080"]
        volumes: ["{{data}}:/data"]
# or:  brew: { formula: name, service: true }   web: { port: 1234 }
notes: What the owner must know after installing (one line).
setup: |
  First-run steps for the agent, e.g.:
  docker exec sd-my-app my-app user create --admin --name <owner> --password <admin_password secret>
  Then set SIGNUPS=false in compose.yaml and restart.
```

Versions

The database has no other skills named add-app.

Database snapshot: 13.11.2026 · package version ae6abe96b288 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 96self-hosted-web-service-ops
    Use when operating or diagnosing a self-hosted web service.
  • 90install-open-mail-server
    Installs Open Mail Server on a Linux VPS over SSH. Asks for the server host, username, and password, installs Docker when it is missing, copies this project and its Compose file, and starts the container. Use when the user asks to install, deploy, or set up Open Mail Server on a…
  • 81compose-apps
    Deploy a self-hosted app that ships as a docker-compose file or upstream images (Mattermost, Gitea, Nextcloud, a database). Use when the user wants such an app running for them.
  • 90add-service
    Use when installing, adding, updating or moving a self-hosted app or container on the homeserver with Docker Compose (Immich, Jellyfin, Plex, Nextcloud, Vaultwarden and others), or when choosing which app fits a need.
  • 100deploy
    Add or redeploy application stacks on a VPS that ALREADY runs bento, via SSH. Drives bento's unattended Step 3 (BENTO_APPS) for the chosen apps, reconciles state against Portainer, verifies each app, and reports URLs + bootstrap artifacts. Use when the user says "add n8n to my…
  • 100thunderid-install
    Install and start the ThunderID server. Use when asked to "set up ThunderID", "install ThunderID", "run ThunderID", or "start ThunderID server".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.