Skill reviews and owners
A skill's owners decide what is published. Turn on review before publishing, read what is proposed, and see how each version has performed.
On this page6 sections
Owners#
Every skill has at least one owner. It starts with the person who made it. All owners have the same say, and the owner of the skill's home workspace can always act as one too.
To change owners, open the skill's tab in its home and go to Owners. Pick a person under Add someone who can edit this workspace and click Add, or click Remove next to a name. An owner has to be able to edit the home. A skill always keeps at least one owner.
What a skill review is#
A skill review is a decision about a skill's files. It is separate from a review on a task, and it is counted separately: you might see "2 tasks need your review · 1 skill review".
Three things raise one:
| Raised when | The decision |
|---|---|
| Someone who is not an owner publishes a skill that requires review | Accept and publish, or decline. |
| A workspace proposes a change it made to its pinned copy | Accept into the draft, or decline. |
| A run of the skill's cases leaves results waiting for a person | Judge the waiting cases. |
A review is for all of a skill's owners. One owner's decision closes it.
Require a review before publishing#
In the skill's tab, under Skill reviews, turn on Publishing needs a review. It is off by default, and only an owner can change it.
| Setting | Effect |
|---|---|
| Off | Anyone who can edit the home publishes immediately. |
| On | A publish by someone who is not an owner is sent for review and publishes nothing until an owner accepts. An owner's own publish still goes out immediately. |
There is one open publish request per skill. Publishing again while one is waiting replaces it with the current draft.
Decide a review#
Open the review from Home, from the home's row on the Workspaces page, or from Skill reviews in the skill's tab.
- Click Show what is proposed. You see which files were added, removed and changed, and a line-by-line comparison with the current published version.
- Click Accept and publish, or click Decline and add a note saying why.
Accepting publishes exactly the files that were proposed, not whatever the draft has become since. If the proposal changed while you were reading it, nothing is decided and you are shown the new proposal.
For a change proposed from a pinned copy, the buttons are Accept into the draft and Decline. Accepting puts the change in the draft and publishes nothing. If the draft had already changed the same file, the draft is left alone and the proposed files are placed beside it for you to merge.
For cases waiting on a verdict, the review has one button, Judge in Compare results, and it closes when the last case is judged.
People who are not owners can read what is proposed but cannot decide.
Who published what#
Under Skill reviews, Who published lists each version with the person who published it and, when it went through a review, the owner who accepted it.
Track record#
The Track record section of a skill's tab shows how the skill has performed in real use.
- A headline: how many times it was used, the typical time a use took, and total and per-use cost.
- A sentence on reviews, such as how many of the last 10 uses were corrected.
- A table by version: uses, typical time, cost, and how many reviewed uses were corrected.
- Recent uses: where it ran, the task, the version, how long it took, what it cost, and how the review came out.
A use is counted when the agent applies the skill to a task. If a person later reviews that task, the answer is attached to the use.
A use in a workspace you cannot open is shown as a place you cannot open. Its numbers still count.
There is no score, and the track record blocks nothing. It is evidence for the people deciding whether a version is better than the last.