How it works

1. 1

   The ticket opens at your first message

   Before any check or question, it reserves a ticket number and publishes a live ticket page. Every finding, action and approval is added to the page as it happens.

2. 2

   It defines the problem

   It restates the problem in one line and asks at most 3 short questions, only when the answer changes what it checks first. Each question is a waiting item on the page, with option buttons and free text. "I don't know" is a valid answer.

3. 3

   General to specific, read-only

   It runs one cheap read-only triage for the affected area (about 20 seconds), then goes deeper only where the output points: symptom, component, layer, current state, and what put it in that state.

4. 4

   It confirms the cause

   It names the cause in one line, with the output line that proves it. A cause without proof is labeled a hypothesis and tested before any fix is proposed.

5. 5

   It finds what caused the fault

   When something changed a setting, it looks for who or what did it: the time of the change, scheduled tasks, policies, startup items, recent installs and events. Scripts it finds are read, never run. The result is one of three: origin found, a legitimate owner (for example a policy or your own choice), or origin not found, said honestly.

6. 6

   A fix, only with your yes

   Each change is shown on the page in plain words, with the exact command, its risk and how to undo it. One action per approval. A restore point is offered before the first change, and admin steps open a visible Windows approval (UAC) window.

7. 7

   It checks that the fix holds

   It reruns the check right away, waits (90 seconds by default) and checks again, and tests your real symptom where possible. If the fault came back, the fix failed, and it goes back to finding the cause.

8. 8

   A short report and the closed ticket

   Up to 5 plain lines: the problem, what was found, what changed, the result after the wait, and anything still open. The ticket closes with a code that matches what happened and is saved on your PC.

Everything on this page comes from SKILL.md v2.8.3. SKILL.md