Skills and scripts

AgentWitch learns skills and scripts from the work your assistants do, and your assistants reuse them on later tasks. A skill is a short set of steps for a kind of job. A script is a small program a skill can run, so a repeated job costs almost no tokens. You do not approve skills before they are used. You can read, undo, block or delete anything from the Skills pages.

#How skills are made

You can write a skill by hand, but you do not have to. Skills usually appear in three ways:

The assistant that did the work creates one. When it finishes something that will clearly repeat, or needs a procedure it could not find, it writes the skill. The skill is live at once and the assistant uses it right away.
AgentWitch finds repeated work. It reads your finished runs and the docs in your project folder, and it notices steps you run again and again. It drafts a skill from them.
A teammate's assistant suggests one. It goes live the same way.

AgentWitch rejects a copy of a skill that already exists. A skill that holds a secret or personal data is dropped. The creating assistant picks who gets it: Just me for personal habits, or Project for how the repo is built, tested and released. The default is Project.

When a skill includes fixed commands, the assistant can add scripts to it. AgentWitch checks every script and test-runs it on your computer first. If the test fails, the script is dropped and only the skill text is kept.

#Find your skills

Open Skills in the main menu. It has three tabs:

Yours. Every skill you have across your projects, with its project and a short description. Choose Add to project, pick a project and choose Add to copy a skill into another project.
Shared with your team. Always empty today. It says "Skills your team shares will show up here." To share a skill now, use the project's own Skills tab, described below.
From AgentWitch. Ready-made skills and assistants. Choose Install on one, then pick a computer and a project.

For one project, open the project and choose Skills, then In use. You see each skill with these labels:

Auto for a skill AgentWitch or an assistant made.
Reused N× for how often assistants used it.
N scripts for the scripts it carries.
Just me, Project, Team or Marketplace for who has it.
Draft for one not yet live.

Use the search box and the filter (All, Skills, Multi-step skills, Shared skills) to narrow the list.

Lessons is the next tab. It lists the traps the project learned to avoid, each with "how to do it", marked Important, Warning or Note, and how many times it was hit. The owner can Delete rule, and choose Undo right after.

#Review, undo and delete

Open a skill to see its content, its scripts and its versions. Skills improve on their own: when AgentWitch finds a better version, it makes it live and keeps every older one. Under Versions, choose Go back to this to make an older version live again.

To remove a skill, open it and choose Delete. Assistants stop finding it. Only the project owner or the person who published it can delete a skill, and members can discard their own drafts. The skill page does not let you type into the text. To change it, ask an assistant to update the skill.

The owner can choose New to write a skill by hand, or Add from another project to copy one in. Members and viewers can only read published skills.

#Scripts

A script runs on your own computer, inside your project folder, with a time limit. A skill's page lists each script with what it does and what it may touch: read only or writes files, and whether it uses the network.

Scripts run without an approval step. You can still stop one:

Open the skill and find the script under Scripts.
Choose Block, then Yes, block. That script version stays blocked on this computer.

For each new script version, a question may appear under Waiting for your answer in Skills › In use, titled "Allow script … to run on your computer?" with Approve and Deny. Deny blocks it. A skill that comes from outside your own projects, installed from the public skill registry, keeps its scripts blocked until you approve them on this computer.

Some scripts have settings, such as a folder path. You set them under Settings on this computer on the skill's page, and they stay on that computer.

A skill with Project reach is used by every member's assistants in that project, on each linked computer. Private files and run history stay on each computer.

To go wider, open a Project skill and choose Share wider:

Promote to team makes a copy for a team you administer.
Promote to marketplace may not be open yet. If it is not, the page says "Sharing to the marketplace is not open yet." If you do not administer a team, it says "You are not an admin of any team."

Both options copy the skill, and your original stays unchanged. Before it is shared, AgentWitch shows the exact text. It replaces anything that looks like a secret, and you confirm before you choose Share copy.

In a project's In use view, Local | Marketplace switches to skills other people published. Choose Pull to bring one in.

#How your assistants find and reuse skills

AgentWitch adds a short instruction to your assistants. It reaches Claude Code and Codex before each prompt, and Cursor and Claude Code through an always-on rule file. It only applies in a folder that belongs to an AgentWitch project. The route has four parts:

A question. Look up saved knowledge first. If it is new, save the answer after.
A request. Split a big one into parts. For each part, look for a skill, read the closest one, and follow it. Run its script instead of retyping the commands. If none fits, create one and then use it.
A wrong or incomplete skill. Update it in place. Do not copy it.
The last line. Every answer ends with a line such as AgentWitch route: used …; created …; updated …, so you see which skills a turn used.

After each turn, AgentWitch checks the route. Work that changed files or ran a script must use or create a skill and also look up or save knowledge. A question needs one library step. If a turn misses it, Claude Code is stopped once and told what to do, Codex shows a message, and Cursor gets a follow-up message. Antigravity turns are not checked.

On the Computers page, What AgentWitch added to each computer lists the switches for each assistant, such as Skills before each prompt, Learn from finished turns and AgentWitch tools. Everything is on by default. Turn one off to remove it from that assistant.

#If something does not work

The assistant never uses a skill. Check the switches on the Computers page, and check that the project folder is linked to the project.
A script says it is blocked. You or a question answer blocked it. Open the skill; a blocked script shows "blocked here".
A script cannot be changed. Open the page on the computer that runs the scripts. Settings and Block need that computer.
A skill is missing on a teammate's computer. Computers copy new skills in the background, so it can take a short while. Check that AgentWitch Local is running on that computer.

See Token check and savings to measure what skills save.

#Query aliases

how does AgentWitch learn skills automatically
block or delete a skill
what is a script in a skill
share a skill with my team
go back to an older skill version