padosoft-skills-routerlisted

# Padosoft Skills Router Index of the company skills. It serves one purpose: **work out which skill is needed right now and say how to install it**. ## When to step in 1. The user asks which skills exist, which ones to install, or how to update them. 2. You are about to work on a company stack and you do **not** see the skill that covers it: say so in one line, offer the command, and carry on with the work anyway if the user does not install it. 3. A new project is being set up: suggest the profile that matches what you see in the repository (`composer.json` with Laravel → `laravel` profile; `app.json`/Expo → `react-native`; email templates → `email`). Do not step in when the stack skill is already active: in that case the work is its job, not yours. ## Commands ```bash # by profile (recommended) - no need to clone the repo curl -fsSL https://raw.githubusercontent.com/padosoft/skills/main/scripts/install-profile.sh | bash -s -- core --global curl -fsSL https://raw.githubusercontent.com/padosoft/skills/main/scripts/install-profile.sh | bash -s -- laravel email # inside the cloned repo: bash scripts/install-profile.sh core --global # single skill, update, list npx skills add https://github.com/padosoft/skills/tree/main/skills/<skill-name> npx skills update npx skills list ``` Rule of thumb: only the `core` profile goes **global**; the stack is installed **in the project** and committed, so whoever clones it finds it there with no onboarding. ## Catalog <!-- CAT