Datasets:
Stop before installing a missing specialist
Browse files
SKILL.md
CHANGED
|
@@ -153,13 +153,18 @@ broader open-source playbook.
|
|
| 153 |
## Dispatch contract
|
| 154 |
|
| 155 |
1. State the selected specialist and the reason in one sentence.
|
| 156 |
-
2.
|
| 157 |
-
|
| 158 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 159 |
whether the user wants the selected skill to run.
|
| 160 |
-
|
| 161 |
-
|
| 162 |
-
|
| 163 |
- outcome or diagnosis;
|
| 164 |
- evidence and assumptions;
|
| 165 |
- artifact or action completed;
|
|
|
|
| 153 |
## Dispatch contract
|
| 154 |
|
| 155 |
1. State the selected specialist and the reason in one sentence.
|
| 156 |
+
2. Check whether that specialist is installed. If it is missing, return only
|
| 157 |
+
the route card and this exact single-skill command, then pause:
|
| 158 |
+
`npx skills add Gingiris-1031/gingiris-skills --skill <specialist>`.
|
| 159 |
+
Do not scan other installed skills for a substitute and do not install it
|
| 160 |
+
without the user's authorization.
|
| 161 |
+
3. After the specialist is available, read its `SKILL.md` completely.
|
| 162 |
+
4. Follow its workflow and load only the references needed for the task.
|
| 163 |
+
5. Execute in the same task when safe and authorized. Do not pause merely to ask
|
| 164 |
whether the user wants the selected skill to run.
|
| 165 |
+
6. Substitute only when the canonical specialist no longer exists in the
|
| 166 |
+
Gingiris source collection; disclose the substitution.
|
| 167 |
+
7. Return a compact result containing:
|
| 168 |
- outcome or diagnosis;
|
| 169 |
- evidence and assumptions;
|
| 170 |
- artifact or action completed;
|