Skill reflection

Skills go stale as tools, processes, and team preferences change. You often end up correcting the same gap every time you use a Skill, and that feedback stays in the conversation unless you remember to edit the Skill yourself. Skill reflection picks up feedback you've shared in chat that's worth keeping for future runs and proposes it as an update to your Skill.

For example, if you keep asking a Skill to put the decision summary first, reflection can propose adding that instruction to the Skill. You approve each change before it applies, so a one-off correction doesn't become a permanent rule without you knowing.

Prerequisites

Have Skills turned on for your account. See Skills.

Start reflection

Reflection reaches you in two ways:

• Glean suggests it. After Glean has collected about 10 learnings from your feedback, it asks clarifying questions in chat to confirm what's worth keeping, then proposes the update.
• You run it. Type /reflect in the composer, the same way you invoke a Skill.

Review and approve a proposal

1. Read the proposed update. Glean shows how the Skill would change.
2. Review the feedback behind the proposal, the corrections and preferences from your chats that led to it.
3. Approve the change to apply it to the Skill, or reject it to leave the Skill as it is.

Nothing changes in a Skill until you approve it.

Improve a shared Skill

If you're an editor of a shared Skill, reflection can propose updates to that Skill based on what you learn while using it. Other editors can do the same, so the Skill improves as each person contributes what works for them. You approve each change before it applies, just as you do for a personal Skill.

If you can only view a shared Skill, reflection doesn't update it. Ask an editor to make the change, or create a personal Skill with the instructions you want.

Limitations

• Typing /reflect starts reflection: Mentioning the command is enough. Typing /reflect in a conversation starts reflection even when you're only talking about the command.
• You can't choose which Skill to reflect on yet: Reflection uses the most recently used Skill you can edit in that conversation. Asking "reflect on my launch doc Skill" targets that Skill only when it was the most recently used editable one.

Understand permissions

Reflection works from your own conversations and the content you're allowed to see. Source permissions still apply, and reflection stays inside your organization.

See also

• Share Skills — how admins publish a Skill to a department or the whole organization