Target Skill Diagnosis
Use this stage after environment diagnosis and before attach, adopt, repair, publish, or reinstall.
Required Inputs
- Target path inside an independent Git Repo. The CLI normalizes it to the Repo root; Harness ownership always stays at that root.
- Target GitHub repo in
OWNER/REPOformat when known. - Skill name override only when the target surface cannot identify it.
Command
python3 scripts/evozeus_wrapper.py skill diagnose \
--target /absolute/path/to/skill \
--repo OWNER/REPO \
--json
Decide
Ask the user only when:
- The target path is missing or has no detectable evolution surface.
- Multiple local repos can be the canonical source.
- Multiple install copies differ from the canonical repo.
- Visibility is not explicitly
publicorprivate. - Private data could enter docs, Issues, release notes, or Pages.
Required Order
- Confirm environment diagnosis has passed. If
~/.evozeusis missing, install / initialize EvoZeus before target transform. - Confirm the target resolves to an independent Git Repo root and no nested Harness manifest exists.
- Check GitHub Repo access, visibility, default branch, and current account permission. Record whether
ADMINauthority is available for later writes. - Classify the target architecture:
single_skillruntime_skill_bundlehooked_skill_bundleskill_bundleagents_runtimeunknown
- Report runtime integration mode and each scoped capability from
skill.integration. Distinguish project maintenance, user-level global dispatch, Skill-entry preflight, tool gateway, and future Skill invocation hooks. Do not call project hooks or wrapper CLI commands native per-Skill invocation hooks. - Report Skill inventory from
skills/*/SKILL.mdwhen present. - Report
evolution_surfacefacts: candidate instruction surfaces, controller files, and evidence boundaries. Do not treat script candidates as final placement. - Use
skills/evolution-surface-diagnosis/SKILL.mdto browse the whole repo and choose the controlling instruction surface. - Report
component_gaps: missing wrapper files, manifest, changelog, and status-check concept after the surface decision is known. - Hand the diagnosis JSON and surface decision to
skills/status-assessment/SKILL.md; do not write user-facing status analysis in the script.
Stop Conditions
- Target Skill identity is ambiguous.
- Target is outside Git or contains an active nested Harness.
- The user has not chosen visibility.
- Sensitive data cannot be safely redacted.