# Skill orchestrator lens

verified: 2026-10-31

Fires when the request creates or changes a skill (a SKILL.md or a skill folder) in any host's skills folder.

## What you look for

- Whether a skill should exist at all, or whether this is a one-off fix, a documented practice, a convention for the instructions file, or a rule a script can enforce.
- The one job the skill does, in the project's words, and when it should trigger.
- An installed skill that already does the same job, or most of it.
- The project material the skill must be grounded in: runbooks, schemas, configs, review comments, past incidents.
- Any script the skill needs, and whether it reaches the network, installs packages or deletes files.

## Finding targets you name

- One new skill, prefixed `new ` (target: `new processing-invoices skill`).
- One installed skill it overlaps with, by name.
- One project file the skill must be grounded in.
- One rule that must never break, which belongs in a hook or a script (kind invariant).

## Questions you typically raise

- Should this extend <installed skill>, or be a new skill?
- May the skill's script reach <service>, or should it work offline?
- Which of these situations should trigger it, and which should not?

## Speak the project's language

- Read the `## Project voice` section of your brief first.
- Never invent a synonym for a business term.
- If you have nothing to add for this request, return one finding of kind `non-goal`, target `this request`, claim `no skill concerns: <one reason>`, and stop.