Skip to content
TakoAPI
Back to skills

ops-journal

by mariusfit

Coding Agents & IDEs
289Downloads reported by clawskills.sh
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Structured operational journal that captures deployments, incidents, changes, and decisions.

Description

What This Skill Does

A command-line ops journal that logs deployments, incidents, configuration changes, and decisions to a local SQLite database. Supports incident lifecycle management with open/resolve tracking, timeline reconstruction, and exportable postmortem reports.

Keeps a structured, searchable record of operational events in a single local database rather than scattered across chat logs, tickets, or memory.

When to Use It

  • Tracking what changed before an outage
  • Reconstructing a timeline for a postmortem
  • Searching past deployments by category or date
  • Generating a weekly ops digest for a team
  • Exporting incident history to a spreadsheet

Example Workflow

INPUT

User asks: What happened during the API latency incident last week?

AGENT
  1. 1

    Run python3 scripts/journal.py incident list --status resolved to find the incident ID

  2. 2

    Run python3 scripts/journal.py timeline INC-001 to reconstruct the event sequence

  3. 3

    Run python3 scripts/journal.py search --category incident --since 7d to surface related entries

  4. 4

    Export the timeline with python3 scripts/journal.py timeline INC-001 --format markdown

OUTPUT

Markdown timeline showing when the incident opened, all logged events during the window, and the recorded root cause and resolution

Installation

clawhub install mariusfit/ops-journal

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links