agentleFS
Sign inStart free
cobusgreylingcobusgreyling/grok-bot-templates/skills/incident-timeline/SKILL.md

incident-timeline

Skill14 starsChanged 3 months agoMITView on GitHub

Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Incident Timeline”. A useful skill states the six fields from Skills and routines. An incident is in flight or just closed and Slack plus GitHub must become a source-linked timeline a human can use for the write-up. Every timeline row has a source pointer. Hypotheses are labeled. No production toggle, merge, revert, or Slack post happened. Timeline, stated impact only if…

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every timeline row has a source pointer.

    line 30
  2. Distinctive:

    Do not toggle production, change alerts, merge, revert, or post to Slack.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Incident Timeline

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Incident Timeline”.

A useful skill states the six fields from Skills and routines.

1. When to use it

An incident is in flight or just closed and Slack plus GitHub must become a source-linked timeline a human can use for the write-up.

2. Required inputs and access

  • Slack incident channel the owner named
  • GitHub issues, PRs, deploys, or commits linked in the thread
  • Incident start time or the first page message

3. Sequence of work

  1. Confirm incident name, start time, and approved Slack channel. If any of those are missing, ask and stop.
  2. Collect Slack messages and GitHub issues, PRs, and deploys in the window. Do not page anyone.
  3. Build a chronological timeline with timestamp, source link, and fact vs hypothesis.
  4. Record production actions humans already took. Do not take any.
  5. List open questions and what the sources never said.

4. How to validate the result

Every timeline row has a source pointer. Hypotheses are labeled. No production toggle, merge, revert, or Slack post happened.

5. What to return

Timeline, stated impact only if a source said it, open questions, not-found list, action log of channels and repos scanned.

6. What requires approval

Do not toggle production, change alerts, merge, revert, or post to Slack.

Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free