Collect pages and ideas now, and decide later what becomes knowledge or a skill. Nothing you collect is knowledge until a signed-in person confirms it in the Cockpit.
The path is always the same: collect → review in chat → confirm → knowledge or skill.
What you need #
- The Web Clipper in Chrome, installed and connected. To install, update or troubleshoot the Web Clipper, see "Collect web pages with the Web Clipper".
- To collect: an account with
intake:readandintake:write. - To confirm: a browser session in the Cockpit with
intake:confirm, plusknowledge:writefor knowledge, orskill:writeandskill:activatefor a skill. Replacing skills also needsskill:archivefor each replaced skill.
Collect something #
- Open the page.
- Optional: select the text you want as an excerpt.
- In the toolbar, select the Web Clipper icon ("SubKit Clipper").
- Check the preview. The source address is captured automatically.
- Optional: add why it matters.
- Pick a category. Your default category is preselected, at first
inbox. - Select Collect.
Learnings from coding-agent sessions arrive in the same Inbox as items with origin session. The Inbox shows the origin as a filter and badge.
Review and organize items #
- In the Cockpit, open Inbox.
(opens in a new tab)Screenshot from build 10.4.12
- Open an item to see its content and original source.
- Optional: edit title, content or category. The captured original is preserved.
- Optional: move, discard or restore the item.
Inbox visibility follows the permissions of your workspace. Categories are not private.
Review in chat #
Review one item:
- In the Inbox, open the item.
- Select Review in chat. The chat shows the item as an
@reference.
Review a whole category:
- In a new chat, start the category's review suggestion, or ask: "Look through my new Research entries and suggest what to keep."
The chat prepares a proposal with content, sources and destination, and links to it. Completed decisions stay in the chat history.
Confirm a proposal #
You need a browser session in the Cockpit, intake:confirm and the destination right. API keys, MCP clients and the Web Clipper cannot confirm.
- Review the proposal: content, sources and destination.
- Select Confirm as knowledge or Confirm as skill.
Only then can ordinary knowledge retrieval use the result, or agent briefings carry the skill. For a skill, confirming also archives the skills it replaces. The proposal shows each change.
Good to know:
- Moving, editing or discarding an item never makes it knowledge.
- If a proposal or its sources change, you review it again.
- SubKit replaces secrets such as API keys and tokens before saving a clip.
- The original clip stays linked to the knowledge or skill.
If something does not work #
| What you see | What to do |
|---|---|
| The Web Clipper reports no connection or an invalid key | Follow "If something does not work" in the chapter "Collect web pages with the Web Clipper". |
| An item is missing in the Inbox | Check the category and the origin filter. |
| The proposal says "Confirming needs: …" | Ask an administrator for the rights it names. |
| "This suggestion changed. Review the current content before confirming it." | Read the current content, then confirm again. |
| "A skill this suggestion refers to can no longer be loaded. …" | Revise the suggestion in the chat before you confirm. |