filippolmt

Run full validation suite (lint + tests + Renovate config) before committing. Use after any app change to ensure everything passes.

Validate Biome 2.3+ configuration and detect outdated patterns. Ensures proper schema version, domains, assists, and recommended rules. Use before any linting work or when auditing existing projects.

Use when modifying ANY file inside an app directory (apps/<app-id>/). Triggers on edits to docker-compose.json, config.json, metadata files, or data files of any app. Must increment tipi_version in config.json for every app change, no exceptions.

Use when syncing this appstore with the official runtipi/runtipi-appstore repo, adding new apps from upstream, updating configurations to match official patterns, or checking if local setup has drifted from upstream best practices. Triggers on requests like "align with official repo", "check upstream", "add app from official store", "update to match upstream".

Expert bash/shell scripting system across ALL platforms. PROACTIVELY activate for: (1) ANY bash/shell script task, (2) System automation, (3) DevOps/CI/CD scripts, (4) Build/deployment automation, (5) Script review/debugging, (6) Converting commands to scripts. Provides: Google Shell Style Guide compliance, ShellCheck validation, cross-platform compatibility (Linux/macOS/Windows/containers), POSIX compliance, security hardening, error handling, performance optimization, testing with BATS, and production-ready patterns. Ensures professional-grade, secure, portable scripts every time.

Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development, state management, provider configuration, multi-environment workflows, infrastructure testing.

Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.

Add a new CLI binary (or wire missing auth/persistence for an existing one) to the toolbox image — Dockerfile install layer + version ARG + `internal/catalog/catalog.go` `Entries` row + `smoke-test.sh` check + Renovate `customManager` + (when the CLI persists state) a `~/.toolbox/<tool>` bind-mount in `internal/mountplan/defaults.go`. Use this whenever the user says things like "add <X> to the toolbox", "install <X> in the container", "put <X> in the image", "add <X> CLI", "wire auth for <X>", "persist <X> credentials", "save <X> authentication", or names a binary they want available inside `toolbox shell`. Also use it when an audit shows a CLI is in the Dockerfile but its credentials don't survive `toolbox stop` — that's the gws-style half-installed case this skill explicitly handles. Always perform the edits autonomously and finish with `/verify`; don't hand the user a checklist to apply themselves.

Add or update external skills in this marketplace as git-subdir entries and keep the README catalog in sync. Usage: /add-external-skill <owner/repo> [path] [name] | /add-external-skill update

Administer the per-prompt caveman/ponytail router — show status, force a mode, or turn routing off.

Every changedetection.io watch, tag, and notification from one CLI — plus offline cross-watch queries the web UI can't do. Trigger phrases: `what changed on my watches`, `list changedetection watches`, `which monitors are stale`, `show errored watches`, `use changedetection`, `run changedetection`.

Restructure and maintain Markdown documentation for section-level navigability and zero redundancy — canonical section index, stable GitHub anchors, targeted deep links, single-source-of-truth, and offline link/anchor checking (lychee in CI plus a local make target). Use this whenever the user wants to reorganize or clean up docs, create or update a docs index, remove duplicated documentation, slim down CLAUDE.md or other agent files, fix broken Markdown links or anchors, or add documentation link checking — even if they only say "the docs are a mess", "make the docs navigable", or "where should this be documented".