Run any Skill in Manus with one click

install-cadence

Stars0

Forks0

UpdatedJune 3, 2026 at 22:03

Before dispatching any agent after a batch of merged PRs, verify that ~/.claude/agents/ and ~/.claude/skills/ are in sync with the repo. Stale installed definitions cause dispatched agents to reintroduce behaviors explicitly removed in recent PRs.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

joshrotenberg

joshrotenberg/agent-tools

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	install-cadence
description	Before dispatching any agent after a batch of merged PRs, verify that ~/.claude/agents/ and ~/.claude/skills/ are in sync with the repo. Stale installed definitions cause dispatched agents to reintroduce behaviors explicitly removed in recent PRs.

Install cadence

The installed copies of skills and agents in ~/.claude/agents/ and ~/.claude/skills/ are what Claude Code and dispatched sessions actually load. Merged changes in the repo do not auto-propagate there. If you merge a batch of PRs and dispatch without re-installing, the dispatched agent runs against the old definitions -- and may reintroduce behaviors you just removed.

When to apply

After merging any batch of PRs that modify skill or agent bodies.
Before dispatching any agent (runner or worker) when you have recently merged agent-tools PRs.
On a fresh machine -- the first ./install.sh bootstraps the install; subsequent runs after PR merges keep it current.

A safe rule: if you merged PRs, run install before dispatching.

The rule

After each batch of merged PRs, run from the repo root:

./install.sh --force

The --force flag overwrites existing files without prompting. install.sh is idempotent -- running it when nothing changed is harmless.

Verify sync before dispatching

If you are unsure whether your install is current, check from the repo root:

diff -r ~/.claude/skills/ skills/
diff -r ~/.claude/agents/ agents/

No output means the installed copies match the repo. Any diff output identifies which files are out of sync. Run ./install.sh --force to resolve.

Failure signature

The most common symptom of a stale install: a dispatched agent re-adds a behavior you explicitly removed in a recent PR. If you see that, the agent loaded the old definition. Re-install and re-dispatch.

Other signs:

A dispatched session references a skill name that was renamed or removed.
The dispatched agent follows an old lifecycle step you replaced.
Worker output matches the behavior described in a closed issue you thought was fixed.

Anti-patterns

Merging PRs and dispatching immediately without re-installing. The most common way to end up running stale definitions.
Relying on the repo being the install. ~/.claude/ is the install location, not the repo directory. They diverge on every merged PR.
Installing once and forgetting. Install cadence is per-PR-batch, not once at project setup.

sandbox-preflight -- the analogous pre-dispatch check for tool allowlist readiness. Run both: verify install sync AND tool allowlist before firing a runner.
durable-context -- the persistence model that explains what survives compaction and what must be externalized. Install sync is a separate concern (filesystem, not context), but both are pre-dispatch hygiene.

More from this repository

same repository

runner-vs-worker

joshrotenberg/agent-tools

Use when deciding whether to dispatch a runner or a worker for a subtask. Describes the decision boundary, the failure mode when runner is used where worker is intended, and the safe composition pattern.

2026-06-180

local-only-repos

joshrotenberg/agent-tools

When a repo has no GitHub remote (or is not yet a git repo) -- use this to route survey, sweep, and dispatch off the GitHub-centric path. Detect with `git remote` empty; treat blank GitHub columns as expected, not an error; route work to commits + CLAUDE.md instead of issues + PRs; degrade a maintenance sweep to the local-only axes.

2026-06-180

maintenance-sweep

joshrotenberg/agent-tools

When the directive is "status check," "what's new across my projects," or "sweep maintenance" -- run a per-project, read-mostly, non-PR sweep. For each project under the owner-prefixed layout, gather stars/forks, open issues/PRs split into mine vs community vs bots, package downloads, release-due (unreleased conventional commits), a test run, a stale-CLAUDE.md flag, and branch-cleanup candidates. Emit a fresh per-project report every sweep; NEVER cache status back into a workspace/manager CLAUDE.md.

2026-06-180

git-branch-pr-workflow

joshrotenberg/agent-tools

Before making any non-trivial code, docs, or config change -- create a feature branch first, then open a PR. Never commit directly to main. Apply by default before any edit; this is the baseline branch discipline that all other git skills build on.

2026-06-180

triage

joshrotenberg/agent-tools

When the issue or PR queue has open unlabeled items -- run a read-only triage pass that labels each one by component, category, priority, and size, flags duplicates, closes noise, and reports the p1 queue before runners are dispatched.

2026-06-180

github-authoring

joshrotenberg/agent-tools

When writing any issue, PR, or commit message, use this for the authoring standard. Covers structure (headings, lists, tables, fenced blocks, the bug block, the before/after) and voice (factual, no emdashes, no editorializing labels, conventional-commit prefixes, no commit trailers).

2026-06-180

name	install-cadence
description	Before dispatching any agent after a batch of merged PRs, verify that ~/.claude/agents/ and ~/.claude/skills/ are in sync with the repo. Stale installed definitions cause dispatched agents to reintroduce behaviors explicitly removed in recent PRs.

Install cadence

When to apply

After merging any batch of PRs that modify skill or agent bodies.
Before dispatching any agent (runner or worker) when you have recently merged agent-tools PRs.
On a fresh machine -- the first ./install.sh bootstraps the install; subsequent runs after PR merges keep it current.

A safe rule: if you merged PRs, run install before dispatching.

The rule

After each batch of merged PRs, run from the repo root:

./install.sh --force

The --force flag overwrites existing files without prompting. install.sh is idempotent -- running it when nothing changed is harmless.

Verify sync before dispatching

If you are unsure whether your install is current, check from the repo root:

diff -r ~/.claude/skills/ skills/
diff -r ~/.claude/agents/ agents/

No output means the installed copies match the repo. Any diff output identifies which files are out of sync. Run ./install.sh --force to resolve.

Failure signature

Other signs:

A dispatched session references a skill name that was renamed or removed.
The dispatched agent follows an old lifecycle step you replaced.
Worker output matches the behavior described in a closed issue you thought was fixed.

Anti-patterns

Merging PRs and dispatching immediately without re-installing. The most common way to end up running stale definitions.
Relying on the repo being the install. ~/.claude/ is the install location, not the repo directory. They diverge on every merged PR.
Installing once and forgetting. Install cadence is per-PR-batch, not once at project setup.

sandbox-preflight -- the analogous pre-dispatch check for tool allowlist readiness. Run both: verify install sync AND tool allowlist before firing a runner.
durable-context -- the persistence model that explains what survives compaction and what must be externalized. Install sync is a separate concern (filesystem, not context), but both are pre-dispatch hygiene.