# Evozeus Wrapper

> Use when EvoZeus routes an independent Skillware Git repository into the EvoZeus-CoEvolve attachment and lifecycle Harness.

- Skill: `metainflow/evozeus-wrapper` (Agent Skill, multi-file: 22 files)
- Install (CLI): `npx get-skill add metainflow/evozeus-wrapper`
- Raw SKILL.md: https://api.skillmd.com/api/skills/metainflow/evozeus-wrapper/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: metainflow (https://skillmd.com/u/metainflow)
- Updated: 2026-11-16
- Page: https://skillmd.com/skills/metainflow/evozeus-wrapper

---


# EvoZeus-CoEvolve

This root Skill is only the wrapper entrypoint. It keeps the stable `evozeus-wrapper` compatibility slug and serves as the thin EvoZeus-CoEvolve attachment entrypoint.

When this Skill applies, immediately use `skills/using-evozeus-wrapper/SKILL.md` for the operating workflow. Do not duplicate lifecycle details here.

## Role

EvoZeus-CoEvolve is the optional evolution extension and public research artifact under EvoZeus. It attaches a governed evolution lifecycle to an independent Skillware Git repository. A Skill, package, pack, app, or other subdirectory inherits its repository Harness and cannot own another Harness.

The wrapper exists to add:

- canonical source tracking
- GitHub repo / Pages dashboard
- feedback Issues
- design docs
- changelog and release governance
- preflight checks
- target-local configurable EvoZeus Notice policy and read-only renderer
- wrapper harness migration records

It must not rewrite target business rules or absorb the evolution runtime, scanner, or prompt management platform.

## Required Flow

Use these Skills in order:

1. `skills/using-evozeus-wrapper/SKILL.md` - full operating workflow and routing.
2. `skills/environment-diagnosis/SKILL.md` - local EvoZeus and tool readiness.
3. `skills/target-skill-diagnosis/SKILL.md` - target repo facts, GitHub access, architecture, candidates, gaps.
4. `skills/evolution-surface-diagnosis/SKILL.md` - whole-repo instruction surface decision.
5. `skills/status-assessment/SKILL.md` - user-understandable assessment and next step.
6. `skills/target-skill-transform/SKILL.md` - attach / adopt / repair / verify planning.
7. `skills/publish-reinstall/SKILL.md` - canonical repo and runtime pointer handling.
8. `skills/evolution-loop/SKILL.md` - feedback-to-release loop.
9. `skills/harness-upgrade/SKILL.md` - wrapper harness version migrations.

## Hard Boundaries

- If `~/.evozeus` is missing, stop and install / initialize EvoZeus before target transform.
- If the target is outside Git or cannot be resolved to an independent repository root, stop.
- If an active Harness exists below the repository root, stop and migrate it to the root boundary.
- Harness mutation, upgrade, and upload require verified `ADMIN` permission on the target GitHub repository.
- If visibility is missing, ask `public` or `private` before creating or pushing anything.
- If an existing repo has no GitHub release and no `.evozeus-wrapper/CHANGELOG.md` version entry, ask the owner to choose the current Skill / kit version.
- If no controlling instruction surface can be proven, run evolution surface diagnosis and ask the owner when needed.
- Keep wrapper-owned additions append-only and do not rewrite target business logic.

