Individual skill

skill-evolution-engine

Manages skill version history and automated improvement cycles. Use for: evolve skills, version skills, skill maintenance, `skill-evolver`.

.grok/skills/skill-evolution-engine/SKILL.md

Read pinned source

Source commit bf31cc83a43ed8069d0d5070c68df4250273eb29

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 14
Repository last updated: Oct 21, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
grok Repository topic
prompt-engineering Repository topic
workflow-automation Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,723 bytes

Read excerpt

# Skill Evolution Engine
## When to Use

- User says **evolve skills** or task matches this capability
- User says **version skills** or task matches this capability
- User says **skill maintenance** or task matches this capability

## Workflow

1. Snapshot the current SKILL.md to a local versioned backup and run the hyper-skill-tester baseline.
2. Prepare the proposed evolution as a reviewable diff with expected benefits, risks, and rollback path.
3. Obtain explicit user approval before applying, committing, publishing, or otherwise persisting the proposed change.
4. After approval, apply the change and compare scores. Present any regression and its rollback option for approval rather than rolling back automatically.

## Integrations