Project skills and global skills.
OneOrg skills work best when teams use them for repeatable procedures, keep project-specific rules local, and reserve global skills for organization-wide practices.
Capture repeatable procedures
Manage project skills from the Skills area inside project settings. Create a project skill when the team has a procedure it expects agents or assistants to repeat: review steps, delivery rules, research patterns, onboarding guidance, file handling, or client-specific standards. Use the editor to keep the skill name, slug, instructions, and supporting files precise.
Decide early whether a skill belongs to one project or the whole organization. Project skills can encode local working agreements without changing how every team operates. Global skills should be reserved for procedures that are stable across projects and safe for broader reuse.
Use AI creation when the team can describe the procedure but does not want to start from a blank editor. Review the generated skill before saving it. A vague skill creates vague execution.
Skills are procedural memory with boundaries.
A practical skill should answer three questions: when to use it, what steps to follow, and how to verify the result. If those are missing, the skill is not ready for repeated use.
If a skill starts accumulating exceptions, split it. One focused skill is easier to trust than one broad skill with hidden branches.
Review skills like reusable operating procedures. A useful skill should have a clear trigger, a short step sequence, and a verification rule. If users keep adding exceptions to the same skill, split it into narrower skills. If a skill applies to only one client, project, or delivery format, keep it local. Promote it to global only after it has proven stable across multiple teams. That keeps global skills from becoming a junk drawer of old project habits.
Project skill or global skill
Use skills for repeatable procedures. Review them when the project changes process, client, quality bar, or delivery standard. Pair skills with project instructions when the team needs both general project context and step-by-step operating rules.
Do not use a skill when the team needs an interactive role with its own persona or behavior. Use an agent for that. Do not put temporary task notes into a skill; keep short-lived context in tasks, channels, or files.