@fede0089/skill-eval 3.0.0 → 3.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -5
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -205,9 +205,7 @@ Refer to your runner's documentation for the full set of settings and policy key
|
|
|
205
205
|
|
|
206
206
|
Each run writes to `.project-skill-evals/runs/<timestamp>/` and includes per-trial logs, the raw eval JSON, and a self-contained HTML report you can open in any browser. The report shows pass@k aggregates per eval, lets you expand each trial, and color-codes triggering vs. functional outcomes.
|
|
207
207
|
|
|
208
|
-
A published sample report is available at [fede0089.github.io/skill-eval/sample-report.html](https://fede0089.github.io/skill-eval/sample-report.html)
|
|
209
|
-
|
|
210
|
-
It was generated from the project root with:
|
|
208
|
+
A published sample report is available at [fede0089.github.io/skill-eval/sample-report.html](https://fede0089.github.io/skill-eval/sample-report.html),generated from this project root with:
|
|
211
209
|
|
|
212
210
|
```sh
|
|
213
211
|
skill-eval functional --workspace . --skill mock-skill --trials 2 --compare-baseline --debug claude-code
|
|
@@ -215,8 +213,6 @@ skill-eval functional --workspace . --skill mock-skill --trials 2 --compare-base
|
|
|
215
213
|
|
|
216
214
|
|
|
217
215
|
|
|
218
|
-
To publish or refresh the GitHub Page, commit the files under `docs/`, then enable **Settings -> Pages -> Build and deployment -> Deploy from a branch** in GitHub and select the `main` branch with the `/docs` folder. GitHub will serve the report at `https://fede0089.github.io/skill-eval/sample-report.html`.
|
|
219
|
-
|
|
220
216
|
### Debug logs
|
|
221
217
|
|
|
222
218
|
When a trial misbehaves, pass `-v` / `--debug` to capture the full transcripts to disk. Each trial writes a `task_<id>_<variant>_trial_<n>.log` file inside the run directory with two sections appended in order:
|