leavemagic-cyber

Relay Task Kernel — Productivity skill for Claude Code

Productivity community

One handoff contract that Claude Code, Codex, Gemini CLI and Copilot all read.

How to install Relay Task Kernel

This entry records only its repository, not the path inside it, so there is no exact command to give. Open leavemagic-cyber/relay-task-kernel and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Relay Task Kernel does

One handoff contract that Claude Code, Codex, Gemini CLI and Copilot all read. Zero-dependency CLI for shared agent rules, scoped memory and handoff cards.

Alternatives in Productivity

  • Rule2hook — Task: Convert Project Rules to Claude Code Hooks 404 ★
  • Carl — Context Augmentation & Reinforcement Layer — Domain-based behavioral rules for Claude Code, keyword-matched an 368 ★
  • Dependency Update Workflow — Workflow command scaffold for dependency-update-workflow in JARVIS 355 ★

README

RTK — Relay Task Kernel

**One handoff contract that Claude Code, Codex, Gemini CLI and Copilot all read.**

[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) ![Node](https://img.shields.io/badge/node-%3E%3D18.17-brightgreen) ![Dependencies](https://img.shields.io/badge/dependencies-0-brightgreen)

繁體中文說明請看 [README.zh-TW.md](README.zh-TW.md)。


The problem

You use more than one coding agent. Each wants its own instruction file:

AGENTS.md                        Codex
CLAUDE.md                        Claude Code
GEMINI.md                        Gemini CLI
.github/copilot-instructions.md  Copilot

So you write the rules four times. Then you tighten one rule and update three files. Then a new session starts, the agent has no idea what happened yesterday, and you re-explain the project for the ninth time — right before it force-pushes something.

RTK makes those four files thin pointers to one shared contract, and gives the project a small, deliberate memory that survives across sessions and across agents.

Quick start

npx github:leavemagic-cyber/relay-task-kernel init --all

`--all` writes the machine-wide protocol to `~/.rtk/` **and** the project overlay into the current repo. Answer four questions, or pass `--yes` to take the detected values.

Already have a `CLAUDE.md` you like? Keep it. RTK only manages the region between its own markers and never touches the rest of the file.

What it writes

~/.rtk/                        the protocol, shared by every repo
├── RTK.md                     load order + core contract
├── rules/                     core, forbidden-actions, code-edit
├── templates/                 task packet, context capsule, memory patch, handoff
└── schemas/                   machine-readable task packet
~/.codex/AGENTS.md             Codex global entry

your-repo/
├── START_HERE.md              the one card every agent reads first
├── AGENTS.md                  ─┐
├── CLAUDE.md