Eve Repo Upkeep

Runs through your Eve-compatible repo and flags or fixes anything that's drifted from current platform conventions: outdated manifest schemas, stale skill references, deprecated CLI patterns, inline secrets, missing build steps. It works in phases: quick assessment, parallel workers for each problem area, then verification with a staging deploy. Handy after platform updates or before a big release when you need to be confident the repo won't break on some obscure schema change. The worker model means you can tackle manifest issues without waiting on documentation updates to finish. Honestly most useful if you maintain multiple Eve repos and want a single pass to catch configuration rot.

skills.sh installs: 315
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add incept5/eve-skillpacks --skill eve-repo-upkeep --agent claude-code

Installs into .claude/skills of the current project.

Files

Eve Repo Upkeep

Keep an app repo current with Eve conventions. The checks are independent — run them in parallel when multiple areas need attention.

When to Use

After Eve platform updates or manifest schema changes
Before a major deploy or release
When onboarding a new maintainer

Phase 1: Assess

Quickly determine which areas need attention. Check which of these files exist and whether they look stale — don't deep-read every file, just note which areas need work:

.eve/manifest.yaml — does it exist? Is the schema line eve/compose/v1?
skills.txt — does it exist? Are there pinned or obsolete entries?
AGENTS.md / CLAUDE.md — do they reference current skills?
agents/ directory — do agents.yaml, teams.yaml, chat.yaml exist?
Codebase — any obvious deprecated CLI patterns or inline secrets?

If only one area needs work, handle it directly. Otherwise, proceed to Phase 2.

Phase 2: Dispatch Workers

Create one worker per area that needs updating. Each worker description below is self-contained — a worker can execute its area independently without context from the others.