New: 97,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

Engineering Journal

by iopsystems in iopsystems/rezolus

A skill your agent uses when starting or picking up a non-trivial effort (feature, investigation, perf probe, refactor, migration) in a shared repo where teammates or future agents must coordinate…

Custom licenceAuto-check passedProduct & Project Management

Install Engineering Journal

skills CLI
$ npx skills add iopsystems/rezolus --skill engineering-journal -a claude-code

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

GitHub CLI
$ gh skill install iopsystems/rezolus engineering-journal --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/iopsystems/rezolus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/engineering-journal .claude/skills/engineering-journal && 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
engineering-journal
GitHub stars
275
Token cost
~2.6k tokens
SKILL.md length
1,534 words
Files
2
Skills in repo
11
Repo updated
First seen
Licence
Custom licence

At a glance

A skill your agent uses when starting or picking up a non-trivial effort (feature, investigation, perf probe, refactor, migration) in a shared repo where teammates or future agents must coordinate…

  • Works in 5 steps: Pick & scope. Gather requirements. Grep… → Open — land intent on main. Write the… → Go / no-go. Probe or price it cheaply… → …
  • Picking up a non-trivial effort (feature
  • SKILL.md covers Overview, When to use, Journal vs. issues (use both) and The lifecycle (per effort), plus 10 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Engineering Journal is an agent skill from iopsystems/rezolus. Use when starting or picking up a non-trivial effort (feature, investigation, perf probe, refactor, migration) in a shared repo where teammates or future agents must coordinate or hand off; when a repo has no durable in-tree record of decisions and dead-ends; when you're about to drop a well-measured negative result; or when bootstrapping a journal from a repo's commit history.

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `publishing-example.md`).

It sits in Product & Project Management. The repository describes itself as: High-resolution, low-overhead systems and service telemetry.

When your agent uses it

  • Picking up a non-trivial effort (feature
  • Migration) in a shared repo where teammates
  • Future agents must coordinate
  • A repo has no durable in-tree record of decisions and dead-ends

Example prompts

  • “/engineering-journal”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Pick & scope. Gather requirements. Grep the journal + git log for prior art first — don't re-litigate a settled question.
  2. Open — land intent on main. Write the entry: goal/hypothesis, requirements, GO/NO-GO criteria (number-gated where possible), plan. Commit…
  3. Go / no-go. Probe or price it cheaply before building. Record the verdict honestly.
  4. Implement & test.
  5. Close out — in the implementing PR. Update the entry with the outcome (shipped / NO-GO + numbers + mechanism) and update any docs the…

What it can do on your machine

Read from SKILL.md and the folder at commit 12c9761. 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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Engineering Journal loads about 2.6k tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 1,534 words of instructions outside code blocks.

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

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,534 words (~2,623 tokens).

“An engineering journal is an in-repo markdown record of efforts — what you set out to do, the decision to proceed or not, what happened, and what was learned. It lives in the tree (docs/journal/ or the repo's docs dir)…”

— opening of SKILL.md by iopsystems, Custom licence
name
engineering-journal

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file in .claude/skills/engineering-journal of iopsystems/rezolus.

  • SKILL.md
  • publishing-example.md

Open the folder on GitHubat commit 12c9761

Compare with similar skills

Engineering Journal 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.

Engineering Journal compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Engineering Journal this skilliopsystems/rezolus275—~2.6kAutomated safety check: PassCustom licence
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Weekly Engineering Retrogarrytan/gstack136k—~2.4kAutomated safety check: PassMIT
To Issuesywwynm/EverythingDone14412 repos~893Automated safety check: PassGPL-3.0
Dough Execute Planterryyin/lizard2.5k—~4.3kAutomated safety check: PassCustom licence

Similar skills

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Weekly Engineering Retro

    garrytan/gstack

    Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • To Issues

    ywwynm/EverythingDone

    Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

    144 GitHub starsUsed in 12 repos~893 tokens
    Product & Project ManagementAuto-check passed

  • Dough Execute Plan

    terryyin/lizard

    Executes one selected story or bounded retrospective correction through an executable plan, or one authorized planless slice from a selected simple story or a contextual instruction, with…

    2.5k GitHub stars~4.3k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • To Spec

    bestofjs/bestofjs

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    3.1k GitHub starsUsed in 22 repos~757 tokens
    Product & Project ManagementAuto-check passed

More from iopsystems/rezolus

All 11 skills in this repo

  • Document Feature

    iopsystems/rezolus

    Write or update the CLI --help text and README section for a new or changed rezolus feature (a subcommand, flag, mode, or behavior change), then prove the help is usable by dispatching a fresh…

    275 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

  • Reviewing Samplers

    iopsystems/rezolus

    A skill your agent uses when reviewing a Rezolus sampler change before merge — a new sampler, a change to an existing sampler's probes/refresh/metrics, or core changes that affect samplers; or…

    275 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed

  • Viewer Render

    iopsystems/rezolus

    Render the running viewer in a real headless browser and assert on what it drew — element geometry, computed colours, wrap points, truncated labels, console errors.

    275 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

  • Prerelease

    iopsystems/rezolus

    Tag and push a prerelease from the current Cargo.toml version.

    275 GitHub stars~514 tokensUpdated yesterday
    Auto-check: notes

  • PR

    iopsystems/rezolus

    Create a feature branch, commit changes, push, and open a PR against iopsystems/rezolus

    275 GitHub stars~906 tokensUpdated yesterday
    Auto-check passed

  • Release

    iopsystems/rezolus

    Create a release PR with version bump and changelog update. An agent skill from iopsystems/rezolus.

    275 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Engineering Journal

What does Engineering Journal do?

A skill your agent uses when starting or picking up a non-trivial effort (feature, investigation, perf probe, refactor, migration) in a shared repo where teammates or future agents must coordinate…. Engineering Journal is an agent skill from iopsystems/rezolus. Use when starting or picking up a non-trivial effort (feature, investigation, perf probe, refactor, migration) in a shared repo where teammates or future agents must coordinate or hand off; when a repo has no durable in-tree record of decisions and dead-ends; when you're about to drop a well-measured negative result; or when bootstrapping a journal from a repo's commit history.

When should I use Engineering Journal?

Engineering Journal fits situations like: picking up a non-trivial effort (feature; migration) in a shared repo where teammates; future agents must coordinate; A repo has no durable in-tree record of decisions and dead-ends.

How do I install Engineering Journal in Claude Code?

Run `npx skills add iopsystems/rezolus --skill engineering-journal -a claude-code`. Or copy the skill folder (.claude/skills/engineering-journal in iopsystems/rezolus) into .claude/skills/engineering-journal in your project. Claude Code loads it when a task matches its description.

How do I install Engineering Journal in Codex?

Run `npx skills add iopsystems/rezolus --skill engineering-journal -a codex`. Or copy the skill folder (.claude/skills/engineering-journal in iopsystems/rezolus) into .agents/skills/engineering-journal in your project. Codex loads it when a task matches its description.

Can I use Engineering Journal 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 iopsystems/rezolus --skill engineering-journal -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/engineering-journal, .gemini/skills/engineering-journal, .github/skills/engineering-journal and .opencode/skills/engineering-journal in your project.

What does Engineering Journal need to run?

SKILL.md names no scripts, command-line tools or credentials: Engineering Journal is instructions for the agent only.

Does Engineering Journal access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Engineering Journal 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 Engineering Journal use?

Engineering Journal has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Engineering Journal use?

About 2.6k tokens (SKILL.md is roughly 10k 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 Engineering Journal?

Skills that share tags, products or a category with Engineering Journal: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars), Weekly Engineering Retro (garrytan/gstack, 136k stars) and To Issues (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Engineering Journal?

iopsystems (a GitHub organization) maintains it in iopsystems/rezolus, which has 275 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 6, 2026.

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