Skip to content

AGENT SKILL EVALUATION

skilledBetter skills start with evidence.

Test what your agent should do. Inspect what it actually did. Improve the Skill and check the result.

macOS · Linux · Windows Runtime included

skilled / your projectWORKFLOW
01

Define the expectation

One Skill. A set of repeatable cases.

skilled validate evals/eval.yaml
02

Run and inspect

Review verdicts alongside the evidence.

skilled run evals/eval.yaml
03

Revise, then compare

Let the next run show what changed.

One installation. Two parts that work together. ​

ComponentResponsibilityWhere you use it
skilledValidate, evaluate, and compareYour terminal or an MCP-compatible agent
skilled-improveGuide diagnosis, revisions, and regression checksA bundled workflow your agent follows

skilled-improve is a prompt and workflow, not a separate executable. Your agent uses it with the evaluation tools; you keep the cases and evidence in your project.

Install once. Start with a local check. ​

The release bundles its own Node runtime and application dependencies. No source build or GitHub account is required.

sh
curl -fsSL https://raw.githubusercontent.com/DeadHead04/skillEd/main/install.sh | bash
export PATH="$HOME/.local/bin:$PATH"
skilled --version
powershell
$installer = Join-Path $env:TEMP 'skilled-install.ps1'
Invoke-WebRequest https://raw.githubusercontent.com/DeadHead04/skillEd/main/install.ps1 -OutFile $installer
& $installer
$env:Path = "$(Join-Path $HOME '.local/bin');$env:Path"
skilled --version

Keep the PATH entry in your shell or user settings for future sessions. Installation options, updates, and uninstall →

Next, create the Hello World example and validate it without calling a model. For a live evaluation, install and authenticate your selected engine first; provider usage may incur charges.

From an expectation to an improvement ​

  1. 01
    Define

    Write the behavior you expect as versioned cases.

  2. 02
    Evaluate

    Run the engine and inspect the report and outputs.

  3. 03
    Improve

    Have your agent revise the Skill using failed cases.

  4. 04
    Compare

    Rerun the suite and check what improved or regressed.

Comparisons use the reports you supply. Background drift monitoring and unrelated conversation capture are not enabled by installing the CLI or connecting MCP. Understand the comparison model →

Try it on one Skill. ​

Start small, keep the report, and make the next change measurable.

Follow the first-evaluation guide → · Read the verification scope · Browse the source

Apache-2.0. TypeScript CLI. Source: DeadHead04/skillEd.