Get an improvement
Check an improvement until it is done or has failed, and see what changed.
status moves through queued, working, validating, then done or failed.
get_skill_improvement.Authorizations
API key with the vd_sk_ prefix, as Authorization: Bearer vd_sk_.... Create keys in Settings → API Keys.
Path Parameters
Response
The improvement's current state.
Where an improvement is: queued → working → validating → done | failed.
done with improved: true means the new recipe version is live; done with
improved: false means the attempt was kept as a candidate version (not live) and
outcome says why. failed means the engine could not run (error). result
says the same in one word.
fix, add_fields, relearn_details Who asked: api | mcp | assistant (Igris) | web | brain (workflow Brain) | imported (from the old Refine history)
running | improved (new version live) | kept_old (not better — the old version stays, the attempt is candidate_version) | no_change (nothing to learn or nothing changed) | failed (could not run) | applied (imported: applied without a check run)
running, improved, kept_old, no_change, failed, applied An entry imported from the old Refine / Re-learn history
The id of the account that asked for it
What the engine made of the words: for add_fields, the request diffed against the skill's contract (genuinely new fields, re-worded duplicates merged into an existing field, ones it could not place, asked back as a question); and what the learn pass did.
fields (re-learn where the fields live) | rerecord (re-do the steps)
The diagnosis the improvement started from
The check run's diagnosis, when it still came back short
Target fields, before → after
The live recipe version once done
Set when the attempt was kept as a candidate, not made live

