help-skills · diff
git:20260804.31fcccc to git:20260804.d053216
22 added, 43 removed. Audit A to A.
---
name: help-skills
- description: Present the installed skills catalog (map + slash/compat phrases) without loading every SKILL.md. Use when listing skills or invoking /help-skills.
- ---
-
- ## STOP - Read before ANY tool call
-
- 1. Read `{{GUARDRAILS_PATH}}`
- 2. Read `{{TOOLKIT_ROOT}}/skills/_shared/sdd-opcodes/SESSION.md`; load session-state for `$Cwd`
- 3. If the relevant gate is not approved: **STOP** - ask user **(pt-BR)** - do **NOT** Write/Shell
- 4. SDD/develop skills: after **ONE** step/task, **STOP** session - handoff only
- 5. This skill body is **English**; user-facing prompts may be **(pt-BR)**
-
- ### Step -1 - Gate check (report in chat before continuing)
-
- ```
- Gate check:
- [ ] guardrails.mdc read
- [ ] SESSION.md read; session-state loaded
- [ ] User confirmed current action (sim)
- -> If any unchecked: STOP
- ```
-
+ description: Present the installed static skills catalog (CATALOG.md + OPERATOR.md) without loading every SKILL.md. Use when listing skills or invoking /help-skills.
---
# Skill: help-skills
## Trigger
- Invoke when the user asks for: `/help-skills`, `list skills`, `skill catalog`, `which skills`, or `mapa de skills`.
+ Invoke when the user asks for: `/help-skills`, `list skills`, `skill catalog`, `which skills`, `mapa de skills`, or operator expectations / confirmations for a skill.
## Outcome
- User sees the **skill map** (groupings, slash forms, short purpose) from the installed catalog — **without** loading every `SKILL.md`.
+ User sees the **static** skill map and operator notes from the installed catalog files — **without** loading every `SKILL.md` and **without** re-analyzing or paraphrasing the catalog into a new essay.
- ## Lazy-load (only when needed)
+ ## Paths (required)
- | When | Path |
+ | File | Path |
|------|------|
- | Skills catalog (required) | `{{TOOLKIT_ROOT}}/skills/_shared/skills-catalog/CATALOG.md` |
- | Relative fallback (same install tree) | `_shared/skills-catalog/CATALOG.md` |
+ | Skills map | `{{TOOLKIT_ROOT}}/skills/_shared/skills-catalog/CATALOG.md` |
+ | Operator notes | `{{TOOLKIT_ROOT}}/skills/_shared/skills-catalog/OPERATOR.md` |
+ | Relative fallback | `_shared/skills-catalog/CATALOG.md` and `OPERATOR.md` (same skills tree) |
## Process
### Caveman Mode
- **NEVER** - This skill ignores `caveman_mode`. Present the catalog in clear prose (pt-BR for the user). Do not load `CAVEMAN.md` for chat compression.
-
- ### 0. Confirm gates
-
- If gates are missing, ask (pt-BR) before continuing. This skill is read-only for the catalog; do not invent skill names.
+ **NEVER** — This skill ignores `caveman_mode`. Present the catalog in clear prose (pt-BR for the user). Do not load `CAVEMAN.md` for chat compression.
- ### 1. Read catalog (required)
+ ### 0. No mutating gates
- 1. **Read** `{{TOOLKIT_ROOT}}/skills/_shared/skills-catalog/CATALOG.md` (or `_shared/skills-catalog/CATALOG.md` when the skill is already under the skills root).
- 2. If the file is missing, **STOP** and tell the user (pt-BR) that the catalog is not installed — suggest re-running agent sync. Do **not** invent a skill list from memory.
+ This skill is **read-only**. Do **not** require guardrails/SESSION/`sim` to show the catalog. Do not invent skill names.
- ### 2. Present to user (pt-BR)
+ ### 1. Read static files (required)
- Summarize the catalog for the user:
+ 1. **Read** `CATALOG.md` (path table above).
+ 2. **Read** `OPERATOR.md` when the user asks about confirmations, options, quirks, Caveman, or “what will I be asked?” — or when presenting a full help response that should include operator expectations. For a bare “list skills”, CATALOG alone is enough; still mention that `OPERATOR.md` exists for nuances.
+ 3. If either required file for the answer is missing, **STOP** and tell the user (pt-BR) the catalog is not installed — suggest re-running agent sync. Do **not** invent a skill list from memory.
- - Total count and how to invoke (`/<name>`; compat: `use skill <name>` when the host supports it)
- - Formas A / B / C with entry skills
- - Stack router (`developer`) and notable ops (`commit`, `push`, `open-github-pr`, …)
- - Point users to invoke a specific skill next; do not load that skill body unless they ask
+ ### 2. Present (do not rewrite)
- Keep the reply lean: tables or short grouped lists are fine; do not paste full skill bodies.
+ - Show groupings, skill ids, invoke phrases, and short purposes **from the file text**.
+ - Prefer tables or short grouped lists already in the static files.
+ - Point the user to invoke a specific skill next; do not load that skill body unless they ask to run it.
+ - Do **not** summarize by inventing new wording that replaces the static guide.
## Must not
- Invent skills that are not in `CATALOG.md`
- - Load every `SKILL.md` to answer a catalog question
+ - Load every `SKILL.md` to answer a catalog or operator-notes question
+ - Require `sim` / SESSION gates for read-only catalog presentation
- Write application code, commit, push, or open PRs
- Treat `_shared/` packs or architect spawn as slash skills