New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Write Ops Log

by marin-community in marin-community/marin

Publish a tagged Echo record after a live infrastructure incident, then link its canonical URL from the associated pull request or issue.

Apache-2.0Auto-check passedDevelopment

Install Write Ops Log

skills CLI
$ npx skills add marin-community/marin --skill write-ops-log -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install marin-community/marin write-ops-log --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/marin-community/marin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-ops-log .claude/skills/write-ops-log && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
write-ops-log
GitHub stars
3.9k
Token cost
~936 tokens
SKILL.md length
395 words
Files
1
Skills in repo
41
Repo updated
First seen
Licence
Apache-2.0

At a glance

Publish a tagged Echo record after a live infrastructure incident, then link its canonical URL from the associated pull request or issue.

  • Tasks that involve Pull requests
  • SKILL.md covers Search before writing, Draft the Echo entry, Write the record and Keep the record useful
  • Calls uv

What it does

Write Ops Log is an agent skill from marin-community/marin. Publish a tagged Echo record after a live infrastructure incident, then link its canonical URL from the associated pull request or issue.

Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. The repository describes itself as: Open-source framework for the research and development of foundation models. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/write-ops-log”

What it can do on your machine

Read from SKILL.md and the folder at commit be1f5f1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Write Ops Log loads about 936 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 395 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~936

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from marin-community/marin at commit be1f5f1, republished under its Apache-2.0 licence (© marin-community). 395 words, ~936 tokens.

Download SKILL.mdSave it as .claude/skills/write-ops-log/SKILL.md (or your agent's skills folder).
name
write-ops-log
description
Publish a tagged Echo record after a live infrastructure incident, then link its canonical URL from the associated pull request or issue.

Skill: Write an Ops Log

Publish the incident record to Echo. Do not add a repository debug-log file. An incident is a service, production run, or shared operational system failure or degradation that required diagnosis or mitigation. Ordinary code debugging, implementation notes, experiment progress, and local failures are not incident records. The audience is a future engineer who must quickly decide what to check or do next. Record the smallest set of facts that supports that action. Link raw evidence and detailed chronology rather than reproducing them; Echo entries consume limited model context whenever they are retrieved.

Search before writing

If the current investigation already fetched an Echo entry for this incident, reuse it and edit that entry without repeating the search. Otherwise, invoke consult-echo and run its complete search-before-write sequence. Start with a natural-language infra/marina/apps/echo/cli.py search, fetch likely matches with get <source-id>, and use grep for the exact error or run identifier. Create a new entry for a different incident even when the symptom resembles an older one; link related incidents and create or extend a separate synthesis only when they establish a reusable cross-incident pattern.

Draft the Echo entry

Write an OKF document in a temporary file:

markdown
---
type: wiki-note
title: "Incident YYYY-MM-DD: <system> — <symptom>"
use_when: when investigating <specific symptom or exact error>
tags:
  - incident
  - debugging
  - ops
  - <system>
  - <severity>
  - <resolution>
---

# <System or component>: <symptom>

## TL;DR

- <user-visible symptom>
- <diagnostic discriminator or immediate action>
- <fix or remaining caveat>

## Response

<The shortest safe procedure for diagnosing, mitigating, or avoiding the
incident.>

## Cause and resolution

<Only the evidence needed to justify the response and explain the resolution.>

## Artifacts

- <Canonical PR, issue, dashboard, durable log bundle, or report>

Use the incident's investigation date. Use lowercase kebab-case tags and no more than 20. Always include incident and debugging; add ops for infrastructure work, followed by the subsystem, severity, and resolution. Omit any body section that adds no actionable value. Add a compact original report, investigation step, or course correction only when it changes how a future reader should recognize or respond to the incident.

Show full SKILL.md (131 more words)Show less

Write the record

Create a new incident:

bash
uv run infra/marina/apps/echo/cli.py wiki add --file incident.md

Continue the same incident:

bash
uv run infra/marina/apps/echo/cli.py wiki show <id> > incident.md
# Edit incident.md.
uv run infra/marina/apps/echo/cli.py wiki edit <id> --file incident.md

Both commands print the canonical Echo URL. Return that URL and add it to the associated PR description or issue. Do not commit the temporary OKF file.

Keep the record useful

  • Preserve exact error strings and canonical evidence URLs.
  • Prefer decisions, discriminating evidence, and response steps over narrative. Do not paste raw logs, duplicate source artifacts, or narrate every tool call.
  • Link readers to the external source of record when its detail is not needed to choose or carry out the action.
  • Keep incident-specific detail here. Promote recurring procedures and guardrails to the relevant OPS.md.
  • Update docs/ when behavior or configuration guidance belongs with the repository.
  • Record an unknown root cause as unknown; do not fill the gap with speculation.

© marin-community, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/write-ops-log of marin-community/marin.

Open the folder on GitHubat commit be1f5f1

Compare with similar skills

Write Ops Log next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Write Ops Log compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Write Ops Log this skillmarin-community/marin3.9k—~936Automated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from marin-community/marin

All 41 skills in this repo

  • Noslop

    marin-community/marin

    Deslop, simplify, or review low-value tests and prose only when explicitly requested for a branch or diff.

    3.9k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Use Iris

    marin-community/marin

    Use Iris to submit, inspect, debug, monitor, or recover jobs and tasks; diagnose scheduling and federation; deploy controllers; or reserve dev GPUs and TPUs.

    3.9k GitHub stars~745 tokensUpdated yesterday
    Auto-check passed

  • Launch Rl

    marin-community/marin

    Define, validate, submit, or restart a Marin SkyRL experiment through its artifact main.

    3.9k GitHub stars~894 tokensUpdated yesterday
    Auto-check passed

  • Marina Applet

    marin-community/marin

    Build, validate, publish, update, inspect, query, roll back, or archive a dynamic Marina applet.

    3.9k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

  • Query Finelog

    marin-community/marin

    Query Finelog logs and telemetry for Iris tasks, workers, profiles, training, vLLM, and cross-cluster forwarding.

    3.9k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Trace Pulumi Diff

    marin-community/marin

    Run a read-only preview for a specified Marin infra/pulumi stack and trace each pending resource change to merged pull requests since its latest successful update when that update records a clean…

    3.9k GitHub stars~663 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Write Ops Log

What does Write Ops Log do?

Publish a tagged Echo record after a live infrastructure incident, then link its canonical URL from the associated pull request or issue. Write Ops Log is an agent skill from marin-community/marin. Publish a tagged Echo record after a live infrastructure incident, then link its canonical URL from the associated pull request or issue.

When should I use Write Ops Log?

Write Ops Log fits situations like: tasks that involve Pull requests.

How do I install Write Ops Log in Claude Code?

Run `npx skills add marin-community/marin --skill write-ops-log -a claude-code`. Or copy the skill folder (.agents/skills/write-ops-log in marin-community/marin) into .claude/skills/write-ops-log in your project. Claude Code loads it when a task matches its description.

How do I install Write Ops Log in Codex?

Run `npx skills add marin-community/marin --skill write-ops-log -a codex`. Or copy the skill folder (.agents/skills/write-ops-log in marin-community/marin) into .agents/skills/write-ops-log in your project. Codex loads it when a task matches its description.

Can I use Write Ops Log in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add marin-community/marin --skill write-ops-log -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-ops-log, .gemini/skills/write-ops-log, .github/skills/write-ops-log and .opencode/skills/write-ops-log in your project.

What does Write Ops Log need to run?

Going by SKILL.md and its folder, Write Ops Log needs the command-line tools its instructions call (uv).

Does Write Ops Log access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Write Ops Log safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Write Ops Log use?

Write Ops Log is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Write Ops Log use?

About 936 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Write Ops Log?

Skills that share tags, products or a category with Write Ops Log: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Write Ops Log?

marin-community (a GitHub organization) maintains it in marin-community/marin, which has 3,902 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 8, 2026.

Source: marin-community/marin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.