Changing an organization skill

The skills your organization gives you arrive on your computer through Harriet Desktop. You can change them for your own use, send a change to your organization's reviewers so everyone gets it, or put them back. Harriet Desktop keeps track of which of these applies to each skill, and tells you when a reviewer has decided.

When Harriet notices a change

If a skill on your computer no longer matches your organization's version, Harriet Desktop shows a Skill changes button at the top of the conversation, in every conversation. Open it to see each skill that needs a decision from you, which files are different, and what you can do about it. The same wording appears on the skill in Settings → Tools, under From your organization.

Choose Review changes to see exactly what is different: every changed file, side by side with your organization's version. From there you can send the change for review, send it as a separate new skill, keep your version, or discard your changes, so you decide with the changes in front of you. Review changes is also on the skill in Settings → Tools.

The skill's menu in Settings → Tools and the menu beside Save in the skill editor have the same choices.

If your organization has updated the skill since you changed it, Harriet says so above the changes, and the comparison is with their latest version. If Harriet no longer has your organization's version on this computer, it shows only your version.

Running a skill's scripts does not count as changing it. Only the skill's own files do.

What each state means

You seeWhat it meansWhat you can do
Changed on this computerYou (or the assistant) edited the skill and have not sent the change anywhere.Submit for review, keep your version, or reset it to your organization's version.
Submitted, waiting for reviewA reviewer has your change and has not decided yet.Nothing is needed. It does not count on the Skill changes button.
Changed again since you submittedYou edited the skill after sending it.Choose Update my request to send the newer version in place of the one you sent.
A reviewer asked for changesThe reviewer wrote back with what to fix. Their note is shown.Edit the skill, then choose Update my request.
Not acceptedA reviewer decided not to adopt your change. Their note is shown.Keep your version, or reset to your organization's version.
Kept as your versionYou chose to keep your own copy. Harriet will not overwrite it.Allow organization updates again whenever you like.

When a reviewer approves your change, there is nothing left to do: Harriet Desktop tells you, syncs, and the skill goes back to being the organization's version, now including your change.

Submitting a change

  1. Choose Submit changes in the review. The dialog lists the files you changed. If nothing differs from your organization's version, there is nothing to submit and Harriet says so.
  2. Add a short note. Say what you changed and why. Reviewers see it with the changes.
  3. Send it. The change goes to your organization's review queue. It is not live for anyone until a reviewer approves it. See Review workflow.

You can have one open request per skill. Sending another one replaces your earlier request, and Harriet asks you first.

Hearing back

Asking the assistant

You can ask the assistant "what have I changed?" and it answers from the same list as the Skill changes button. You can also ask it to send a change for review. It writes a draft note and shows a Review and submit button, and a See what changed button that opens the review first. Nothing is sent until you confirm in the dialog.

A change made in Settings or by the assistant applies to both, so what you review is what the assistant uses.

💡

In a cloud workspace, Harriet shows the same Skill changes button and Review changes on the web, comparing the skill in the workspace with your organization's current version. There you can send the change for review or send it as a new skill. Keeping your version or discarding changes is not available in a cloud workspace yet, and the assistant in a cloud workspace cannot list or submit changes itself yet.