system-evolution

Analyze OpenCode installations for health issues, drift, and compliance gaps.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/kiryteo/opencode-setup --skill system-evolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-evolution
Source: https://github.com/kiryteo/opencode-setup/tree/main/skills/system-evolution
Command: npx skills add https://github.com/kiryteo/opencode-setup --skill system-evolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes OpenCode installations to identify health issues, drift, and compliance gaps, enabling proactive evolution.

Core Features & Use Cases

  • Six-phase system health analysis that covers config audit, session analytics, compliance review, drift detection, knowledge health, and evolution planning.
  • Generates actionable dashboards and recommendations to close gaps and maintain healthy configurations across OpenCode deployments.
  • Suitable for weekly health checks, after major changes, or during long-term platform evolution planning across large installations.

Quick Start

Run the evolution workflow to generate a health report and improvement plan.

Frequently Asked Questions about system-evolution

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

FAQPage Schema
How do I check OpenCode installation health and system configuration compliance?

OpenCode system health and compliance are analyzed through a configurable six-phase workflow that audits configurations, reviews sessions, and detects drift to generate actionable JSON dashboards.

What is system drift detection and when should I run an audit for large deployments?

System drift detection identifies configuration deviations across OpenCode deployments, and you should run audits during weekly health checks, post-change reviews, or long-term evolution planning.

How do I generate a system health dashboard and recommended actions for OpenCode?

To generate a system health dashboard and recommended actions for OpenCode, run the evolution workflow which orchestrates a six-phase analysis and outputs JSON dashboards with gap-closing recommendations.

Does the system health analysis require any specific dependencies or components to run?

No specific dependencies or components are required to run the system health analysis, as the skill operates independently by reading sentinel state and orchestrating its configurable six-phase analytical workflow.

What is the best way to plan long-term platform evolution for OpenCode installations?

The best way to plan long-term platform evolution for OpenCode is to execute a six-phase analysis covering knowledge health and evolution planning, producing actionable JSON recommendations for large deployments.