sc-skill

# sc-skill — discover first, install safely, then verify ## Language Keep durable instructions in English. Reply in the user's language unless requested otherwise. ## Default workflow When the user asks for a new capability or says to install/create a skill: 1. Search before installing: ```bash sc-skill <keywords> ``` Use the user's intent words, not only a guessed skill name. Examples: `sc-skill ui`, `sc-skill accessibility mobile`, `sc-skill email`, `sc-skill database`. 2. If an installed skill already owns the task, use that skill instead of creating a duplicate. 3. If a new skill is needed and the exact creation contract is unclear, run: ```bash sc-skill --new ``` In a non-interactive agent shell this returns a machine-readable contract describing the required inputs and what SC fills automatically. 4. Do **not** manually invent search tags by default. SC derives tags and aliases from the skill name, description, `use_when`, and instructions. Provide `--tags` or `--aliases` only to correct a materially wrong result. 5. Verify after installation with: ```bash sc skill show <name> --json sc-skill <expected-keyword> ``` ## Create a skill from a concise intent For a new local workflow: ```bash sc-skill --new release-readiness \ --description "Check tests, security, rollback readiness, release artifacts, and live health before publishing." ``` Default scope is project. Use `--scope global` only when the capability should be reusable ...