agent-kit

Manages the portable rules layer of laws, hooks, checks, and overrides shipped by the agent-kit package.

1|Updated Jan 14, 2024
One-click install
npx skills add https://github.com/Eyhenij/rt-tools --skill agent-kit-eyhenij
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-kit
Source: https://github.com/Eyhenij/rt-tools/tree/main/.claude/skills/agent-kit
Command: npx skills add https://github.com/Eyhenij/rt-tools --skill agent-kit-eyhenij

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a repository consumes the @rt-tools/agent-kit package, its laid-out rules files carry an rt-kit header and must never be edited in place. This Skill tells you where every kind of change actually belongs — package source, override, gate map, or config — so layouts, version bumps, and audits stop failing mysteriously. ## Core Features & Use Cases - Edit-location routing: Maps each kind of change (gate rules, ports, checks, overrides, drops, roles) to the exact file that owns it, such as .claude/rt-kit/gate-map.sh or .claude/rt-kit.json. - Layout and audit workflow: Covers agent-kit sync, sync --check, doctor, and adopt, including the all-or-nothing layout semantics and the push-gate audit. - Safe version bumps: Prescribes the three-step upgrade procedure — snapshot the old assets, install and lay out, then audit replaced override sections against the snapshot. - Use Case: You are about to edit a file carrying the header rt-kit v0.29.0 · ... · правится надстройкой, не здесь. Load this Skill to learn that the edit belongs in an override or the package source, not in the laid-out copy. ## Quick Start Load the agent-kit skill before editing any file that carries the rt-kit layout header, then follow its edit-location table to place the change in the correct override or config file.

Frequently Asked Questions about agent-kit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I edit a file that has the rt-kit layout header?

Files with the rt-kit header are laid out by the package and must not be edited in place. Edit the package resource source if your tree holds it, otherwise create or extend an override under .claude/rt-kit/overrides/ for that resource.

How do I safely upgrade the agent-kit package version?

Snapshot the old assets directory to /tmp before installing, then install and run the layout, then audit every replaced override section against the snapshot using agent-kit doctor --since. Package additions inside replaced sections must be carried into the override by hand.

Why does agent-kit sync --check refuse in the push gate?

The audit refuses when a laid-out file's body diverges from the package edition, usually from an in-place edit or a formatter rewrite. A stale header alone is re-laid automatically; a genuinely diverged body must be moved into an override or reverted.

What is the difference between skip and rolesOff in agent-kit config?

The skip key prevents a resource from being laid out at all, while rolesOff only disables the mandatory guard-triggered call of a role. With rolesOff the role file stays laid out and can still be invoked manually.

Can agent-kit be installed in a tree that already has its own hooks and checks?

Yes. Run init, skip everything the tree already owns, then hand over existing files with agent-kit adopt, which sets the former content aside marked .before-rt-kit. Migrate resource by resource, comparing behavior against a pre-migration snapshot.