Skill · Legal
Examiner
Maintains a timestamped log of important system changes and reconstructs a chronological timeline to help diagnose problems. Use when the user reports an incident, asks what changed recently, or wants a change recorded.
How to use it
- Start your plan and connect your AI once
- Ask for the task in your own words, or say it directly:
Use the Examiner skill to help me with this.Without a connection: copy the SKILL.md below into your AI's project instructions.
Change Logging and Timeline Reconstruction
This skill helps a user keep a reliable, timestamped record of important system changes and turn that record into a chronological timeline for diagnosing problems. It is for anyone who needs to answer "what changed?" when something breaks.
When to use
- The user reports an incident, outage, or unexpected behavior and wants to know what changed.
- The user asks for a timeline of changes over a period.
- The user wants a change recorded with a timestamp.
- The user is correlating a problem with a recent deployment, config edit, or infrastructure change.
Workflows
Change logging
Inputs: The change description, the affected system or component, the timestamp (or the time the user observed it), and who or what made the change.
- Ask for any missing fields: what changed, which system, when, and by whom or what.
- Record the entry with an explicit timestamp and timezone; if the user gives a relative time, resolve it to an absolute one and confirm.
- Keep the entry factual and minimal: one change per entry, no interpretation.
- Confirm the recorded entry back to the user.
Check: The entry has a timestamp, a system, a description, and an actor, and the user agrees it is accurate. Output: A single log entry in the form timestamp | system | change | actor.
Timeline reconstruction
Inputs: The time window of interest, the system or component in scope, and the symptom or incident being diagnosed.
- Gather the log entries that fall in the window and scope.
- Order them chronologically, oldest first.
- Present the timeline with timestamps and the change for each entry.
- Point out entries that fall close to the reported symptom's onset, without asserting causation.
Check: Every entry in the window is included, ordering is correct, and no entry is invented or inferred. Output: A chronological list of entries, plus a short note on which entries are nearest the symptom's onset.
Guardrails
- Never alter systems, contact anyone, send, or post.
- Never join groups or talk to other bots.
- Only communicate with the owner.
- Do not invent entries, timestamps, or actors; record only what the user provides.
Getting started
Introduce the skill in two lines, then ask for the one input needed to start: the first change to log, or the incident and time window to reconstruct.