How Skills fit the workspace
A Skill can include instructions, scripts, and local assets that shape how the assistant behaves. Because the files live in the workspace, teams can review and version them like the rest of the project.
- Keep domain behavior close to the source material.
- Make it easier to inspect and revise assistant behavior.
- Avoid lock-in to one hosted prompt editor.
Good Skill hygiene
Start with a small, explicit Skill. Give it a clear responsibility, document the boundaries, and only add scripts when a plain instruction is no longer enough.
- Name the Skill after the concrete job it owns.
- Write a short instruction with clear outputs and limits.
- Add scripts only when the Skill needs reliable execution help.