Sharing Skills

Sharing is how skills compound. One person figures out the right way to do something, an admin promotes the skill org-wide, and everyone in the organization picks it up automatically the next time it’s relevant. This page walks through the model.

Personal vs. Org-Shared

Every skill exists in one of two visibility states:

• Personal — only the creator can see, edit, or load the skill. This is the default. New skills always start personal.
• Org-Shared — visible to every member of the organization. Everyone can load it into chats; only admins (and the original creator) can edit it.

The states are mutually exclusive. A skill is either personal or org-shared at any moment. You can move a skill in either direction — share it now, unshare it later — and the change takes effect immediately.

Who Can Do What

The permission model is straightforward but has a few details worth understanding.

Action	Creator (non-admin)	Other org member	Org admin
Create a personal skill	Yes	Yes	Yes
Edit own personal skill	Yes	n/a	Yes
Delete own personal skill	Yes	n/a	Yes
See an org-shared skill	Yes (loads it)	Yes (loads it)	Yes
Edit an org-shared skill	Yes (own only)	No	Yes
Toggle a skill org-shared	No	No	Yes
Delete an org-shared skill	Yes (own only)	No	Yes

A few things to highlight from the table:

• Non-admins can create skills freely. The Skills section is visible to every authenticated org member, not just admins. This is a deliberate decision — the people closest to the analysis are usually the ones with the best recipes to share.
• Only admins can promote a skill org-wide. This is the gate that protects the org-shared list from becoming a free-for-all. If a non-admin wants their skill shared, they ask an admin to flip the toggle.
• Original creators retain edit access on their own skills even after sharing. If you wrote a skill and an admin shared it org-wide, you can still edit and delete it.
• Other org members can load and use a shared skill, but cannot edit it. Only admins (and the creator) can change its content.

How to Share a Skill (Admins)

If you’re an admin, you’ll see a Share with org toggle on every skill — both in the editor and on the skill cards in the library. Toggling it on:

1. Makes the skill visible to every member of your organization.
2. Moves it from the My Skills section into the Shared with Org section for non-creator viewers.
3. Surfaces it in skill suggestions on the home screen for everyone.

Toggling it off reverses all three effects immediately. Anyone who currently has the skill loaded in an open chat will keep using it for the current conversation, but the skill will no longer be loadable in new conversations.

Validate Before Sharing

A bad skill shared org-wide is worse than no skill at all — it biases the agent toward the wrong approach for many people at once. Before flipping the toggle, run the skill through a few real questions yourself and check the output against what you’d expect.

How to Request Sharing (Non-Admins)

If you’ve built a skill that you think the whole team should have, the easiest path is:

1. Use the skill yourself in a few chats to make sure it’s working well.
2. Pull an admin into a chat showing the skill working — or send them a .qskill export of it (see Importing & Exporting).
3. Ask them to review and toggle it org-shared.

Admins can also adopt a personal skill from someone else by asking the creator to export it as a .qskill, importing it themselves, and sharing the imported copy. This is useful if you want admin-level edit control over the canonical version.

Naming and Discovery

Once a skill is shared org-wide, every member can find it through:

• The Skills page — under the Shared with Org section.
• The chat skill loader — alongside personal skills.
• Home-screen suggestions — surfaced as one-click prompts when relevant.

Because shared skills are discoverable to everyone, naming matters more once a skill is shared than it does when it’s personal. A title that made sense to you (“the rollup thing”) will not make sense to a teammate who’s never seen the analysis. Before sharing, take a pass at the title and description with the whole org as your audience.

Removing a Shared Skill

Two paths exist for taking a shared skill out of circulation:

• Toggle off Share with org — keeps the skill in the creator’s personal library, just removes org-wide visibility. Use this when the skill is still useful but not for everyone.
• Delete the skill — removes it permanently. Use this when the skill is wrong, outdated, or no longer needed at all.

Deletion is permanent — the skill cannot be recovered. If anyone has loaded the skill in an active chat, the chat keeps working but no new chats can load it.

Export Before Deleting

If you’re deleting a shared skill but want a record of what it contained, export it to a .qskill file first. You can keep the file as a backup or share it with whoever maintains the new replacement.