skill-improve

Evaluates a skill against behavioral specs with and without changes via parallel subagents.

66|4|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/SummerEngine/summer --skill skill-improve-summerengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-improve
Source: https://github.com/SummerEngine/summer/tree/main/library/skills/skill-improve
Command: npx skills add https://github.com/SummerEngine/summer --skill skill-improve-summerengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Summer skill fails behavioral spec assertions or produces low-quality output, reading the skill text alone often cannot reveal why. This Skill runs the skill in parallel subagents with and without proposed changes, scores both versions against the spec, and ships the winner. ## Core Features & Use Cases - Baseline Evaluation: Spawns subagents with the current skill body against each spec Case, capturing tool calls, diffs, and assertion scores. - Parallel A/B Comparison: Repeats the run with a proposed SKILL.md revision and compares assertion pass rates, tool-call efficiency, and hallucination penalties per case. - Guarded Shipping: Overwrites the skill and commits only after explicit user confirmation, with a structured win/tie/loss summary. - Use Case: A contributor's skill fails 2 of 6 spec assertions. Run this Skill to baseline the failures, draft a fix, verify the fix wins on net across all cases, and ship it with a conventional commit. ## Quick Start Ask the agent to run /skill-improve on the skill named <name> using the cases in tests/specs/<name>.md and compare the proposed revision against the baseline.

Frequently Asked Questions about skill-improve

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

FAQPage Schema
How do I test whether a change to an AI agent skill actually improves it?

Run the skill against a behavioral spec twice: once with the current SKILL.md and once with the proposed revision, using parallel subagents. Score each run on assertions passed, tool-call efficiency, and hallucinations, then ship only if the proposed version wins on net.

What is the difference between skill-test and skill-improve?

skill-test reasons over the skill text and spec without executing anything, making it cheap but lossy. skill-improve actually runs the skill in subagents with and without changes, which is more expensive but produces accurate behavioral evidence.

When should I use an eval harness instead of just editing the skill directly?

Use the eval harness when spec assertions keep failing and you cannot diagnose the gap by reading the skill alone. It is designed for cases where the agent's actual tool calls diverge from what the skill instructs.

Does skill-improve modify my skill files automatically?

No. It writes proposed versions and run outputs only after asking at each step, and overwrites the original SKILL.md plus commits only after you confirm the comparison results.

What inputs does the skill improvement eval harness need?

It needs the skill name resolving to skills/<category>/<name>/SKILL.md and a behavioral spec at tests/specs/<name>.md containing Case blocks with Input, Fixture, and Assertions. Run outputs are saved under tests/runs/<skill-name>/.